Scenario A – You can boot normally or into Safe Mode:
Scenario B – You cannot boot at all:
To understand the fix, you must first understand the terminology.
Therefore, SYSTEM THREAD EXCEPTION NOT HANDLED means a system thread generated an error that the operating system did not know how to catch or fix. Because the thread didn't know what to do, Windows panicked and stopped itself to prevent data corruption.
1
The "System Thread Exception Not Handled" error is one of the most common Blue Screen of Death (BSOD) stop codes. While it looks intimidating, it usually boils down to a single driver or piece of hardware trying to execute a command it shouldn't.
If you’ve recently installed new hardware or updated your OS, here is a comprehensive guide to identifying the culprit and fixing the loop. 1. Identify the Culprit (The File Name) system thread exception not handled new
Often, the BSOD screen will list a specific file next to the error code. Identifying this file is 90% of the battle: nvlddmkm.sys: NVIDIA graphics driver issue. atikmdag.sys: AMD graphics driver issue. rtwlane.sys: Realtek Wireless LAN driver issue. dptf_cpu.sys: Intel Dynamic Tuning Technology issue.
If no file is listed, you'll need to use the BlueScreenView utility or Windows Event Viewer after rebooting to see which driver crashed. 2. Boot into Safe Mode
If the error is preventing you from reaching your desktop, you must enter Safe Mode:
Interrupt the boot process three times (turn the PC off as it starts) to trigger Automatic Repair.
Navigate to: Advanced options > Troubleshoot > Advanced options > Startup Settings > Restart. Press 4 or F4 to start in Safe Mode. 3. Roll Back or Reinstall Drivers
Since "new" errors often follow an update, the most likely fix is resetting your drivers. To Reinstall: Right-click the Start button and select Device Manager. Scenario A – You can boot normally or into Safe Mode:
Locate the suspect hardware (usually Display Adapters or Network Adapters). Right-click the device and select Uninstall device.
Check the box "Delete the driver software for this device" and restart. Windows will attempt to install a generic, stable version.
To Roll Back:If you recently updated a driver and the error started immediately, right-click the device in Device Manager, go to Properties, select the Driver tab, and click Roll Back Driver. 4. Repair System Files
Windows might have "tripped" over itself during an update, leading to corrupted system files. Use the built-in repair tools:
Type cmd in the search bar, right-click, and Run as Administrator. Type sfc /scannow and press Enter. Let it finish. Follow up with: DISM /Online /Cleanup-Image /RestoreHealth. 5. Rename the Faulty Driver
If you know exactly which .sys file is causing the crash (e.g., nvlddmkm.sys), but you can't uninstall it normally: In Safe Mode, navigate to C:\Windows\System32\drivers. Locate the file and rename it to filename.sys.old. Scenario B – You cannot boot at all:
Restart. Windows will be forced to recreate the file or use a default version, often breaking the crash loop. 6. Check for BIOS/Firmware Updates
If you are seeing this on a "new" build or after a major Windows feature update (like moving to a new version of Windows 11), your motherboard's BIOS might be incompatible with how the system handles threads. Visit your motherboard manufacturer's website to download the latest BIOS version. Summary Checklist Check the BSOD screen for a specific file name. Uninstall/Roll back display and network drivers. Run SFC and DISM to repair Windows system integrity.
Disable Fast Startup in Power Options (sometimes this prevents drivers from initializing correctly).
Does your BSOD mention a specific .sys file, or does it happen only when you launch a certain app?
Here’s a focused guide to troubleshooting the "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" Blue Screen error, specifically when it mentions "new" (e.g., What failed: new or a driver containing "new").