How to fix the “System Thread Exception Not Handled” Error in Windows 10.


When you press the power button on your computer tower or laptop, you usually expect it to power on and load without error. Unfortunately, users using Windows 10 computers who do not understand what device drivers are or how to update device drivers may encounter a blue screen of death instead. This blue screen of death may appear immediately after booting your computer, or it may take ten to fifteen seconds before the laptop encounters the fault that causes the notorious blue screen of death. In the instance of the error code “system thread exception not handled,” this issue is typically noticed on boot up and can cause your computer to become trapped in a reboot loop, rendering it inoperable. This post will look at what this code implies, why it occurs, and five techniques for fixing it.

What exactly does the error “System Thread Exception Not Handled” mean?

The “system thread exception not handled” error indicates that a system thread in your computer created an exception for a missed mistake by the handler. A blue screen of death has occurred due to it failing to detect and correct the error, leading the computer to attempt to gather information about the error. The following numbers frequently follow this stop code: 0x0000007E, 0x1000007E, or, if you’re lucky, the file name causing the issue, such as atikmdag. Sys, nvlddmkm. Sys, igdkmd64.sys, and so on. Unfortunately, the computer nearly always reboots with this problem, which forces you to utilize safe mode to break.

When does this error occur, and why does it happen?

The “system thread exception not handled” problem usually appears when you restart or restart your computer after being shut down. It can, however, occur seldom and is known to appear when the user is using software that requires specialized graphic drivers to function. This issue occurs when incompatible drivers (most typically graphic drivers) are installed on the computer and are either old, corrupted, or incorrect. Malware can modify graphic drivers, and they can also be wrongly installed, which is why you get the “system thread exception not handled” error in Windows 10.

The error code is associated with a file name: What Does It Imply?

If you’re lucky, the “system thread exception not handled” error code will be accompanied by a file name indicating which graphic driver is causing the issue. You will resolve the error if you upgrade or repair this graphic driver. Some of the most common file names associated with this BSOD error are the following.

  • Atikmdag. Sys — This graphic driver is part of the ATI Radeon Family and is associated with your ATI graphic card. If you have an AMD graphics card installed on your computer, it signifies that the drivers for this device are out of date or have been loaded incorrectly.
  • Nvlddmkm. Sys – this visual driver is for the Nvidia Windows kernel driver and is associated with your Nvidia video have an Nvidia graphics card installed, it signifies that the drivers for this card are either out of date or wrongly installed.
  • Dxgmms2. Sys – this is linked to the DirectX drivers you’ve installed.
  • Ntfs. Sys – is a Windows NT Server file.
  • Bcmwl63a. sys- is the Broadcom 802.11 Network Adaptor driver. This adaptor necessitates the use of a wireless driver created by Broadcom Corporation. If you install this incorrectly or are out of date, you will most likely receive the “system thread exception not handled” issue.
  • CMUDA.sys- is the driver connected with USB device audio.

If you see any of the above when the issue appears, it implies you need to uninstall and reinstall the driver or update the driver. If the error number is associated with a separate system file, you will need to look up the driver file name online to determine which driver is causing the problem. Suppose the problem does not appear in any system files. In that case, you will need to update all main drivers on your computer, including any network, LAN, wireless, sound, and audio drivers, and display drivers (graphics).

How Do I Enter Safe Mode in Windows 10?

The first thing you’ll want to do is boot into safe mode, which will allow you to break the reboot loop that you’ll indeed get caught in. Because you are unlikely to access your settings, we will have you boot into Windows Recovery Environment (winRE) before entering safe mode.

  1. Hold down the power button on your computer for at least 10 seconds to turn it off. To turn it back on after being entirely turned off, hit the power button once again.
  2. The power button hold down for 10 seconds as soon as you see any indication that Windows has begun (such as the logo) to switch it off again. To turn it back on, press the power button.
  3. Repeat this step until your device restarts completely, and you enter winRE.

To enter safe mode from winRE, select the “Troubleshoot” option from the list. Then, choose “Advanced Options,” “Startup settings,” and “restart.” After restarting your computer, you will be presented with a menu of alternatives. You wish to enter Safe Mode with Networking by pressing F5.

5 Ways to fixing “System Thread Exception Not Handled” Errors on Windows 10 Systems

1. Find out which driver is the default.

There are numerous ways to accomplish this, but the simplest is to examine the system log, which records events. You’ll need to launch the event viewer to achieve this.

  1. To open the “run” dialogue box, press the Windows key + R on your keyboard.
  2. Enter “eventvwr” into the box and press OK.
  3. Scroll down to “Windows logs” and click to bring up the menu drop-down.
  4. Select “system” from the drop-down option to view all recent occurrences.
  5. Determine which driver is responsible for the “system thread exception not handled” problem.

2. Reinstall, rollback, or update your drivers

The simplest way to resolve mismatched drivers is to update them, roll them back to a prior version, or reinstall them if you have the most recent version. To do so, launch your device manager by typing “device manager” into your computer’s search or by pressing the Windows key + X and selecting “device management.”

  • To update your drivers, go through your device list, right-click on each piece of hardware with a driver, and select update. All included disk drives, audio devices, network adaptors, sound devices, and display adaptors. Select “update driver,” it will automatically look for the most recently updated version.
  • To revert your drivers, navigate to your device list and right-click on each piece of hardware that has a driver, then select “properties.” You should then go to the “driver” page and select the “rollback” option. Yes, make sure to click!
  • To reinstall a driver, you must first uninstall the device. You must then browse the device manufacturer’s website, locate your device, and manually download and install the most recent driver for that device.

3. Rename the erroneous driver

If you have a file name related to the “system thread exception not handled” error code, you may always rename the driver, and Windows will retrieve a new copy and reinstall it. First, you must determine which hard drive the driver is installed on.

  1. Search for “command prompt” or type “cmd” into your computer’s search bar to launch the command prompt software.
  2. Enter C: (hit enter) cd windowssystem32drivers (hit enter) ren FILENAME.sys FILENAME.old into the command prompt box (replace filename here with the faulty driver file listed with the error code).
  3. Then press the “exit” key to restart the computer.

4. Restore the system files

If you suspect that you have corrupted system files interfering with your device drivers, you can repair them using Windows repair tools such as SFC and DISM.

  1. Open the command prompt as an administrator to run SFC. When in safe mode, look for the command prompt option in the list of “advanced settings.”
  2. Enter “SFC /scannow” and press Enter key. This will replace any system files that have been destroyed, lost, or modified.

Note: If you encounter an SFC /Scannow issue while running the scan, we have a specific post on how to resolve “Windows Resource Protection Could Not Perform The Requested Operation.”

If the problem persists after executing SFC, you can use DISM to restore your computer’s “health.”

  1. Open the command prompt as administrator and enter the following commands one by one.
  2. Exe /Online /Image-cleanup /Scanhealth
  3. Exe /Online /Image-cleaning /Health-restoration

5. Revert your computer to a previous version

If you have backups of your computer system, you can restore it to when you were not receiving the “system thread exception not handled” error code. To do so, you’ll need either a Windows system repair disc or a recovery disc.

  1. the system repair disc into the PC and select your preferred language.
  2. Select troubleshoot advanced options after clicking on the repair option.
  3. Then select System Restore and follow the on-screen directions.

While most individuals will resolve the issue by uninstalling, reinstalling, and upgrading out-of-date drivers, those who continue to receive the error after completing all five of the above steps may want to consider a clean reinstallation of the operating system. A completely clean and reinstallation of the operating system will return you to “factory settings,” requiring you to upgrade your operating system and primary drivers to the most recent versions.


Please enter your comment!
Please enter your name here