System Thread Exception Not Handled New [2021] Jun 2026
Look for IMAGE_NAME: and MODULE_NAME: . That is your failing driver.
Navigate to . Press 4 or 5 to enter Safe Mode. Step 3: Reinstall or Roll Back Display Drivers
The that occurs when a background system process generates an error that the operating system cannot properly interpret or contain . This specific crash code, also tracked as Bug Check 0x0000007E , is primarily triggered by outdated device drivers, corrupted system files, or faulty hardware upgrades.
If a graphics driver ( nvlddmkm.sys , atikmdag.sys ) is causing the crash, a standard uninstallation might not clean out corrupted registry files. system thread exception not handled new
The "System Thread Exception Not Handled" error can be caused by a variety of factors, including:
…before connecting to the internet for automatic updates.
sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth Look for IMAGE_NAME: and MODULE_NAME:
Type into the search bar and open the app. Click Restart now and check for problems .
If a file name is listed, you can skip general troubleshooting and focus entirely on updating or reinstalling that specific component. Step 2: Boot into Safe Mode
This error is almost always a software or driver conflict, but it can also stem from hardware problems. The most frequent causes include: Press 4 or 5 to enter Safe Mode
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
The error may name files like nvlddmkm.sys (NVIDIA), atikmpag.sys (AMD), or igdkmd64.sys (Intel), pointing to a graphics driver issue. The most thorough fix uses DDU (Display Driver Uninstaller) to remove all traces of the current driver. The process is:
Unboxing a new PC or finishing a fresh Windows installation only to be met with a Blue Screen of Death (BSOD) is incredibly frustrating. The error is one of the most common Windows stop codes, and seeing it on a "new" system usually points to a specific set of culprits: incompatible drivers, BIOS settings, or (rarely) faulty hardware.