Overview
KMODE_EXCEPTION_NOT_HANDLED is a kernel-level BSOD. It means a driver or service running in kernel mode (the highest privilege level) caused an exception Windows didn't know how to handle.
The cause is almost always a driver — most often graphics, network, or audio. Hardware issues are a distant second. The good news: the BSOD itself usually names the culprit driver in parentheses (like `KMODE_EXCEPTION_NOT_HANDLED (igdkmd64.sys)`). That filename is your starting point.
This guide explains how to identify the bad driver and either update or roll it back, plus the broader fixes for cases when no driver name appears.
Before you start
- ✓Note the driver filename from the BSOD if shown (e.g., nvlddmkm.sys, igdkmd64.sys, Netwtw06.sys)
- ✓Administrator account
- ✓Recent backup recommended
5-step guide
Read time: ~15-40 min
Identify the Failing Driver
If the BSOD listed a filename in parentheses, that's your culprit. Common ones:
nvlddmkm.sys→ NVIDIA graphics driverigdkmd64.sys→ Intel graphics driveratikmpag.sys/atikmdag.sys→ AMD graphicsNetwtw06.sys→ Intel Wi-Fitcpip.sys→ Network stackndis.sys→ Network driver
If you missed it, open Event Viewer (eventvwr.msc) → Windows Logs → System and look for the most recent BugCheck entry around your BSOD time.
Update the Driver via Device Manager
Outdated drivers cause most KMODE failures.
Steps:
- Right-click Start → Device Manager.
- Find the device matching the failed driver (Display adapters / Network adapters / etc.).
- Right-click → Update driver → Search automatically.
For comprehensive updates, Driver Easy scans all hardware in one pass.
Roll Back the Driver If BSOD Started Recently
If the BSOD started right after a driver auto-update, roll back to the previous version.
Steps:
- In Device Manager, right-click the device → Properties.
- Click the Driver tab.
- If Roll Back Driver is enabled, click it.
- Restart and test for 24 hours.
Run Driver Verifier (Advanced — for persistent BSOD)
If no driver name appears and updates don't help, Driver Verifier stress-tests all drivers and crashes the PC immediately when one fails — making it easy to identify.
Steps:
- Press
Windows + R, typeverifier, press Enter. - Choose Create custom settings (for code developers).
- Select Standard settings.
- Choose Select driver names from a list.
- Tick all third-party (non-Microsoft) drivers and click Finish.
- Restart. PC will BSOD within minutes if a driver is bad — note the filename.
- After identification, disable Verifier:
bashverifier /resetDriver Verifier is intentionally aggressive. Only run it if you're comfortable troubleshooting BSODs. Disable with /reset before normal use.
Run System File Checker and Memory Diagnostic
Rule out corrupted system files and bad RAM:
SFC + DISM:
bashsfc /scannow
DISM /Online /Cleanup-Image /RestoreHealthStill seeing KMODE_EXCEPTION_NOT_HANDLED?
If the guide is not enough, describe the issue first. We will explain whether remote help is appropriate before any access is granted.
No automatic remote access.
- DIY steps first
- Permission before access
- Hardware limits explained
Common questions
Is KMODE_EXCEPTION_NOT_HANDLED a hardware or software problem?
Why does it crash to BSOD instead of just an app error?
Should I disable my antivirus to test?
What if Driver Verifier doesn't catch anything?
Is it safe to use my PC while troubleshooting?
Written by PCDoc Team
Tested on a real Windows machine on 2026-05-20. Found a mistake? Tell us.