How to Fix System Thread Exception Not Handled Error on Windows 10 

How to Resolve “System Thread Exception not handled” Error on Windows 10 

 

When you press the button on your PC tower or laptop, usually, you want the computer to power on and load up without any error. However, those on Windows 10 computers that are not familiar with the windows drivers and are not aware of how to update the drivers may end up with a blue screen. This blue screen of death may pop after you start your PC or take a little bit of time before the computer runs to show the error that is creating the trouble of the notorious blue screen of death.

More Interested For You: How To Resolve The Audio Problem – Realtek Digital Output

In the case of the error code, “system_thread_exception_not_handled” this error is generally viewed on boot up and can be the cause to get your computer stuck in a reboot loop. So, under such circumstances, it becomes next to impossible to use your PC. This article will tell you about what the code is, how it takes place, and will tell you the best possible methods to fix the error. 

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

The “system_thread_exception_not_handled” error shows that a system thread in your computer has produced an exception for an error that the handler did not catch and creates a problem. It results in the blue screen death, making the computer collect the knowledge about how and why the error occurred. This stop code often comes along with the following numbers: 0x0000007E, 0x1000007E or, if you are lucky, is accompanied by the file name that is causing the error, such as atikmdag.sys, nvlddmkm.sys, igdkmd64.sys, etc. However, with this specific kind of error, the computer almost always meets up with a reset cycle that needs you to utilize the safe mode to break.

When does this error occur and why does it take place

The “system_thread_exception_not_handled” error happens when you boot the computer up from shutdown. However, it can occur randomly and is recognized to pop up when a program is being run by a user that needs particular graphic drivers to function. You may experience this error when the computer has drivers installed that are not compatible (most commonly graphic drivers), either out of date, corrupted, or have some glitch. Graphic drivers can be controlled by an antivirus program such as avast and may be installed incorrectly, which are other reasons you would get the “system_thread_exception_not_handled” on Windows 10.

There is a file name attached to the error code: What Does It Mean?

If you are fortunate, the “system_thread_exception_not_handled” error code will possess a file name attached to it, indicating which graphic driver is creating the problem. If you update or repair this graphic driver, you can potentially resolve the error. Common file names that come up with this BSOD error are as follows. 

  • Nvlddmkm.sys – this graphic driver is for the Nvidia Windows kernel driver, and it is relevant to your Nvidia video card. If you contain an Nvidia powered graphics card installed, it indicates that this card’s drivers are out of date or incorrectly installed.
  • Atikmdag.sys – this graphic driver comes from the ATI Radeon Family relevant to your ATI video card. If you contain an AMD installed graphics card in your PC, it indicates that this card’s drivers are out of date or not installed correctly. 
  •  
  • Dxgmms2.sys – this is related to the DirectX drivers that you have installed. 
  • Ntfs.sys – this is for the Windows NT Server.
  • CMUDA.sys – this is the driver that is associated with USB device audio.
  • Bcmwl63a.sys – this is for the Broadcom 802.11 Network Adaptor. This adaptor requires a wireless driver that is developed by Broadcom Corporation. If this is installed incorrectly or outdated, you are likely to get the “system_thread_exception_not_handled” error.

If you have any of those mentioned above when the error pops up, it shows that you need to remove it and reinstall it or another possible option is to update the driver. If you have a different system file attached with the error code, you will need to look for the driver file name online to find out which driver possesses an issue. If no system file comes up with the error, you will need to update all the drivers on your computer, consisting of any network, LAN, sound, wireless drivers, audio drivers, and display drivers (graphics). 

How to Boot Into Safe Mode on Windows 10?

The most important thing you are supposed to want to do is start your PC into safe mode, as this is what will enable you to break the reboot loop that you are automatically stuck in. Since it is most probable that you cannot reach your settings, we will get you to boot into the Windows Recovery Environment (winRE) before the safe mode.

  1. Press the computer’s power button for at least 10 seconds to let it get turned off. Once it gets shut down completely, hit the power button again to turn it back on. 
  2. As long as you see any sign that Windows has started, hold down the power button for 10 seconds to turn it off. Press the power button to turn it back on.
  3. Keep doing this process until your device fully restarts, and you enter winRE.

To move to safe mode from winRE, you will need to select the “Troubleshoot” option from the list. Then select“Advanced Options,” “Startup settings,” and “restart”. After your computer restarts, you will be presented with a list of options. You want to hit F5 for Safe Mode with Networking. 

5 Methods for Fixing “System Thread Exception Not Handled” on Windows 10 Systems

  1. Find out which driver is faulty

There are several ways to do that, but the most convenient way is to check the system log which tracks events. If you want to do it, you will need to open up the event viewer.

  1. On your keyboard, press the Windows key + R to pull up the “run” dialogue box.
  2. Enter “eventvwr” into the box and hit okay.
  3. Head down to where it says “Windows logs” and click to have the menu drop-down.
  4. Click on “system” within this drop-down menu to see all recent events.
  5. Find the “system_thread_exception_not_handled” error and see which driver it is connected with.
  6. Update, roll back or reinstall your drivers.

The most convenient way to fix incompatible drivers is by updating them, rolling them back to the previous version. Apart from that, if you have installed the most recent version, reinstalling them. To do this, you will need to open up your device manager by either typing “device manager” into your computer’s search or by pressing the Windows key + X and selecting “device manager”.

  • To update your drivers, you will need to go through your device list and right-click on every piece of hardware that would have a driver and choose to update it. This includes your disk drives, audio devices, sound devices, network adaptors, and display adaptors. When you click “update driver” you can automatically search for the most recently updated version.
  • To roll back your drivers, go through your device list and right-click on every piece of hardware that has a driver, and choose “properties”. You will then want to navigate to the “driver” tab and click on the “roll back” option. Make sure to click, yes!
  • To reinstall a driver, you will need to uninstall the device first. You will then need to navigate to the device manufacturer’s website, find your device there, and download the most recent driver for that device and install manually.
  1. Rename the faulty driver

If you have a file name associated with the “system_thread_exception_not_handled” error code, you can rename the driver to something else, and Windows will fetch a new copy of it and install it again. You will need to figure out what hard drive the driver is installed on first.

  1. Open up the command prompt app by searching “command prompt” or type “cmd“ in your computer’s search.
  2. Type into the command prompt box, C: (hit enter) cd windows\system32\drivers (hit enter) ren FILENAME.sys FILENAME.old (replace filename here with the faulty driver file listed with the error code).
  3. Then type “exit” and restart the computer.
  4. Repair your system files

If you think that you have corrupted system files affecting your device drivers, you can repair them by running Windows repair programs, SFC and DISM. 

  1. To run SFC, open up the command prompt as an administrator. If you are in safe mode, you will find the command prompt option under the “advanced options” list.
  2. Type in sfc/scannow and hit you enter key. This will replace any damaged or changed system files.

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

  1. Open up the command prompt as administrator and type in the following one by one.
  2. Exe /Online /Cleanup-image /Scanhealth
  3. Exe /Online /Cleanup-image /Restorehealth
  4. Reboot your PC to an earlier version

If you have made backups of your computer system, you can restore it to an earlier period when you did not receive the “system_thread_exception_not_handled” error code. To do this though, you will need either a system repair disc for Windows or a recovery drive.

  1. Insert the system repair disc into the computer and choose your language preference.
  2. Click on the repair option and choose to troubleshoot advanced options.
  3. Then choose system restore and follow the instructions given.

While uninstalling, reinstalling, and updating out-of-date drivers will resolve the issue for most people, those who still get the error after completing all five of the above methods may need you to consider a clean reinstallation of the operating system. Doing a complete wipe and reinstall of the operating system will reset you back to factory settings so to speak. It will require you to update your operating system and update the basic drivers to their latest versions.

 

how to fix ‘system thread exception not handled’ error in windows 10stop code system thread exception not handledsystem thread exception not handled windows 10system thread not handledsystem_thread_exception_not_handledthread exception not handledwindows 10 system thread exception not handled
Comments (0)
Add Comment