KMODE_EXCEPTION_NOT_HANDLED Blue Screen
KMODE_EXCEPTION_NOT_HANDLED (stop code 0x1E) means a driver or other kernel-mode program hit an error that nothing caught, so Windows stopped. A faulty or outdated driver is the usual cause. Note any file named under “What failed,” undo recent hardware or driver changes, then install the latest Windows and driver updates.
Try these quick fixes first
- If the PC restarted and has worked normally since, save your work and watch for a repeat. Microsoft notes that a restart often resolves a one-time crash.
- Write down the stop code and any file named under “What failed.” A phone photo works. On newer Windows 11 versions, this screen can be black instead of blue.
- Think about what changed just before the first crash: new hardware, new software, a driver or a Windows update.
- Save your work, unplug accessories you connected recently, such as a new dock or USB device, and restart.
- Check for updates: press
Windows + Iand select Windows Update > Check for updates.
Install Windows and driver updates
Updates replace buggy drivers and system files, and Microsoft fixed one cause of this exact stop code in a June 2026 update (KB5094126).
- Press
Windows + Iand select Windows Update > Advanced options. - Turn on Receive updates for other Microsoft products.
- Select Optional updates, check any driver updates, and select Download and install.
- Go back to Windows Update, select Check for updates and install everything offered.
- Save your work and restart the PC, even if Windows doesn’t ask you to.
Update or roll back the driver named in the error
When the blue screen names a file, often one ending in .sys, that driver is the prime suspect, and Microsoft’s advice is to update or remove it.
- Right-click Start and select Device Manager.
- Look for devices marked with an exclamation point, and for the device that matches the file name if you know it.
- Right-click the device and select Update driver > Search automatically for drivers. This needs administrator rights. At work, ask your IT team.
- If the crashes started after a driver update, right-click the device and select Properties > Driver > Roll Back Driver instead. This needs administrator rights. At work, ask your IT team.
- If you can’t tell which device the file belongs to, give the file name to IT.
- Get drivers only from Windows Update or your PC maker’s support site, never from driver download sites or “driver updater” tools.
Disconnect hardware you added recently
New hardware that isn’t compatible with your version of Windows can trigger this stop code.
- Save your work and shut down: select Start > Power > Shut down.
- Unplug anything added recently, such as a dock, USB device, external drive or adapter.
- Start the PC and use it normally.
- If the crashes stop, reconnect devices one at a time to find the culprit, then check its maker’s site for a Windows 11 driver.
Uninstall software you added just before the crashes
Some programs install their own drivers or services, and Microsoft recommends removing any that were added recently.
- Select Start > Settings > Apps > Installed apps.
- Find the program you installed shortly before the crashes started.
- Select More (the three dots) > Uninstall, then restart. This needs administrator rights. At work, ask your IT team.
- Don’t remove antivirus, VPN or other security software your company installed. If one of those is the suspect, tell IT.
Remove a recent Windows update
If the crashes began right after a Windows update and newer updates don’t help, removing that update can stop them.
- Ask IT first. Security updates protect your PC, and some updates can’t be removed.
- Press
Windows + Iand select Windows Update > Update history. - Under Related settings, select Uninstall updates.
- Save your work. Select the update you want to remove, then select Uninstall. This needs administrator rights. At work, ask your IT team.
Start in safe mode if Windows keeps crashing
Safe mode starts Windows with only a basic set of drivers, which usually keeps a faulty driver from loading while you remove it.
- If the PC asks for a BitLocker recovery key at any point, stop and call IT.
- If Windows starts, save your work, go to Settings > System > Recovery and select Restart now next to Advanced startup.
- If Windows won’t start, turn the PC on and hold the power button to shut it down as soon as the Windows logo appears. Do this twice. On the third start, select Advanced options on the Automatic Repair screen.
- Select Troubleshoot > Advanced options > Startup Settings > Restart.
- When the list of options appears, press
4orF4for Safe Mode. - In safe mode, roll back or uninstall the suspect driver or program as described above, then restart normally.
Test your PC’s memory
Memory problems can also cause this stop code, and Windows includes a memory test.
- Save your work and close your apps.
- Press
Windows + R, typemdschedand select OK. This needs administrator rights. At work, ask your IT team. - Select Restart now and check for problems (recommended). The test runs before Windows starts and takes a while.
- After you sign back in, a notification shows the result. If you miss it, IT can find it in Event Viewer.
- If the test finds errors, stop and call IT. Failing memory is a hardware repair.
Why does this happen?
- A driver is faulty, outdated or not built for your version of Windows. Microsoft’s own crash analysis traces most stop errors to third-party drivers.
- A program or system service installed its own driver.
- New hardware isn’t compatible with Windows 11.
- The PC’s BIOS is out of date or incompatible. Updating it is a job for IT.
- Memory problems, such as a failing memory module.
- A Windows update. In June 2026, Microsoft fixed a case where an earlier update could cause this stop code on some devices during restarts, virtual machine use or gaming.
When should you call IT?
- The crashes keep coming back after updates, or Windows crashes during startup.
- The PC asks for a BitLocker recovery key.
- The file under “What failed” belongs to security software, a VPN or another tool your company installed.
- The memory test finds errors, or memory or other internal hardware was added recently.
- Several PCs show the same stop code.
- Files you need aren’t backed up.
If a crash has left files you can’t reach, read about our data recovery services.
OAC Technology’s IT support team fixes problems like this for businesses across the Twin Cities. Clients can call 952-548-5558, Monday to Friday, 8 a.m. to 6 p.m. Central. Not a client yet? Call the same number or send us a message.
Common questions
What does KMODE exception not handled mean?
It means a program running in Windows’ kernel mode, usually a driver, caused an error that its error handler didn’t catch. Windows stops with a blue screen to protect your files and settings from damage.
How serious is KMODE_EXCEPTION_NOT_HANDLED?
A single crash that doesn’t come back usually needs no further action, Microsoft says. Repeated crashes need fixing, because each one loses unsaved work and can point to a failing driver or hardware.
What does 0x1E mean on a blue screen?
0x1E, written in full as 0x0000001E, is the numeric code for KMODE_EXCEPTION_NOT_HANDLED. Both names mean the same error, so the same fixes apply.
Can a Windows update cause KMODE_EXCEPTION_NOT_HANDLED?
Yes. In June 2026, Microsoft fixed an issue where an earlier update could cause this stop code during restarts, virtual machine use or some games (KB5094126). Installing the latest updates is the fix.
How do I fix SYSTEM_THREAD_EXCEPTION_NOT_HANDLED?
Use the same steps. It’s a related stop code (0x7E) where a system thread hit an error nothing caught, and Microsoft’s advice is again to update or remove the driver named on the screen.









