This error mainly occurs due to a driver malfunction. An outdated, corrupted or incompatible driver can get your system into display this blue screen. Outdated drivers and overclocking softwares, or a recently overclocked tweak are also known to cause this BSOD. If a recently installed program or a driver caused this issue; then the first approach should be to uninstall them since they are simply not compatible, keep track of updates and attempt reinstall when a patch or update to the driver has been released. You can do this by booting into Safe Mode. (see below)

What to do to Fix the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Error

Analyse the Minidump Files

This BSOD has several variations, it is best to analyse the minidump file which is responsible for logging the crashes and can provide more details on what exactly is causing the SYSTEM THREAD EXCEPTION BSOD. In order to continue with this, please see steps below.

Under System Failure, click to select the check boxes for the actions that you want Windows to perform if a system error occurs:

Under Write Debugging Information, select the type of information that you want Windows to record in a memory dump file if the computer stops unexpectedly:

There are other options as well but we recommend you use the Small Memory Dump option as it’s small in size but it still contains enough information for you to solve your issue. Additionally, you will need to use this option in order to read and open the minidump file properly. Let’s find out just how to open and read the minidump file. You will need to download a certain tool made available by Microsoft. Firstly, it was a part of the Debugging Tools for Windows but Microsoft decided to create a standalone package.

if after analysing dump files you were able to figure out the issue, then most likely it is now resolved but if not then you proceed with these methods below.

Check Display Drivers

Display drivers are one of the most common reason for this error to occur. We will uninstall them and then re-install the latest version of the display drivers. If you can log in to Windows for even a few minutes then skip to Step 2. But if you can’t even log in to Windows then start with Step 1.

Step 1: Boot into Safe Mode

In safe mode, your drivers and services are disabled which are not necessary to run Windows. To boot Windows 8/8.1 and 10 into safe mode, turn your system on and force it to shut down by pressing the power button, turn it back on and repeat the steps until the system starts in repair mode. (you may need to repeat this for 4 to 5 times). The aim is to somehow trigger and push your system to go into repair/advanced mode. Click on Troubleshoot > Advanced options > Command Prompt. A black command prompt window will appear. Now type the following command and press Enter. Now type Exit and press Enter. Click Continue. Now restart your system and keep tapping F8 (Shift + F8 for some) before the Windows logo appear.  Advanced Boot Options menu will appear. In it highlight Safe Mode with Networking and press Enter. Now log in. You will be running your Windows in Safe Mode now.

If for some reason you can’t get the recovery options to show up, then get an installation media of your Windows operating system, which can be either a DVD or make a bootable USB through Media Creation tool. You will need an 8 GB USB and a computer with internet access. To create a Windows 10 Bootable USB Installation media, follow our guide on this link. To create a Windows 8.1 Bootable USB Installation media, go to this link. Scroll down and click on Download Tool Now. Run the tool and follow the onscreen instructions. Enter the DVD or insert the USB into the target computer. Power on and keep tapping F2 to access Boot menu. The button to enter boot menu may differ by your system’s model. Normally, for Dell it is F12, for HP it is F9. You may have to check your system’s manufacturer’s website for yours. After accessing the boot menu, highlight and select CD/DVD if you inserted a DVD, or select USB drive if you inserted a USB. If you are asked to press any key to boot from the media do so. Click Next if the time zone, keyboard layout preference and language are fine for you. Now in the lower left corner, click on Repair your computer. Now follow the above given method to open command prompt and get into safe mode.

Step 2: Uninstall Display Drivers

Hold down Windows key and press R. In the Run dialog, type devmgmt.msc and press Enter.

Device manager window will appear. In it, double click Display adapters to expand it. Under it will be your graphic card installed. (write down the full name of your display driver, before uninstalling it) once done, Right click on it, and chose Uninstall.

Then click Delete the driver software for this device and click OK. Restart your system normally. After restarting, video drivers will get installed automatically. If not, or if you are having the same issue again, then you will have to install the updated version of the drivers manually. Follow step 3 to see how.

Step 3: Install/Update Drivers

To get an updated version of drivers for your graphic card, visit your graphic card manufacturer’s website. Search by the card’s model and download the appropriate drivers compatible with your operating system and system type (x64 or x86). To know them both, hold Windows key and press R, type msinfo32 and press Enter. In the system information window, note down OS type and System type in the right pane. The downloaded files will probably be an executable. Simply run it and follow the onscreen instructions. If you don’t have an external graphic card installed, then you will have a integrated display adapter embedded on your motherboard. Visit your motherboard’s manufacturers website (The one whose logo splashes when you power on your system) to get updated drivers for your onboard graphic adapter. In addition to operating system and system type, you will also need your system model, which is also mentioned in the System Information window. The downloaded file here will also be an executable. Simply run it and follow the onscreen instructions.

Uninstall Your Sound Card Drivers

Sometimes this error message is caused by a faulty driver called C-Media USB Audio Class 1.0 and 2.0 DAC Device Driver which can be found with some Xerox sound cards. Updating the driver may not fix the issue properly so you might try uninstalling the driver completely and letting the Device Manager replace it with the default sound card driver.

Rename the Faulty Driver

If next to SYSTEM THREAD EXCEPTION NOT HANDLED, you can see a file name such as atikmdag.sys, nvlddmkm.sys, etc.. in a bracket, then we can rename the culprit driver into something that the windows can’t find, hence it will fetch a new copy of the driver file.

Get into the command prompt through steps shown in first solution. In the black window, type the following commands, and press Enter after each. If the results of the dir command shows a folder named “Windows” then it is the target drive. If not, type d: and press Enter. Now type the following commands and press Enter after each line. In the above command, drivername is the name of the fault driver, e.g atikmdag.sys. Restart your system. The driver we deleted will be installed automatically. If not, log in normal mode, hold Windows key and press R. Type devmgmt.msc and press Enter. The uninstalled device driver will have a yellow exclamation mark. Right click on it and click Update Driver Software. Click Search automatically for Updated Driver Software. Windows will search for the driver online and install it once it finds it

Reset your PC

Resetting our PC is considered to a last resort for this issue but it is definitely efficient and it’s able to fix most of the BSOD issues, including the one described in this article. Here’s how to reset your PC in Windows 10.

Fix: KMODE EXCEPTION NOT HANDLEDHow to Fix ‘Kmode Exception Not Handled’ Error on Windows 11Fix: System Service Exception VirtualBox BSOD on Host MachineHow to Fix Thread Stuck In Device Driver BSOD on Windows 8 and 10 FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 87FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 96FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 41FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 22FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 27FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 2FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 12FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 74FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 88FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 69FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 53FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 96FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 17FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 69FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 24FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 84FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 60FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 51FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 72FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 85FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 36FIX  SYSTEM THREAD EXCEPTION NOT HANDLED - 11