How to Resolve the “SYSTEM THREAD EXCEPTION NOT HANDLED” Error on Windows 10
The “SYSTEM THREAD EXCEPTION NOT HANDLED” error is a common Blue Screen of Death (BSOD) issue on Windows 10 that can cause your system to crash unexpectedly. This error typically occurs due to issues with outdated or incompatible drivers, corrupted system files, or hardware problems. The error message is often followed by a file name, such as nvlddmkm.sys or igdkmd64.sys, which can help identify the problematic driver.
In this guide, we’ll cover several effective methods to fix the “SYSTEM THREAD EXCEPTION NOT HANDLED” error and get your Windows 10 PC running smoothly again.
Common Causes of the “SYSTEM THREAD EXCEPTION NOT HANDLED” Error
Before diving into the solutions, it’s helpful to understand the common causes of this error:
- Outdated or incompatible drivers.
- Corrupt or damaged system files.
- Driver conflicts after a Windows update.
- Overclocking or hardware issues.
Method 1: Boot Into Safe Mode
Before attempting any fixes, it’s recommended to boot your system into Safe Mode. This will allow your PC to run with minimal drivers and services, making it easier to troubleshoot the problem.
Steps to Boot into Safe Mode:
- Restart Your PC:
- Press the power button to turn off your PC. Turn it back on and as soon as Windows starts to load, press and hold the power button again to turn it off. Repeat this process two more times until you see the Windows Recovery Environment (WinRE) screen.
- Select Troubleshoot:
- Once in the recovery environment, select Troubleshoot > Advanced options > Startup Settings.
- Choose Safe Mode:
- Click Restart, and then select Safe Mode with Networking by pressing F5.
Once in Safe Mode, you can start troubleshooting the error.
Method 2: Update or Reinstall Faulty Drivers
One of the most common reasons for the “SYSTEM THREAD EXCEPTION NOT HANDLED” error is an outdated or incompatible driver. Identifying and updating the faulty driver can resolve the issue.
Steps to Update or Reinstall Drivers:
- Open Device Manager:
- Press
Windows + X
and select Device Manager from the list.
- Press
- Find Faulty Driver:
- In Device Manager, look for drivers with a yellow warning icon. These are usually the problematic drivers. Common culprits include graphics drivers (Display adapters) and network drivers (Network adapters).
- Update Driver:
- Right-click the faulty driver and select Update driver. Choose Search automatically for updated driver software.
- Reinstall Driver (If Updating Doesn’t Work):
- If updating the driver doesn’t fix the issue, you can uninstall the driver by right-clicking it and selecting Uninstall device. Restart your computer, and Windows will automatically reinstall the driver.
Method 3: Run the System File Checker (SFC) and DISM
If the error is caused by corrupted system files, running the System File Checker (SFC) and DISM tools can help repair the damage.
Steps to Run SFC:
- Open Command Prompt as Admin:
- Press
Windows + X
and select Command Prompt (Admin).
- Press
- Run SFC Command:
- Type the following command and press Enter:
bash
sfc /scannow
- Type the following command and press Enter:
- Wait for the Scan to Complete:
- The scan may take some time. Once completed, restart your PC to see if the error is resolved.
Steps to Run DISM:
If SFC doesn’t fix the problem, run DISM to repair the Windows image.
- Open Command Prompt as Admin:
- Open Command Prompt (Admin) as described above.
- Run DISM Command:
- Type the following command and press Enter:
mathematica
DISM /Online /Cleanup-Image /RestoreHealth
- Type the following command and press Enter:
- Restart Your PC:
- After the scan is complete, restart your computer to apply the changes.
Method 4: Roll Back Recent Windows Updates or Drivers
If the error started after a recent Windows update or driver installation, rolling back to a previous version may resolve the issue.
Steps to Roll Back Windows Updates:
- Open Settings:
- Press
Windows + I
to open Settings.
- Press
- Go to Update & Security:
- Select Update & Security > View update history.
- Uninstall Updates:
- Click Uninstall updates at the top of the screen. Choose the most recent update that might be causing the problem and click Uninstall.
Steps to Roll Back Drivers:
- Open Device Manager:
- Press
Windows + X
and select Device Manager.
- Press
- Find the Problematic Driver:
- Right-click the driver you suspect is causing the issue and select Properties.
- Roll Back Driver:
- In the Driver tab, click Roll Back Driver if the option is available.
Method 5: Perform a System Restore
If the error persists, you can use System Restore to revert your system to a previous point in time when it was functioning correctly.
Steps to Perform System Restore:
- Open System Restore:
- Press
Windows + S
and type System Restore. Select Create a restore point from the results.
- Press
- Launch System Restore:
- In the System Protection tab, click System Restore.
- Select a Restore Point:
- Choose a restore point created before the error started occurring and follow the on-screen instructions.
- Restore Your System:
- After the restoration process, your PC will restart, and the issue should be resolved.
Method 6: Check for Hardware Issues
If none of the above methods work, the SYSTEM THREAD EXCEPTION NOT HANDLED error might be caused by hardware failure, such as faulty RAM or a malfunctioning hard drive. Running hardware diagnostics can help identify the problem.
Steps to Run Memory Diagnostics:
- Open Windows Memory Diagnostic:
- Press
Windows + R
, type mdsched.exe, and press Enter.
- Press
- Restart and Check for Problems:
- Select Restart now and check for problems. Your PC will reboot and scan for memory issues.
- Review the Results:
- After the scan is complete, check the results for any hardware errors that need attention.
Conclusion
The “SYSTEM THREAD EXCEPTION NOT HANDLED” error on Windows 10 can be caused by a range of issues, from driver problems to hardware malfunctions. By following the steps outlined in this guide—updating drivers, using SFC and DISM, rolling back updates, and checking for hardware issues—you should be able to resolve the error and get your system back on track.
If the issue persists after trying all these methods, consider seeking professional assistance or performing a clean installation of Windows 10.