Solution 4 – Run DISM
And the third troubleshooting tool we’re going to try is DISM. Deployment Image Servicing and Management (DISM), as its name says, re-deploys the system image, and resolves potential issues along the way. So, it could also resolve the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M error.
We’ll walk you through both standard and the procedure that utilizes the installation media below:
- Standard way
- Right-click Start and open Command Prompt (Admin).
- Paste the following command and press Enter:
- Wait until the scan is finished.
- Restart your computer and try updating again.
- With the Windows installation media
- Insert your Windows installation media.
- Right-click the Start menu and, from the menu, choose the Command Prompt (Admin).
- In the command line, type the following commands and press Enter after each:
- dism /online /cleanup-image /scanhealth
- dism /online /cleanup-image /restorehealth
- Now, type the following command and press Enter:
- DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:SourcesInstall.wim:1 /LimitAccess
- Make sure to change an X value with the letter of the mounted drive with Windows 10 installation.
- After the procedure is finished, restart your computer.
Solution 5 – Check the hard drive
If your hard drive is damaged, BSOD issues are more than possible. To eliminate the doubt, you should run the chkdsk, which scans all your partitions, and resolves potential problems (if possible). So if the culprit of the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M is a corrupt hard drive, this tool will likely resolve the problem.
Here’s how to run the chkdsk command in Windows 10:
- Enter the Advanced Startup (Restart your computer while holding the Shift key).
- Choose Troubleshoot > Advanced Options.
- Select Command Prompt from the list of options.
- When Command Prompt appears, enter the following lines and press Enter after each line in order to run it:
- Some users are also suggesting that you need to run additional chkdsk commands as well. To perform these commands, you need to know drive letters for all your hard drive partitions. In Command Prompt you should enter the following (but remember to use the letters that match your hard drive partitions on your PC):
This is just our example, so keep in mind that you have to perform chkdsk command for every hard drive partition that you have.
- Restart your computer and check if the issue is resolved.
Solution 6 – Remove your antivirus software
Antivirus software is crucial for your system’s safety, but sometimes your antivirus software can cause these types of errors to appear. To fix SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M and many other BSoD errors, it’s important that you temporarily remove your antivirus software. Bear in mind that by removing your antivirus software you won’t be completely defenseless because Windows 10 comes with Windows Defender that works as a default antivirus program. To completely remove certain antivirus from your PC, it’s recommended that you use a dedicated removal tool. Almost all antivirus companies have these tools available on their websites, so be sure to download one of these tools for your antivirus software.
Users reported that Norton and McAfee are the cause for this error, but bear in mind that almost any antivirus program can cause this error to appear, so be sure to remove all third-party antivirus programs from your PC. If removing your antivirus fixes the problem, you can now reinstall it or you can switch to a different antivirus solution.
Solution 7 – Remove problematic applications
Even though your antivirus is the common cause for BSoD errors, almost any third-party application can cause SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M error to appear. To fix this problem, be sure to remove any recently installed or updated applications.
According to the users, MSI Afterburner, RealTemp, UltraISO and SoundTap Streaming Audio Recorder can cause this error to appear, therefore if you’re using any of these applications we strongly suggest that you remove them.
Solution 8 – Reset your BIOS
If your BIOS isn’t properly configured, you might get SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M or any other Blue Screen of Death error. To quickly fix this problem you just need to enter BIOS and reset it. By resetting BIOS all your settings will be reverted to default, thus fixing the BSoD error. To see how to enter BIOS and how to reset it, we strongly advise that you check your motherboard manual for detailed instructions.
Solution 9 – Reset Windows 10
If the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M error is caused by certain software, you can fix it easily by performing a Windows 10 reset. We should warn you that this process is similar to clean install, therefore we suggest that you back up your important files. To complete Windows 10 reset you might also need a bootable USB flash drive with Windows 10 on it, so be sure to create one. To perform Windows 10 reset follow these steps:
- Restart your PC few times during the boot sequence to start the Automatic Repair.
- Select Troubleshoot > Reset this PC > Remove everything. Insert Windows 10 installation media if you’re asked to.
- Choose Only the drive where Windows is installed > Just remove my files and click the Reset button to start the process.
- Follow the instructions on the screen to complete the reset.
After you complete Windows 10 reset, don’t install any software or drivers, instead test if your PC is working properly. If the error appears again, it means that your hardware is causing it.
Solution 10 – Check for faulty hardware
Hardware can be the common cause for BSoD errors, especially if it’s not compatible with your PC. If you installed any new hardware recently, we strongly suggest that you remove it or replace it and check if your PC works well without it. If the problem isn’t caused by new hardware, we strongly advise that you perform a detailed hardware inspection in order to find and replace the faulty hardware.
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M error isn’t as serious as other Blue Screen of Death errors, and you can easily fix it by updating your drivers or by removing the problematic software.
Editor’s Note: This post was originally published in June 2016 and has been since completely revamped and updated for freshness, accuracy, and comprehensiveness.