[COLOR=Red]KERNEL_DATA_INPAGE_ERROR (7a)[/COLOR]
The requested page of kernel data could not be read in. [COLOR=Red]Typically caused by
a bad block in the paging file or disk controller error.[/COLOR] Also see
KERNEL_STACK_INPAGE_ERROR.
[COLOR=Red]If the error status is[/COLOR] 0xC000000E, 0xC000009C, 0xC000009D or[COLOR=Red] 0xC0000185[/COLOR],
[COLOR=Red]it means the disk subsystem has experienced a failure.[/COLOR]
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc40009a30, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 000000012c5fa860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88001346758, 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]
[B][COLOR=Red]DISK_HARDWARE_ERROR: There was error with disk hardware[/COLOR][/B]
BUGCHECK_STR: 0x7a_c0000185
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre