Windows BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x0000007E)
Criticalbsod
Overview
Windows BSOD error 0x0000007E occurs when a system thread generates an exception that the error handler cannot catch, typically caused by driver issues.
Key Details
- Stop code: 0x0000007E — unhandled exception in a kernel thread
- Parameter 1 indicates the exception code (e.g., 0xC0000005 = access violation)
- Parameter 2 shows the address where the exception occurred
- Often names a specific .sys driver file on the BSOD screen
- Can occur during boot, making it hard to access Safe Mode
Common Causes
- Incompatible or corrupt device driver (.sys file)
- Insufficient disk space on the system partition
- Incompatible BIOS version after a Windows upgrade
- Corrupted system files or Windows installation
- Faulty hardware such as RAM or hard drive
Steps
- 1Note the driver file name shown on the BSOD screen (e.g., nvlddmkm.sys)
- 2Boot into Safe Mode (hold Shift while clicking Restart) and uninstall the offending driver
- 3Run sfc /scannow from an elevated Command Prompt
- 4Run DISM /Online /Cleanup-Image /RestoreHealth
- 5Check for BIOS updates from your PC manufacturer
Tags
windowsbsodsystem-thread-exceptiondrivercrash
More in Bsod
windows-0000000A-irql-not-less-or-equalWindows Error 0x0000000A — IRQL NOT LESS OR EQUAL
Criticalwindows-00000050-page-fault-in-nonpaged-areaWindows Error 0x00000050 — PAGE FAULT IN NONPAGED AREA
Criticalwindows-0000007E-system-thread-exception-not-handledWindows Error 0x0000007E — SYSTEM THREAD EXCEPTION NOT HANDLED
Criticalwindows-0000007A-kernel-data-inpage-errorWindows Error 0x0000007A — KERNEL DATA INPAGE ERROR
Criticalwindows-000000EF-critical-process-diedWindows Error 0x000000EF — CRITICAL PROCESS DIED
Criticalwindows-00000133-dpc-watchdog-violationWindows Error 0x00000133 — DPC WATCHDOG VIOLATION
CriticalFrequently Asked Questions
The BSOD screen often lists the .sys file name. You can also check Event Viewer > Windows Logs > System for the faulting module.