| Previous | Next |
| STATUS_PRIMARY_TRANSPORT_CONNECT_FAILED | STATUS_PAGE_FAULT_DEMAND_ZERO |
STATUS_PAGE_FAULT_TRANSITION
The page was resident but not currently valid in the process
A transition page table entry refers to a physical page that is no longer in the active working set but has not yet been reused. Resolving this fault normally means restoring a valid mapping and updating working-set accounting; it does not require reading the page from the paging file or the mapped file.
This is an internal success status from the fault-resolution path, not an application failure. In a trace it is useful for separating soft faults from storage-backed hard faults. Repeated transition faults can still indicate working-set trimming or memory pressure, but a single occurrence does not imply corrupt memory or a damaged page file.
What to inspect
- Correlate the status with the faulting virtual address, process, and access type.
- Check whether the page was on a standby or transition list and whether the working set was recently trimmed.
- Use ETW or debugger memory diagnostics to compare transition faults with paging-file and mapped-file reads.
References
- Microsoft: Active memory dumps and page states
- ReactOS source: NT page-fault resolution
- Microsoft: Process working sets
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.