How to Fix BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x0000007E)
What error 0x0000007E means
Windows runs thousands of threads — small units of executing code — at any moment. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (stop code 0x0000007E) means one of those threads threw an exception (a crash inside the code) that Windows couldn't catch or recover from, so it halted the whole system with a blue screen to prevent further damage. The name is technical, but the practical meaning is simpler: something running low-level on your PC broke in a way nothing was prepared for.
The best news about this blue screen is that it often names the exact driver file that faulted — names like nvlddmkm.sys (NVIDIA), igdkmd64.sys (Intel), or atikmdag.sys (AMD) right on the screen. That turns a vague crash into a specific target: fix that one driver and you're done. When no file is named, the usual suspects are a buggy or incompatible driver update, corrupted Windows system files, failing RAM feeding garbage data to running code, or an unstable overclock pushing hardware past its limits. Hardware failure is the minority cause; configuration is the majority. Work through the steps below in order and most people never need to touch a component.
Common causes
- Incompatible or corrupt graphics driver: NVIDIA, AMD, and Intel driver updates are the most common trigger — the crashes often begin shortly after an update or a botched install.
- Corrupted Windows system files: a failed update, a forced shutdown, or malware cleanup can leave system files damaged, and drivers then trip over the damage mid-execution.
- Failing RAM: defective memory cells feed garbage data to running threads, producing exactly the "unhandled exception" this blue screen reports.
- Unstable overclocking: pushed CPU, GPU, or memory clocks (including XMP/EXPO memory profiles) are a distinct trigger for uncaught thread exceptions.
- Overheating or failing hardware: sustained high temperatures or a dying drive/GPU can corrupt execution in ways the OS can't handle gracefully.
How to fix error 0x0000007E — step by step
Work through these fixes in order. If the blue screen named a driver file, steps 1–4 alone usually end the crashes.
- Read the driver name shown on the blue screen. Before you do anything else, capture the clue 0x0000007E often hands you for free. The blue screen sometimes lists the faulting file — nvlddmkm.sys means NVIDIA, igdkmd64.sys means Intel, atikmdag.sys means AMD. Photograph the screen or write the name down before the PC restarts. That single name tells you exactly which driver to roll back, update, or clean-install instead of guessing your way through every device.
- Boot into Safe Mode. Interrupt the boot process three times in a row (hold the power button during the Windows logo) to reach the Recovery screen. Go to Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 for Safe Mode. Safe Mode loads only Microsoft's own drivers, so if the PC is stable here, a third-party driver is guilty — and you can work on removing it without crashing mid-fix. If it crashes even in Safe Mode, system files, RAM, or hardware become the prime suspects.
- Roll back or update the suspect driver. Press Win + X and open Device Manager. Find the device that matches the driver name from the blue screen — graphics adapters are the usual suspect, but check sound, network, and chipset devices too. Right-click it, choose Properties, open the Driver tab, and click Roll Back Driver, choosing the most fitting reason. If a recent update started the crashes, this one click usually ends them. If the button is grayed out, click Update driver and search automatically, or use Uninstall device and restart — Windows will install its stable stock driver, which is older but reliable.
- Clean-install the graphics driver with DDU. When graphics drivers are implicated, a plain reinstall often isn't enough: leftover files and registry entries from previous versions are a classic 0x0000007E trigger. Download Display Driver Uninstaller (DDU) and the latest driver from NVIDIA, AMD, or Intel — not from Windows Update. Boot into Safe Mode, run DDU, select your GPU brand, and choose "Clean and restart." After rebooting normally, install the downloaded driver, pick Custom installation, and tick "Perform a clean installation." Then test stability for a while before declaring victory.
- Repair system files with SFC and DISM. If no single driver is obviously at fault, repair the foundation. Open an admin Terminal (right-click Start > Terminal (Admin)). First run
sfc /scannowand let it finish — it repairs protected Windows files. Then runDISM /Online /Cleanup-Image /RestoreHealth, which repairs the component store that SFC relies on. If SFC reported corruption it couldn't fix, run it again after DISM completes. Restart the PC and use it normally to see whether the crashes stop. - Test the RAM for errors. Unhandled thread exceptions are a classic symptom of defective memory, because bad cells silently feed wrong data into running code. Press Win + R, type
mdsched.exe, and run the Windows Memory Diagnostic, choosing "Restart now and check for problems." Let the test complete fully — any reported error means a memory stick is defective and needs replacing. For a deeper check, MemTest86 from a USB drive runs multiple passes and catches faults the built-in tool misses. - Reset any overclock and check temperatures. Restart into the BIOS/UEFI (usually Del or F2 during boot), restore default settings, and specifically disable XMP or EXPO memory profiles — pushed memory is a frequent 0x0000007E trigger. Back in Windows, check temperatures with a tool like HWMonitor: CPUs and GPUs sustaining 95°C+ under load can throw uncaught exceptions. If crashes stop at stock settings, your overclock was never stable; re-apply it gradually or accept stock stability.
Did this fix it? Quick checklist
- Driver named on the blue screen rolled back or clean-installed
- PC stable in Safe Mode and after each driver change
- SFC and DISM completed without unrepairable corruption
- Memory diagnostic passed with zero errors and overclocks reset
If crashes continue after all seven steps, open Event Viewer (Win + X > Event Viewer), go to Windows Logs > System, and look for BugCheck entries — the parameters and any named .sys file tell you exactly what faulted. You can also check the minidump files in C:\Windows\Minidump with a tool like BlueScreenView to confirm which driver or address keeps crashing. As a last resort, a clean Windows install removes every driver and damaged file at once: back up your files first and choose "Keep nothing" so nothing suspect survives.
Frequently asked questions
What causes SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x0000007E)?
A program thread threw an exception that Windows could not catch, almost always because a driver misbehaved. The most common triggers are incompatible or corrupt graphics drivers, corrupted system files, faulty RAM, or an unstable overclock. It is a software or configuration problem far more often than a dead component.
My 0x0000007E blue screen names a driver file. What does that mean?
It is the single most useful clue this error gives you. A name like nvlddmkm.sys, igdkmd64.sys, or atikmdag.sys identifies the exact driver that faulted, so you can go straight to rolling it back, updating it, or clean-installing it instead of guessing. Match the name to a GPU maker: NVIDIA, Intel, or AMD.
Can overclocking cause 0x0000007E?
Yes. Pushed CPU, GPU, or memory clocks cause exactly this kind of uncaught thread exception, which is why resetting everything to stock and disabling XMP or EXPO profiles is part of the fix list. If the crashes stop at stock settings, your overclock was not stable.
Will reinstalling Windows fix 0x0000007E?
Usually, yes, because it removes every corrupt driver and damaged system file at once. But it wipes your setup, so treat it as the last resort after Safe Mode driver rollback, a clean DDU install, SFC and DISM, a memory test, and resetting any overclock. Most cases are fixed without reinstalling.