*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {20, ffffffffc000009d, fffffa800838f078, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c830 )
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: fffffa800838f078, 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: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 1
LAST_CONTROL_TRANSFER: from fffff80002af9bec to fffff80002ac1f00
STACK_TEXT:
fffff880`03308828 fffff800`02af9bec : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`0838f078 : nt!KeBugCheckEx
fffff880`03308830 fffff800`02aabe67 : fffffa80`0838f010 00000000`c000009d 00000000`00000000 fffffa80`0838f0a8 : nt! ?? ::FNODOBFM::`string'+0x4c830
fffff880`033088f0 fffff800`02a9e92f : fffffa80`06cf4040 fffffa80`06cf4090 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57
fffff880`03308920 fffff800`02ac925d : fffffa80`06cf4040 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`033089a0 fffff800`02ac554b : 00000103`08371001 00000000`00000000 00000000`00000000 fffff880`03308a50 : nt!KiCommitThreadWait+0x3dd
fffff880`03308a30 fffff800`02a5aa8f : fffffa80`00000002 fffff880`03308d20 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271
fffff880`03308ce0 fffff800`02d65166 : fffffa80`06cf4040 ffe477e8`ffffe814 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`03308d40 fffff800`02aa0486 : fffff880`02f64180 fffffa80`06cf4040 fffff880`02f6efc0 873ee8cd`8b48087e : nt!PspSystemThreadStartup+0x5a
fffff880`03308d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4c830
fffff800`02af9bec cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4c830
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c830
BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c830
Followup: MachineOwner
---------