How to fix SYSTEM_THREAD_EXCEPTION_NOT_HANDLED error in Windows
One of the most confusing Blue screen of death Stop code, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED acts as a fallback for normal error handling.its Microsoft Document The page says “This error check indicates that the system thread generated an exception that was not caught by the error handler.” In my book, it is equivalent to “mysterious or unrecognized error” (because the error handler cannot give it to the predefined Error handling routine) or “error handling program error” (because the error handling program lets the error go through without processing it).
The Windows programming documentation explains that SYSTEM_THREAD_EXCEPTION_NOT_HANDLED usually includes three well-known exception codes, which further clarify error checking or stop code errors in Windows. all these are:
- 0x80000002: STATUS_DATATYPE_MISALIGNMENT Indicates that an unaligned data reference was encountered.
- 0x80000003: STATUS_BREAKPOINT Indicates that a breakpoint or assertion was encountered when no kernel debugger was connected to the system.
- 0xC0000005: STATUS_ACCESS_VIOLATION indicates that a memory access conflict has occurred.
In these codes, you most likely only see the third and last item. This is because the other two codes should only appear in the pre-release code used for debugging, or when running the code in the debugger.
Another common information that appears when analyzing crash dumps from SYSTEM_THREAD_EXCEPTION_NOT_HANDLED is the file name, such as atikmdag.sys, igdkmd64.sys, or nvldmkm.sys. Savvy readers will recognize these names as part of the runtime environment of AMD ATI, Intel Graphics Circuits, and NVIDIA GeForce graphics drivers. If you see these names or other similar names, then your graphics driver is likely to function in situations that cause a BSOD marked with this error code.
If this is the case, you should try three basic strategies, in order of increasing complexity and difficulty:
1. Check if a newer version of the graphics driver is available. If so, please install it. This usually resolves graphics driver issues.
2. If this doesn’t work, Attempt to roll back to the previous version of the driver In the device manager (you will find this option in the “Properties” page, “Driver” tab of the corresponding display adapter)
Please note that the “roll back driver” option here is grayed out. This means that this option is not available on the target PC.
3. If the rollback is not available or does not help, please find the manufacturer’s driver download page and Try the next old version. Repeat until you find a valid one.
Another driving trick may help
Sometimes messing up existing drivers—especially graphics drivers—does not make things better. In this case, you may benefit from a thorough cleaning of the graphics environment and then a “fresh install” of a brand new driver.For this, there is nothing better than a tool called Guru3D Display driver uninstaller, Also known as DDU. When I wrote this interpreter, the current version was 18.0.4. The preceding link should always give you access to any latest version.
DDU is available for AMD and NVIDIA drivers (you may need to visit the Intel support page for help with Intel graphics drivers). I have used it many times myself and can prove that it has done a complete and thorough job in removing all traces of previously installed graphics drivers that it can handle. Before using this tool, please be sure to read the recommended instructions for the tool. I can say from experience that this will save time, energy and potential frustration.
What else can be done about SYSTEM_THREAD_EXCEPTION_NOT_HANDLED?
If the previous suggestions did not make the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED stop code disappear, you should try next Clean bootIf this helps, something in your startup software may be related to the problem that caused this stop code, and you need to follow the elimination process to find out what it is.
If a clean boot does not help, your next step is Boot your system into safe modeAfter running in safe mode, use the built-in DISM (Deployment Image Servicing and Management) command to repair the running Windows image as follows:
dism /online /cleanup-image /restorehealth
In many cases, this will repair Windows image files that may be damaged or missing. Next, try the following fix:
This will run the Windows System File Checker (SFC) and will replace any damaged or suspicious system files it finds. Both of these commands will take some time to complete, so don’t be surprised if they run for half an hour or more before they complete.
Use recent reports and intelligence
If you visit TenForums.com, BleepingComputer.com, Answers.Microsoft.com or techy’s points Forum And search for the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED error string, you will see how often this error has occurred recently. You will also learn more about how other people diagnose any underlying causes and what repair methods they tried or used.
Reading about repairs that claim to be successful is especially helpful, because they may also be useful to you. Otherwise, unsuccessful fixes will also provide information because they will tell you which fixes to try (or not try at all) later instead of earlier.