| Previous | Next |
| STATUS_PAGE_FAULT_COPY_ON_WRITE | STATUS_PAGE_FAULT_PAGING_FILE |
STATUS_PAGE_FAULT_GUARD_PAGE
A guard-page condition was found while resolving a page fault
This success-severity status is used inside memory-management paths to classify a fault involving a page marked with PAGE_GUARD. It is not interchangeable with the user-visible STATUS_GUARD_PAGE_VIOLATION exception: the former can be an internal result while the system is deciding whether stack growth or another guard-page policy can satisfy the access.
When it appears in diagnostics, correlate it with the faulting virtual address, the thread stack limits, and the page protection before treating it as an application failure. A stack can legitimately touch its current guard page and cause another page to be committed. Repeated faults at the same address, failure to establish a new guard page, or a guard page outside the expected stack range are the stronger signs of corruption or exhaustion.
What to inspect
- Capture the faulting address and the page protection reported by the debugger.
- Compare the address with the thread stack base, stack limit, and reserved range.
- Determine whether the fault was consumed by stack growth or propagated as an exception.
- Do not report an I/O failure merely because the event was recorded as a page fault.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft Windows SDK metadata: ntstatus.h
- Microsoft Learn: Creating Guard Pages
- Microsoft Learn: Debugging a Stack Overflow
Looking for a different code? Search another status or error code.