How to Fix ‘Kmode Exception Not Handled’ (Error 0x0000001E) in Windows 11

Experiencing sudden system crashes in Windows 11 where the screen turns blue displaying the stop code: “Your device ran into a problem and needs to restart. Stop code: KMODE_EXCEPTION_NOT_HANDLED”, often citing a specific driver file like ndis.sys, nvlddmkm.sys, or storport.sys, halts work or gaming sessions. In the Windows operating system architecture, the processor operates in two primary modes: user mode (where standard applications run) and kernel mode (where core OS code and hardware drivers execute with unrestricted hardware access). Bug check 0x0000001E occurs when a kernel-mode program or device driver raises an illegal software exception—such as an access violation or null pointer dereference—that the kernel’s default exception handler fails to catch. This troubleshooting guide provides systematic methods to identify the offending driver, resolve memory corruption, and restore stability in Windows 11.

Primary Triggers Behind Bug Check 0x0000001E

Because kernel mode code executes at the lowest system level, unhandled exceptions typically indicate driver bugs or physical hardware faults:

  • Faulty or Incompatible Device Drivers: Graphics, network (Wi-Fi/Ethernet), or audio drivers attempting to execute invalid memory instructions.
  • Physical Memory (RAM) Degradation: Damaged RAM modules or unstable memory overclocks (XMP/EXPO) flipping bits in kernel memory space.
  • Corrupted Windows Fast Startup State: The Windows hibernation file (hiberfil.sys) loading a corrupted kernel driver state upon boot.
  • Outdated Motherboard BIOS/UEFI Firmware: Processor microcode incompatibilities with modern Windows 11 hardware scheduling architectures.
  • Third-Party Antivirus Filter Drivers: Antivirus software injecting kernel drivers that conflict with Windows memory isolation features.

Method 1: Identify the Failing Driver from the Blue Screen or Dump File

Pinpointing the exact driver file cited in the crash avoids guessing which hardware component failed.

  1. If the blue screen cited a specific filename in parentheses (e.g. KMODE_EXCEPTION_NOT_HANDLED (netwtw10.sys)):
    • nvlddmkm.sys / amdkmdag.sys: NVIDIA or AMD Graphics Driver.
    • ndis.sys / netwtw10.sys / rtwlanu.sys: Network or Wi-Fi adapter driver.
    • storport.sys / storahci.sys: Storage controller driver.
  2. If no driver was named, download and run BlueScreenView or open the memory dump (C:\Windows\Minidump) using WinDbg to locate the crashing module.
  3. Once identified, boot Windows, right-click the Start menu, open Device Manager, and update or reinstall that specific driver.

Method 2: Test RAM for Physical Memory Errors

Physical memory defects are the leading cause of random kernel mode access violations.

  1. Press Windows Key + R, type mdsched.exe, and press Enter.
  2. Select Restart now and check for problems (recommended).
  3. Your PC will restart into the blue Windows Memory Diagnostic environment and begin testing.
  4. Press F1, select the Extended test mix, and press F10 to execute a deep diagnostic scan.
  5. If errors are reported, defective RAM modules must be replaced or XMP/EXPO memory profiles disabled in your BIOS.

Method 3: Disable Windows Fast Startup

Disabling Fast Startup ensures Windows initializes a completely pristine kernel and driver state on every boot.

  1. Press Windows Key + R, type powercfg.cpl, and press Enter.
  2. Click Choose what the power buttons do in the left sidebar.
  3. Click Change settings that are currently unavailable.
  4. Uncheck Turn on fast startup (recommended) at the bottom.
  5. Click Save changes and reboot your PC.

Method 4: Run SFC and DISM System Repairs

Repairing corrupted Windows system files ensures that system-level kernel modules are verified against clean Microsoft repository hashes.

  1. Open an administrative Command Prompt (Windows Key, type cmd, right-click, select Run as administrator).
  2. Execute:
    DISM /Online /Cleanup-Image /RestoreHealth
  3. Once complete, execute:
    sfc /scannow
  4. Restart Windows 11 upon completion.

Get the best tech tips delivered straight to your inbox.

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