| Previous | Next |
| PROCESS_HAS_LOCKED_PAGES | PHASE0_EXCEPTION |
KERNEL_STACK_INPAGE_ERROR
The KERNEL_STACK_INPAGE_ERROR bug check has a value of 0x00000077. This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
Important
KERNEL_STACK_INPAGE_ERROR Parameters
The four parameters that listed in the message have two possible meanings.
If the first parameter is 0, 1, or 2, the parameters have the following meaning.
| Parameter | Description |
|---|---|
1 |
0: The page of kernel data was retrieved from page cache. 1: The page was retrieved from a disk. 2: The page was retrieved from a disk, the storage stack returned SUCCESS, but Status.Information is not equal to PAGE_SIZE. |
2 |
The value that appears in the stack where the signature should be. |
3 |
0 |
4 |
The address of the signature on the kernel stack |
If the first parameter is any value other than 0, 1, or 2, the parameters have the following meaning.
| Parameter | Description |
|---|---|
1 |
The status code |
2 |
The I/O status code |
3 |
The page file number |
4 |
The offset into page file |
Cause
If the first parameter is 0 or 1, the stack signature in the kernel stack was not found. This error is probably caused by defective hardware, such as a RAM error.
If the first parameter is 2, the driver stack returned an inconsistent status for the read of the page. For example, the driver stack returned a success status even though it did not read the whole page.
If the first parameter is any value other than 0, 1, or 2, the value of the first parameter is an NTSTATUS error code that the driver stack returns after it tries to retrieve the page of kernel data. You can determine the exact cause of this error from the I/O status code (the second parameter). 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 might be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).
Resolution
Interpret the stop parameters before choosing a recovery path. When Parameter 1 is greater than 2, treat it as the NTSTATUS returned while reading the kernel-stack page and use Parameter 2 as the I/O status; values such as 0xC000009C, 0xC000016A, and 0xC0000185 point toward different storage-path failures.
Preserve the dump, paging-file location, storage stack, controller/device events, and any repeated failing block or device identity. If Parameter 1 is 0 or 1, investigate memory corruption; if it is 2, investigate the driver stack that reported a successful read without returning the complete page.
See also
Bug Check 0x7A (KERNEL_DATA_INPAGE_ERROR)
Official references
Looking for a different code? Search another status or error code.