*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
[COLOR="Red"]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.[/COLOR]
Arguments:
Arg1: fffff6fc40032558, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000008765abe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff880064ab000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
[COLOR="red"]DISK_HARDWARE_ERROR: There was error with disk hardware[/COLOR]
BUGCHECK_STR: 0x7a_c000000e
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002d46742 to fffff80002cd3b80
STACK_TEXT:
fffff880`03563708 fffff800`02d46742 : 00000000`0000007a fffff6fc`40032558 ffffffff`c000000e 00000000`8765abe0 : nt!KeBugCheckEx
fffff880`03563710 fffff800`02cfa91f : fffffa80`0ce1b870 fffff880`03563880 fffff800`02f0e540 fffffa80`0ce1b870 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`035637f0 fffff800`02ce11b9 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff 00000000`00000008 : nt!MiIssueHardFault+0x28b
fffff880`035638c0 fffff800`02d07700 : 00000000`00000001 fffff880`064ab000 fffffa80`0fc1ba00 fffff6fc`40032530 : nt!MmAccessFault+0x1399
fffff880`03563a20 fffff800`02d078f0 : fffffa80`0cdd67c0 fffffa80`00000001 fffffa80`00000000 fffff800`02c7cd62 : nt!MiInPageSingleKernelStack+0x134
fffff880`03563b30 fffff800`02d0787f : 00000000`00000000 00000000`00000001 fffffa80`0ca6bae0 00000000`00000080 : nt!MmInPageKernelStack+0x40
fffff880`03563b90 fffff800`02d075c4 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0ca6ba00 : nt!KiInSwapKernelStacks+0x1f
fffff880`03563bc0 fffff800`02f71bae : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0x84
fffff880`03563c00 fffff800`02cc48c6 : fffff880`009eb180 fffffa80`0ca96040 fffff880`009f5fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03563c40 00000000`00000000 : fffff880`03564000 fffff880`0355e000 fffff880`03563910 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+36c1a
fffff800`02d46742 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+36c1a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 51fb06cd
FAILURE_BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+36c1a
BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+36c1a
Followup: MachineOwner
---------