BSOD 30 (KMODE_EXCEPTION_NOT_HANDLED): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: KMODE_EXCEPTION_NOT_HANDLED a kernel-mode program raised an exception that no handler caught. Parameter 1 is the exception code, Parameter 2 is the.

Could be also:
Constant	Type	OS
ERROR_READ_FAULT	Win32 error	Windows
KERN_ALREADY_WAITING	Kern return	Mac
ippStsWrongIntersectQuad	Intel Ipp Status	Any
EROFS	errno	Any

Previous	Next
NO_SPIN_LOCK_AVAILABLE	SHARED_RESOURCE_CONV_ERROR

KMODE_EXCEPTION_NOT_HANDLED

KMODE_EXCEPTION_NOT_HANDLED meaning

KMODE_EXCEPTION_NOT_HANDLED is bug check 0x0000001E. A kernel-mode program raised an exception that no handler caught. Parameter 1 is the exception code, Parameter 2 is the faulting address, and Parameters 3 and 4 contain exception-specific information.

How to analyze the result

Decode the NTSTATUS exception, resolve the faulting instruction, inspect the trap or exception record, registers, stack, and accessed address. Distinguish access violation, breakpoint, misalignment, and other exception classes before blaming a module.

Preserve the complete dump, all four parameters, Windows build, loaded modules, and the event timeline before changing drivers or firmware while investigating this result.
Run !analyze -v and follow the parameter-specific objects and the stack associated with this result rather than relying only on the symbolic name or a single probable-cause line.
Compare multiple dumps when available; a stable instruction or object path associated with this result is stronger evidence than a module that appears only after earlier corruption.

Recovery boundary

Fix the driver or kernel code that raised the unhandled exception. A module name near the fault can be a victim of prior memory corruption, so preserve the full stack and earlier verifier or hardware evidence.

Official references

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