How to Fix System Thread Exception Not Handled in Windows 11 (2026 Fix)

You are right in the middle of working on a project or loading into a game, when suddenly your screen turns solid blue with a sad face and a scary stop code: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

Blue Screen of Death (BSOD) crashes are the ultimate productivity killer. One moment your computer is running smoothly, and the next, everything freezes up, leaving you staring at a bright blue screen with a cryptic error message. Among all the Windows 11 crash codes, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED is one of the most frequent glitches PC users face.

This specific crash happens when a system thread—a basic background task running inside your computer—generates an error that the operating system's handler fails to catch. Because Windows cannot recover from the unexpected thread failure, it shuts down your machine instantly to prevent data corruption or hardware damage.

While a blue screen looks terrifying, the actual cause is rarely a broken processor or dead motherboard. In over 90% of cases, this error is caused by a buggy device driver, an incompatible system update, or a corrupted system file.

This guide will walk you through the exact steps needed to troubleshoot this stop code, stop the boot loop, and get your Windows 11 PC back to rock-solid stability.

What Causes the System Thread Exception Not Handled BSOD?

Understanding what triggers this crash makes fixing it much easier. Sometimes, the blue screen will display a specific file name in parentheses right next to the error code, such as nvlddmkm.sys, amdkmdag.sys, or RTKVHD64.sys.

These filenames tell you exactly which hardware driver crashed:

• nvlddmkm.sys: Conflicts with NVIDIA graphics drivers.

• amdkmdag.sys or atikmdag.sys: Issues with AMD graphics card drivers.

• RTKVHD64.sys: Malfunctioning Realtek audio drivers.

• NETIO.SYS or ndis.sys: Corrupted network adapter or Wi-Fi drivers.

If no specific file is listed, the crash is usually tied to outdated system files, aggressive Fast Startup cached errors, or recent cumulative updates that clashed with your hardware.

How to Boot into Safe Mode (If You Are Stuck in a Boot Loop)

If your computer crashes immediately upon hitting the desktop and keeps restarting, you will need to access Safe Mode before trying any fixes. Safe Mode boots Windows with minimal drivers, preventing the faulty driver from crashing your PC while you repair it.

1. Turn off your PC completely by holding down the physical power button for 10 seconds.

2. Press the power button to turn your PC on. As soon as the manufacturer logo (like Dell, HP, or ASUS) appears, hold the power button down again to force a shutdown.

3. Repeat this process two to three times. Windows will automatically launch the Automatic Repair screen.

4. Click on Advanced options, then navigate to Troubleshoot > Advanced options > Startup Settings.

5. Click Restart.

6. When your PC reboots, press 4 or F4 on your keyboard to enable Safe Mode.

Once you arrive at your Safe Mode desktop, you can comfortably execute the following fixes.

Fix 1: Uninstall or Roll Back the Faulty Driver

Because bad drivers cause the vast majority of thread exception errors, replacing or rolling back your graphics or network drivers should be your first line of defense.

1. Press Windows Key + X and select Device Manager.

2. If your blue screen listed a specific file (like an NVIDIA or Realtek driver), locate that device category. For example, expand Display adapters for graphics card errors.

3. Right-click your graphics card (NVIDIA, AMD, or Intel) and select Properties.

4. Go to the Driver tab.

5. If available, click Roll Back Driver to restore the previously stable driver version.

6. If the rollback option is grayed out, click Uninstall Device, check the option to remove driver software, and click Uninstall.

7. Restart your computer normally. Windows will automatically reinstall a clean base driver upon rebooting.

If you are stuck dealing with broader startup failures or system crashes, reviewing Microsoft's official guide to Windows recovery options can help you navigate startup repair settings and system restore points safely.

Fix 2: Run SFC and DISM to Repair Corrupted System Files

Corrupted core files can cause background system threads to misfire continuously. Windows includes powerful command-line utilities designed to find and replace damaged system files automatically.

1. Press the Windows Key, type cmd, right-click Command Prompt, and select Run as administrator.

2. Type the following command and press Enter: sfc /scannow

3. Wait for the scan to finish (it usually takes 5 to 10 minutes). System File Checker will locate and repair any compromised files it finds.

4. Once SFC finishes, run the Deployment Image Servicing and Management (DISM) tool by typing this command and hitting Enter: DISM /Online /Cleanup-Image /RestoreHealth

5. After the scan completes 100%, restart your PC.

Fix 3: Disable Windows Fast Startup

Windows 11 uses a feature called Fast Startup to help your computer boot up faster after a shutdown. It does this by saving a snapshot of your system kernel and running drivers to your hard drive. However, if a driver crashes during shutdown, Fast Startup reloads that exact corrupted driver state every time you turn your PC back on.

1. Press Windows Key + R, type control, and press Enter to open the classic Control Panel.

2. Set "View by" to Large icons and click Power Options.

3. In the left sidebar, click Choose what the power buttons do.

4. Click on the link at the top that says Change settings that are currently unavailable.

5. Scroll down to the Shutdown settings section and uncheck Turn on fast startup (recommended).

6. Click Save changes and restart your machine.

Fix 4: Check Your Memory (RAM) for Hardware Faults

If you tried updating drivers and repairing system files but the blue screens persist, faulty RAM sticks might be generating arithmetic errors during active thread processing.

1. Press Windows Key + R, type mdsched.exe, and hit Enter.

2. Select Restart now and check for problems (recommended).

3. Your computer will reboot into the Windows Memory Diagnostic Tool and test your physical RAM modules for hardware defects.

4. If the test reports hardware errors, try removing your RAM sticks, cleaning the contacts with a dry micro-fiber cloth, and re-seating them in different motherboard slots.

Frequently Asked Questions (FAQs)

What does the filename next to the stop code mean?

The filename (such as nvlddmkm.sys or netio.sys) points directly to the system driver that suffered the unhandled thread exception. Identifying this file allows you to pinpoint whether your GPU, sound card, or Wi-Fi adapter triggered the crash.

Will fixing this BSOD delete my personal files?

No. Updating drivers, running SFC repair scans, and disabling Fast Startup will not affect your personal documents, photos, or installed programs.

What should I do if the blue screen happens right after a Windows Update?

If the error started immediately after installing a new Windows 11 cumulative update, go to Settings > Windows Update > Update history > Uninstall updates. Remove the most recent quality update to restore system stability while Microsoft patches the driver conflict.

Did updating your graphics driver clear up the blue screen loop, or did a quick SFC command save the day? Drop a comment below and let me know which fix worked for your setup!