Here are six simple steps to fix this annoying Windows 10 error. The ” SYSTEM THREAD EXCEPTION NOT HANDLED ” is a common Windows 10 error, mainly caused by outdated or incompatible drivers.
What is more difficult to fix than other BSODs is that various drivers can cause problems and sometimes your computer may not be able to detect them. That is why the first step a user should take to resolve this error is to find the exact driver that caused the problem.
The following is a method to fix the SYSTEM THREAD EXCEPTION NOT HANDLED error in Windows 10.
1. Boot Into Safe Mode
The first step users should take before attempting to solve this problem is to start their computer in safe mode. Depending on your preference and whether you can start the computer at the login screen, there are several ways to do this:
Boot Into Safe Mode via Settings
- Click on the Start button, then select Settings.
- Navigate to Update & Security then click on Recovery.
- Under Advanced startup, click on Restart now.
- When your PC restarts the Choose an option screen should appear.
- From here go to Troubleshoot > Advanced options > Startup Settings. Then click on Restart
- When your PC reboots, press F5 to boot your computer in Safe Mode with Networking.

From the Sign-In Screen
- Simply hold down Shift and select the Power button followed by Restart.
- Follow steps 4, 5, and 6 from the section above.
From a Blank Screen
- If you’re unable to reach the sign-in screen, then follow these steps.
- Hold down the power button on your device for 10 seconds to switch it off.
- Press the power button again to boot it.
- As soon as your PC starts i.e., the manufacturer’s logo appears, press the power button again for 10 seconds.
- Press the power button to start your device.
- If done correctly, your computer will boot into the Windows Recovery Environment.
- Follow steps 4, 5, and 6 from the first section.
2. Finding Which Driver is Responsible
Since the error is most likely caused by a faulty driver, you can use the Windows registry to find out which one.
To do this, simply follow these steps:
- Press Windows Key + R and in the Run dialog box, type eventvwr.
- Navigate to the Windows Logs menu and expand it, then select System.
- Look for a log named system_thread_exception_not_handled and click on it to find out which driver is causing the issue.

Usually, the associated driver is going to be a display driver or a network driver since these are notorious for causing this BSOD. If the associated file happens to be nvlddmkm.sys, you can have a look at some easy ways to fix it.
3. Rollback or Update the Drivers
Depending on which driver is responsible for the SYSTEM THREAD EXCEPTION NOT HANDLED error, you may need to update or reinstall the related driver.
If the driver has not been updated for a long time, updating the driver will probably solve the problem. If the driver has been updated recently, it is better to roll back the driver or reinstall the update.
Related: How to Solve the “RPC Server is Unavailable” Error in Windows 10
How to Update Drivers on Windows 10
- Press Windows Key + R and type in devmgmt.msc to open the Device Manager.
- Navigate to the associated device and expand the menu. For instance, if the error was being caused by a display driver, you would have to expand the Display adapters option.
- Right-click on the driver and click Update driver.
- In the dialog box that opens, click on Search automatically for updated driver software.
- Windows will then automatically search the web for the latest drivers and install them.

How to Rollback Drivers on Windows 10
- Open Device Manager and navigate to the driver in question.
- Expand the menu and right-click on the driver.
- Click on Properties.
- Under the Driver tab, click on Roll Back Driver.
- Windows will automatically rollback to the last available version of the driver.

4. Rename the Faulty File
When retrieving the file name associated with an unhandled system thread exception error, the user must rename the file. Doing so will cause Windows to create a new copy and reinstall it. The driver files are located in C:\ Windows\ System32\ drivers
Follow these steps to rename the file:
- Open File Explorer and go to C:\Windows\System32\drivers
- Look for the affected driver
- Click on it and press F2.
- Replace the filename extension with .old.
- Hit Enter and restart your computer.
5. Use SFC and DISM to Repair System Files
SFC and DISM are two powerful tools that all Windows users can use. Combined, they can find and fix almost all system-related errors. They are also easy to implement.
Related: How to Fix the VIDEO_TDR_FAILURE BSOD in Windows 10
Make sure to create a system restore point, as these commands will change system files.
How to Use DISM
- Run Command Prompt as Administrator
- In the console, type DISM /Online /Cleanup-Image /ScanHealth and press Enter.
- Wait for Windows to finish scanning. Then type DISM /Online /Cleanup-image /RestoreHealth
- Windows will repair all the problems that were found during the scan.

How to Use SFC
- In the Start menu search bar, type cmd then right-click on Command Prompt and run it as administrator.
- In the console, enter sfc /scannow
- Be patient as Windows will take time to scan and replace corrupt system files.

6. Use System Restore to Restore Your PC
If the problem is still not resolved, you will have to use System Restore as a last resort. System Restore is a function that restores Windows to its previous state. These restore points are created periodically when new software is installed. Alternatively, you can configure Windows to create a restore point every day
How to Use System Restore

- In the Start menu search bar, type Control Panel and click open it.
- In the Control Panel search bar, enter Recovery and open it from the results.
- Click on Open System Restore.
- Hit Next and select a restore point from the list.
- Click on Finish.
Exception Handled
The tips listed above provide a simple solution to the troubles caused by BSOD such as SYSTEM THREAD EXCEPTION NOT HANDLED. The best part is that most of the tips can also be used to diagnose many other common blue screen of death (BSOD) errors in Windows.