Code:
-
Loading Dump File [K:\BSODDmpFiles\Moteo\Windows_NT6_BSOD_jcgriff2\012712-27144-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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03264000 PsLoadedModuleList = 0xfffff800`034a9670
Debug session time: Fri Jan 27 00:34:03.579 2012 (GMT-7)
System Uptime: 0 days 0:05:17.422
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa80102f8b30, fffffa80102f8e10, fffff800035e48b0}
Probably caused by : csrss.exe
Followup: MachineOwner
---------
0: 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: 0000000000000003, Process
Arg2: fffffa80102f8b30, Terminating object
Arg3: fffffa80102f8e10, Process image file name
Arg4: fffff800035e48b0, Explanatory message (ascii)
Debugging Details:
------------------
PROCESS_OBJECT: fffffa80102f8b30
IMAGE_NAME: csrss.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: csrss
FAULTING_MODULE: 0000000000000000
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:
fffff880`0edb9438 fffff800`0366b5e2 : 00000000`000000f4 00000000`00000003 fffffa80`102f8b30 fffffa80`102f8e10 : nt!KeBugCheckEx
fffff880`0edb9440 fffff800`0361899b : ffffffff`ffffffff fffffa80`11628060 fffffa80`102f8b30 fffffa80`102f8b30 : nt!PspCatchCriticalBreak+0x92
fffff880`0edb9480 fffff800`03598448 : ffffffff`ffffffff 00000000`00000001 fffffa80`102f8b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`0edb94d0 fffff800`032dfed3 : fffffa80`102f8b30 fffff800`c0000006 fffffa80`11628060 00000000`013d0f40 : nt!NtTerminateProcess+0xf4
fffff880`0edb9550 fffff800`032dc470 : fffff800`0332c67f fffff880`0edba038 fffff880`0edb9d90 fffff880`0edba0e0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0edb96e8 fffff800`0332c67f : fffff880`0edba038 fffff880`0edb9d90 fffff880`0edba0e0 00000000`013d1c50 : nt!KiServiceLinkage
fffff880`0edb96f0 fffff800`032e02c2 : fffff880`0edba038 00000000`0001e102 fffff880`0edba0e0 00000000`013d1728 : nt! ?? ::FNODOBFM::`string'+0x49874
fffff880`0edb9f00 fffff800`032dee3a : 00000000`00000000 000007fe`fe1e1330 fffffa80`11628001 00000000`0001e102 : nt!KiExceptionDispatch+0xc2
fffff880`0edba0e0 00000000`77ac9c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`013d1670 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ac9c12
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe
BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe
Followup: MachineOwner
---------
-
Loading Dump File [K:\BSODDmpFiles\Moteo\Windows_NT6_BSOD_jcgriff2\012712-23337-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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0321e000 PsLoadedModuleList = 0xfffff800`03463670
Debug session time: Thu Jan 26 21:30:00.826 2012 (GMT-7)
System Uptime: 0 days 0:05:32.670
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa80105d9b30, fffffa80105d9e10, fffff8000359e8b0}
Probably caused by : wininit.exe
Followup: MachineOwner
---------
6: 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: 0000000000000003, Process
Arg2: fffffa80105d9b30, Terminating object
Arg3: fffffa80105d9e10, Process image file name
Arg4: fffff8000359e8b0, Explanatory message (ascii)
Debugging Details:
------------------
PROCESS_OBJECT: fffffa80105d9b30
IMAGE_NAME: wininit.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: wininit.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:
fffff880`07701e38 fffff800`036255e2 : 00000000`000000f4 00000000`00000003 fffffa80`105d9b30 fffffa80`105d9e10 : nt!KeBugCheckEx
fffff880`07701e40 fffff800`035d299b : ffffffff`ffffffff fffffa80`1004db60 fffffa80`105d9b30 fffffa80`105d9b30 : nt!PspCatchCriticalBreak+0x92
fffff880`07701e80 fffff800`03552448 : ffffffff`ffffffff 00000000`00000001 fffffa80`105d9b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`07701ed0 fffff800`03299ed3 : fffffa80`105d9b30 fffff800`c0000006 fffffa80`1004db60 00000000`00c80d00 : nt!NtTerminateProcess+0xf4
fffff880`07701f50 fffff800`03296470 : fffff800`032e667f fffff880`07702a38 fffff880`07702790 fffff880`07702ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`077020e8 fffff800`032e667f : fffff880`07702a38 fffff880`07702790 fffff880`07702ae0 00000000`7750f928 : nt!KiServiceLinkage
fffff880`077020f0 fffff800`0329a2c2 : fffff880`07702a38 00000000`00d00000 fffff880`07702ae0 00000000`7751bed8 : nt! ?? ::FNODOBFM::`string'+0x49874
fffff880`07702900 fffff800`03298e3a : 00000000`00000000 00000000`774d0c34 00000000`776a8d01 00000000`00d00000 : nt!KiExceptionDispatch+0xc2
fffff880`07702ae0 00000000`77598f55 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00c81420 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77598f55
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe
BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe
Followup: MachineOwner
---------
- A windows system process was terminated unexpectedly. Possible causes are hard disk errors... Viruses... Lack of Windows updates... Drivers...
- A windows system process was terminated unexpectedly. Possible causes are hard disk errors... Viruses... Lack of Windows updates... Drivers...
Each of those crashes occurred probably 3-4 times each at least.
Definitely points to the hard drive being bad. I would also run Memtest86+ to make sure you do not have multiple hardware problems.