KMODE_EXCEPTION_NOT_HANDLED — Causes & Fix
Windows Stop code 0x0000001E (KMODE_EXCEPTION_NOT_HANDLED) means a kernel-mode program generated an exception the error handler didn't catch — typically a faulty driver.
- Applies to
- Any Windows PC
- Time to fix
- 30 minutes – 2 hours
What it means
Causes include a buggy/incompatible driver, faulty hardware, or corrupt system files. This is a Windows Stop error (a "bugcheck" / blue screen) documented by Microsoft. The blue screen shows this code; more detail sits in the crash dump (%SystemRoot%\Minidump), which usually names the specific driver or component at fault — a free tool like BlueScreenView or WinDbg can read it.
Symptoms
- Blue screen citing KMODE_EXCEPTION_NOT_HANDLED
- Crashes at boot or when a device loads
How to fix it
- 1
Update/roll back the driver
1. Identify the driver in the dump and update or roll it back.
- 2
Boot into Safe Mode
1. If it crashes on boot, use Safe Mode to remove the offending driver/app, then repair system files.
Frequently asked questions
Which driver causes 0x1E?
Read the crash dump — it names the module. Graphics and third-party low-level drivers are common culprits.
Last updated July 20, 2026
Guidance only — always consult a qualified professional or the official service manual before carrying out repairs.