KMODE_EXCEPTION_NOT_HANDLED (0x0000001E)? Find the Driver That Threw It
Your PC blue-screens with KMODE_EXCEPTION_NOT_HANDLED (stop code 0x0000001E), sometimes with a .sys filename on screen.
Why: Microsoft’s bug-check page says 0x1E “indicates that a kernel-mode program generated an exception that the error handler didn’t catch.” It names a faulty device driver or system service as a cause, and notes hardware issues — including a system BIOS incompatibility, memory conflicts, and IRQ conflicts — can also generate it. If a driver is named on screen, that’s your starting point.
Fix 1: Disable or update the named driver
Microsoft is explicit: “If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.”
- Note any filename shown on the blue screen (for example a network or GPU
.sys). - Press Win + X → Device Manager, find that device.
- Right-click → Update driver, or grab the current driver from the hardware maker. If the crash followed a recent update, use Properties → Driver → Roll Back Driver.
If you can’t boot normally, the page suggests Safe Mode to disable the driver in Device Manager.
Fix 2: Remove recently added drivers and services
The page advises disabling or removing any drivers or services added recently. Uninstall low-level software like third-party antivirus, VPNs, or disk utilities to test, then check Event Viewer → Windows Logs → System for errors around the crash time that name a device or driver.
Fix 3: Update the BIOS/UEFI
Microsoft names a “system BIOS incompatibility” as a possible cause and says you can resolve it by upgrading the system BIOS version.
- Find your exact PC or motherboard model.
- On the maker’s support page, download the latest BIOS/UEFI update.
- Follow their flashing instructions exactly — don’t interrupt the process.
Fix 4: Run the memory scanner
The page says to run hardware diagnostics from your system manufacturer, “especially the memory scanner.” Run the built-in Windows Memory Diagnostic too: press Start, type mdsched.exe, press Enter, and choose Restart now and check for problems.
FAQ
The blue screen doesn’t name a .sys file. Then the exception address (Parameter 2) holds the culprit, but you’d need a dump to read it. Work through Fixes 2-4 first — undo recent changes, update the BIOS, and test memory.
Is 0x1E a hardware or software problem? Either. It’s most often a faulty driver, but Microsoft also lists BIOS incompatibility and memory/IRQ conflicts — which is why both the driver and the memory/BIOS fixes are here.
Sources: Microsoft Learn — Bug Check 0x1E KMODE_EXCEPTION_NOT_HANDLED