Do not tell me to check my hard drive for failures, Ive checked over 10 times.
Ive salvaged one Minidump, and used it in Windbg for analysis. The main error is a 0x000000F4, which is a system process failure, or to make it easier to find, CRITICAL_OBJECT_TERMINATION.
Windbg also says that Csrss.exe is the cause, but I cant delve any further due to lack of knowledge.
Enough of me talking, I can give more information about the problems when asked.
Error Codes: 0x000000F4(0x00000003, 0x878BB950, 0x878BBABC, 0x82E41D50)
WinDBG Analysis:
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010410-62150-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C://symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82c3d000 PsLoadedModuleList = 0x82d85810
Debug session time: Mon Jan 4 08:00:26.573 2010 (GMT-8)
System Uptime: 0 days 0:09:12.370
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
..........
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 878de228, Terminating object
Arg3: 878de394, Process image file name
Arg4: 82e65d50, Explanatory message (ascii)
Debugging Details:
------------------
PROCESS_OBJECT: 878de228
IMAGE_NAME: csrss.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: csrss
FAULTING_MODULE: 00000000
PROCESS_NAME: csrss.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
BUGCHECK_STR: 0xF4_IOERR
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
STACK_TEXT:
998a3c9c 82f1907b 000000f4 00000003 878de228 nt!KeBugCheckEx+0x1e
998a3cc0 82e9ce44 82e65d50 878de394 878de498 nt!PspCatchCriticalBreak+0x71
998a3cf0 82e9ecdf 878de228 86b5c030 c0000006 nt!PspTerminateAllThreads+0x2d
998a3d24 82c8042a ffffffff c0000006 09cef394 nt!NtTerminateProcess+0x1a2
998a3d24 76fa64f4 ffffffff c0000006 09cef394 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
09cef394 00000000 00000000 00000000 00000000 0x76fa64f4
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0xF4_IOERR_IMAGE_csrss.exe
BUCKET_ID: 0xF4_IOERR_IMAGE_csrss.exe
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 878de228, Terminating object
Arg3: 878de394, Process image file name
Arg4: 82e65d50, Explanatory message (ascii)
Debugging Details:
------------------
PROCESS_OBJECT: 878de228
IMAGE_NAME: csrss.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: csrss
FAULTING_MODULE: 00000000
PROCESS_NAME: csrss.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
BUGCHECK_STR: 0xF4_IOERR
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
STACK_TEXT:
998a3c9c 82f1907b 000000f4 00000003 878de228 nt!KeBugCheckEx+0x1e
998a3cc0 82e9ce44 82e65d50 878de394 878de498 nt!PspCatchCriticalBreak+0x71
998a3cf0 82e9ecdf 878de228 86b5c030 c0000006 nt!PspTerminateAllThreads+0x2d
998a3d24 82c8042a ffffffff c0000006 09cef394 nt!NtTerminateProcess+0x1a2
998a3d24 76fa64f4 ffffffff c0000006 09cef394 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
09cef394 00000000 00000000 00000000 00000000 0x76fa64f4
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0xF4_IOERR_IMAGE_csrss.exe
BUCKET_ID: 0xF4_IOERR_IMAGE_csrss.exe
Followup: MachineOwner
---------