SYSTEM_THREAD_EXCEPTION_NOT_HANDLEDHighSystem thread exception not handled
What this error means
System thread exception not handled is a Windows blue screen stop code that appears when a system process or driver causes a crash and Windows has to restart. It often shows up during startup, after a driver update, or when a device such as a graphics card, Wi-Fi adapter, or storage controller is having trouble.
This usually points to a driver problem, corrupted system files, or a recent change that affected how Windows starts.
Common causes
- 1A graphics, network, or storage driver is incompatible or corrupted
- 2A recent Windows update or driver update caused a conflict
- 3Damaged system files are preventing Windows from loading normally
- 4A faulty external device or new hardware is triggering the crash
- 5Malware or disk problems are interfering with startup
How to fix it
- Restart your PC once. If this happened only once, a simple restart may clear a temporary driver or startup glitch. If the stop code returns, continue with the next steps.
- Disconnect any recently added devices. Unplug external drives, printers, docks, and other accessories, then restart. If the computer starts normally after removing one device, that device or its driver may be the cause.
- Start Windows in Safe Mode. Safe Mode loads only the basics. If Windows starts there, the problem is likely a driver or software that loads during normal startup.
- Roll back or update the driver most likely involved. Focus first on display, Wi-Fi, Bluetooth, and storage drivers. If the problem began right after a driver update, try rolling that driver back. If it started after installing new hardware or after a long time without updates, install the latest driver from the device maker or your PC manufacturer.
- Run Windows repair checks. Use built-in repair tools to look for corrupted system files and Windows image issues. These checks can fix files that a bad update or sudden crash may have damaged.
- Install pending Windows updates and restart again. Some stop-code issues are resolved by later fixes from Microsoft, especially when the crash is tied to a known driver or startup problem.
- If the crash continues, scan for malware and check your storage. A full malware scan and a disk health check can uncover deeper problems that may be triggering repeated blue screens.
Recommended fixes
Restart your device
A restart clears temporary state that often causes transient errors.
- Save your work and close open apps.
- Restart the device from the power menu.
- Reproduce the issue to check whether it persists.
Install Windows updates
- Open Settings > Windows Update.
- Click Check for updates and install everything available.
- Restart if prompted.
Boot into Safe Mode (Windows)
- Open Settings > System > Recovery and click Restart now under Advanced startup.
- Go to Troubleshoot > Advanced options > Startup Settings > Restart.
- Press 4 (or 5 for Safe Mode with Networking).
Update your drivers (Windows)
- Open Device Manager.
- Right-click the affected device and choose Update driver.
- Select Search automatically for drivers.
Run System File Checker and DISM
- Open Command Prompt as administrator.
- Run
sfc /scannowand let it complete. - Then run
DISM /Online /Cleanup-Image /RestoreHealth. - Restart your PC.
Scan for malware (Windows)
- Open Windows Security > Virus & threat protection.
- Run a Full scan.
- Quarantine or remove anything detected, then restart.
When to seek help
Seek professional help if the stop code keeps coming back after Safe Mode, driver updates, and repair checks, or if Windows will not start at all. Get help sooner if the crashes began after a hardware upgrade, if you hear unusual clicking from a drive, or if the computer is showing repeated restarts, file loss, or other signs of failing hardware. If the PC is still under warranty, contact the manufacturer before attempting advanced repairs.
Need more help?
Run a free diagnostic scan to identify and fix issues automatically.
Download Quickfix AI