Windows BSOD Error 0x0000008E — KERNEL_MODE_EXCEPTION_NOT_HANDLED Fix

What Does This Error Mean?

Error 0x0000008E means a program running in kernel mode — the most protected area of Windows — caused an exception that nothing was able to catch and handle. An exception is like an alarm triggered by an unexpected or illegal operation. Normally exceptions are caught and dealt with gracefully. But when one happens deep inside the kernel with no handler to catch it, Windows must crash. This is almost always caused by a faulty driver, bad RAM, or hardware failure.

Affected Models

Windows 10
Windows 11
Windows 8.1
Windows 7
Windows Server

Common Causes

A third-party hardware driver is performing an illegal operation inside the kernel
Defective RAM is causing random memory errors that manifest as unhandled exceptions
The system is overclocked and producing instability that causes kernel-level crashes
Malware that operates at the kernel level (a rootkit) is corrupting kernel operations
A failing hard drive or SSD is causing data corruption in kernel memory pages

How to Fix It

Run Windows Memory Diagnostic to test RAM. Search for it in the Start menu, run it, and restart. Let the full test complete and review the results when Windows reboots.

Faulty RAM is the single most common hardware cause of this specific error. Test RAM before anything else.
Identify the failing driver from the crash dump. The blue screen usually names a .sys file. Note that file name. Open Device Manager and look for a driver with that name. Update or uninstall it.

The file name shown on the blue screen (like nvlddmkm.sys for NVIDIA or iastora.sys for Intel storage) tells you exactly which driver caused the crash.
Boot into Safe Mode and check for malware. Access Safe Mode from the Windows Recovery Environment. Run a full scan with Windows Defender or Malwarebytes.

Rootkits and kernel-level malware can cause this exact error. Scanning in Safe Mode catches threats that hide themselves during normal operation.
Reset overclocking settings if applicable. Enter BIOS/UEFI and choose 'Load Optimized Defaults' to return the CPU, RAM, and bus speeds to their factory settings.

Even modest overclocks can cause kernel exceptions under sustained load. Confirm stability at stock speeds before re-enabling overclocking.
Run a full disk health check. Download CrystalDiskInfo (free) and check the SMART data for your drive. Look for any status other than 'Good.' Also run: chkdsk C: /f /r from an Administrator Command Prompt.

A failing drive can corrupt kernel data in ways that look exactly like a driver bug. Check drive health before spending time on driver fixes.

When to Call a Professional

If RAM tests confirm faulty memory, the RAM sticks must be physically replaced — there is no software fix for hardware memory errors. If a rootkit is suspected, professional malware removal is recommended before reinstalling drivers.

Frequently Asked Questions

What is the difference between 0x0000008E and 0x0000001E?

Both errors involve unhandled kernel exceptions. Error 0x0000001E (KMODE_EXCEPTION_NOT_HANDLED) is triggered when an exception occurs and there is no handler registered for that exception type. 0x0000008E is triggered by a specific class of exception — a STATUS_ACCESS_VIOLATION — meaning kernel code tried to access memory it was not allowed to access. Both have similar causes and the same general fixes.

The crash mentions a file called win32k.sys. What is that?

Win32k.sys is the kernel component that manages the Windows graphical interface — windows, menus, mouse input, and drawing. If Win32k.sys is named in the crash, a graphics driver or display-related component is the likely cause. Try uninstalling and reinstalling your GPU drivers as a first step.

This only happens when I play games or use demanding apps. Why?

High load pushes hardware closer to its limits and exposes instability that idle operation never triggers. Faulty RAM that passes light use may fail under the sustained stress of a game. Overclocked components are especially vulnerable. Run Memtest86+ for a full overnight memory test to detect intermittent RAM errors that the Windows diagnostic might miss.