Error AtlasError Documentation and Resolution
Back to search

Windows Bug Check

Windows blue screen KMODE_EXCEPTION_NOT_HANDLED

Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

Windows stopped with a KMODE_EXCEPTION_NOT_HANDLED bug check because kernel-mode code raised an exception that no error handler caught.

KMODE_EXCEPTION_NOT_HANDLEDruntime

Observed message

Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

Why it happens

  • A kernel-mode driver or system service raised an exception that went unhandled.
  • A low-level driver bug, bad pointer, or memory access violation destabilized kernel execution.
  • A recent hardware, BIOS, or firmware change introduced low-level incompatibility.

How to fix it

  1. Review dump analysis, Event Viewer, and recent system changes to identify the likely module involved.
  2. Update, roll back, or remove the most likely faulting driver or system component.
  3. Check BIOS, firmware, and hardware compatibility if the issue started after a platform change.

Official reference

Bug check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

Related errors

CRITICAL_PROCESS_DIEDWindows blue screen CRITICAL_PROCESS_DIEDIRQL_NOT_LESS_OR_EQUALWindows blue screen IRQL_NOT_LESS_OR_EQUALMEMORY_MANAGEMENTWindows blue screen MEMORY_MANAGEMENTPAGE_FAULT_IN_NONPAGED_AREAWindows blue screen PAGE_FAULT_IN_NONPAGED_AREA

Explore more

runtimeBrowse more runtime errors
KMODE_EXCEPTION_NOT_HANDLED BSOD: causes and fixes | Error Atlas