BSOD 61 (INTERRUPT_EXCEPTION_NOT_HANDLED): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: INTERRUPT_EXCEPTION_NOT_HANDLED

Could be also:
Constant	Type	OS
ERROR_PRINTQ_FULL	Win32 error	Windows
ENODATA	errno	Linux
ECONNREFUSED	errno	Mac
ENODATA	errno	Solaris

Previous	Next
SYSTEM_EXIT_OWNED_MUTEX	MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED

INTERRUPT_EXCEPTION_NOT_HANDLED

INTERRUPT_EXCEPTION_NOT_HANDLED is bug check 0x3D. Microsoft describes a specific kernel condition: the exception handler for a kernel interrupt object could not handle an exception that was generated. This is narrower than a generic “interrupt failed” message and should keep the investigation centered on the interrupt-related kernel path in the dump.

Do not substitute the 0x7E exception contract

The public 0x3D page does not publish the four-parameter exception-code/address layout used by SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Preserve the raw arguments, but derive exception and instruction context from the debugger output for this dump rather than assigning those meanings by position.

What to inspect

Run !analyze -v and inspect the current stack around interrupt-object and handler frames.
Use symbolized addresses to identify the driver or module represented by the first relevant non-kernel frame.
Compare device and driver versions across repeat dumps only after the same interrupt path is established.

References

Looking for a different code? Search another status or error code.