ThisCalculator

Everyday

Stop Code System Thread Exception Not Handled

Updated · Standard formula, shown below

The “SYSTEM_THREAD_EXCEPTION_NOT_HANDLED” Blue Screen of Death (BSOD) error means a system thread running in kernel mode triggered an unhandled exception, and Windows forcibly shut down to prevent damage. The fix usually involves updating or rolling back a driver, especially a graphics or storage driver, and the specific driver is named in the error message. Below is a complete guide to understanding and resolving this error on current Windows versions (10 and 11).

What This Error Actually Means

Windows runs many background threads (small units of work) inside the kernel, the core part of the OS that controls hardware and memory. When one of these threads encounters an error it cannot recover from—like trying to access invalid memory or executing an illegal instruction—the system stops. The error code is 0x0000007E, and the full message often lists a file name, such as nvlddmkm.sys (NVIDIA graphics) or iaStorA.sys (Intel storage). That file name is your primary clue: it identifies the driver that caused the crash.

This is not a random hardware failure. It is almost always a software conflict, a corrupt driver, or an incompatible update. The system is designed to stop rather than continue with corrupted memory, which could cause data loss or permanent damage.

Most Common Causes

  • Outdated or buggy graphics drivers — the most frequent trigger, especially after a Windows feature update.
  • Incompatible storage drivers — especially NVMe or RAID drivers that fail during boot or heavy I/O.
  • Recent Windows Update — a patch that conflicts with an existing driver.
  • Corrupted system files — damaged kernel files or driver store entries.
  • Overclocking or unstable hardware — less common, but a failing RAM stick or CPU instability can cause similar crashes.
  • Third-party antivirus or security software — kernel-level hooks can interfere with system threads.

Step-by-Step Fixes

Start with the simplest fix and move down the list. Back up important files before making major changes.

  1. Note the driver file name in the error message. Write it down; it tells you which driver to target.
  2. Boot into Safe Mode. Restart your PC, and at the sign-in screen, hold Shift while clicking Restart. Then go to Troubleshoot > Advanced options > Startup Settings > Restart, and press 4 or F4 for Safe Mode. If you cannot reach the sign-in screen, interrupt the boot loop three times by pressing the power button during startup to trigger automatic repair.
  3. Uninstall the problematic driver. In Safe Mode, right-click the Start button and select Device Manager. Find the device category (e.g., Display adapters), right-click the device, and choose Uninstall device. Check the box that says “Delete the driver software for this device” if it appears, then restart normally. Windows will reinstall a generic driver.
  4. Update the driver. If the crash happens again, go to the hardware manufacturer’s website (not Windows Update) and download the latest driver for your exact model. Install it, then restart.
  5. Roll back a recent Windows Update. Go to Settings > Windows Update > Update history > Uninstall updates. Remove the most recent quality update, then restart.
  6. Run System File Checker. Open Command Prompt as Administrator and run sfc /scannow. This repairs corrupted system files.
  7. Check for disk errors. In the same Command Prompt, run chkdsk /f /r and restart. This scans for bad sectors and file system errors.
  8. Disable overclocking. If you overclocked your CPU, GPU, or RAM, reset BIOS/UEFI to default settings and test again.
  9. Test RAM. Use Windows Memory Diagnostic (search for it in the Start menu) to check for memory errors. A failing RAM stick can cause this exact error.

How to Read the Error Message Correctly

Many users panic and miss the most important part. The full BSOD text often reads: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (driver_name.sys). That file name is the key. If you see atikmpag.sys, it’s AMD graphics; e1i65x64.sys is Intel Ethernet; rtwlane.sys is Realtek Wi-Fi. Do not attempt to delete the file directly—that will cause more problems. Instead, uninstall or update the driver that owns it. If no file name appears, use a tool like BlueScreenView (free, from a reputable source) to read the crash dump and identify the culprit.

Also note whether the error occurs during boot or after heavy use. Boot-time crashes often point to storage or system drivers; crashes under load point to graphics or power management.

Why Safe Mode Works (and What It Tells You)

Safe Mode loads only the minimum set of drivers. If the BSOD does not appear in Safe Mode, you have confirmed that a third-party driver is the cause. This is a diagnostic goldmine. It rules out hardware failure in most cases, because the hardware still works with generic drivers. If the error appears even in Safe Mode, the problem is likely a corrupted Windows component or failing hardware, and you should run the system file checker and memory test immediately.

Prevention and Long-Term Stability

  • Keep your GPU, chipset, and network drivers updated from manufacturer sites, not just Windows Update.
  • Pause Windows feature updates for a few weeks after a major release to let driver issues surface and get patched.
  • If you use third-party antivirus, consider switching to Windows Defender, which is less likely to conflict with kernel threads.
  • Monitor system temperatures. Overheating can cause random kernel exceptions.
  • After a crash, check the reliability monitor (search “reliability” in Start) to see which software failed before the BSOD.

Frequently Asked Questions

Can this error be caused by a virus?

Yes, but it’s rare. Rootkits and bootkits can inject code into kernel threads. If you suspect malware, run a full offline scan with Windows Defender (Settings > Privacy & Security > Windows Security > Virus & threat protection > Scan options > Microsoft Defender Offline scan).

Will I lose my files?

No, the BSOD itself does not delete files. However, if the crash happens during a disk write, there is a small risk of corruption. Always keep backups, and run chkdsk after a crash to repair any file system issues.

Why does it say “thread exception” and not “driver error”?

Because the exception happens inside a thread that belongs to a driver. The error is named after the thread, not the driver. The driver file name is provided separately to help you identify the source.

Should I reinstall Windows?

Only as a last resort. Try all the steps above first. If you have exhausted driver updates, system file checks, and hardware tests, a clean install will eliminate any software corruption. But this error is almost always fixable without reinstalling.

Is this error more common on laptops or desktops?

Laptops, because they use power-saving features and hybrid graphics (integrated + discrete) that add driver complexity. If you have a laptop, update both the Intel/AMD integrated graphics and the NVIDIA/AMD discrete graphics drivers.

Can a Windows Insider build cause this?

Yes. Insider builds are pre-release and often have driver compatibility issues. If you are on an Insider build, revert to the latest stable build via Settings > Windows Update > Windows Insider Program > Stop getting preview builds.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.