Your computer crashes to a blue screen displaying the stop code SYSTEM_THREAD_EXCEPTION_NOT_HANDLED with the error value 0x0000007E. The system may restart automatically after the crash, or it may get stuck in a loop of crashing and restarting before Windows can fully load. This error means a system thread generated an exception that the error handler did not catch — typically caused by a faulty driver, corrupted system file, incompatible hardware, or insufficient disk space preventing the system from handling the exception.
What error 0x0000007E means
The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED error occurs when a kernel-mode thread produces an unhandled exception. The blue screen usually names the specific driver file that caused the crash (a .sys file listed on the screen or in the crash dump). This file name is the most important clue for diagnosis
Common driver files associated with this error include atikmdag.sys (AMD graphics), nvlddmkm.sys (NVIDIA graphics), ntfs.sys (file system), win32k.sys (Windows graphics subsystem), and various third-party .sys files from antivirus, VPN, or utility software
The error can be triggered during startup (preventing Windows from loading), during normal use (random crashes), or when performing specific actions (launching a game, connecting a USB device, or waking from sleep)
Boot into Safe Mode
If the error prevents Windows from starting normally, boot into Safe Mode to troubleshoot. Force-interrupt the boot process three times (power on, wait for the Windows logo, hold the power button to force shutdown, repeat) to trigger Automatic Repair. Select Advanced Options, Troubleshoot, Advanced Options, Startup Settings, Restart, then press 4 or 5 for Safe Mode
Safe Mode loads only essential drivers, bypassing the problematic driver that causes the crash. Once in Safe Mode, you can uninstall drivers, run system repairs, or check for other causes
If the blue screen names a specific .sys file, note it before entering Safe Mode. This file identifies the driver that needs to be updated, rolled back, or uninstalled
Update or roll back the graphics driver
Graphics drivers are the most common cause of this error. If the blue screen mentions atikmdag.sys, amdkmdag.sys, nvlddmkm.sys, or igdkmd64.sys, the GPU driver needs attention. In Safe Mode, open Device Manager, expand Display Adapters, right-click the GPU, and select Update Driver or Roll Back Driver
If the error started after a driver update, roll back to the previous version. If the error appeared without a recent driver change, update to the latest version from the GPU manufacturer website. For persistent issues, use a clean install: download the latest driver, use DDU (Display Driver Uninstaller) to completely remove the current driver in Safe Mode, then install the new driver fresh
Uninstall recently installed software
If the error started after installing new software, that software may have installed a kernel driver that causes the crash. In Safe Mode, open Settings, Apps, Installed Apps, sort by install date, and uninstall the most recent additions
Antivirus software, VPN clients, virtual machine software, and system utilities frequently install kernel drivers that can conflict with Windows. If you cannot identify the specific program, try uninstalling these categories of software first
Run System File Checker
Corrupted system files can cause this error when Windows encounters a damaged file during normal operation. In Safe Mode, open Command Prompt as Administrator and run sfc /scannow. The System File Checker scans all protected system files and replaces corrupted ones
If SFC reports corruption it cannot fix, run DISM /Online /Cleanup-Image /RestoreHealth first to repair the component store, then run SFC again. These tools can resolve crashes caused by damaged Windows system files including ntfs.sys and win32k.sys
Check disk space
Insufficient disk space on the system drive can cause this error because Windows cannot create the page file, temporary files, or crash dump files needed to handle exceptions. If the C drive is critically low (less than 1 GB free), the system cannot recover from exceptions and crashes instead
In Safe Mode, check the free space on C drive. If it is critically low, delete temporary files (open the Temp folder from the Run dialog using %temp%), empty the Recycle Bin, and run Disk Cleanup to free space. The system needs at least several gigabytes of free space to operate reliably
Check for hardware problems
Faulty RAM can cause this error because corrupted memory contents trigger exceptions when the processor tries to execute garbled instructions. Run the Windows Memory Diagnostic: search for Memory Diagnostic in the Start menu, select Restart Now and Check for Problems. The tool runs a memory test during the next restart
If the memory diagnostic finds errors, a RAM module is defective. Open the computer, remove one RAM stick at a time, and test with each individual stick to identify which module is faulty. Replace the defective module
Overheating can cause intermittent crashes including this error. If the crash happens during demanding tasks (gaming, rendering), check CPU and GPU temperatures with a monitoring tool. Clean dust from heatsinks and fans if temperatures are excessive
Use System Restore
System Restore can revert the system to a point before the error started appearing. In the Advanced Options menu (from the Automatic Repair screen or from Safe Mode), select System Restore. Choose a restore point dated before the first occurrence of the blue screen
System Restore reverts system files, drivers, and registry settings without affecting personal files. If the error was caused by a driver update, software installation, or Windows Update, System Restore undoes those changes
Analyze the crash dump
Windows saves crash dump files that contain detailed information about what caused the blue screen. The minidump files are stored in C colon Windows Minidump. These files can be analyzed with the free WinDbg tool from Microsoft to identify the exact driver and code location that triggered the crash
Open the dump file in WinDbg and run the analyze command with the verbose flag. The analysis output names the faulting module, the exception code, and a stack trace showing the sequence of events that led to the crash. This information pinpoints the exact cause when the blue screen message is too generic
Check BIOS settings
Incorrect BIOS settings related to memory timing, CPU voltage, or PCIe configuration can cause system thread exceptions. If you recently changed BIOS settings or updated the BIOS, reset to default values. Enter BIOS during startup and load Optimized Defaults
If the error appeared after installing new hardware (a new GPU, RAM, or expansion card), check BIOS compatibility settings. Some hardware requires specific BIOS options (like PCIe generation setting, UEFI vs Legacy boot mode, or Above 4G Decoding) to function correctly
Need help with this blue screen?
If your computer keeps showing the 0x0000007E blue screen error and the troubleshooting steps above have not resolved it, LuxuriousComputers Repair can diagnose the crash dumps, identify the faulting driver, update or replace problematic hardware drivers, run system repairs, and get your computer running without blue screen crashes.