| Previous | Next |
| SYSTEM_SERVICE_EXCEPTION | INTERRUPT_EXCEPTION_NOT_HANDLED |
INTERRUPT_UNWIND_ATTEMPTED
Invalid unwind through interrupt context for INTERRUPT_UNWIND_ATTEMPTED
INTERRUPT_UNWIND_ATTEMPTED is bug check code 0x0000003C. This code points at exception/unwind logic interacting with interrupt or trap state. It is typically about corrupted control-flow state, a bad trap frame, or code attempting to unwind through a context that cannot be unwound normally.
How to read it in a dump
- Inspect interrupt/trap frames and the processor context saved in the dump.
- The stack may be misleading if the unwind metadata is already corrupted.
- Hardware interrupt handlers, DPCs, and low-level drivers are important suspects when present.
What to check
- Analyze trap frames and processor state in WinDbg.
- Check low-level drivers, filter hooks, and recent security or instrumentation software.
- Consider memory corruption if the interrupt stack or saved context is damaged.
References
Dump evidence
Preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each parameter instead of relying only on the probably-caused-by line. - find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with interrupt / unwind / attempted.
- keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by this result before collecting the dump and event logs. Recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Looking for a different code? Search another status or error code.