| Previous | Next |
| ERROR_PAGE_FAULT_COPY_ON_WRITE | ERROR_PAGE_FAULT_PAGING_FILE |
ERROR_PAGE_FAULT_GUARD_PAGE
Access reached a guard page and triggered one-shot notification
ERROR_PAGE_FAULT_GUARD_PAGE corresponds to Win32 error value documented as: Page fault was a demand zero fault. Guard pages raise a notification on first access and then lose the guard attribute. Windows uses them for stack growth, while applications may use them to detect buffer boundaries or lazy commitment.
Where the result appears in real systems
- Automatic stack expansion.
- Custom allocators with guard regions.
- Debuggers.
- Fiber and coroutine stacks.
What to collect before making changes
Record faulting address, instruction pointer, thread stack limits, allocation base, and protection flags; determine whether the address is the expected next stack page or an unrelated overrun; capture a stack trace before continuing.
Handling and recovery
For legitimate stack growth, let the operating system handler proceed. For custom guards, restore PAGE_GUARD only when the design requires repeated detection. Treat an address outside the planned guard region as a likely bounds defect.
What not to infer from this code
This result can be part of normal execution, while STATUS_GUARD_PAGE_VIOLATION exposed to application exception handling may require explicit handling depending on context.
References
Looking for a different code? Search another status or error code.