The "SYSTEM THREAD EXCEPTION NOT HANDLED" error is a common Blue Screen of Death (BSOD) stop code that occurs when a system thread generates an exception that the error handler does not catch. In Windows 10 and 11 (as of mid-2026), this is frequently linked to incompatible, outdated, or corrupted device drivers, system file corruption, or recent software changes.
sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth
If a crash loop persists, your video or storage driver is likely the issue.
Damage to core Windows system files can cause a wide range of BSODs, including the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED error. system thread exception not handled new
(If you can boot) → System Properties → Advanced → Startup & Recovery → Write debugging information → Small memory dump (256 KB).
By approaching the error methodically rather than panicking, you can usually resolve the issue and prevent it from recurring. Remember to keep your drivers updated regularly to avoid future conflicts.
!analyze -v
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.
Files associated with third-party security suites (like Avast, McAfee, or Bitdefender). Step 1: Boot into Safe Mode (If Windows Won't Start)
This guide will break down exactly what this error means, why the "new" variant occurs, and the precise steps to eliminate it for good. The "SYSTEM THREAD EXCEPTION NOT HANDLED" error is
Don't panic. If the crash happened only once, you might have encountered a random glitch, and a simple restart could fix it. If the error persists, first note any driver filename mentioned on the BSOD screen (e.g., igdkmd64.sys , amdkmdag.sys ). This is your biggest clue.
While the general troubleshooting steps work for most, here are some specific, proven fixes for common scenarios.
In 80% of cases, either rolling back the GPU driver or uninstalling the latest Windows update solves the problem immediately. For the remaining 20%, methodical debugging using Safe Mode, DISM, and memory testing will identify the culprit. Damage to core Windows system files can cause