How to Fix KMODE_EXCEPTION_NOT_HANDLED BSOD (0x1E)
What KMODE_EXCEPTION_NOT_HANDLED (0x1E) means
Windows runs its core code — and the drivers for your graphics card, network card, storage, and antivirus — in kernel mode, a trusted zone where software talks directly to hardware and shares memory freely. KMODE_EXCEPTION_NOT_HANDLED means a kernel-mode program generated an error that Windows' own error handlers did not catch. Since kernel-mode code can corrupt anything it touches, Windows has no safe way to keep going, so it halts everything and gives you the blue screen with stop code 0x1E.
The name itself is the diagnosis: the unhandled exception happened in kernel mode, and the only software allowed in kernel mode is drivers (plus the Windows kernel itself). That is why this error almost always comes down to a driver that is buggy, outdated, or conflicting with another driver. The good news is that it is usually very fixable: find the failing driver, update it or roll it back, and the crashes stop. Work through the steps below in order — they move from the fastest, most likely fix toward the deeper system repairs.
Common causes
- Buggy or outdated device driver: the number one cause. Graphics, network, storage, and audio drivers run in the kernel, and a bad release crashes the whole system. The blue screen often names the file, such as nvlddmkm.sys or igdkmd64.sys.
- Driver conflicts between security and system software: third-party antivirus and firewall tools install their own kernel drivers. When two such drivers fight over the same system hooks, one of them throws an exception Windows cannot handle.
- Faulty or mismatched RAM: corrupt memory scrambles the data a driver passes to the kernel. If each blue screen names a different driver, bad RAM — or an unstable XMP memory profile — is the likely real cause.
- Corrupt system or driver files: a damaged disk, a failed update, or a bad shutdown can leave the Windows image or driver files half-written, so drivers that used to work start crashing.
- Unstable overclocking: pushing the CPU, GPU, or memory past stable limits corrupts the data drivers move around in kernel memory, turning an overclock into a blue screen.
How to fix KMODE_EXCEPTION_NOT_HANDLED (0x1E) — step by step
Work through these fixes in order. The majority of 0x1E crashes are resolved by steps 1 through 3.
- Identify the driver that caused the crash The blue screen usually names the culprit: look for a file name in parentheses after KMODE_EXCEPTION_NOT_HANDLED, such as ntoskrnl.exe, igdkmd64.sys, or nvlddmkm.sys. For a deeper look, download the free tool BlueScreenView or WhoCrashed, which reads your crash dump files in C:\Windows\Minidump and highlights the driver in red. If the same file name appears in two or more dumps, you have found your prime suspect. Knowing the exact driver turns a vague blue screen into a targeted fix and saves you from reinstalling things that were never broken.
- Update the failing driver from the manufacturer's site Once you know the driver name, update it — but skip the generic Windows update and go to the source. For a graphics driver, download the latest release from NVIDIA, AMD, or Intel directly; for a network or storage driver, visit your laptop or motherboard manufacturer's support page and get the driver for your exact model. Right-click the device in Device Manager, choose Update driver, then Browse my computer for drivers and point it at the downloaded package, or run the manufacturer's installer. Fresh manufacturer drivers fix the overwhelming majority of 0x1E crashes, because the error almost always starts with a buggy driver version. Restart when the installer asks and watch whether the blue screen comes back.
- Roll back or uninstall a recent driver update If the crashes started right after a driver update, the new driver is the likely culprit. Open Device Manager, right-click the device you suspect — very often the display adapter or network adapter — and choose Properties, then go to the Driver tab and click Roll Back Driver. If that button is greyed out, uninstall the driver instead: right-click the device, choose Uninstall device, tick Delete the driver software for this device if the option appears, and restart. Windows will fall back to an older or built-in driver. Then use the manufacturer's site to install the last version that worked for you, and pause automatic driver updates for that device until a fixed release arrives.
- Remove conflicting antivirus and run a clean boot Third-party antivirus and security tools run their own kernel drivers, and those drivers are a classic source of KMODE_EXCEPTION_NOT_HANDLED. If you run anything beyond Windows Defender — Norton, McAfee, Avast, AVG, or similar — download the vendor's official removal tool and uninstall it completely, because normal uninstall often leaves kernel drivers behind. Then test with a clean boot to rule out other background software: press Windows key plus R, type msconfig, open the Services tab, tick Hide all Microsoft services, click Disable all, then restart. If the blue screen stops, re-enable services in small groups until the crashes return, and you will have found the conflicting program.
- Test your RAM and check the disk Bad memory can corrupt the data a driver passes to the kernel and trigger 0x1E, especially if the crashes mention random driver names each time. Press Windows key plus R, type mdsched.exe, and press Enter to open Windows Memory Diagnostic, then choose Restart now and check for problems and let the full scan finish — it takes twenty minutes or more. If it reports hardware errors, power off, open the case, and reseat each RAM stick; if errors persist, test one stick at a time to isolate the bad module. While you are at it, check the disk: open Command Prompt as administrator and run chkdsk /f /r, confirm the prompt to schedule it at next restart, and reboot. A failing disk can corrupt the very driver files that cause the crash.
- Repair system files and reset overclocking Finish with a system repair sweep. Open Command Prompt as administrator and run sfc /scannow to repair protected Windows files — this takes about fifteen minutes — then run DISM /Online /Cleanup-Image /RestoreHealth to fix the Windows image the scan draws from. Also undo any overclocking or undervolting on your CPU, GPU, or RAM: enter the BIOS and load optimized defaults, and turn off XMP or EXPO memory profiles, because unstable memory timings are a well-known trigger for kernel exceptions. If the blue screen survives all of this, back up your files and consider a clean Windows reinstall, which eliminates any corrupted driver stack the repair tools could not untangle.
Did this fix it? Quick checklist
- Your PC runs normally for a full day of use without blue-screening
- The previously failing driver is updated or rolled back to a stable version
- RAM passes a full Windows Memory Diagnostic run with no errors
- No third-party kernel-level software is installed beyond what you need
If the error persists after all six steps, the fault is almost certainly hardware-level: a failing RAM stick, a dying disk, or in rare cases a degrading CPU or motherboard. Back up your important files now, because repeated kernel crashes can corrupt data. Test RAM sticks one at a time, check your disk's health with the manufacturer's diagnostic tool, and if the machine is under warranty, contact the manufacturer with your notes on everything you already tried — that list will speed up the RMA process.
Frequently asked questions
What does KMODE_EXCEPTION_NOT_HANDLED mean?
It means a program running in kernel mode — the trusted core of Windows where drivers live — generated an exception that the system did not know how to handle. Drivers share the kernel's memory space, so one misbehaving driver can crash the entire operating system, and Windows shows this blue screen to stop things before data gets corrupted. The error name literally says the unhandled exception happened in kernel mode. Nine times out of ten the underlying cause is a faulty or outdated device driver, often for graphics, network, or storage hardware.
How do I find which driver caused the 0x1E blue screen?
Start with the blue screen itself: it usually shows a file name in parentheses right after KMODE_EXCEPTION_NOT_HANDLED, and that file is your first lead. For a definitive answer, use the free tool BlueScreenView or WhoCrashed to open the dump files in C:\Windows\Minidump — the tool highlights the faulting driver in red and shows its file name and description. If the same driver shows up in multiple dumps, that is your culprit. You can also search the file name online to learn exactly which hardware or software it belongs to before you update or remove it.
Can antivirus software cause KMODE_EXCEPTION_NOT_HANDLED?
Yes — third-party antivirus is one of the most common triggers. Security programs install kernel-level drivers to monitor files and network traffic in real time, and those drivers sit in exactly the place where a KMODE_EXCEPTION_NOT_HANDLED begins. If the crashes started after installing or updating a security suite, uninstall it using the vendor's official removal tool — a normal uninstall often leaves kernel drivers behind — and test for a few days with Windows Defender alone. If the blue screen stops, the antivirus driver was the cause; check the vendor's support site for a fixed version before reinstalling.
Is KMODE_EXCEPTION_NOT_HANDLED a hardware problem?
Sometimes, but drivers are the cause far more often than hardware. Bad RAM is the most common hardware suspect: if each crash names a different driver, memory corruption is likely and a Windows Memory Diagnostic run is the right next step. A failing disk can also corrupt driver files and produce this error. If you have updated drivers, removed conflicting software, tested RAM, and checked the disk, and the crashes continue — especially at stock clock speeds — then deeper hardware trouble such as a failing CPU or motherboard becomes more likely, and a clean Windows reinstall is the final way to separate software from hardware.
Can a Windows update fix KMODE_EXCEPTION_NOT_HANDLED?
It can, but do not rely on it as the first fix. Windows Update sometimes delivers newer drivers that replace the buggy version behind the crashes, and cumulative updates occasionally patch kernel behavior that contributes to the problem. Check Settings, then Windows Update, then Advanced options and Optional updates, where driver updates often wait. If nothing new appears, go to the hardware manufacturer's own support page — they almost always have fresher drivers than Microsoft's catalog. And remember the reverse case: if the blue screens began right after a Windows update, roll back the suspect driver in Device Manager, because the update itself may have introduced the broken one.