Introduction
You press the power button, Windows 10 loads, and a blue screen flashes: System Thread Exception Not Handled. The system reboots and the loop starts again. This stop error looks scary, but you can fix it with a clear plan. Most cases come from faulty or mismatched drivers. Some stem from corrupt system files, unstable overclocks, or a recent Windows or driver update that went wrong.
This guide walks you through proven steps to stop the BSOD and protect your files. You will learn how to identify the driver that crashes, repair Windows components, and stabilize your hardware and drivers. If Windows will not boot, you will also see how to reach recovery tools and get back to the desktop.
Before you change drivers and settings, you need a safe baseline. You will start with quick pre-checks and a way into Safe Mode. Then you will move on to driver fixes, system repairs, and final prevention tips so the error does not come back. With that roadmap in mind, let us define what this error means and why it appears.
What System Thread Exception Not Handled Means on Windows 10: Causes and Symptoms
This BSOD appears when a system thread throws an exception that the kernel cannot handle. On Windows 10, it often points to a bad or incompatible driver. The official name is System Thread Exception Not Handled, but many users search for system exception thread not handled windows 10. Both refer to the same stop error.
Common causes include:
– A GPU driver that crashes during startup or logon.
– Storage or chipset drivers (AHCI/NVMe, Intel RST) that conflict with your Windows build.
– Network, Wi-Fi, or USB/HID drivers that fail under certain power states.
– Corrupted system files after a failed update or sudden power loss.
– BIOS or firmware bugs combined with aggressive power settings or overclocks.
– Third-party filter drivers from antivirus, VPN, or disk tools.
Typical symptoms:
– A boot loop with the same BSOD code on every restart.
– A driver file name on the BSOD or in the minidump (for example, nvlddmkm.sys, atikmdag.sys, igdkmd64.sys, iaStorA.sys, ntfs.sys).
– Random crashes under GPU load, sleep or wake, or network activity.
Now that you recognize the likely causes, you need to work safely. The next section sets up backups, Safe Mode access, and restore points so changes are low risk and reversible.
Quick Pre-Checks: Backups, Safe Mode Access, and Restore Point Setup
Before you change drivers or system files, reduce risk.
Do these pre-checks:
1) Back up important files:
– If you can reach the desktop, copy your Documents, Pictures, and projects to an external drive or cloud.
– If you cannot boot, plan to use a USB Windows installer or WinRE to copy files later.
2) Verify a path to Safe Mode:
– From the sign-in screen or desktop: hold Shift > select Restart > Troubleshoot > Advanced options > Startup Settings > Restart > press 4 for Safe Mode or 5 for Safe Mode with Networking.
– If you are in a boot loop: interrupt boot three times (power off at the spinning dots) to trigger the recovery menu, then follow the same path.
– With install media: boot from a Windows 10 USB, select Repair your computer, then go to Troubleshoot.
3) Create or verify a restore point:
– Press Win+R, type SystemPropertiesProtection, and enable protection for your system drive.
– Click Create and name the restore point.
You now have a fallback and Safe Mode access. With safety in place, the next step is to pinpoint the driver or module that triggers the crash so you can apply targeted fixes.
Identify the Faulty Driver or Module Causing the BSOD
Finding the culprit speeds up the fix. You can do this from the desktop or Safe Mode.
Use these methods:
– Check the BSOD screen: note any file name shown (for example, nvlddmkm.sys, atikmdag.sys, igdkmd64.sys, iaStorA.sys, bcmwl63a.sys, rt640x64.sys).
– Read minidumps:
1) Navigate to C:\Windows\Minidump.
2) Use a viewer such as BlueScreenView or WhoCrashed to scan dumps.
3) Note the Caused by driver line and any repeating file names.
– Inspect Event Viewer:
1) Press Win+X > Event Viewer.
2) Under Windows Logs > System, filter by Critical and Error around the crash time.
3) Look for driver service failures.
– Use Device Manager:
1) Press Win+X > Device Manager.
2) Expand Display adapters, Storage controllers, Network adapters, and Universal Serial Bus controllers.
3) Right-click devices > Properties > Driver tab > note version and date.
– Optional: WinDbg Preview from the Microsoft Store can open dumps for deeper analysis. Use the !analyze -v command and look for Probably caused by and any driver stack mentions.
Once you know the driver area (GPU, storage, network, USB or HID), you can apply targeted fixes. Most cases start with the graphics driver, so begin there before moving deeper.
Fix Graphics Driver Issues (NVIDIA, AMD, Intel) Triggering the Error
Graphics drivers top the list of causes. A bad update, leftover files, or mismatched versions can trigger the error at logon or during hardware acceleration.
Do this:
1) Try a quick update or rollback:
– Press Win+X > Device Manager > Display adapters.
– Right-click your GPU > Properties > Driver.
– Click Roll Back Driver if available. Reboot and test.
– If rollback is unavailable, click Update driver > Search automatically. Test again.
2) Install a clean, matching driver:
– Go to your laptop OEM support page for your model, or the desktop motherboard or GPU vendor page.
– Download a driver that matches your Windows 10 build and GPU.
– Prefer WHQL-signed, stable versions over optional betas.
3) Disable hardware acceleration in apps temporarily:
– If you reach the desktop, turn off hardware acceleration in browsers and creative tools to reduce GPU stress while you troubleshoot.
If simple steps do not work or the system crashes during install, perform a clean GPU driver removal with DDU next. If the GPU is not to blame, storage and chipset drivers are the next most likely culprits.
Update or Roll Back Storage and Chipset Drivers (AHCI/NVMe, Intel RST)
Storage and chipset drivers sit deep in the kernel. A wrong or outdated version can cause the system thread exception.
Follow these steps:
1) Identify your storage stack:
– In Device Manager, expand IDE ATA or ATAPI controllers and Storage controllers.
– Note drivers such as Standard AHCI Controller, Intel Chipset SATA or PCIe RST, NVMe controller, or vendor-specific entries.
2) Update from OEM first:
– Visit your laptop or motherboard support page.
– Download the latest chipset drivers and Intel RST or NVMe packages approved for your model and Windows 10 version.
– Install chipset first, then storage. Reboot after each.
3) Roll back if issues started after an update:
– In Device Manager, right-click the controller > Properties > Driver > Roll Back Driver.
– Reboot and test for stability.
4) Avoid mixing packages:
– Do not install drivers from multiple vendors for the same controller.
– Keep RST versions that your OEM recommends for your BIOS or firmware.
With the storage stack stable, move to network and peripheral drivers. These components can also trigger the same stop error under certain power or traffic conditions.
Stabilize Network and Peripheral Drivers (Wi-Fi, Ethernet, USB, HID)
Network and input device drivers can crash during power transitions or under heavy traffic.
Try these actions:
1) Update drivers from OEM or chipset vendors:
– Wi-Fi or Ethernet: get drivers from your laptop or motherboard support page or from Intel, Realtek, Broadcom, or Qualcomm websites if OEM lacks updates.
– USB or HID: check motherboard support for USB controller drivers and device firmware for keyboards, headsets, and hubs.
2) Remove and reinstall problematic devices:
– In Device Manager, right-click the adapter or device > Uninstall device > check Delete the driver software if available > OK.
– Reboot. Windows will reinstall a baseline driver. Test stability.
3) Change power settings:
– Control Panel > Power Options > Change plan settings > Change advanced power settings.
– Expand Wireless Adapter Settings > Power Saving Mode > set to Maximum Performance.
– Expand USB settings > USB selective suspend setting > Disabled. Test again.
If the BSOD keeps pointing to the GPU, use a clean removal with DDU next. If it points to storage or network, keep those drivers in mind while you repair system files, which can affect all drivers.
Cleanly Uninstall and Reinstall GPU Drivers with DDU
Display Driver Uninstaller (DDU) strips leftover files and services that can survive normal uninstalls.
Use DDU safely:
1) Download DDU from the official Wagnardsoft site. Extract it.
2) Boot into Safe Mode.
3) Disconnect from the internet to prevent Windows from auto-installing drivers.
4) Run DDU. Select your GPU vendor (NVIDIA, AMD, Intel).
5) Click Clean and restart.
6) After reboot, install the fresh GPU driver you downloaded earlier.
7) Reconnect to the internet and test.
If crashes continue after a clean reinstall, the base operating system may be damaged. The next step repairs Windows system files so drivers have a healthy foundation.
Repair Windows System Files with SFC and DISM
Corrupted system files can cause driver instability. Run these tools from an elevated Command Prompt or PowerShell.
Steps:
1) Open Start, type cmd, right-click Command Prompt, choose Run as administrator.
2) Run System File Checker:
– sfc /scannow
3) If SFC finds corruption it cannot fix, run DISM:
– DISM /Online /Cleanup-Image /RestoreHealth
4) Reboot and run sfc /scannow again to confirm repairs.
If you still see crashes, check disk health and the file system next. A failing or corrupt drive can mimic driver faults and trigger kernel exceptions.
Check Disk and File System Health with CHKDSK and SMART Tools
A failing or corrupt drive can trigger kernel exceptions.
Do this:
1) Check the file system:
– Open an elevated Command Prompt and run:
– chkdsk C: /f
– Accept the prompt to schedule at next restart. Reboot and allow the scan to complete.
2) Review SMART health:
– Use tools such as CrystalDiskInfo to check drive SMART status.
– If you see reallocated sectors or pending sector counts rising, back up and plan a drive replacement.
If the BSOD began after a recent change, roll back those updates or drivers next. Reversing recent changes quickly isolates the trigger and restores stability.
Undo Recent Changes: Roll Back Drivers and Uninstall Problematic Updates
Sudden BSODs often follow updates.
Try these reversals:
– Undo driver changes:
1) Device Manager > device Properties > Driver > Roll Back Driver.
2) If roll back is unavailable, uninstall the device and driver, then install a known stable version.
– Remove recent Windows updates:
1) Settings > Update & Security > View update history > Uninstall updates.
2) Remove the most recent quality update and test.
If the crash persists, fine-tune power and startup behavior to reduce edge-case failures. These tweaks help avoid problematic low-power transitions that expose fragile drivers.
Power and Startup Tweaks: Disable Fast Startup, Adjust PCIe Link State
Fast startup and aggressive power saving can expose driver bugs.
Apply these tweaks:
1) Disable Fast Startup:
– Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable.
– Uncheck Turn on fast startup. Save.
2) Adjust PCIe Link State Power Management:
– Power Options > Change plan settings > Change advanced power settings.
– PCI Express > Link State Power Management > Off.
3) Test sleep or wake cycles and cold boots.
If you overclock or run older firmware, reset and update next. Hardware instability can look like a driver fault and cause the same BSOD.
Firmware and Overclocking: Reset BIOS or UEFI, Update Device Firmware
Unstable BIOS settings or outdated firmware can crash drivers.
Take these steps:
1) Reset overclocks:
– Set CPU, GPU, and RAM to stock speeds and voltages.
– Disable XMP for testing if memory instability is suspected.
2) Update BIOS or UEFI:
– Visit your motherboard or laptop support page.
– Apply the latest stable BIOS or UEFI that matches your device.
3) Update device firmware:
– Check SSD firmware using the vendor tool (Samsung Magician, Crucial Storage Executive, Intel MAS).
– Update GPU, dock, or docking station firmware if available.
With firmware and power stabilized, you can recover a non-bootable system using built-in recovery tools. The next section shows how to use WinRE to regain access when Windows will not start.
If Windows Will Not Boot: Use WinRE for Startup Repair and System Restore
When you cannot reach the desktop, use the Windows Recovery Environment (WinRE).
Access and repair:
1) Enter WinRE:
– Force-interrupt boot three times, or boot from a Windows 10 USB and click Repair your computer.
2) Run Startup Repair:
– Troubleshoot > Advanced options > Startup Repair. Let it complete and reboot.
3) Use System Restore:
– Advanced options > System Restore > pick a restore point before the BSOD started.
4) Uninstall updates from WinRE:
– Advanced options > Uninstall Updates > remove recent quality or feature updates.
5) Command line repairs (advanced):
– Open Command Prompt and run:
– sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
– bootrec /fixmbr
– bootrec /fixboot
– bootrec /rebuildbcd
If the system boots but remains unstable, consider a repair that keeps your data intact. The next section explains when to choose an in-place upgrade repair and when to use Reset this PC.
In-Place Upgrade Repair vs Reset This PC (Keep Files): What to Choose
When targeted fixes fail, a repair install can replace system files without wiping data.
Choose the right option:
– In-place upgrade repair:
1) Download the latest Windows 10 ISO with the Media Creation Tool.
2) Run setup.exe from the desktop.
3) Choose Keep personal files and apps.
4) Let the installer refresh Windows components.
Use this first if you still suspect system file damage.
– Reset this PC (Keep my files):
1) Settings > Update & Security > Recovery > Reset this PC.
2) Select Keep my files.
3) Reinstall Windows while removing apps and drivers.
Use this if the system remains unstable after a repair install.
If the error survives a clean baseline, collect deeper diagnostics to find the exact driver or hardware fault. The next step uses advanced tools to force crashes that point at the flawed component.
Advanced Diagnostics: Driver Verifier, Memory Tests, and Stress Testing
Advanced tools can expose faulty third-party drivers and weak hardware.
Proceed carefully:
1) Driver Verifier (use with caution):
– Open an elevated Command Prompt and run:
– verifier
– Choose Create standard settings > Automatically select unsigned drivers and third-party drivers only.
– Reboot and use the PC. If a BSOD points to a specific driver, disable Verifier:
– verifier /reset
– Reboot.
– Do not enable Verifier for Microsoft drivers or on unstable systems for long periods.
2) Memory testing:
– Run MemTest86 from a bootable USB for several passes.
– If errors appear, test sticks one by one and reseat modules. Replace faulty RAM.
3) GPU and storage stress tests:
– Use vendor tools or benchmarking suites at stock clocks to confirm stability.
– Run vendor SSD diagnostics and recheck SMART data.
With the root cause identified and fixed, keep the system stable with good driver hygiene and monitoring. A few simple habits prevent the error from returning.
Post-Fix Prevention: Driver Hygiene, Update Discipline, and Monitoring
Prevent the error from returning with simple habits.
Best practices:
– Prefer OEM-approved drivers for laptops. On desktops, check both motherboard and component vendors.
– Avoid automatic driver updaters. Install drivers you need, not everything offered.
– Keep Windows 10 updated, but delay optional driver updates until they prove stable.
– Create a restore point before major driver or Windows updates.
– Export a list of drivers and versions after you reach a stable state.
– Monitor hardware health: temperatures, SMART attributes, fan curves.
– Keep a bootable Windows USB and your key installers handy for quick recovery.
If you ever see the system exception thread not handled windows 10 error again, you now have a checklist to fix it fast and with minimal risk. Let us close with a brief summary to reinforce the plan.
Conclusion
You can fix the System Thread Exception Not Handled BSOD on Windows 10 by following a structured path: secure backups, reach Safe Mode, identify the faulty driver, and apply targeted repairs. Start with the GPU, then review storage, network, and USB drivers. Repair system files and check disk health. If Windows will not boot, use WinRE. As a last resort, perform an in-place repair or a reset that keeps your files.
With clean drivers, healthy firmware, and careful updates, the error usually disappears for good. Keep your recovery tools close and your drivers tidy. You will spend more time working and less time staring at a blue screen.
Frequently Asked Questions
Why does System Thread Exception Not Handled keep happening on Windows 10?
The error keeps returning when a bad driver loads early at boot. Graphics drivers cause most repeats, but storage, network, and USB or HID drivers can also fail. If you updated a driver or Windows recently, mismatched versions may be at fault. Corrupted system files or unstable overclocks can make a borderline driver crash more often. Fix it by rolling back or clean-installing the related driver, repairing system files with SFC and DISM, and disabling Fast Startup. If you overclock, return to stock settings and update your BIOS or UEFI. If it still happens, run Driver Verifier for third-party drivers and test RAM with MemTest86.
How do I fix system exception thread not handled if I cannot boot into Windows 10?
Enter the Windows Recovery Environment. Run Startup Repair first. If the loop continues, use System Restore to roll back to a working state. Uninstall recent updates from Advanced options if the BSOD started after Patch Tuesday. From Command Prompt, run SFC with offline parameters and DISM if needed. You can also enter Safe Mode, use DDU to clean GPU drivers, and reinstall a stable driver while offline. As a last step, perform an in-place upgrade repair from a Windows 10 USB while choosing Keep personal files and apps.
Is this BSOD caused by hardware or drivers, and will resetting Windows 10 delete my files?
Most cases come from drivers, not hardware. However, bad RAM, failing SSDs, or unstable power and overclocks can trigger the same stop error. Test memory and check drive SMART data to rule out hardware. A Reset this PC with Keep my files keeps your personal files but removes desktop apps and drivers; you will have to reinstall programs. If you want to keep apps too, try an in-place upgrade repair first. Always back up important data before any major repair step.