Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\013111-19266-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03012000 PsLoadedModuleList = 0xfffff800`0324fe50
Debug session time: Mon Jan 31 21:38:58.957 2011 (UTC - 5:00)
System Uptime: 0 days 0:20:10.003
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa80059cdb30, fffffa80059cde10, fffff8000338d5d0}
Probably caused by : hardware_disk
Followup: MachineOwner
---------
2: 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: fffffa80059cdb30, Terminating object
Arg3: fffffa80059cde10, Process image file name
Arg4: fffff8000338d5d0, Explanatory message (ascii)
Debugging Details:
------------------
PROCESS_OBJECT: fffffa80059cdb30
IMAGE_NAME: hardware_disk
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: csrss.exe
EXCEPTION_RECORD: fffff88002872b78 -- (.exr 0xfffff88002872b78)
ExceptionAddress: 00000000777b5a45
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 0000000000000000
Parameter[1]: 000007fefed60824
Parameter[2]: 00000000c000000e
Inpage operation failed at 000007fefed60824, due to I/O error 00000000c000000e
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.
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
ERROR_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.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 000007fefed60824
EXCEPTION_PARAMETER3: 00000000c000000e
IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
EXCEPTION_STR: 0xc0000006_c000000e
FAULTING_IP:
+23a
00000000`777b5a45 ?? ???
BUGCHECK_STR: 0xF4_IOERR_C000000E
FOLLOWUP_IP:
+23a
000007fe`fed60824 ?? ???
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware_disk
STACK_COMMAND: kb
FAILURE_BUCKET_ID: X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk
BUCKET_ID: X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\013111-21933-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03013000 PsLoadedModuleList = 0xfffff800`03250e50
Debug session time: Mon Jan 31 22:03:15.532 2011 (UTC - 5:00)
System Uptime: 0 days 0:22:32.968
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {20, ffffffffc000009d, fffffa8005aeb078, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c5e0 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa8005aeb078, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000009d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 1
LAST_CONTROL_TRANSFER: from fffff800030bb3fc to fffff80003083740
STACK_TEXT:
fffff880`03308a88 fffff800`030bb3fc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`05aeb078 : nt!KeBugCheckEx
fffff880`03308a90 fffff800`0306d637 : fffffa80`05aeb010 00000000`c000009d 00000000`00000000 fffffa80`05aeb0a8 : nt! ?? ::FNODOBFM::`string'+0x4c5e0
fffff880`03308b50 fffff800`030600c7 : fffffa80`03706b60 fffffa80`03706bb0 00000000`00000000 fffffa80`00000204 : nt!IopCompletePageWrite+0x57
fffff880`03308b80 fffff800`0308ab9d : fffffa80`03706b60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`03308c00 fffff800`030ca985 : fffffa80`03706b60 fffff880`02f67f40 00000000`00000000 fffff800`0301d9f0 : nt!KiCommitThreadWait+0x3dd
fffff880`03308c90 fffff800`0301da4a : fffffa80`03706b60 fffff880`00000008 00000000`00000001 fffffa80`03673b30 : nt!KeWaitForGate+0x101
fffff880`03308ce0 fffff800`03327c06 : fffffa80`03706b60 00000030`002e0031 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0x5a
fffff880`03308d40 fffff800`03061c26 : fffff880`02f63180 fffffa80`03706b60 fffff880`02f6dfc0 00000000`10000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03308d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4c5e0
fffff800`030bb3fc cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4c5e0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0
BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0
Followup: MachineOwner
---------