| Previous | Next |
| MISMATCHED_HAL | INACCESSIBLE_BOOT_DEVICE |
KERNEL_DATA_INPAGE_ERROR
The KERNEL_DATA_INPAGE_ERROR bug check has a value of 0x0000007A. This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
Important
KERNEL_DATA_INPAGE_ERROR Parameters
The four parameters that are listed in the message can have three possible meanings. If the first parameter is 1 or 2, or 3 and the third parameter is 0, the parameters have the following definitions.
| Parameter | Description |
|---|---|
1 |
The lock type that was held (1, 2, or 3) |
2 |
The error status (usually an I/O status code) |
3 |
If Lock Type is 1: the current process If Lock Type is 2 or 3: 0 |
4 |
The virtual address that could not be paged into memory |
If the first parameter is 3 (and the third parameter is nonzero) or 4, the parameters have the following definitions.
| Parameter | Description |
|---|---|
1 |
The lock type that was held (3 or 4) |
2 |
The error status (typically an I/O status code) |
3 |
The address of the InPageSupport structure |
4 |
The faulting address |
Otherwise, the parameters have the following definitions.
| Parameter | Description |
|---|---|
1 |
The address of the page table entry (PTE) |
2 |
— |
3 |
The PTE contents |
4 |
The faulting address |
Cause
Frequently, you can determine the cause of This bug check from the error status (Parameter 2). Some common status codes include the following:
These status codes are the most common ones that have specific causes. For more information about other possible status codes that can be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).
Another common cause of this error message is defective hardware or failing RAM.
Resolution
Use Parameter 2 as the primary discriminator: it is the I/O status from the failed in-page operation. Correlate that status with Parameter 1, the faulting virtual address in Parameter 3, the page-file or backing-file device, and storage-controller events from the same failure window.
Repeated 0xC000009C or 0xC000016A results support unreadable media; 0xC0000185 points to an I/O-path communication problem. If the storage evidence is clean, use the dump and hardware-error telemetry to distinguish memory corruption from a driver or DMA path corrupting the page.
See also
Bug Check 0x77 (KERNEL_STACK_INPAGE_ERROR)
Official references
Looking for a different code? Search another status or error code.