Home / Error Lookup / 0X0000008E

0X0000008E

Blue Screen (BSOD) KERNEL_MODE_EXCEPTION_NOT_HANDLED Applies to: Windows 7, Windows 10, Windows 11

What it means

Similar to KMODE_EXCEPTION_NOT_HANDLED — a kernel-level error a driver couldn't recover from.

Also seen as: KERNEL_MODE_EXCEPTION_NOT_HANDLED, 0x8E

Quick fix steps

  1. Check Reliability Monitor for what was active during the crash.
  2. Update or roll back the most recently changed driver.
  3. Run Windows Memory Diagnostic if crashes seem random rather than app-specific.
For the full step-by-step walkthrough, see How to Read and Respond to Any Blue Screen.

Frequently Asked Questions

Is KERNEL_MODE_EXCEPTION_NOT_HANDLED serious?
It's a genuine system-level crash, but like most driver-related stop codes, it's usually fixable through driver updates and standard diagnostics rather than indicating permanent hardware damage.
Should I suspect a specific type of hardware first?
Graphics and network drivers are common culprits across this whole family of stop codes, so checking those first is a reasonable starting point before broader troubleshooting.

Other error codes

0X0000001A — MEMORY_MANAGEMENT

Points to a problem with how memory is being handled — faulty RAM, a driver mismanaging memory, or disk corruption.

0X0000000A — IRQL_NOT_LESS_OR_EQUAL

Almost always a driver issue — most commonly network, audio, or graphics drivers.

0X000000EF — CRITICAL_PROCESS_DIED

A core Windows process crashed unexpectedly — often tied to a recent update or corrupted system files.

0X0000001E — KMODE_EXCEPTION_NOT_HANDLED

A driver running in kernel mode hit an error it couldn't recover from — usually a specific faulty or outdated driver.