ErrorBase
Independent technical referenceOfficial site
  • Software and digital services
  • Operating system

KMODE_EXCEPTION_NOT_HANDLED

KMODE_EXCEPTION_NOT_HANDLED (0x1E) on Windows: a kernel-mode exception was not handled

Verified with sources3 sourcesReviewed Oct 3, 2026
Technician coming? See the 2 steps they must show you

Risk level

Medium

Proceed carefully and stop if the check is unclear.

Urgency

High

Quick answer

A Windows kernel program, usually a driver, raised an error that nothing caught. If the screen names a driver, disable or update it; if you just added one, remove it first.

Safety first

Stop and check this first

  • A 0x1E alone does not prove the memory is faulty: faulty drivers produce the same stop. Ask for the scanner result before agreeing to replace modules.

Safe checks you can perform

  • Named driver and recent changes
  • Safe Mode to disable the driver
  • System log

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Read the exception and address from the dump
  • Do not attempt this professional task: Hardware and BIOS diagnostics

What a technician must be able to justify

Technician visit

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Read the exception and address from the dump

    What they doIT support opens the dump in WinDbg, identifies the exception code in parameter 1 and the address in parameter 2 and, if needed, rebuilds the stack with .exr, .cxr and kb.

    They must show youthe exception code and the module tied to the address.

    In writingwhich driver was identified and what was done with it.

  2. Hardware and BIOS diagnostics

    What they doThey run the system maker's diagnostics, especially the memory scanner, and check for a newer BIOS version.

    They must show youthe memory scanner report and the BIOS version before and after.

    In writingtest results and, if a module is replaced, its reference and reason.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Follow these steps

Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. Named driver and recent changes

    No special tools

    Who:
    you.
    How:
    photograph the blue screen, look for a .sys file and list the drivers or services you installed in recent days.
    Result that matters:
    whether a driver is named or something was recently added.
    If so:
    disable or uninstall it and check whether the error stops.
    If not:
    continue with the System log and memory diagnostics.
    Evidence to keep:
    photo of the code and dated list of added drivers.

    Evidence: Bug Check 0x1E KMODE_EXCEPTION_NOT_HANDLED · Stop code error or bug check troubleshooting (IT professionals)

  2. Safe Mode to disable the driver

    No special tools

    Who:
    you.
    How:
    if the error appears at startup, go to Settings, Recovery, Advanced startup, Restart now, Troubleshoot, Advanced options, Startup Settings, Restart and press 4 or F4; in Device Manager disable the suspect driver.
    Result that matters:
    whether Windows starts in Safe Mode and then normally without that driver.
    If it does:
    the disabled driver was the source; look for a fixed version.
    If it will not start even in Safe Mode:
    hand the case to IT support.
    Evidence to keep:
    name of the disabled driver and the startup result.

    Evidence: Bug Check 0x1E KMODE_EXCEPTION_NOT_HANDLED · Stop code error or bug check troubleshooting (IT professionals)

  3. System log

    No special tools

    Who:
    you.
    How:
    in Event Viewer open Windows Logs, System, and look for device or driver errors at the time of the crash.
    Result that matters:
    whether a specific device shows up.
    If it does:
    it strengthens the case against that driver.
    If not:
    the memory dump will be the source to identify it.
    Evidence to keep:
    screenshot of the event.

    Evidence: Bug Check 0x1E KMODE_EXCEPTION_NOT_HANDLED

Still not solved

If the error persists, stop here. See what the technician must do and show you.

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and digital services
Brand
Microsoft Windows
Product type
Operating system

Known code variants

  • 0x0000001E
  • 0x1E
  • KMODE EXCEPTION NOT HANDLED
  • STOP 0x0000001E
  • stop code KMODE_EXCEPTION_NOT_HANDLED

What it means

Microsoft defines 0x0000001E as an exception raised by a kernel-mode program that the error handler did not catch. Parameter 1 gives the exception (for example 0xC0000005, a memory access violation) and parameter 2 the address where it happened, which usually points to the driver. The listed causes are a faulty driver or system service and hardware issues such as BIOS incompatibility, memory conflicts or IRQ conflicts. Without those parameters the code does not say which.

Warnings and stop conditions

  • Mediumeditorial warning

    A 0x1E alone does not prove the memory is faulty: faulty drivers produce the same stop. Ask for the scanner result before agreeing to replace modules.

    Evidence: Bug Check 0x1E KMODE_EXCEPTION_NOT_HANDLED

Symptoms and causes

Probable causes · in order

  • Faulty driver or serviceCommon

    Microsoft says to disable or remove any driver named in the message and any recently added. If the crashes stop once it is removed, it is confirmed.

    Evidence: Bug Check 0x1E KMODE_EXCEPTION_NOT_HANDLED · Stop code error or bug check troubleshooting (IT professionals)

  • BIOS incompatibilityPossible

    Suspected if the error appears after the first restart of Windows Setup or once Setup finishes; a newer BIOS resolves it.

    Evidence: Bug Check 0x1E KMODE_EXCEPTION_NOT_HANDLED

  • Memory or IRQ conflictsPossible

    Hardware issues that can also produce this code; the system maker's memory scanner helps separate them.

    Evidence: Bug Check 0x1E KMODE_EXCEPTION_NOT_HANDLED

Virtual technician

Does KMODE_EXCEPTION_NOT_HANDLED still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Start diagnosis

Sources and technical references

  1. 1

    Bug Check 0x1E KMODE_EXCEPTION_NOT_HANDLED

    Microsoft · 2026 · official_doc

  2. 2

    Stop code error or bug check troubleshooting (IT professionals)

    Microsoft · 2026 · official_doc

  3. 3

    Troubleshooting Windows unexpected restarts and stop code errors

    Microsoft · 2026 · official_doc

Sources: Bug Check 0x1E KMODE_EXCEPTION_NOT_HANDLED · Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errorsreviewed 2026-10-03 · verified

Was this entry useful?