How to Fix Windows Stop Code 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

Quick Answer

The Windows stop code 0x0000008E (KERNEL_MODE_EXCEPTION_NOT_HANDLED) indicates that Windows encountered an exception in kernel-mode code that it could not handle. Possible causes include faulty device drivers, incompatible hardware, memory problems, or other system-level faults. The stop code alone does not identify the exact cause.

To troubleshoot this error, check for recent hardware or driver changes, install applicable updates, examine Windows crash information, and run hardware diagnostics when indicated. If Windows repeatedly crashes, use Windows Recovery Environment (WinRE) to access available recovery options. For recurring errors, analyze the crash dump with WinDbg to help identify the underlying problem.

What Is KERNEL_MODE_EXCEPTION_NOT_HANDLED?

KERNEL_MODE_EXCEPTION_NOT_HANDLED is a Windows bug check, commonly called a Blue Screen of Death (BSOD). It occurs when an exception is raised while Windows is executing kernel-mode code and the exception cannot be handled successfully.

Kernel mode is a privileged execution environment used by the Windows kernel and many device drivers. An error in this environment can destabilize the operating system, causing Windows to stop and display a blue screen to prevent further uncontrolled execution.

Microsoft documents bug check 0x0000008E and the related 0x1000008E bug check, known as KERNEL_MODE_EXCEPTION_NOT_HANDLED_M, in its official bug-check reference.

Common Causes

The following conditions may contribute to this error. They are possible causes rather than confirmed explanations for every crash.

• Faulty device drivers: A graphics, storage, network, USB, or other kernel-mode driver may encounter an unhandled exception.
• Incompatible hardware: A recently installed device or component may not be compatible with the system configuration.
• Memory problems: Defective RAM or memory corruption may contribute to system instability.
• Low-level software: Software that installs drivers or interacts directly with the operating system may introduce compatibility or stability problems.
• Firmware incompatibility: BIOS or device firmware issues may contribute in certain configurations.
• System configuration problems: Recent updates, configuration changes, or other system-level issues may be relevant to the crash.

Use the circumstances of the crash, diagnostic results, and available dump files to distinguish among these possibilities.

Symptoms

• A blue screen displays KERNEL_MODE_EXCEPTION_NOT_HANDLED.
• The system displays stop code 0x0000008E.
• The computer restarts unexpectedly or repeatedly crashes.
• The error occurs during startup, while using an application, or when connecting a device.
• The problem begins after a driver update, software installation, or hardware change.
• Windows becomes difficult to start normally because the error recurs during boot.

How to Fix Windows Stop Code 0x0000008E

1. Restart the Computer and Identify the Trigger

If the crash occurred only once and Windows starts normally, save your work and monitor the computer. A single occurrence does not necessarily indicate a persistent hardware problem.

1. Restart Windows if it is safe to do so.
2. Record the complete stop code and any driver filename displayed on the blue screen.
3. Note what the computer was doing immediately before the crash.
4. Check whether the error returns during the same activity.

If the computer repeatedly crashes, prioritize backing up important data and investigating the cause instead of repeatedly restarting it.

2. Disconnect Recently Added External Devices

If the problem started after connecting a peripheral, disconnect nonessential external devices to determine whether one of them is involved.

1. Shut down the computer if it is stable enough to do so.
2. Disconnect recently added USB devices, docks, external adapters, and other nonessential peripherals.
3. Restart the computer and check whether the error recurs.
4. Reconnect devices one at a time, testing the system after each connection.
5. If a device consistently triggers the crash, check its compatibility and obtain the appropriate driver from the manufacturer's official website.

Do not remove internal components while the computer is powered on. Internal hardware troubleshooting should follow the manufacturer's service instructions.

3. Update or Roll Back the Suspected Device Driver

Drivers are an important area to investigate when a crash begins after a driver change or when crash analysis identifies a particular device driver. Do not assume that every driver is responsible.

1. Open the Windows Start menu and search for Device Manager.
2. Expand the category containing the suspected device.
3. Right-click the device and select Properties.
4. Open the Driver tab and review the available driver information.
5. If the problem began after a driver update and Roll Back Driver is available, consider returning to the previous driver.
6. Otherwise, check Windows Update or the computer or device manufacturer's official support website for an appropriate compatible driver.
7. Restart Windows if required and check whether the problem returns.

Driver rollback is useful only when a suitable previous version is available. If Windows cannot start normally, consider using Safe Mode through Windows Recovery Environment, if available, to investigate recent driver changes.

4. Install Applicable Windows Updates

Windows updates may address operating-system reliability or compatibility problems. Installing updates is a general troubleshooting measure, not a guaranteed fix for this specific stop code.

1. Open Windows Settings.
2. Select Windows Update. The navigation may differ between Windows versions.
3. Check for available updates and install applicable updates from trusted sources.
4. Review optional driver updates carefully to ensure that they are suitable for the hardware.
5. Restart the computer if requested and monitor the system.

If the computer cannot remain running long enough to complete updates, investigate the startup problem and use the available recovery options first.

5. Review Event Viewer for Related Errors

Event Viewer can help establish whether other system errors occurred around the time of the blue screen. An event that appears before a crash is not necessarily its cause.

1. Press Windows + R.
2. Enter the following command:

eventvwr.msc

This command opens Event Viewer and does not change system settings.

1. Expand Windows Logs and select System.
2. Review errors and warnings around the crash time.
3. Record relevant event sources, event IDs, driver names, and device-related messages.
4. Compare the timestamps with recent software, driver, or hardware changes.

Do not treat a generic unexpected-shutdown event as proof of the root cause. If the logs do not reveal a useful lead, examine the available crash dump.

6. Run Hardware Diagnostics

If the crash persists after investigating plausible driver and compatibility problems, use appropriate hardware diagnostics.

• Memory: Run Windows Memory Diagnostic or a diagnostic tool supplied by the computer manufacturer.
• Storage: If storage errors or read failures are present, use the drive or computer manufacturer's supported diagnostic utility.
• Cooling and power: Investigate overheating, cooling failures, or power instability when the symptoms suggest them.
• Recently installed hardware: Check the manufacturer's compatibility documentation and installation requirements.

If a memory test reports errors, back up important data and arrange appropriate hardware service. Passing a diagnostic test does not conclusively rule out an intermittent hardware fault.

7. Check BIOS and Firmware Compatibility

Firmware incompatibility can contribute to some system crashes, but a BIOS update is not a universal solution for bug check 0x8E.

1. Identify the exact computer or motherboard model.
2. Check the manufacturer's official support website for applicable firmware updates or compatibility advisories.
3. Read the update instructions and prerequisites carefully.
4. Back up important data and ensure reliable power before beginning an update.

8. Use Windows Recovery Environment if Windows Will Not Start

If the computer repeatedly crashes during startup, Windows Recovery Environment (WinRE) may provide access to recovery tools. Available options depend on the Windows version and recovery configuration.

1. Enter WinRE using the computer manufacturer's recovery method or suitable Windows recovery media.
2. Select Troubleshoot and then Advanced options, if available.
3. If the problem began after a recent Windows update, consider the appropriate update-uninstallation option.
4. If a suitable restore point exists, consider System Restore to return system configuration to an earlier state.
5. If available, use Startup Settings to enter Safe Mode and investigate recently changed drivers or software.

Some recovery operations require administrator credentials or a BitLocker recovery key. Read the displayed prompts carefully because recovery operations can change system configuration. If a recovery option fails, investigate the crash evidence before considering more disruptive measures.

Advanced Troubleshooting: Analyze the Crash Dump

For recurring blue screens, a Windows crash dump can provide useful diagnostic evidence. Microsoft's WinDbg debugger can examine the bug-check parameters, exception details, stack trace, and potentially relevant drivers.

Locate the Crash Dump

Depending on the system's crash-dump configuration, files may be stored in these locations:

• C:\Windows\Minidump — small memory dumps, when configured and successfully created.
• C:\Windows\MEMORY.DMP — a larger memory dump, when configured and successfully created.

These files may not exist if dump collection is disabled, disk space is insufficient, or Windows cannot write the dump during the crash.

Analyze the Dump with WinDbg

1. Install or open WinDbg using Microsoft's official debugging-tools resources.
2. Use the option to open a crash dump. In WinDbg, the keyboard shortcut is Ctrl + D.
3. Select the relevant dump file.
4. After the dump loads, enter the following command in the debugger command window:

!analyze -v

This is a WinDbg debugger command, not a command intended for the ordinary Windows Command Prompt. It requests verbose automated analysis of the crash.

Review the bug-check parameters, exception information, stack trace, and suspected modules. Missing symbols or an incomplete dump may limit the analysis.

Consult Microsoft's documentation for opening crash dump files with WinDbg and the !analyze debugger command.

Understand the Bug-Check Parameters

Microsoft documents four parameters for bug check 0x8E.

For example, exception code 0xC0000005 represents STATUS_ACCESS_VIOLATION, which indicates an invalid memory access. It does not independently prove whether the underlying cause is a driver defect, corrupted state, hardware fault, or another issue.

A driver filename in the crash report is a diagnostic clue, not conclusive proof of responsibility. Compare the complete debugging output, recent system changes, and multiple crash dumps when available.

Use Driver Verifier Only When Appropriate

Driver Verifier is an advanced Windows diagnostic tool that checks driver behavior and may deliberately trigger a bug check when it detects a violation. It is primarily intended for driver development and controlled troubleshooting.

When advanced driver verification is justified, follow Microsoft's Driver Verifier documentation for configuration, driver selection, and recovery. Avoid enabling verification for all drivers without a specific diagnostic reason.

How to Verify the Fix

After making a change, test the computer under the conditions that previously triggered the error.

• Restart Windows and confirm that it starts normally.
• Repeat the activity or device connection associated with the original crash.
• Check whether the blue screen returns or a different stop code appears.
• Review new crash dumps and event logs if the problem recurs.
• Confirm that the affected hardware and applications continue to function correctly.

A successful restart alone does not prove that the underlying issue is resolved. Monitor the system to determine whether the original failure returns.

When to Seek Technical Assistance

Seek assistance from a qualified technician or the hardware manufacturer if:

• The system continues to crash after appropriate driver and compatibility checks.
• Hardware diagnostics report memory or storage errors.
• Windows cannot start and available recovery options fail.
• Crash dumps contain complex or conflicting diagnostic evidence.
• Firmware updates, internal hardware repairs, or advanced debugging are required.

Crash dumps can contain sensitive system information and, depending on the dump type, data from memory. Share them only with a trusted technician or support provider through an appropriate channel.

Frequently Asked Questions

Is stop code 0x0000008E caused by faulty RAM?

Not necessarily. Memory faults are one possible cause, but drivers, low-level software, incompatible hardware, and firmware problems can also contribute. Use diagnostic results and crash-dump evidence to narrow down the possibilities.

Can a faulty driver cause KERNEL_MODE_EXCEPTION_NOT_HANDLED?

Yes. A faulty or incompatible driver can generate an unhandled kernel-mode exception. Investigate recent driver changes and use crash analysis to determine which component deserves closer examination.

What does exception code 0xC0000005 mean?

0xC0000005 identifies an access violation, meaning that code attempted an invalid memory access. The exception code describes the type of exception but does not establish its underlying cause.

What should I do if Windows crashes before sign-in?

Use Windows Recovery Environment to access available options such as Safe Mode, System Restore, or update removal. The appropriate procedure depends on when the crashes began and which recovery options are available.

Should I reinstall Windows to fix this stop code?

Reinstalling Windows should not be the first troubleshooting step. Investigate recent driver and hardware changes, review crash evidence, and perform relevant diagnostics first. Reinstallation may cause data loss and will not necessarily resolve a hardware fault.

Does a driver named in the crash dump always cause the error?

No. The named module is a useful lead, but it does not always identify the original cause. Review the stack trace, exception details, and other diagnostic evidence before deciding to remove or replace a driver.

Sources

• Microsoft Learn: Bug Check 0x8E — KERNEL_MODE_EXCEPTION_NOT_HANDLED
• Microsoft Learn: Open a Dump File with WinDbg
• Microsoft Learn: !analyze (WinDbg)
• Microsoft Learn: Driver Verifier
• Microsoft Learn: Bug Check Code Reference