Note the file shown under “What failed” (for example e1d68x64.sys = Intel network driver). Update or roll back that driver, uninstall recently added software (especially antivirus and VPNs), turn off Fast Startup, and run Windows Memory Diagnostic if no driver is named.

KMODE_EXCEPTION_NOT_HANDLED, explained

KMODE_EXCEPTION_NOT_HANDLED (bug check 0x1E) means code running in kernel mode raised an exception that no error handler caught. Kernel mode is where drivers live, so a buggy or incompatible driver is the cause in the large majority of cases.

The blue screen often names the faulting file under What failed. Network, graphics, storage, antivirus and VPN drivers are the most likely causes. If no file is named, faulty RAM or a damaged system file is more likely.

Signs of the problem

  • Blue screen: “Your PC ran into a problem… Stop code: KMODE_EXCEPTION_NOT_HANDLED”.
  • Sometimes a file is listed under “What failed”, such as a .sys driver.
  • Crashes after installing hardware, a driver, Windows update or security software.

Why KMODE_EXCEPTION_NOT_HANDLED happens

  • Outdated, corrupt or incompatible device driver (network, graphics, storage).
  • Antivirus, VPN or other software that installs kernel drivers.
  • Fast Startup restoring a bad driver state.
  • Faulty RAM or corrupted Windows system files.

Fixes to try, in order

  1. Identify the driverLook under What failed on the blue screen. To see which driver crashed, open C:\Windows\Minidump after the next restart and load the newest .dmp file in Microsoft's free WinDbg app (run !analyze -v), or use a dump viewer such as BlueScreenView. The “probably caused by” file names the driver to update or remove.
  2. Update or roll back that driverIn Device Manager, right-click the device → Properties → Driver. Use Roll Back Driver if it started after an update, or install the newest driver from the PC or component maker.
  3. Remove recent softwareUninstall recently added antivirus, VPN, overclocking or RGB utilities from Settings → Apps. If Windows won't stay up long enough, hold Shift while clicking Restart (or let it fail to boot three times) and choose Troubleshoot → Advanced options → Startup Settings → Restart → 4 for Safe Mode.
  4. Turn off Fast StartupControl Panel → Power Options → Choose what the power buttons do → Change settings that are currently unavailable, untick Turn on fast startup.
  5. Repair system filesRun the commands below.
  6. Test memoryRun Windows Memory Diagnostic (mdsched.exe) and choose restart now. Any error means a RAM stick needs replacing or reseating.

Command

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Run in an elevated Command Prompt (Run as administrator). DISM can take 10–20 minutes; run sfc after it finishes, then restart.

Check it's fixed: The PC runs normally for several days, including under the workload that used to trigger the crash, with no new files in C:\Windows\Minidump.

Prevent it from coming back

Install drivers from the PC or chip maker, avoid driver-updater utilities, and use one antivirus product.