KERNEL_DATA_INPAGE_ERROR (7a)
[U][B]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[/B][/U]. Also see
KERNEL_STACK_INPAGE_ERROR.
[U][B]If the error status is[/B][/U] [U][B]0xC000000E[/B][/U], 0xC000009C, 0xC000009D or 0xC0000185,
[U][B]it means the disk subsystem has experienced a failure[/B][/U].
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c0416820, lock type that was held (value 1,2,3, or PTE address)
[U][B]Arg2: c000000e, error status (normally i/o status code)[/B][/U]
Arg3: 12389860, current process (virtual address for lock type 3, or PTE)
Arg4: 82d04d37, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
ERROR_CODE: (NTSTATUS) 0xc000000e - [U][B]A device which does not exist was specified[/B][/U].
[U][B]DISK_HARDWARE_ERROR: There was error with disk hardware[/B][/U]
[U][B]BUGCHECK_STR: 0x7a_c000000e[/B][/U]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: 88f1fa14 -- (.trap 0xffffffff88f1fa14)
ErrCode = 00000010
eax=84aacc01 ebx=00010000 ecx=2c000128 edx=00010000 esi=84aacb80 edi=84a97008
eip=82d04d37 esp=88f1fa88 ebp=88f1fab0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!PnpRequestDeviceRemoval:
82d04d37 8bff mov edi,edi
Resetting default scope
LOCK_ADDRESS: 82bacbe0 -- (!locks 82bacbe0)
Resource @ nt!PiEngineLock (0x82bacbe0) Available
WARNING: SystemResourcesList->[U][B]Flink chain invalid. Resource may be corrupted, or already deleted.[/B][/U]
WARNING: SystemResourcesList->[U][B]Blink chain invalid. Resource may be corrupted, or already deleted.[/B][/U]
1 total locks
PNP_TRIAGE:
Lock address : 0x82bacbe0
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from 82ae9dd8 to 82b24e9c
STACK_TEXT:
88f1f874 82ae9dd8 0000007a c0416820 c000000e nt!KeBugCheckEx+0x1e
88f1f8e4 82aed6b9 88f1f938 82bb0300 88f1f958 nt!MiWaitForInPageComplete+0x302
88f1f974 82ad691b 82bb0300 82d04d37 854ada00 nt!MiIssueHardFault+0x3b3
88f1f9fc 82a87468 00000008 82d04d37 00000000 nt!MmAccessFault+0x2656
88f1f9fc 82d04d37 00000008 82d04d37 00000000 nt!KiTrap0E+0xdc
88f1fa84 82c040e3 00000018 84a97008 00000000 nt!PnpRequestDeviceRemoval
88f1fab0 82c03093 95c2f8c0 84a97008 00000002 nt!PipEnumerateCompleted+0x12e
88f1fca4 82c03e29 84a97008 95c2f8c0 88f1fcd0 nt!PipProcessDevNodeTree+0x352
88f1fcd8 82a5ad10 82baab00 841ba798 82b813bc nt!PiProcessReenumeration+0x74
88f1fd00 82ac3a6b 00000000 00000000 841ba798 nt!PnpDeviceActionWorker+0x224
88f1fd50 82c4f056 00000001 9c185680 00000000 nt!ExpWorkerThread+0x10d
88f1fd90 82af71a9 82ac395e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiWaitForInPageComplete+302
82ae9dd8 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiWaitForInPageComplete+302
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4f766ae5
IMAGE_NAME: [U][B] memory_corruption[/B][/U]
FAILURE_BUCKET_ID: 0x7a_c000000e_nt!MiWaitForInPageComplete+302
BUCKET_ID: 0x7a_c000000e_nt!MiWaitForInPageComplete+302