How to Fix ‘KMODE_EXCEPTION_NOT_HANDLED’ (0x0000001E) in Windows 11

A sudden blue screen crash displaying the stop code: ‘KMODE_EXCEPTION_NOT_HANDLED’ or bug check code 0x0000001E is a serious kernel-mode halt in Windows 11. In Windows NT operating system architecture, kernel-mode programs (including core system processes and third-party hardware device drivers) execute with unrestricted access to memory and physical hardware. When a kernel routine generates an unexpected software exception—such as an illegal memory access (0xC0000005) or divide-by-zero—that the kernel error handler cannot intercept or recover from, Windows halts immediately to prevent corruption of the operating system.

What Causes KMODE_EXCEPTION_NOT_HANDLED in Windows 11?

Bug check 0x0000001E indicates an unhandled error inside kernel-mode space. Common causes include:

  • Faulty or Incompatible Device Drivers: Recently installed graphics, audio, or network drivers overwriting restricted memory spaces.
  • Corrupted Windows Fast Startup State: The Windows 11 hybrid hibernation file (hiberfil.sys) loading corrupted kernel drivers into memory upon startup.
  • Defective Hardware RAM Modules: Physical memory bit-flips corrupting kernel execution pointers.
  • Corrupted Windows System Files: Damaged system dynamic link libraries or missing kernel binaries.
  • Outdated Motherboard BIOS / Chipset Drivers: Incompatible CPU power state transitions causing driver instruction faults.

Step 1: Check the BSOD for Driver Filenames

Windows often lists the offending .sys file directly on the blue screen.

  1. Look for text such as What failed: ndis.sys (network), nvlddmkm.sys (NVIDIA graphics), or epfwwfp.sys (antivirus firewall).
  2. If no file is shown, open Event Viewer (press Win + X > Event Viewer).
  3. Navigate to Windows Logs > System and inspect the details of the latest BugCheck (Event ID 1001) entry.
  4. Parameter 1 displays the exception code: 0xC0000005 indicates an illegal memory access violation.

Step 2: Disable Fast Startup

Windows Fast Startup writes the kernel session to disk upon shutdown, which can reload corrupted driver states into RAM during boot.

  1. Press Win + R, type powercfg.cpl, and press Enter to open Power Options.
  2. In the left sidebar, click Choose what the power buttons do.
  3. Click Change settings that are currently unavailable (requires administrative rights).
  4. Under Shutdown settings, uncheck Turn on fast startup (recommended).
  5. Click Save changes and restart your PC.

Step 3: Update or Roll Back Problematic Drivers in Device Manager

Restoring stable WHQL drivers resolves invalid memory addressing.

  1. Press Win + X and open Device Manager.
  2. If a specific driver was cited, expand that category (e.g. Display adapters or Network adapters).
  3. Right-click the device and select Properties > Driver.
  4. If the blue screen began after a recent driver update, click Roll Back Driver.
  5. Otherwise, download and install the latest certified WHQL driver directly from the hardware vendor’s website.

Step 4: Test Hardware Memory with Windows Memory Diagnostic

Failing RAM sticks generate unpredictable kernel exceptions.

  1. Press Win + R, type mdsched.exe, and press Enter.
  2. Choose Restart now and check for problems (recommended).
  3. Allow the test passes to run completely. If errors appear, test individual RAM sticks separately to identify the defective module.

Step 5: Run DISM and SFC Kernel Integrity Scans

Repairing corrupted Windows system files ensures core kernel binaries are authentic.

  1. Open Command Prompt (Admin).
  2. Execute:
    DISM /Online /Cleanup-Image /RestoreHealth
    sfc /scannow
  3. Wait for the verification to reach 100% and confirm corrupted files were replaced.
  4. Reboot your computer.

Disabling Fast Startup, rolling back unstable device drivers, running memory diagnostics, and executing DISM repairs resolves KMODE_EXCEPTION_NOT_HANDLED crashes in Windows 11.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.