Okay, several things to consider. First, my Windebugger could not read a complete minidump because every file stated that the symbol packages are wrong for a full read. But the problem does not lie with the Debugger or the symbol packages but the minidump files themselves in light of what I believe is going on..
Every one cited a Windows Operating System driver as the issue but the problem with OS drivers is that they are usually too general to be of much help. Four times ntoskrnl.exe was noted and this is a core driver. Once csrss.exe was noted and this is a critical driver as well for Windows to operate.
One error is 0x8E and these are almost always caused by hardware.
Three errors are 0x00000077 KERNEL_STACK_INPAGE_ERROR
Kernel data could not be read from the paging file into memory.
The Stop 0x77 message indicates that a page of kernel data requested from the paging (virtual memory) file could not be found or read into memory. This Stop message can also indicate disk hardware failure, disk data corruption, or possible virus infection.
STOP Message 0x00000077 is a related kernel traps that are caused when the operating system tries to load a page into memory from the paging file on the hard disk, but cannot access the page because of either a software or hardware failure.
The final error is 0x000000F4: CRITICAL_OBJECT_TERMINATION
One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message. One user, who experienced this on return from Standby mode on Win XP SP2, found the cause was that Windows was installed on a slave drive.
This dump cited csrss.exe and is responsible for console windows, creating and/or deleting threads, and implementing some portions of the 16-bit virtual MS-DOS environment.
In light of the 0x77s and the two other errors especially the F4 you need to attempt the following:
1. Back up everything A.S.A.P. , find the name of the manufacture of your HDs, and run their free harddrive utility. Do BOTH short and long tests.
2. Next, a Windows Repair is probably in order here. But you are going to have to find out which harddrive is slaved, etc.
3. Scan for viruses.
3. Update to Service Pack 3 if for nothing else that come July 10th XP with SP 2 will no longer be supported.
