Fix KMODE_EXCEPTION_NOT_HANDLED BSOD (0x0000001E) in Windows 10/11


The KMODE_EXCEPTION_NOT_HANDLED error (stop code 0x0000001E) is a common Blue Screen of Death (BSOD) error in Windows 10 and Windows 11. It occurs when a kernel-mode program generates an exception that the error handler did not catch. The result is a sudden crash and restart, often with loss of unsaved data.

This BSOD is typically caused by faulty drivers, corrupted system files, or hardware issues. In this guide, we explain the common causes and walk you through 8 proven solutions to fix KMODE_EXCEPTION_NOT_HANDLED and get your PC back to normal.

PAGE CONTENT

What Causes KMODE_EXCEPTION_NOT_HANDLED (0x0000001E)?

The KMODE_EXCEPTION_NOT_HANDLED error means that a program running in kernel mode encountered an unexpected condition that was not handled properly. Common causes include:

Note
The BSOD screen often shows a file name (e.g., ntoskrnl.exe, a .sys driver file) next to the stop code. Note this down as it points to the specific driver causing the crash.

Solution 1: Update or Reinstall Device Drivers

Faulty drivers are the most common cause of KMODE_EXCEPTION_NOT_HANDLED. Update or reinstall your drivers, especially the graphics card, network adapter, and chipset drivers.

Step 1. Press Win + X and select "Device Manager".

Step 2. Expand "Display adapters", right-click your graphics card, and select "Update driver". Choose "Search automatically for drivers".

Step 3. Repeat for "Network adapters" and "System devices".

Step 4. If updating does not work, right-click the device and select "Uninstall device". Restart your PC, and Windows will reinstall the driver automatically.

Step 5. For the best results, download the latest drivers from the manufacturer's website (NVIDIA, AMD, Intel, Realtek, etc.) and do a clean install using the manufacturer's installation utility.

Solution 2: Disable Fast Startup

Fast Startup can cause driver conflicts and BSOD errors during shutdown or startup. Disabling it often fixes KMODE_EXCEPTION_NOT_HANDLED.

Step 1. Open Control Panel > Power Options.

Step 2. Click "Choose what the power buttons do".

Step 3. Click "Change settings that are currently unavailable".

Step 4. Uncheck "Turn on fast startup (recommended)".

Step 5. Click "Save changes" and restart your PC.

Solution 3: Run SFC and DISM Scans

Corrupted system files can trigger this BSOD. Use the System File Checker (SFC) and DISM tools to repair them.

Step 1. Press Win + X and select "Windows Terminal (Admin)".

Step 2. Run DISM to repair the Windows image:

DISM /Online /Cleanup-Image /RestoreHealth

Step 3. Run the SFC scan:

sfc /scannow

Step 4. Wait for both scans to complete. If corrupted files are found and repaired, restart your PC.

Solution 4: Check RAM with Windows Memory Diagnostic

Faulty RAM is a common cause of KMODE_EXCEPTION_NOT_HANDLED. Test your memory with the built-in Windows Memory Diagnostic tool.

Step 1. Press Win + R, type mdsched.exe, and press Enter.

Step 2. Click "Restart now and check for problems (recommended)".

Step 3. Your PC will restart and run the memory test. When it finishes, check the results.

If errors are found, try reseating your RAM modules (remove and reinsert them) or test each module individually to identify the faulty one. Replace faulty RAM.

Solution 5: Run CHKDSK to Fix Disk Errors

Hard drive errors or bad sectors can cause BSOD crashes. Run CHKDSK to scan and repair your drive.

Step 1. Open Windows Terminal (Admin).

Step 2. Run the CHKDSK command on your system drive:

chkdsk C: /f /r

Step 3. If the drive is in use, type Y to schedule the scan on the next restart. Restart your PC.

Step 4. CHKDSK will run before Windows starts. Let it complete.

Solution 6: Disable Overclocking

If you have overclocked your CPU, GPU, or RAM, the extra speed may be causing instability and BSOD errors. Disable overclocking and run components at their stock speeds.

Solution 7: Perform a Clean Boot

A clean boot starts Windows with only essential services and drivers, helping you identify if a third-party program is causing the BSOD.

Step 1. Press Win + R, type msconfig, and press Enter.

Step 2. Go to the "Services" tab, check "Hide all Microsoft services", then click "Disable all".

Step 3. Go to the "Startup" tab, click "Open Task Manager", and disable all startup items.

Step 4. Restart your PC. If the BSOD no longer occurs, enable services and startup items one by one to find the culprit.

Solution 8: System Restore or Reset Windows

If none of the above solutions work, the KMODE_EXCEPTION_NOT_HANDLED error may be caused by deep system corruption.

Before resetting, back up your important data to avoid data loss. You can use Qiling Backup to create a system image.

FAQs About KMODE_EXCEPTION_NOT_HANDLED

What is KMODE_EXCEPTION_NOT_HANDLED?

KMODE_EXCEPTION_NOT_HANDLED (stop code 0x0000001E) is a BSOD error that occurs when a kernel-mode program encounters an unhandled exception. It is usually caused by faulty drivers, corrupted system files, or hardware problems.

Can outdated drivers cause KMODE_EXCEPTION_NOT_HANDLED?

Yes. Outdated, corrupted, or incompatible drivers are the most common cause of this error. Updating or reinstalling your graphics, network, and chipset drivers usually resolves the issue.

How do I find which driver is causing the BSOD?

Check the BSOD screen for a file name (usually a .sys file). You can also use Event Viewer (Win + X > Event Viewer > Windows Logs > System) to find error logs that identify the problematic driver.

Is KMODE_EXCEPTION_NOT_HANDLED caused by RAM?

It can be. Faulty RAM is a common hardware cause of this BSOD. Run Windows Memory Diagnostic to test your RAM. If errors are found, reseat or replace the memory modules.

Can overclocking cause KMODE_EXCEPTION_NOT_HANDLED?

Yes. An unstable overclock of the CPU, GPU, or RAM can trigger this BSOD. Disable overclocking and run components at stock speeds to see if the error stops.

Back Up and Restore Windows with Qiling Disk Master

Before you roll back drivers, disable third-party services, or repair system files to stop KMODE_EXCEPTION_NOT_HANDLED, create a full system backup. This stop code is usually driver-related, so a system image gives you a safe rollback path if Windows still crashes after your changes. Qiling Disk Master handles both the backup and the restore.

Part 1: Create a Full System Backup

Step 1. Install and open Qiling Disk Master. On the home screen, open "Backup and Recovery" and choose "System Backup". This option automatically includes Windows and the hidden boot partitions, so you do not have to select them one by one.

open Backup and Recovery in Qiling Disk Master

Step 2. Check the source. The disk where Windows is installed and its system partitions are already ticked for you. If you only need your personal documents, run a separate "File Backup" task instead.

choose System Backup to protect Windows 11

Step 3. Click the destination box and choose where the image should be saved. Use an external HDD or SSD, a NAS, or any drive other than the one you are about to repair, and make sure it has enough free space.

select an external drive as the system backup destination

Step 4. Review the task summary and click "Proceed". Wait until the progress bar reaches 100%. Do not unplug the drive or turn off the PC while the backup is running.

click Proceed to start the system backup

Part 2: Restore Windows from the Backup

Step 1. Open Qiling Disk Master again, go to "Backup and Recovery", and select the recovery option. Your backup images are listed, so pick the one you created before the repair.

select the system backup image to restore

Step 2. Choose the target disk or partition. Normally you restore to the original system disk. If the drive was replaced, select the new disk instead, and the restore rebuilds Windows together with its boot partitions.

choose the target disk for the system restore

Step 3. Preview the restore plan, click "Proceed", and confirm the warning. The PC restarts to finish the job, and Windows comes back exactly as it was on the day the image was created.

preview the restore plan before proceeding

Note
Keep the backup image on a separate drive, and refresh it before every major change, such as a Windows update, a driver upgrade, or a disk operation.

Conclusion

The KMODE_EXCEPTION_NOT_HANDLED (0x0000001E) BSOD is most often caused by driver issues, corrupted system files, or hardware problems. Start by updating your device drivers and running SFC/DISM scans. If the error persists, test your RAM, check your hard drive, and disable overclocking. In most cases, one of these solutions will resolve the error.

If you need to back up your data before trying advanced fixes, consider using Qiling Backup to protect your important files.

Related Articles


Is this information helpful?     

What can we do to improve this information? (Optional)
Refresh Please enter the verification code!


Products

Articles & Tutorials



About

Products

Articles & Tutorials

Company | Cookies Policy | Refund Policy | License | Legal

Copyright © 2026 QILING Tech Co., Ltd. All Rights Reserved.

QilingTech uses cookies to ensure you get the best experience on our website.  Learn more  Got it