How to fix the KMODE_EXCEPTION_NOT_HANDLED (0x0000001E) blue screen
This stop code means a kernel program raised an error that nothing was set up to handle. A faulty driver is the usual culprit, sometimes paired with fast startup or bad memory. Jump to your situation below or work through the methods in order.
By Neeraj Singh ~11 min Updated Jun 2026 88% found this helpful
Error message
KMODE_EXCEPTION_NOT_HANDLED. Stop code 0x0000001E. A kernel-mode program generated an exception the handler did not catch.
Summary
KMODE_EXCEPTION_NOT_HANDLED (stop code 0x0000001E) means a program running in kernel mode generated an exception, and no error handler caught it, so Windows stopped. The crash screen often names the driver that misbehaved (a .sys file), and a faulty, outdated or incompatible driver is by far the most common cause. Fast Startup can contribute by loading drivers from a stale saved state, and bad RAM can trigger it too. The fix is to identify the failing driver from the screen or the minidump and update or roll it back, disable Fast Startup so drivers load cleanly, test your memory, and repair system files. Removing recently installed low-level software or a new device also clears it when one of those introduced the bad driver.
What this error means
Well-behaved kernel code wraps risky operations so that if something goes wrong, an exception handler deals with it. This stop code means an exception happened with no handler ready, which leaves Windows nowhere to go but a controlled crash.
The thing that usually raises that unhandled exception is a driver. So the screen frequently tells you which one, and fixing or removing that driver resolves it. Fast Startup and failing memory are secondary contributors that can produce the same result.
“The good news with KMODE_EXCEPTION_NOT_HANDLED is that Windows usually tells you the driver right on the screen, look for the .sys file under what failed. Update or roll back that one and most of these are done. The sneaky contributor is Fast Startup, which reloads drivers from a saved snapshot, so I always turn it off here so drivers initialise fresh. If it is still crashing, I test the RAM, because memory faults throw the same unhandled exception.”
Manager, Tech Support & Operations · 19+ years fixing Windows and system errors
✓ How to fix it
Method 1
Find the failing driver
1Read the .sys file named on the blue screen under what failed.
2Or open the minidump in C:\Windows\Minidump with BlueScreenView.
3That identifies the driver to fix.
Method 2
Update or roll back the driver
1Update the named driver, or roll it back in Device Manager if the crash began after an update.
2Reinstall or remove a recently added device's driver.
3Get drivers from the device or PC maker.
Method 3
Disable Fast Startup
1Open Control Panel, Power Options, Choose what the power buttons do, and untick Turn on fast startup.
2This makes drivers load cleanly on each boot instead of from a saved state.
3Restart and test.
Method 4
Test your memory
1Run Windows Memory Diagnostic (mdsched.exe) or MemTest86.
2Reseat or replace any failing stick.
3Bad RAM can cause this stop code.
Method 5
Repair system files
1Run DISM /Online /Cleanup-Image /RestoreHealth then SFC /scannow from an elevated prompt.
2This repairs corrupt system files that can trigger the stop code.
3Reboot and watch for the crash.
Method 6
Boot into Safe Mode if it keeps crashing
1If the PC will not stay up, let it fail twice so it enters the Recovery environment, then choose Troubleshoot, Advanced options, Startup Settings, and pick Safe Mode with Networking.
2Safe Mode loads only basic drivers, so you can work on the fix without the crash recurring.
3From there, update or roll back drivers and run the repairs below.
The blue screen often names the failing driver for KMODE_EXCEPTION_NOT_HANDLED, so start there: update or roll it back. Disable Fast Startup so drivers load fresh rather than from a stale snapshot, which is a common hidden contributor. Test RAM and repair system files if the driver fix does not hold.
Frequently asked questions
What does KMODE_EXCEPTION_NOT_HANDLED mean?
Stop code 0x0000001E means a kernel-mode program raised an exception that no handler caught, so Windows stopped. A faulty driver is the usual cause, and the screen often names it.
How do I find the driver that caused it?
Look for the .sys file named on the crash screen, or open the minidump in C:\Windows\Minidump with BlueScreenView, which identifies the failing driver.
Why disable Fast Startup?
Fast Startup loads drivers from a saved state rather than initialising them fresh, which can carry a faulty driver into each boot. Turning it off makes drivers load cleanly and often stops the crash.
Could it be a memory problem?
Yes. Bad or failing RAM can raise the unhandled exception behind this stop code. Run Windows Memory Diagnostic or MemTest86 and replace any failing module.
It started after installing software
Recently installed low-level software such as antivirus or a VPN can introduce a bad kernel driver. Uninstall it to test, then reinstall a current version if needed.
How do I fix it if Windows won't boot?
Let it fail twice to reach the Recovery environment, then boot Safe Mode with Networking to update or roll back drivers and disable Fast Startup.
Still not working?
If the driver is not obvious, enable Driver Verifier against non-Microsoft drivers to force the faulty one to surface in the next dump, then turn Verifier off after you identify it. Keep Safe Mode handy in case Verifier increases crashes before the fix. You can also submit your error to us for a tailored fix.
