KMODE_EXCEPTION_NOT_HANDLED is Windows stop code 0x0000001E. It means a kernel-mode program generated an exception that Windows could not handle. The practical fix is to identify what changed, use Safe Mode if necessary, test drivers and memory, check BIOS compatibility, repair Windows files, and then use System Restore or reinstall only as a last resort.
What KMODE_EXCEPTION_NOT_HANDLED means
Microsoft defines bug check 0x0000001E as a kernel-mode exception that the error handler did not catch. Kernel-mode code includes core Windows components, device drivers and low-level services. The stop code identifies the class of failure, not the exact defective part.
As an Amazon Associate I earn from qualifying purchases.
Microsoft lists several possible causes:
- A faulty, incompatible or corrupted device driver.
- A defective or incompatible system service.
- Hardware that is incompatible with the computer or Windows installation.
- BIOS incompatibility, particularly after a hardware upgrade or firmware change.
- Conflicting or failing memory.
- Interrupt request (IRQ) conflicts between devices.
A blue-screen viewer may name a .sys file. That filename and the four 0x1E parameters are useful clues, but they are not proof that the named module is the original cause. For example, ntoskrnl.exe often appears in generic crash reports because it is where Windows detected the failure; its presence alone does not identify the bad driver or hardware.
Do this before changing anything
Preserve evidence before uninstalling drivers, cleaning dump files or resetting Windows. Evidence is most useful when the failure is still reproducible.
#1 Best Overall
- Dual USB-A & USB-C Bootable Drive – compatible with nearly all Windows PCs, laptops, and tablets (UEFI & Legacy BIOS). Works with Surface devices and all major brands.
- Fully Customizable USB – easily Add, Replace, or Upgrade any compatible bootable ISO app, installer, or utility (clear step-by-step instructions included).
- Complete Windows Repair Toolkit – includes tools to remove viruses, reset passwords, recover lost files, and fix boot errors like BOOTMGR or NTLDR missing.
- Reinstall or Upgrade Windows – perform a clean reinstall of Windows 7 (32bit and 64bit), 10, or 11 (amd64 + arm64) to restore performance and stability. (Windows license not included.). Includes Full Driver Pack – ensures hardware compatibility after installation. Automatically detects and installs drivers for most PCs.
- Premium Hardware & Reliable Support – built with high-quality flash chips for speed and longevity. TECH STORE ON provides responsive customer support within 24 hours.
- Photograph the blue screen. Capture the exact text,
KMODE_EXCEPTION_NOT_HANDLED, the code0x0000001E, and any named.sysmodule. - Record the timing. Note whether the crash began after a Windows update, driver installation, antivirus or filter-driver installation, new hardware, a BIOS change, or another software change.
- Preserve a minidump. If Windows created a crash dump, copy it to external storage before running cleanup utilities or deleting temporary files.
- Write down the trigger. Record whether the crash occurs during startup, login, gaming, sleep/wake, printing, networking or another repeatable action.
Do not assume that the most recently displayed filename is automatically responsible. Compare the filename with the timing, Event Viewer entries, dump evidence and whether the failure disappears in Safe Mode.
Use the evidence to rank likely causes
When several explanations are possible, compare them on four axes rather than guessing.
| Evidence axis | What to ask | What it suggests |
|---|---|---|
| Timing | Did the first crash follow a driver, hardware, BIOS or software change? | A recent change becomes the first rollback or removal candidate. |
| Repeatability | Does the same action trigger the stop error? | A repeatable trigger helps connect the crash to a device, service or workload. |
| Diagnostic evidence | Is a driver named, is there a matching System-log error, or did a dump identify a module? | Converging evidence is stronger than a filename shown by one generic viewer. |
| Scope | Does Windows crash only in normal mode, or also in Safe Mode and diagnostics? | Normal-mode-only failures favor software or drivers; failures across modes raise the hardware probability. |
A driver that stops causing crashes in Safe Mode is more suspicious than one that fails identically during memory diagnostics. Conversely, a failed memory test or crashes in several boot modes should move hardware investigation ahead of repeated driver reinstalls.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Start Windows in Safe Mode when it reboots in a loop
Safe Mode loads a limited set of drivers and services. Microsoft specifically notes that, when 0x1E occurs during startup, Safe Mode may let you disable the driver in Device Manager.
- Turn on the computer. If normal startup repeatedly fails, allow Windows Recovery Environment to appear. If it does not, interrupt startup only as needed for the recovery screen to load; avoid repeatedly forcing power-offs once recovery is available.
- Select Troubleshoot.
- Select Advanced options.
- Select Startup Settings, then Restart.
- At the numbered Startup Settings screen, choose Safe Mode. Use the networking option only if you specifically need network access for a manufacturer download.
In Safe Mode, first copy your personal files and any minidump. Then open Device Manager and work on the device most closely connected with the crash:
- Roll back the driver if the problem followed an update and the Roll Back Driver button is available.
- Update it using the computer or device manufacturer’s official support page, matching the exact model and Windows 8.1 edition.
- Disable the device temporarily when you need to confirm whether it is involved. This can remove the device’s function until you re-enable it.
- Uninstall the recently added or corrupted driver when rollback is unavailable. Restart and install the correct manufacturer package rather than relying on an unrelated package.
Do not remove several unrelated drivers at once. Changing one variable at a time makes the result attributable and preserves a path back if the device becomes unusable.
Investigate a named driver or recent change
Check the System log
Open Event Viewer and inspect the Windows Logs → System log for errors and warnings immediately before the crash time. Look for the same device, service or driver name appearing repeatedly. A log entry that occurs at the same time as every stop error is useful corroboration, but a single warning is not by itself a diagnosis.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchUndo changes in a controlled order
If the crashes began after a change, reverse that change before making unrelated repairs:
- Roll back or uninstall a newly installed device driver.
- Temporarily remove newly added hardware and reconnect only essential devices.
- Undo a recently installed antivirus or filter driver according to its vendor’s removal procedure.
- Return a firmware or BIOS change to the previous stable setting if the computer maker documents that option.
Restart after each change and test the same action that previously triggered the blue screen. If the failure stops, keep the working configuration and obtain a corrected package from the hardware manufacturer before re-enabling the feature.
Do not treat a generic crash report as proof
A dump or viewer that names a Windows component can reflect the point at which the exception was noticed rather than the component that caused it. Give more weight to a third-party driver that matches the timing, appears in the dump context, and disappears from the failure in Safe Mode.
Test memory and other hardware
Microsoft recommends the computer manufacturer’s hardware diagnostics, especially its memory scanner. Microsoft’s stop-error guidance also identifies Windows Memory Diagnostic as a way to help exclude physical-memory problems.
Run Windows Memory Diagnostic
- Save open work.
- Press Windows key + R, type
mdsched.exe, and press Enter. - Choose Restart now and check for problems if you can restart immediately, or schedule the check for the next boot.
- Allow the test to complete without powering off the computer.
- After Windows starts, review the reported result. If no notification appears, check the System log for the memory-diagnostic result.
A failed test means you should stop treating the issue as a software-only problem. Power down, reseat or test memory only according to the computer maker’s service guidance, and replace the failing module or obtain service. If the machine has multiple modules and the manufacturer’s procedure permits individual testing, test them separately to identify the failing part. Do not continue installing drivers while defective RAM remains in use, because unstable memory can corrupt files and make every later test less trustworthy.
Run the manufacturer’s diagnostics
Use the diagnostic environment supplied by the PC manufacturer for memory and other components such as storage, processor and system board. Record any error code exactly. A hardware failure that appears outside normal Windows is strong evidence that replacing or servicing the component is necessary.
Consider IRQ and device conflicts
IRQ conflicts are among Microsoft’s listed causes of 0x1E. If the crash follows installation of a particular expansion card or peripheral, disconnect nonessential devices, boot, and reconnect them one at a time. A device that consistently brings the stop error back deserves a compatible driver, a different connection or hardware service.
Check BIOS and hardware compatibility
BIOS incompatibility can produce 0x1E, especially after a computer upgrade, a new device installation or Windows setup. Check the PC maker’s support page for the exact model and confirm whether a BIOS update addresses compatibility or stability. Follow the maker’s power and recovery instructions precisely; an interrupted firmware update can leave the computer unable to start.
Free tools Windows power users keep installed
One-click scans. No signup required.
Also verify that the new hardware is listed as compatible with the computer and Windows 8.1. If the blue screen started immediately after an upgrade, remove the new component or return to the previous firmware configuration, then test again. Do not apply a BIOS file intended for a different model.
Repair corrupted Windows components
Windows component corruption can cause kernel exceptions, although DISM and System File Checker cannot prove that RAM or a third-party driver is healthy. Run them from an elevated Command Prompt after saving work.
- Open the Start screen, type
Command Prompt, right-click it, and select Run as administrator. - Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth - Wait for DISM to finish. Do not close the window if progress appears to pause.
- Run:
sfc /scannow - When both commands finish, restart Windows and repeat the activity that caused the crash.
DISM repairs the Windows component store when it can; SFC scans protected system files and replaces damaged copies. If either command reports that it could not complete, note the exact message and address the underlying storage, servicing or recovery problem instead of repeatedly running the same command. A clean result does not clear a device driver, BIOS or physical-memory fault.
Interpret the results before moving on
Use each test to change the probability of a cause, not to declare the entire computer fixed. If Safe Mode is stable, return to normal mode only after changing the suspected driver and then repeat the original trigger. If the same stop error returns immediately, restore the last working driver state and investigate the next change in your timeline.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- High-speed USB 3.0 performance of up to 150MB/s(1) [(1) Write to drive up to 15x faster than standard USB 2.0 drives (4MB/s); varies by drive capacity. Up to 150MB/s read speed. USB 3.0 port required. Based on internal testing; performance may be lower depending on host device, usage conditions, and other factors; 1MB=1,000,000 bytes]
- Transfer a full-length movie in less than 30 seconds(2) [(2) Based on 1.2GB MPEG-4 video transfer with USB 3.0 host device. Results may vary based on host device, file attributes and other factors]
- Transfer to drive up to 15 times faster than standard USB 2.0 drives(1)
- Sleek, durable metal casing
- Easy-to-use password protection for your private files(3) [(3)Password protection uses 128-bit AES encryption and is supported by Windows 7, Windows 8, Windows 10, and Mac OS X v10.9 plus; Software download required for Mac, visit the SanDisk SecureAccess support page]
If a memory or manufacturer diagnostic reports an error, treat that result as more important than a clean DISM or SFC scan. Windows file repair cannot compensate for data being changed by unreliable memory. Likewise, a clean memory test does not certify a graphics, storage, network or other device driver. Keep a simple log of each change, the reboot result and the exact trigger; this prevents cycling through the same unsuccessful fixes.
When the error occurs only with one peripheral attached, leave other devices disconnected while testing. When it occurs in both normal and Safe Mode, prioritize hardware, BIOS and compatibility checks. When it occurs only after a particular application starts, examine the application’s low-level services or filter drivers rather than assuming the application itself is the kernel fault.
Common troubleshooting mistakes to avoid
- Replacing a named Windows file. A module such as
ntoskrnl.exemay only be the detection point. Do not download replacement system files from unrelated sites. - Installing several driver packages together. If the crash stops, you will not know which change helped; if it worsens, you have more variables to undo.
- Using a driver meant for another model. Match the exact computer or component model and Windows 8.1 edition on the manufacturer’s support page.
- Continuing after a failed memory test. Repair or replace the failing hardware first.
- Interrupting a diagnostic or BIOS update. Allow tests to finish and follow the manufacturer’s power instructions.
- Resetting before saving evidence. A reset or reinstall can erase dumps, logs and the configuration that explains the failure.
- Assuming one successful boot proves a fix. Repeat the activity that normally triggers the stop error and observe the machine over several restarts.
Use System Restore if the crash began recently
System Restore can return system files, drivers and settings to a restore point created before the crashes. It is a later recovery step, not a substitute for preserving personal files or identifying a failing component.
- Back up personal files to separate storage first.
- From Windows, open the recovery tools and select System Restore. If normal startup fails, use Windows Recovery Environment → Troubleshoot → Advanced options → System Restore.
- Choose a restore point dated before KMODE_EXCEPTION_NOT_HANDLED began.
- Review the affected programs and drivers, start the restore, and allow the computer to restart.
- Test the original trigger. If the crash returns, the restored state did not remove the underlying cause.
System Restore does not replace personal-file backups and does not repair defective hardware. If no suitable restore point exists, continue with diagnostics rather than selecting an arbitrary point.
Recommended Free Tools
When none of the fixes works
At this stage, gather the photographs, minidumps, Event Viewer timestamps, memory-test results, manufacturer diagnostic codes and the list of changes already reversed. That record prevents a repair shop or support technician from repeating inconclusive steps.
- If crashes occur only in normal mode and correlate with one device, keep that device disabled and obtain a manufacturer-specific driver or replacement.
- If memory or manufacturer diagnostics fail, arrange hardware repair or replacement before reinstalling Windows.
- If crashes began after a BIOS or hardware upgrade, ask the PC maker about compatibility and the correct firmware for the exact model.
- If Windows files remain damaged and hardware tests pass, use System Restore or consider a reset or clean reinstall after backing up personal data.
A reset or reinstall erases troubleshooting context and may remove applications, drivers and personal data depending on the option selected. Document the stop code and copy dumps before proceeding. Reinstalling Windows cannot make incompatible hardware or defective RAM reliable.
If you use an OEM service center, local technician or data-recovery provider, give them the timeline and test results rather than only saying “blue screen.” Ask them to test the suspected component and confirm compatibility before authorizing a replacement. Keep a separate backup of irreplaceable files; recovery work is not a substitute for a current backup.
Windows 8.1 support ended
Microsoft ended Windows 8.1 support on January 10, 2023. Microsoft no longer provides technical assistance, software updates, security updates or fixes for the operating system, and there is no Extended Security Update program for it. The computer can continue to run, but unsupported software increases security and compatibility risk.
After stabilizing the machine and backing up your files, plan migration to a supported Windows release or replacement hardware if the computer cannot meet current requirements. Keep the crash evidence until the migration is complete so that a recurring driver or hardware fault is not carried into the next installation.
As an optional shortcut, Outbyte PC Repair can look for more than 100 common Windows issues where possible, including broken system elements, invalid redirects and shared DLL problems, while also offering settings tweaks, temporary-file cleanup, privacy tools, vulnerability checks, a real-time boost, file shredding and an app-crash log. It runs on Windows 11, 10, 8 and 7; its free trial is offered by category for at least two days, followed by a paid subscription. It complements antivirus software rather than replacing it, results vary, and no tool repairs every crash.
Frequently Asked Questions
What does stop code 0x0000001E mean?
Microsoft calls 0x0000001E KMODE_EXCEPTION_NOT_HANDLED. A kernel-mode program generated an exception that its error handler did not catch. The code does not identify whether the cause is a driver, service, memory, BIOS, compatibility or IRQ problem.
How can I stop a Windows 8.1 reboot loop?
Enter Windows Recovery Environment and choose Troubleshoot → Advanced options → Startup Settings → Restart, then select Safe Mode. In Safe Mode, preserve your files and minidump, and roll back, update, disable or uninstall the driver most closely associated with the crash.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Which driver caused KMODE_EXCEPTION_NOT_HANDLED?
A named .sys file is a lead, not proof. Compare it with the crash timing, Event Viewer’s System log, dump context and Safe Mode behavior. A third-party driver that matches those clues and disappears in Safe Mode is more credible than a generic report naming ntoskrnl.exe.
Should I run DISM and SFC first?
They are appropriate for possible Windows component corruption, but they should not replace evidence capture, driver checks and memory testing. Run DISM.exe /Online /Cleanup-Image /RestoreHealth, then sfc /scannow from an elevated Command Prompt and reboot. Clean results do not clear defective RAM or a bad driver.
What if Windows Memory Diagnostic reports an error?
Stop treating the crash as software-only. Follow the computer maker’s service guidance to reseat or test modules, replace the failing part or obtain service. Do not keep installing drivers while unreliable memory may be corrupting files and test results.
Can a BIOS update fix this blue screen?
BIOS incompatibility is one possible cause, especially after new hardware or an upgrade. Check the exact PC model at the manufacturer’s support site and apply only the documented firmware. An update is not a general remedy, and an interrupted or incorrect update can prevent startup.
Will System Restore delete my personal files?
System Restore targets system files, drivers and settings, but you should still back up personal files first. Choose a restore point from before the crashes, review affected programs, and test the original trigger afterward. It cannot repair defective hardware.
Is Windows 8.1 still supported?
No. Microsoft ended support on January 10, 2023, with no further technical assistance, software updates, security updates or fixes and no Extended Security Update program. Stabilize and back up the computer, then plan migration to a supported release or replacement hardware.
The Bottom Line
0x0000001E is a kernel exception, not a diagnosis. Save the blue-screen details and dump, compare timing and logs, then use Safe Mode to isolate recent drivers or devices. Test memory and manufacturer hardware diagnostics before trusting software repairs; check BIOS compatibility after upgrades; run DISM and SFC for possible component corruption; and use System Restore only after backing up. If tests point to hardware, repair it before reinstalling Windows. Because Windows 8.1 has been unsupported since January 10, 2023, plan a supported replacement or upgrade once the machine is stable.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors
