| Previous | Next |
| STATUS_ACCESS_VIOLATION | STATUS_PAGEFILE_QUOTA |
STATUS_IN_PAGE_ERROR
The memory reference failed while paging data into RAM
This exception means that the virtual address was valid enough to require paging, but Windows could not obtain the page from its backing store. The backing object may be an executable image, a memory-mapped file, or the paging file. In an EXCEPTION_RECORD, the first parameters describe the access and address, while a later parameter carries the underlying I/O NTSTATUS that explains why the page-in failed.
Treat the nested status as the primary diagnostic clue. Storage removal, media errors, network-backed mappings, filter-driver failures, or a truncated mapped file can all surface through the same outer exception. The instruction pointer can be misleading when the failed page contains data rather than code, so collect both the exception record and the mapped-file information for the referenced address.
What to inspect
- Read every ExceptionInformation element, especially the underlying I/O status.
- Resolve the referenced address to its mapped file, image section, or page-file backing.
- Check storage and file-system events at the same timestamp.
- Preserve a dump before remapping or reopening the file changes the evidence.
References
- Microsoft Learn: EXCEPTION_RECORD
- Microsoft Learn: Exception Dispatching
- Microsoft Open Specifications: NTSTATUS values
- Microsoft Windows SDK metadata: ntstatus.h
Looking for a different code? Search another status or error code.