| Previous | Next |
| STATUS_RECOVERY_FAILURE | STATUS_FAIL_CHECK |
STATUS_STACK_OVERFLOW_READ
An internal stack-overflow read path must handle the request
This status is an internal routing result whose published message says that the request must be handled by stack-overflow code. Despite the word “read,” it should not be diagnosed as an ordinary file or device read failure. It can appear while the system or a compatibility layer is processing a memory access near an exhausted stack.
Public documentation does not define a separate application recovery contract for this code. Preserve the raw status and diagnose it with the same evidence used for STATUS_STACK_OVERFLOW: stack bounds, guard-page state, recursion, frame size, and the instruction that accessed memory. Converting it immediately to a generic access violation can hide the distinction that a debugger or runtime needs to select its stack-overflow path.
What to inspect
- Keep the original NTSTATUS value in crash telemetry and exception translation.
- Inspect the current stack pointer and guard-page boundary.
- Look for recursion or large automatic allocations before investigating storage I/O.
- Avoid inventing retry behavior; use the owning runtime’s documented overflow path.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft Windows SDK metadata: ntstatus.h
- Microsoft Learn: Debugging a Stack Overflow
- Microsoft Learn: Creating Guard Pages
Looking for a different code? Search another status or error code.