Fix Windows Stop Code 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

Quick Answer

The Windows stop code 0x0000008E – KERNEL_MODE_EXCEPTION_NOT_HANDLED indicates that a kernel-mode component generated an exception that Windows could not handle. Possible causes include faulty device drivers, incompatible hardware, memory problems, firmware incompatibilities, or other kernel-level faults.

To troubleshoot this error, check recent hardware and software changes, update or roll back the suspected driver, test the RAM, and start Windows in Safe Mode if necessary. If the blue screen continues, analyze the crash dump using WinDbg. The stop code alone does not identify the exact cause.

What Does KERNEL_MODE_EXCEPTION_NOT_HANDLED Mean?

Bug check 0x0000008E occurs when Windows encounters an unhandled exception while executing kernel-mode code. Kernel mode is the privileged execution environment used by the Windows kernel and many device drivers.

The error can occur when a kernel-mode component performs an invalid operation, encounters an unexpected condition, or accesses memory incorrectly. The underlying reason varies between computers, so the stop code should be treated as a diagnostic starting point rather than a definitive diagnosis.

This error is different from other similarly named Windows stop codes, including 0x0000001E – KMODE_EXCEPTION_NOT_HANDLED and 0x0000007E – SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Each bug check has its own documented meaning and diagnostic requirements.

Common Causes

• Faulty or incompatible device drivers: A graphics, storage, network, or other kernel-mode driver may encounter an exception.
• RAM problems: Defective or unstable memory can contribute to system crashes.
• Recently installed hardware: A new device or component may be incompatible with the computer or its drivers.
• Firmware incompatibility: BIOS/UEFI problems or unsupported hardware configurations may contribute to instability.
• Kernel-level software: Security software, virtualization utilities, and other applications that install low-level drivers may be involved.
• Recent Windows or driver updates: A change may expose an existing compatibility problem.
• System installation problems: If the error occurs during Windows Setup, investigate installation conditions, hardware compatibility, and available storage.

These are possible causes, not confirmed explanations for every occurrence of bug check 0x8E.

Symptoms and Diagnostic Clues

Common symptoms include a blue screen, unexpected restarts, repeated crashes during startup, or failures when using a particular device or application.

A driver or module named in a crash report is a useful clue, but it does not automatically prove that the component is defective.

How to Fix Windows Stop Code 0x0000008E

1. Check Recent Hardware and Software Changes

1. Disconnect newly attached, nonessential USB devices and peripherals.
2. Review any hardware, driver, Windows update, or system utility installed immediately before the first crash.
3. If the error began after a specific change, reverse that change using the manufacturer's supported procedure where possible.
4. Restart Windows and check whether the error returns.

Do not disconnect storage devices required for Windows to start. If the system becomes stable after reversing a change, investigate that component further before concluding that the problem is permanently resolved.

2. Update or Roll Back the Suspected Driver

1. Press Windows + X and open 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 provider, version, and date.
5. If the problem began after a driver update, select Roll Back Driver if available.
6. Otherwise, obtain a compatible driver from Windows Update or the computer or hardware manufacturer's official website.
7. Restart the computer and check whether the crash recurs.

Administrator permissions may be required. The rollback option may be unavailable if a previous driver package is not present. Do not remove an unidentified driver solely because its name appears in a crash report.

See Microsoft's official guidance on updating drivers through Device Manager.

3. Install Applicable Windows Updates

1. Open Settings and select Windows Update.
2. Check for available updates.
3. Install applicable updates for your Windows version.
4. Restart the computer if prompted.
5. Observe whether the blue screen returns.

Updates may address compatibility or stability problems, but they are not a guaranteed fix for this particular bug check. If the problem started immediately after an update, review the relevant release information before considering a supported rollback.

4. Start Windows in Safe Mode

Safe Mode starts Windows with a limited set of drivers and services. It can help determine whether a recently installed driver or service is involved.

1. Enter Windows Recovery Environment (Windows RE). If necessary, use official Windows installation or recovery media and select the recovery option.
2. Select Troubleshoot > Advanced options > Startup Settings > Restart, where these options are available.
3. After the restart, select the Safe Mode option displayed on screen.
4. If Windows starts, reverse recent driver or software changes using supported procedures.
5. Restart normally and test the computer.

The available recovery options vary by Windows version. Some recovery operations may require a BitLocker recovery key. Locate the key before proceeding if prompted.

For additional instructions, consult Microsoft's guide to starting a PC in Safe Mode.

5. Test the RAM and Other Hardware

Memory problems are one possible cause of this stop code. Run appropriate hardware diagnostics before replacing components.

1. Save your work and close open applications.
2. Run the memory diagnostic tool supplied with the computer or recommended by its manufacturer.
3. If memory errors are reported, record the results and follow the manufacturer's service guidance.
4. If RAM was recently installed or changed, verify that the modules and configuration are supported.
5. Investigate any additional hardware diagnostic failures.

Windows Memory Diagnostic may also be available. Press Windows + R, enter the following command, and press Enter:

mdsched.exe

Follow the on-screen instructions to schedule a memory test. The test requires a restart, so save your work first. Review the diagnostic results after the test completes.

A successful test does not rule out every intermittent memory problem, and this stop code alone does not justify replacing RAM.

6. Check BIOS/UEFI and Firmware Compatibility

Firmware incompatibility may contribute to system instability, but updating BIOS/UEFI is not a routine fix for every occurrence of 0x8E.

1. Identify the exact computer or motherboard model and current firmware version.
2. Visit the manufacturer's official support website.
3. Review the firmware release notes and compatibility requirements.
4. Install an update only when it is relevant and supported by the manufacturer.
5. Follow the manufacturer's instructions and ensure reliable power throughout the update.

7. Check Windows Installation Conditions

If the error occurs during Windows installation, investigate the installation media, target drive, available disk space, hardware compatibility, and firmware configuration.

Do not format partitions or delete existing volumes as an initial troubleshooting step. Such operations can permanently erase data. Back up important files and establish a recovery plan before making destructive changes.

Advanced Troubleshooting: Analyze the Crash Dump

If the error continues, a crash dump may help identify the exception and the code involved when Windows failed.

1. Locate the Dump File

Depending on the configured dump type, Windows may store crash data in one of these locations:

• %SystemRoot%\Minidump — small memory dump files.
• %SystemRoot%\MEMORY.DMP — a larger crash dump, if configured and successfully created.

These files may not exist if dump collection was disabled, storage was insufficient, or Windows could not write the dump.

2. Analyze the Dump Using WinDbg

1. Install or open WinDbg using Microsoft's official Windows debugging tools documentation.
2. Open the relevant crash dump through the debugger's file menu.
3. Allow the debugger to load the necessary symbols.
4. Enter the following command in the debugger command window:

!analyze -v

This command requests detailed automatic crash analysis. Review the bug check code, exception information, stack trace, and driver or module details.

For bug check 0x8E, Microsoft documents the parameters as follows:

For example, 0xC0000005 represents STATUS_ACCESS_VIOLATION. This indicates an invalid memory access, but it does not independently identify the responsible driver or prove that the RAM is defective.

Use the exception address, stack trace, recurring crash patterns, and driver history together. A module named in the debugger output is a diagnostic clue rather than conclusive proof of fault.

See Microsoft's documentation for Bug Check 0x8E and analyzing a kernel-mode dump with WinDbg.

3. Protect Crash Dump Privacy

Crash dumps may contain memory and diagnostic information from the time of the failure. Depending on the dump type, they may include sensitive information.

• Restrict access to authorized support personnel.
• Avoid uploading dump files to public websites without assessing their contents and privacy implications.
• Use a trusted, approved support channel when sharing diagnostic files with a vendor.

What to Do If Windows Continues to Crash

1. Use Windows RE to try Safe Mode and reverse recent driver or software changes.
2. Consider System Restore if a suitable restore point exists and the recovery option is available.
3. Run appropriate hardware diagnostics and investigate any reported failures.
4. If the storage device may be failing, prioritize data preservation before running intensive repair operations.
5. Consider resetting or reinstalling Windows only after less disruptive options have been evaluated.

Recovery procedures may remove applications, change system settings, or result in data loss. Confirm that important data is backed up and that any required BitLocker recovery key is available before proceeding.

How to Verify the Fix

• Restart Windows and confirm that it starts normally.
• If safe, repeat the activity that previously triggered the crash.
• Monitor the system for recurring blue screens.
• Compare any new crash dump with previous reports.
• Confirm that hardware diagnostics and any recommended repairs have completed successfully.

If the error returns, collect new diagnostic evidence instead of repeatedly changing drivers, firmware, or system settings without a clear reason.

Frequently Asked Questions

Is stop code 0x0000008E always caused by faulty RAM?

No. RAM problems are one possible cause. Drivers, incompatible hardware, firmware, and other kernel-level components may also be involved.

Can a graphics driver cause KERNEL_MODE_EXCEPTION_NOT_HANDLED?

A graphics driver may be involved, particularly if crashes began after a driver change or occur during graphics-intensive tasks. Review the crash evidence before deciding to roll back or update it.

What does exception code 0xC0000005 mean?

It represents STATUS_ACCESS_VIOLATION, which indicates an invalid memory access. Further debugging is required to determine the underlying cause.

Can I fix this error without reinstalling Windows?

Yes, troubleshooting can begin with less disruptive steps such as checking recent changes, correcting a suspected driver problem, starting Safe Mode, and testing hardware. Reinstallation is not the default solution for this stop code.

Should I update BIOS to fix this error?

Only when the manufacturer's documentation or diagnostic evidence supports investigating a firmware issue. A BIOS update carries risks and is not a guaranteed fix.

Does a driver name in a crash dump prove that the driver is faulty?

No. The named module may be involved, but memory corruption or another component can cause the failure to appear in that module. Interpret the dump in context.

Sources

• Microsoft Learn: Bug Check 0x8E – KERNEL_MODE_EXCEPTION_NOT_HANDLED
• Microsoft Learn: Analyzing a Kernel-Mode Dump File with WinDbg
• Microsoft Learn: Windows Debugging Tools
• Microsoft Support: Start Your PC in Safe Mode in Windows
• Microsoft Support: Update Drivers Through Device Manager