Skip to main content

KMODE_EXCEPTION_NOT_HANDLED: what causes it, and how to fix it on Windows 11 and 10

Short answer

KMODE_EXCEPTION_NOT_HANDLED (0x1E) means a driver or other kernel code hit an error nothing caught. A faulty driver is the usual cause. A May 2026 Windows update also caused it until KB5094126 fixed it, so check your build first, then read the crash dump to find the driver and update or roll it back.

On this page

KMODE_EXCEPTION_NOT_HANDLED (stop code 0x1E) means a driver or other code running inside the Windows kernel hit an error that nothing caught, so Windows stopped the PC to protect your data. A faulty driver is the usual cause, followed by RAM, storage and BIOS problems. In May and June 2026 a Windows update caused it on some PCs until Microsoft fixed it in KB5094126. Fix it in this order: check your Windows build, get into Safe Mode if it loops, read the crash dump to find the driver, then update or roll back that driver.

How we put this together: this guide is research, not a test. We didn’t crash a PC to write it. It’s built from Microsoft’s bug check reference and update notes, Dell’s support note on the 2026 update, and real crash threads on Microsoft Q&A and Tom’s Hardware, all listed under Sources. Steps apply to Windows 11 (24H2, 25H2 and 26H2) and Windows 10.

What does KMODE_EXCEPTION_NOT_HANDLED mean?

Microsoft’s reference describes it as “a kernel-mode program generated an exception that the error handler didn’t catch.” In plain words, something with deep access to Windows, almost always a driver, did something illegal, such as reading memory it had no right to. Microsoft estimates drivers cause about three quarters of all stop errors.

The first number in the crash details tells you what kind of mistake it was:

First parameterWhat it means
0xC0000005Access violation: code touched memory it shouldn’t
0x80000003A breakpoint was hit with no debugger attached
0x80000002Misaligned data
0xC0000006Windows couldn’t read a page from disk. In one Microsoft Q&A case an advisor read this as a disk or RAM fault, not a driver

Was it the May 2026 Windows update?

It might be, if the crashes started in late May or June 2026. Microsoft’s notes for update KB5094126, released on 9 June 2026, list a fix for KMODE_EXCEPTION_NOT_HANDLED and HYPERVISOR_ERROR stop errors that appeared after the May preview update KB5089573. Microsoft says they could happen during restarts, while running virtual machines or in some games. Dell published its own note for affected Alienware and Dell Tower Plus models.

Press Windows+R, type winver and press Enter. If your build is 26100.8655 or 26200.8655 or newer, you already have the fix, and your crash has another cause. If it’s older, install the latest update first.

One more version note: Windows 11 24H2 Home and Pro stopped getting updates on 13 October 2026, so move up to 25H2 or 26H2 to keep receiving fixes.

What causes it?

Here are the causes, most likely first, going by Microsoft’s guidance and real crash reports:

  1. A faulty third-party driver. Graphics, Wi-Fi and Bluetooth, network filters, VPNs, anti-cheat and storage drivers all run in the kernel. In one Tom’s Hardware thread the culprit turned out to be a MediaTek Bluetooth filter driver, after the owner had already uninstalled a game’s anti-cheat.
  2. A Windows update. Confirmed for KB5089573 in 2026, as above.
  3. Unstable RAM, including memory running a fast XMP, DOCP or EXPO profile.
  4. Disk errors, when the first parameter is 0xC0000006.
  5. Old BIOS or unstable CPU settings. Microsoft lists BIOS incompatibility as a cause. Owners of Intel Core 13th and 14th Gen desktop chips should run current BIOS microcode, as Intel advised after its 2024 instability findings.

How to fix KMODE_EXCEPTION_NOT_HANDLED, step by step

1. Write down what the screen says

Take a photo of the crash screen, including any file name it shows, such as a .sys driver. On Windows 11 24H2 and later the crash screen is black, not blue. Also note when it happens: right after boot, only in one game, or after sleep. That pattern decides which step below matters most.

2. Undo whatever changed

Microsoft’s first step is to remove any hardware you added recently. Do the same for a new driver, app or BIOS update. If the crashes started the day you installed something, roll that back before trying anything else.

3. If the PC keeps crashing, start in Safe Mode

If Windows crashes before you can do anything, interrupt startup three times in a row to reach the recovery screen. Choose Troubleshoot, Advanced options, Startup Settings, Restart, then press 4 for Safe Mode or 5 for Safe Mode with Networking. From the same Advanced options screen, Uninstall Updates removes the latest quality update, which is the quick way out of the 2026 bug.

If Safe Mode is stable, a third-party driver or service is the likely cause, because Safe Mode loads only the basics. If Safe Mode crashes too, go straight to step 8 and test the hardware.

4. Make sure Windows saves a crash dump

The dump file is what names the driver, so check Windows is writing one. Open System Properties (search for “View advanced system settings”), go to Startup and Recovery, Settings, and make sure Windows is set to write a small or automatic memory dump. Small dumps land in C:\Windows\Minidump. They need a page file of at least 2 MB on the system drive.

5. Read the dump to find the driver

Install Microsoft’s free WinDbg debugger, point it at Microsoft’s symbol server, then open the newest file from the Minidump folder with File, Open Crash Dump. In a Command Prompt:

winget install Microsoft.WinDbg

Then, inside WinDbg, set symbols and run the analysis:

.symfix C:\Symbols
.reload
!analyze -v

Look at the first argument (see the table above), IMAGE_NAME and the stack. If a third-party driver shows up, check its version and date with lmvm drivername. A dump that names ntoskrnl.exe doesn’t mean Windows itself is broken. Read further down the stack for the third-party driver that was running.

Don’t trust a single dump. Even Microsoft’s own engineers have shown !analyze blaming the wrong module, so look for the same driver in two or more dumps. NirSoft’s BlueScreenView gives a quicker first look, but its own page says its driver detection isn’t fully accurate and lists support only up to Windows 10, so treat it as a hint.

6. Update or roll back the driver it names

Get the driver from your PC maker, motherboard maker or the device maker’s own site. Don’t use a “driver updater” app. In Device Manager, a device with a yellow “!” can be updated, rolled back or disabled from its right-click menu. If you disable a suspect and the crashes carry on, it wasn’t the cause: move on rather than chasing it.

7. Repair system files

Damaged system files rarely cause a 0x1E, but the check is cheap. Microsoft’s order is DISM first, then SFC, from an administrator Command Prompt:

DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow

The details go to C:\Windows\Logs\CBS\CBS.log. One clean pass is enough.

8. Test your RAM and drive

Run Windows Memory Diagnostic (press Windows+R, type mdsched.exe) for a quick pass. For a proper test, boot PassMark’s MemTest86, which runs 4 passes by default. Turn off XMP, DOCP or EXPO in the BIOS first and test at default speed. For the disk, run chkdsk c: /f /r from an administrator prompt and check the drive’s health in its maker’s tool.

An error means replace the part. A clean result doesn’t clear it, though: one Tom’s Hardware user passed eight MemTest86 passes and the fault was still a driver.

9. Update the BIOS and chipset drivers

Get both from your PC or motherboard maker. On an Intel Core 13th or 14th Gen desktop, Intel says to use a BIOS with microcode 0x12B or newer and the Intel Default Settings profile.

10. Run Driver Verifier to catch the driver in the act

Driver Verifier stresses drivers until a bad one breaks the rules and crashes the PC on purpose, naming itself in the dump. Microsoft warns it can crash the computer, so make a restore point first. In an administrator Command Prompt, run verifier, choose “Create standard settings”, then “Select driver names from a list”, tick only the non-Microsoft drivers, and restart.

Use the PC until it crashes two or three times, then read the new dumps as in step 5. Verifier crashes usually show stop code 0xC4. Switch it off afterwards:

verifier /reset

If Windows won’t start with Verifier on, boot into Safe Mode (step 3) and run the reset there.

11. Last resort: repair-install Windows

Try System Restore first. Then do an in-place repair install from the Windows 11 ISO, choosing to keep your files and apps. Only wipe and reinstall once the hardware tests have passed. In one Microsoft Q&A thread a clean install did fix it, while in another it didn’t, which pointed to hardware.

Still on Windows 10?

The steps above work the same, but Windows 10’s free support ended on 14 October 2025. Paid Extended Security Updates, which run to 12 October 2027, bring only security fixes. If a Windows bug causes your crash, no fix is coming, so drivers, the BIOS and hardware are where you’ll solve it.

What to skip

Skip paid “PC repair” and “boot repair” suites, and driver-updater apps. They can’t read your dump, and they install drivers from sources you can’t check. Skip registry cleaners too: none of the Microsoft guidance or crash threads behind this guide fixes a 0x1E that way.

Frequently asked questions

Is KMODE_EXCEPTION_NOT_HANDLED a hardware or software problem?

Usually software: a driver. Microsoft also lists BIOS and memory problems, and only the crash dump tells you which one you have.

Can a Windows update cause it?

Yes. Microsoft confirmed that the May 2026 update KB5089573 caused it on some PCs, and fixed it in KB5094126 on 9 June 2026.

Why is my crash screen black, not blue?

Windows 11 version 24H2 and later show stop errors on a black screen. The stop code means the same thing.

My RAM passed MemTest86. Is it fine?

Probably, but not certainly. PassMark says intermittent faults can need longer runs, and a clean memory test doesn’t rule out a driver.

Do I need to reinstall Windows?

Rarely, and never first. Microsoft’s order is hardware, Safe Mode, drivers and updates, then restore options.

What to do now

Run winver and check your build against 26100.8655. Then open C:\Windows\Minidump and see whether there’s a dump from your last crash. If there is, step 5 is where you’ll most likely find the driver.

Related guides

Sources

Changelog

24 Oct 2026: rewritten from Microsoft’s documentation, the 2026 update notes and recent crash reports. It replaces a guide first published on 23 February 2018 that covered Windows 10 only.