How to Fix System Thread Exception Not Handled (Windows BSOD)

 Fix the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED BSOD error on Windows 10 and 11. This guide covers identifying the faulty driver, safe mode fixes, SFC/DISM commands, and hardware checks.

A sudden blue screen with the error “SYSTEM_THREAD_EXCEPTION_NOT_HANDLED” is one of the more alarming things that can happen to a Windows PC, but it is usually fixable without professional help. This particular Blue Screen of Death tells you that a system thread, essentially a process running at the core of Windows, generated an error that the operating system could not handle or recover from. The computer stops to prevent potential damage and shows you the BSOD. The good news is that this error is almost always caused by a driver issue, and driver issues have clear solutions.

This guide walks through every fix in order from easiest to most involved so you can get back to a stable system as quickly as possible.

What Does SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Mean?

The error name tells you what happened at a technical level: a thread running inside the Windows kernel encountered an exception (an unexpected condition or error) and the operating system had no way to handle it gracefully. Rather than continuing in an unstable state, Windows crashes to a blue screen.

In most cases the BSOD screen also displays a file name ending in .sys, which is a system driver file. That file name is your most important clue because it tells you which driver caused the crash.

Common file names that appear with this error and what they point to:

• nvlddmkm.sys: NVIDIA graphics driver
• amdkmdag.sys or atikmdag.sys: AMD graphics driver
• iaStorA.sys: Intel storage controller driver
• netwtw06.sys: Intel Wi-Fi driver
• ntfs.sys: NTFS file system (may indicate corrupted system files or storage issues)
• dxgkrnl.sys: DirectX graphics kernel (GPU related)

If you see a file name on your BSOD, note it before you do anything else. It saves significant troubleshooting time.

Step 1: Boot Into Safe Mode

If Windows crashes during normal startup, Safe Mode lets you get into the operating system with only the essential drivers loaded. This gives you a stable environment to troubleshoot without the crash-causing driver running.

How to enter Safe Mode from Windows 11 or 10:

1. Hold the Shift key and click Restart from the Start menu or the sign-in screen.
2. The PC restarts into Windows Recovery Environment (WinRE).
3. Go to Troubleshoot > Advanced Options > Startup Settings > Restart.
4. After the restart, press 4 or F4 for Safe Mode, or 5 or F5 for Safe Mode with Networking.

If Windows cannot boot at all, turn the PC off by holding the power button three times in a row during startup. On the third failure, Windows automatically boots into WinRE.

Step 2: Identify and Update the Problem Driver

If you saw a .sys file name on the BSOD, that file tells you which driver to target.

In Safe Mode or normal Windows:

1. Right-click the Start button and select Device Manager.
2. Look for any devices with a yellow warning triangle.
3. Right-click the device associated with your .sys file and select Update driver.

For graphics drivers specifically, using the manufacturer’s website is more reliable than Device Manager.

NVIDIA: Download the latest driver from nvidia.com. Before installing, use Display Driver Uninstaller (DDU) in Safe Mode to fully remove the existing driver. Then install the fresh download.

AMD: Download from amd.com. Use the AMD Cleanup Utility to fully remove the existing driver before installing the new one.

General drivers (network, chipset, storage): Go to your motherboard manufacturer’s website (ASUS, MSI, Gigabyte, ASRock, etc.) and download the latest drivers for your board model.

Step 3: Run System File Checker (SFC)

Corrupted system files can cause the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED error even when drivers are fine. The built-in SFC tool scans Windows system files and repairs any it finds corrupted.

1. Open Command Prompt as administrator. Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin).
2. Type the following and press Enter:

sfc /scannow

3. Wait for the scan to complete. This can take 10 to 20 minutes.
4. If SFC finds and repairs files, restart your PC.

If SFC reports that it found issues but could not repair them, run DISM first and then try SFC again.

Step 4: Run DISM to Repair Windows

DISM (Deployment Image Servicing and Management) repairs the Windows component store that SFC draws from. Running it before SFC gives the repair tool a clean base to work with.

1. Open Command Prompt as administrator.
2. Run this command:

DISM /Online /Cleanup-Image /RestoreHealth

3. This process can take 15 to 30 minutes and requires an internet connection.
4. After it completes, run sfc /scannow again.
5. Restart when both complete.

Step 5: Check Windows Updates

An outdated version of Windows can have compatibility issues with newer drivers or hardware. Keeping Windows fully updated removes many potential causes of BSOD errors.

1. Go to Settings > Windows Update.
2. Click Check for updates and install everything available.
3. Restart after updates complete.

Also check the Optional updates section, which sometimes contains driver updates for your specific hardware that do not install automatically.

Step 6: Test Your RAM

Faulty RAM is a less common but real cause of the system thread exception not handled error. The Windows Memory Diagnostic tool checks RAM for errors.

1. Press Windows + R, type mdsched.exe, and press Enter.
2. Choose Restart now and check for problems.
3. The PC restarts and runs memory tests automatically.
4. After the test completes and Windows restarts, check the results by searching for Event Viewer in the Start menu and looking under Windows Logs > System for MemoryDiagnostics events.

If the test finds errors, your RAM is faulty and needs replacement.

Step 7: Advanced Fixes

If the above steps do not resolve the error, these additional measures address less common causes.

Update BIOS/UEFI firmware: Outdated firmware can cause compatibility issues with hardware and drivers. Go to your motherboard or laptop manufacturer’s website, find your model, and follow their instructions for a BIOS update. This is a more advanced step and should be done carefully following the manufacturer’s guide exactly.

Disable overclocking: If your CPU, GPU, or RAM is overclocked, instability from the overclock can cause BSOD errors. Restore default clock speeds through BIOS and test whether the crashes stop.

Perform a System Restore: If the crashes started after a specific change (a Windows update, a new driver, or newly installed software), rolling back to a restore point from before that change may resolve it.

1. Search for Create a restore point in the Start menu.
2. Click System Restore.
3. Choose a restore point from before the error started.
4. Follow the prompts to complete the restore.

Common File Names and What to Do

When to Get Professional Help

Contact a repair technician or Microsoft Support if:

• The BSOD occurs repeatedly after all the above steps
• The Windows Memory Diagnostic reports RAM errors and replacing the RAM does not stop the crashes
• The error appears during Windows installation or recovery, suggesting storage hardware failure
• You cannot boot into Safe Mode at all and WinRE tools do not resolve the issue

These scenarios point to hardware failure that software fixes cannot address.

The Short Answer

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED is a Windows BSOD error caused in the vast majority of cases by a faulty, outdated, or incompatible driver. Check the .sys file name on the blue screen, boot into Safe Mode if needed, update or cleanly reinstall the driver linked to that file, run SFC and DISM to repair system files, and check Windows updates. For persistent crashes, test your RAM and consider a BIOS update. Most cases resolve at the driver step without needing to go further.