FIX · CRASHES AND BLUE SCREENS
KMODE_
KMODE_EXCEPTION_NOT_HANDLED means a kernel-mode program raised an exception that its error handler did not catch. Microsoft's first suspects are drivers and system services, particularly anything added recently. If the PC will not start, Safe Mode can still give you a way in.
Updated .
TECHNICAL SUMMARY
| Stop code | 0x0000001E |
|---|---|
| Meaning | A kernel-mode program generated an exception the error handler didn't catch |
| First suspects | A named driver, then recently added drivers and services |
| Hardware causes | BIOS incompatibilities, memory conflicts, IRQ conflicts |
| PC Tweaker plan | No control fixes it; Tweaky Driver lists your drivers |
Start with drivers and services
If a driver is named in the bug check message, disable or remove it, or check with its manufacturer for an update. If nothing is named, disable or remove the drivers and services you added most recently.
If the PC crashes during startup
Microsoft says that when the error occurs during the startup sequence on an NTFS system partition, you might be able to use Safe Mode to disable the driver in Device Manager.
Then check the hardware
Microsoft's remaining checks cover compatibility and diagnostics.
- Confirm that any new hardware is compatible with your version of Windows
- Check the System log in Event Viewer for messages that identify the device or driver
- Run the hardware diagnostics your PC's manufacturer supplies, especially the memory scanner
During Windows Setup
The error can appear after the first restart during Windows Setup or after Setup finishes. Microsoft gives a system BIOS incompatibility as a possible cause, resolved by upgrading the BIOS version.
Do it by hand
Check the System log (read-only)
Critical and error entries from the last 24 hours. Move StartTime back if the crash was earlier, and look for a device or driver named close to the time of the blue screen.
PowerShellGet-WinEvent -FilterHashtable @{LogName='System'; Level=1,2; StartTime=(Get-Date).AddDays(-1)} -MaxEvents 30 | Format-Table TimeCreated, ProviderName, Id -AutoSizeOpen Device Manager
Find the named or recently added driver, then disable it, update it or remove it from its properties.
cmddevmgmt.mscTest the memory
It restarts the PC to run. Your PC maker's own memory scanner is the test Microsoft mentions for this code, so run that too if there is one.
cmdmdsched.exe
With PC Tweaker
PC Tweaker does not read crash dumps, and none of its controls fixes this error. If the logs point to a driver, Tweaky Driver, our free driver update checker, shows that device's driver version, the updates available and where the package comes from before you install anything.
Rather not edit the registry by hand?
PC Tweaker shows the exact change before it runs, records the value it replaces and puts it back with Restore. The Free plan needs no account. If a payment fails or a plan ends, Pro tools lock; changes already applied stay as they are and Restore still undoes them.
Common questions
How do I fix KMODE_EXCEPTION_NOT_HANDLED?
Disable, update or remove any driver the blue screen names, then any recently added drivers or services. Check the System log, confirm new hardware is compatible, and run your manufacturer's hardware diagnostics.
Can I fix KMODE_EXCEPTION_NOT_HANDLED if Windows will not start?
Microsoft says that on an NTFS system partition you might be able to use Safe Mode to disable the driver in Device Manager.
Can a BIOS update fix KMODE_EXCEPTION_NOT_HANDLED?
It can when the cause is a BIOS incompatibility, which Microsoft gives as a possible cause of the error around Windows Setup.
Try PC Tweaker
Free download for Windows 10 and Windows 11.