| Previous | Next |
| STATUS_ENCOUNTERED_WRITE_IN_PROGRESS | STATUS_PURGE_FAILED |
STATUS_PTE_CHANGED
A concurrent mapping transition invalidated the fault assumptions
Page-fault handling inspects a page-table entry, may drop locks while performing work, and then must verify that the mapping still represents the same state. Another thread can protect, unmap, decommit, or replace the region during that interval. This status requests a controlled retry against the new PTE state.
It is an internal synchronization result, not evidence that the page tables are corrupt. If it escapes unexpectedly or repeats indefinitely, look for a race that continually changes the region or for code translating an internal retry status into a terminal application error.
What to inspect
- Capture the faulting address and concurrent VirtualProtect, unmap, decommit, or mapping operations.
- Check whether the status is consumed by the normal Memory Manager retry loop.
- Investigate repeated retries for a thread continuously changing the same region.
References
- Microsoft: VirtualProtect
- Microsoft: VirtualFree
- Microsoft: UnmapViewOfFile
- ReactOS source: NT page-fault resolution
- ReactOS source: virtual memory manager
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.