| Previous | Next |
| CANCEL_STATE_IN_COMPLETED_IRP | IRQL_GT_ZERO_AT_SYSTEM_SERVICE |
PAGE_FAULT_WITH_INTERRUPTS_OFF
PAGE_FAULT_WITH_INTERRUPTS_OFF is bug check 0x49. Microsoft marks it very infrequent and does not publish a four-parameter contract on the individual reference page. The name identifies the important state combination: a page-fault condition occurred while interrupts were off, but it does not identify the address or driver through documented argument positions.
The state matters more than a generic “bad RAM” diagnosis
Kernel code has strict execution constraints when interrupts are disabled. The dump should be used to locate the path that entered that state and the instruction or module involved in the fault. The stop name alone does not prove physical-memory failure, nor does it publish the read/write-style layout used by some other page-fault bug checks.
What to inspect
- Use
!analyze -vand inspect the symbolized stack and processor context. - Look for the code path that disabled interrupts and whether control remained in a context that could fault.
- Keep raw arguments and exact build data for comparison, without assigning undocumented address fields.
References
- Microsoft: Bug Check 0x49 PAGE_FAULT_WITH_INTERRUPTS_OFF
- Microsoft: hardware priorities and execution constraints
- Microsoft: kernel dump analysis
Looking for a different code? Search another status or error code.
