Fix System Thread Exception Not Handled Windows 10

If you see the System Thread Exception Not Handled blue screen error on Windows 10, the fix usually involves updating or rolling back a driver, especially a graphics or storage driver. This stop code means a system thread generated an exception that the error handler did not catch, and Windows shuts down to prevent damage. Below is a complete guide to resolving it, from quick checks to advanced commands.

What Does This Error Mean?

The error is a bug check (also called a STOP code) that Windows 10 displays on a blue screen (BSOD) when a critical system thread encounters an unexpected condition. It is often accompanied by a file name, such as nvlddmkm.sys (NVIDIA graphics) or iaStorA.sys (Intel storage). That file name is your biggest clue: the faulty driver is usually the one listed.

This error is not a hardware failure by default; it is a software conflict, a corrupted driver, or an incompatible update. The system thread that failed might belong to a driver, a kernel component, or a service. Because the thread cannot be handled, Windows forces a restart to avoid data corruption.

Why Does It Happen?

Common triggers include:

Outdated or buggy drivers – especially GPU, network, or storage drivers.
Incompatible Windows updates – a recent update may clash with an older driver.
Corrupted system files – often from a failed update or disk errors.
Overclocking – unstable CPU or memory overclocks can cause this.
Faulty RAM – though less common, memory errors can trigger it.

If the error happens during installation or right after a hardware change, suspect driver incompatibility. If it happens after a Windows Update, suspect the update itself.

Step-by-Step Fixes

Try these in order. Stop when the error stops appearing.

Note the file name in the error. Write it down or take a photo. It tells you which driver to target.
Boot into Safe Mode. Restart your PC, and as it boots, press F8 (or hold Shift while clicking Restart) to access Advanced Startup Options. Choose Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 or F4 for Safe Mode.
Uninstall the problematic driver. In Safe Mode, open Device Manager (right-click Start), find the device (e.g., Display adapters), right-click it, and choose Uninstall device. Check “Delete the driver software for this device” if available, then restart.
Run Windows Update. After restarting, go to Settings > Update & Security > Windows Update and install all updates. This may replace the driver with a compatible version.
Use System Restore. If the error started recently, restore your PC to a point before the issue. Search for “Create a restore point,” click System Restore, and follow the wizard.
Run the Blue Screen Troubleshooter. In Windows 10, go to Settings > Update & Security > Troubleshoot and run the “Blue Screen” troubleshooter. It can automatically detect and fix common issues.
Check for disk errors. Open Command Prompt as Administrator and run chkdsk /f /r. Restart when prompted.
Run SFC and DISM. In Command Prompt, run sfc /scannow. Then run DISM /Online /Cleanup-Image /RestoreHealth. These repair corrupted system files.
Disable overclocking. If you overclocked your CPU or RAM, revert to default settings in BIOS/UEFI.

If the Error Persists: Advanced Options

If the above fails, try these more advanced steps:

Update the BIOS/UEFI. Check your motherboard manufacturer’s website for a newer version.
Test your RAM. Use Windows Memory Diagnostic (search “Windows Memory Diagnostic”) or a third-party tool like MemTest86.
Check the minidump file. The error creates a .dmp file in C:\Windows\Minidump. Use a tool like BlueScreenView to read it and identify the exact driver.
Perform a clean install. If nothing works, backup your files and reinstall Windows 10. This eliminates any lingering software conflict.

If the error mentions a specific file, search that file name online to see if it belongs to a known problematic driver. For example, rtwlane.sys is a Realtek wireless driver, and dxgmms2.sys relates to DirectX graphics.

Prevention Tips

Once fixed, avoid future occurrences by:

Keeping Windows Update on automatic.
Only downloading drivers from official manufacturer websites.
Avoiding “driver booster” tools that may install incompatible versions.
Not overclocking unless you know it’s stable.
Regularly cleaning your PC’s internals to prevent overheating, which can cause random BSODs.

Frequently Asked Questions

Will I lose my files if I get this error?

No, the blue screen itself does not delete files. However, if the error is caused by disk corruption, you could lose unsaved work. Always back up important data regularly.

Can this error damage my hardware?

No, the error is a software protection mechanism. It stops the system before a driver can cause memory corruption. Hardware damage is unlikely unless the root cause is overheating or a failing power supply.

Why does the error happen after a Windows Update?

Windows Update may install a driver that is incompatible with your hardware or an older driver. Windows sometimes replaces a working driver with a generic one. Rolling back the driver (Device Manager > Driver tab > Roll Back Driver) often fixes it.

Is it safe to keep using my PC after a BSOD?

It is safe to restart and try to fix the issue, but do not ignore repeated errors. Each BSOD could indicate a deeper problem that may lead to data loss if left unaddressed.

How do I know which driver is causing the problem?

The error message usually lists the driver file name. If not, open the minidump file with a tool like BlueScreenView. Alternatively, check the Windows Event Viewer under “System” for errors around the time of the crash.

Can a faulty hard drive cause this error?

Yes, a failing hard drive can corrupt system files and trigger this error. Run chkdsk and check the drive’s health with tools like CrystalDiskInfo (for SSDs/HDDs).

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →