SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, the blue screen, explained and fixed
This stop code (0x0000007E) means a system thread, one of the background workers Windows itself runs, hit an exception that no error handler caught. The culprit is almost always a driver, and the blue screen often names the guilty file, ending in .sys, right on the crash screen. That name is the single most useful clue on the page.
The fix, in order
- Note the file name on the blue screen, if there is one. Names like nvlddmkm.sys (NVIDIA graphics), atikmdag.sys or amdkmdag.sys (AMD graphics), and rtwlane.sys (Realtek Wi-Fi) point straight at the driver to fix. If no file is named, the steps below still narrow it down.
- Boot into Safe Mode. Hold Shift while choosing Restart, then Troubleshoot → Advanced options → Startup Settings → Restart → Safe Mode. Safe Mode loads almost no third-party drivers, so if the crashes stop there, a driver is confirmed as the cause.
- Update or roll back that driver. In Device Manager, right-click the device → Properties → Driver: choose Roll Back Driver if the crashes started after an update, otherwise install the latest driver from the PC or component maker’s website rather than a driver-updater app.
- Update the other core drivers too. Graphics, chipset, storage, and network drivers are the usual set. Get them from the manufacturer, in that order of suspicion.
- Repair Windows files. In an admin Command Prompt run
DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. Corrupt system files can make a healthy driver look guilty.
- Test the RAM. Run Windows Memory Diagnostic (search the Start menu) or let it run from the recovery menu. Bad memory produces random-looking driver crashes, including this one.
Undo any overclocking while you troubleshoot. CPU, GPU, and RAM overclocks (including XMP pushed past the memory’s rated speed) can make stable drivers crash with this code, and every test you run is unreliable until clock speeds are back to stock.
If it still happens
If the crashes continue after clean drivers and file repairs, check the drive’s health with chkdsk /f and the maker’s diagnostic tool, then try System Restore to a point before the crashes began. When this code survives a clean Windows install on a healthy drive, suspect the RAM or the motherboard, in that order.
Common questions
The blue screen names a .sys file. Is that the broken part? It is the driver that was running when the thread crashed, which makes it the prime suspect. Updating it, or rolling it back to the previous version, fixes most cases. Occasionally a healthy driver is just where bad RAM happened to strike, which is why the memory test is in the list.
Can SYSTEM_THREAD_EXCEPTION_NOT_HANDLED mean failing hardware? Yes, but drivers come first. Faulty RAM is the most common hardware cause, followed by a failing drive corrupting driver files. Treat it as hardware only after clean drivers, repaired system files, and a memory test all check out.
Related errors