Fix: “System Thread Exception Not Handled” Error on Windows 10

by | Feb 9, 2021

system thread exception not handled
i

Table of Contents

$

WHAT IS THE ERROR MEANING

$

POSSIBLE REASONS FOR system_thread_exception_not_handled

$

READING THE FILE ATTACHED TO THE ERROR CODE

$

ARE YOU UNABLE TO ACCESS THE WINDOWS OPERATING SYSTEM?

$

THE TOP METHOD TO RESOLVE "SYSTEM THREAD EXCEPTION NOT HANDLED"

$

DETERMINE WHICH DRIVER IS FAULTY

$

REPAIR CORRUPTED DRIVERS TO REPAIR SYSTEM THREAD EXCEPTION NOT HANDLED BSOD ERROR

$

CHECK SCREEN DRIVERS

$

INSTALL/UPDATE GRAPHIC DRIVERS

$

UNINSTALL YOUR SOUND CARD DRIVERS

$

RENAME THE FAULTY DRIVER

$

SEARCH AND FIX CORRUPTED SYSTEM FILES IN WINDOWS OS

$

RESTORE YOUR PC TO A PREVIOUS VERSION

What is the error meaning

System Thread Exception Not Handled (TSOD) is a common problem among Windows 8.x and Windows 10 users. And it can happen at any time while doing some random job or whenever the computer starts-up. This blue screen of death (BSOD) issue is among the most annoying problems you might encounter with your computer system.

The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED is an error that appears on the blue screen of death (BSoD), which means that the system error handler can not handle this error, and it did throw it. This error can occur in Windows 7,8 and Windows 10 after booting the Windows operating system or while using it.

Because the Windows operating system does not handle this error, it will throw it and cause an immediate shutdown to stop further damage to the system.

Possible reasons for system_thread_exception_not_handled

As with every error in an operating system, the system thread exception not handled error code that appears in the BSoD is caused mainly by a driver fault due to an outdated driver or a wrong version. It is also can be due to a recent program installation or an overclocked tweak.

We mention several ways to fix this error (also applicable to both Windows 8.x and 10. X) for users who always get BSOD at startup or when doing a random task.

Reading the file attached to the error code

If you’re fortunate, the”system_thread_exception_not_handled” error code will have a record name attached to it, indicating which graphic driver is causing the issue. If you upgrade or repair this graphic driver, you will have the ability to solve the error completely. 

Common file names that follow this BSOD error are the following :

  • Atikmdag.sys: this graphic driver comes in the ATI Radeon Family related to an ATI video card. In case you’ve got an AMD installed graphics card into your computer, it usually means that the drivers for this card are out of date or incorrectly installed.
  • Nvlddmkm.sys: this graphic driver is for your Nvidia Windows kernel driver, and it’s linked to an Nvidia video card.
  • Dxgmms2.sys: that is related to the DirectX drivers you’ve installed.
  • Ntfs.sys: that will be for the Windows NT Server. This adaptor demands a wireless driver that’s created by Broadcom Corporation. If this driver is not set up correctly or obsolete, you’re likely to get the “system_thread_exception_not_handled” BSoD error.
  • CMUDA.sys: that is the driver that’s connected with USB device sound.

Are you unable to access the Windows operating system?

In Safe mode, your drivers and providers are disabled that isn’t essential to operate Windows. 

The first thing you’re likely to need to do would be to boot to safe mode since it’s going to make it possible for you to split the reboot loop you’re necessarily stuck inside. As it’s probable that you can’t access your preferences, we’re likely to get you to boot to Windows Recovery Environment (winRE) before safe mode.

Hold off your computer’s power button for a minimum of 10 seconds, so it is shut down. Once it’s completely off, then press the power button to turn it back on.

The moment you find any indication that Windows has started (such as the windows logo ), hold down the power button for 10 seconds to turn it off again (you might want to replicate this for 4 to 5 times).

Repeat this procedure until your device completely restarts, and you get into Windows Recovery Environment (WinRE); the intent is to activate somehow and push your system to enter repair/advanced mode.

To reach safe mode from WinRE, you will have to choose the “Troubleshoot” option from the listing. Then select “Advanced Options,” “Startup Settings,” and”restart”. After your computer restarts, you’ll be greeted with a list of options. It would be best if you pressed F5 for safe mode with networking to start.

windows recovery environment safe mode

The other solution is in the WinRE Click Troubleshoot > Advanced Options > Command Prompt. A black command prompt window may appear. Now type the following command and press Enter:

bcdedit /set {default} bootmenupolicy legacy

windows safe mode legacy

Restart your system and keep tapping F8 (Shift + F8 for some) until the Windows logo shows up. Advanced Boot options menu may appear. Choose Safe Mode with Networking and press the enter key. You will log into your Windows account with safe mode activated.

The top method to resolve “System Thread Exception Not Handled”

Determine Which driver is faulty

There are numerous ways that you can achieve this, but the simplest method is checking the system log that tracks events. To do this, you’ll have to open the event viewer.

  1. With the keyboard, hit the Windows key + R to pull the”run” dialog box.
  2. Input in”eventvwr” into the box and hit okay.
  3. Click “system” in this drop-down menu to see all recent events.
  4. Locate the”system_thread_exception_not_handled” error and see which driver it’s associated with it( you can short the events by Date and Time)
  5. The simplest way to fix incompatible drivers is by upgrading them, rolling them back to the previous version, or in case you’ve got the latest version, reinstalling them.

system_thread_exception_not_handled-system-event 

Repair Corrupted Drivers To Repair System Thread Exception Not Handled BSOD Error

If there is an issue with drivers onto your computer, it might cause the System Thread Exception Not Handled error. If you can still get into your Windows computer (it is boot into Windows OS usually, following the BSOD happened), it is possible to go to “Device Manager” to assess and locate corrupted drivers.

After the corrupted driver is detected, let us uninstall it, replace it with the new one, or upgrade to the latest version.

Learn how to Repair system thread exception not handled error on Windows 7, 8, 8.1, and Windows 10. At the next step, you’ll find error hardware with corrupt drivers. You need to update these drivers to the most recent version or uninstall and replace them with the new one.

To do this, you’ll have to open up your device manager by typing “device manager” into your computer’s search or by hitting the Windows key + X; this opens a secret menu then select “device manager”.

  • To upgrade your drivers, you’ll have to go via your device listing and right-click on each hardware piece that would have a driver and choose to upgrade it, including your disk drives, sound devices, network adaptors, and display adaptors. When you click on “update driver”, you can have it search automatically for the most recently updated version. 
  • To roll back your drivers, go through your device listing and right-click on each piece of hardware that has a driver, and select “properties”. You will then need to navigate the “driver” tab and click on the “rollback” option. Be sure that you click, yes!
  • To reinstall a driver, you’ll have to uninstall the device. You will then have to navigate to the device manufacturer’s site, locate your apparatus there, download the latest driver for this device, and set it up manually.

For those who have a file name associated with the “system_thread_exception_not_handled” error code, you can always rename the driver into something else, and Windows will fetch a fresh copy of it and reinstall it.

You’ll have to find what hard drive name the driver is set up on first: 

    • Open up the command prompt program by looking for “command prompt” or type “cmd” on your computer’s search. 
    • Type into the command prompt box:

C: (hit enter)

cd windows\\system32\\drivers (hit enter)

ren FILENAME.sys FILENAME.old (replace filename here using the faulty driver file recorded together with the error code).

 

ren-FILENAME.sys-FILENAME.OLD-Command

Check Screen Drivers

Display drivers are among the most frequent causes of this error to occur. We’ll uninstall them and then reinstall the newest edition of the display drivers. If you can’t log into Windows for even a couple of minutes, go back to the section to access Windows in safe mode.

From the Run dialog(Windows key+R), type devmgmt.msc and hit enter. In it, double click on Screen adapters to enlarge it. Under it’ll be your graphic card installed. (write down the complete name of your display driver before uninstalling it) once done, right-click on it, and hit Uninstall.

Then check the option delete the driver software for this device and click on OK. Otherwise, or if you’re having the same issue again, then you’ll need to install the upgraded version of these drivers manually.

uninstall graphics driver

To find the last version of your graphic card drivers, go to your graphic card manufacturer’s website and search and download the right driver model compatible with your operating system and system type (x64 or x86). To know them both, hold the Windows key and press R, type msinfo32, and hit enter.

Install/Update graphic Drivers

From the system information window, note down OS type and System type in the right pane. Run the downloaded driver and follow the on-screen directions.

If you do not have an outside graphic card installed, you’ll have an integrated display adapter embedded onto your motherboard. Go to your motherboard’s manufacturer’s site (The one whose logo splashes when you power on your system) to get updated drivers for your onboard graphic adapter. Along with the operating system and system type, you’ll also want your system version, which can be mentioned in the System Information window. The downloaded file here is also executable. Run it and follow the on-screen directions.

Uninstall Your Sound Card Drivers

Sometimes this error message results from a faulty driver named C-Media USB Audio Class 1.0 and 2.0 DAC Device Driver, which can be found with some Xerox audio cards. Updating the driver might not correct the issue properly. You may try uninstalling the driver completely and allowing the Device Manager to replace it with the default sound card driver.

Click Start and type Run, then put “devmgmt.msc” in the box and click on the OK button to run this command; this will open the device manager. Under the sound class, right-click on anything associated with C-Media USB Audio Class 1.0 and 2.0 DAC Device Driver. Then select Uninstall device.
You might have to confirm the uninstallation. Check the box next to “Delete the driver software for this device” and click on the OK button. 

uninstall sound driver

Restart your PC for the change to take effect. After restarting, Windows will try to reinstall the driver and replacing it with the company’s driver. If Windows does not replace the sound card driver, open Device Manager again, choose Action, and click on the Scan for hardware changes.

Rename the Faulty Driver

If, alongside SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, you can see a file name such as nvlddmkm.sys, atikmdag.sys, etc… In a bracket, we could rename the corrupted driver into something that the windows cannot find. Hence it’ll fetch a fresh copy of the driver file.

Get in the command prompt through measures displayed in the precedent solutions. In the black window, type the following commands, and press Input after each one:

c:

dir

 

If the dir command outcome indicates a folder called “Windows” then it’s the target drive. Otherwise, type d: and dir to check if it contains the Windows folder.

Currently, type the following commands and press enter after every line.

Cd windows\\system32\\motorists

ren drivername.sys drivername.old

In the above command, drivername is the name of the faulty driver, e.g atikmdag.sys.

Restart your system. The driver we deleted will be set up automatically. Otherwise, log into normal mode, hold the Windows key and press R, put devmgmt.msc and hit Enter to open the device manager.

The uninstalled device driver is going to have a yellowish exclamation mark. Right-click on it and click on Update Driver.

update driver

Click Search for Updated Driver version; Windows will search for the driver on the internet and install it.

Search And Fix Corrupted System Files In Windows OS

Corrupted files might bring on windows 8 and 10 system thread exception not handled error. You may fix them via SFC and DISM applications. This method is applicable regardless of if the computer can boot to Safe Mode.

Any corrupt system files in your Windows OS can lead to an error, in addition to several other difficulties. To solve them, you may use CHKDSK control to inspect and check your Windows system files to make sure that there is no corrupted file. This control can help to fix any corrupt document if found.

First, start the Command Prompt as Administrator hit Windows key +R to open the “Run” box, type “cmd” into the box, and then press Ctrl+Shift+Enter to run the command an administrator.

If you can’t access windows os, then go to Troubleshoot > Advanced Options > Command Prompt as we did in the first solution.

Type SFC /scannow and hit enter; your Windows computer will boot up and begin to assess and check the entire system to come across any corrupted file.

It may take some time to finish, so grab a cup of coffee, and please do not switch off the PC while it’s assessing and verifying your system files.

At times, scanning and repairing Windows system files will help fix many issues on your PC.

If you believe you have corrupted system files that affect your apparatus drivers and that the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED error is still showing up, you can fix them using the DISM application.

Open the command prompt as an administrator; you can refer to SFC section to do it, input the following command, and hit enter after each one:

exe /Online /Cleanup-image /Scanhealth

exe /Online /Cleanup-image /Restorehealth

    Restore your PC to a previous version

    Resetting your own Windows 10 Computer to default settings will be the final hope for this particular issue. Still, it’s powerful, and it is ready to fix the majority of the BSOD, even the system_thread_exception_not_handled problem.

    You may get there by clicking on the gear icon on the Start menu. Then select “Update & security” and click on Recovery from the left sidebar.

    Windows presents you with three big choices: Reset this PC, return to a previous build and Advanced startup. Reset this PC will be the ideal alternative for starting new. The advanced startup enables you to boot a retrieval USB drive or disk and “Go into a previous version” is created for Windows Insiders that wish to roll back to a prior version of this OS.

    recovery pc reset

    Click get started to begin, under Reset this PC, click “Keep my files” or “Eliminate everything,” depending on if you would like to maintain your data files intact. All your settings will go back to their default preferences, and programs will probably be uninstalled in any event.

    Select “Only remove my files” or “Remove files and clean out the driveway” if you decided to “eliminate everything” from the previous step. Cleaning the drive requires much more but will ensure that if you’re giving away the computer, another person will have difficulty regaining your deleted documents. If you’re maintaining the computer, then select “Only remove my files “. Click Next in case Windows warns you that you will not have the ability to roll back to a previous version of this OS. Click on Reset if prompted.

    recovery-pc-reset files

     

    Bottom Line 

    we did give you some solutions to fix the system thread exception not handled error, hoping that you can stop this blue screen of death(BSoD) from appearing again. if not please comment below for more help or contact us.

    Related Articles

    Keep your code clean and simple

    Keep your code clean and simple

    “Keep it simple, stupid” Always write code that you'll be able to understand in six months time when you've moved on to bigger and better things. If you have to be clever, leave yourself clues. It's less likely to break this week, and when it breaks in 6 months time,...

    Thou shalt always(ish) use UTF-8 in PHP

    Thou shalt always(ish) use UTF-8 in PHP

    Character sets are a mystery to many native-English coders, and if you're not aware of them then you'll occasionally find that things break, or go weird. Unicode was designed to replace all existing character sets with a single universal one. This article explains how...

    Escaping your output in PHP

    Escaping your output in PHP

    Output escaping happens when you tell your PHP script to output some content, usually to a web page, but also to other servers, or XML files, or even the command-line. Every kind of output needs to be escaped differently, which means PHP never does it automatically....