The screen turns blue and shows SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, sometimes with a file name underneath, such as nvlddmkm.sys, atikmdag.sys, or a network driver. The PC restarts, and slot88 the crash may come back during start-up or while gaming. When Windows 10 system thread exception not handled appears, a driver has caused an error that Windows could not recover from.
A “system thread” is work being done by Windows or a driver in the background. When that work hits an unexpected error and nothing handles it, Windows stops everything to prevent damage.
Graphics, network, and audio drivers are the most common culprits, especially after a Windows update installs a version that does not suit the hardware.
The file name shown on the blue screen is the best clue, because it points directly to the faulty driver.
Note the stop code and any file name before the PC restarts. Taking a phone photo of the blue screen is the easiest way to keep both details.
What Might Be Causing It
This stop code has these common causes:
- An outdated or incompatible graphics driver.
- A network, Wi-Fi, or audio driver that conflicts with a recent update.
- Overclocking that makes the hardware unstable.
- Damaged system files.
If the crash names a .sys file, search for that name to find out which device it belongs to.
First Steps to Try
Start in Safe Mode if the crash prevents normal start-up.
- Turn the PC off at the logo three times, then choose Troubleshoot > Advanced options > Startup Settings > Restart, and press 4.
- Open Device Manager and find the device linked to the file named on the blue screen.
- Right-click the device, choose Properties > Driver, and select Roll Back Driver if available.
- If rollback is not possible, uninstall the device and tick the option to delete the driver.
- Restart normally and let Windows install a basic driver.
Graphics drivers can be removed completely with Display Driver Uninstaller in Safe Mode, then reinstalled from the GPU maker.
If the Problem Continues
Look deeper.
- Install the latest driver from the hardware maker’s website, not a driver-update tool.
- Remove any CPU, GPU, or memory overclock in the BIOS or tuning software.
- Repair Windows files with sfc /scannow, followed by DISM /Online /Cleanup-Image /RestoreHealth.
- Use System Restore to return to a point before the crashes began.
- Read the minidump with a crash-analysis tool to confirm the driver.
Protect Your Data First
Repeated blue screens can corrupt open files, so back up documents as soon as Windows starts. Avoid unofficial driver download sites.
The Bottom Line
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED is almost always a driver problem. Use the file name on the blue screen, roll back or reinstall that driver from Safe Mode, and remove any overclock.