*******************************************************************************
* *
* 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.
[U][COLOR=Red]If the error status is[/COLOR][/U] 0xC000000E, 0xC000009C, 0xC000009D or [U][COLOR=Red]0xC0000185[/COLOR][/U],
[U][COLOR=Red]it means the disk subsystem has experienced a failure.[/COLOR][/U]
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c057ffd0, lock type that was held (value 1,2,3, or PTE address)
Arg2: c0000185, error status (normally i/o status code)
Arg3: 54a8b820, current process (virtual address for lock type 3, or PTE)
Arg4: afffaff0, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
[COLOR=Red]ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.[/COLOR]
[COLOR=Red][B]DISK_HARDWARE_ERROR: There was error with disk hardware[/B][/COLOR]
BUGCHECK_STR: 0x7a_c0000185
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: 8a91ba04 -- (.trap 0xffffffff8a91ba04)
ErrCode = 00000000
eax=afffaff0 ebx=ad413340 ecx=001caff0 edx=00000000 esi=ad413340 edi=ad413008
eip=82e47c44 esp=8a91ba78 ebp=8a91ba88 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!HvMarkCellDirty+0x220:
82e47c44 8b00 mov eax,dword ptr [eax] ds:0023:afffaff0=00000000
Resetting default scope
LAST_CONTROL_TRANSFER: from 82cfe60a to 82d26d10
