Windows BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x0000007E)

Windows BSOD error 0x0000007E occurs when a system thread generates an exception that the error handler cannot catch, typically caused by driver issues. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: 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. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: 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. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: Note the driver file name shown on the BSOD screen (e.g., nvlddmkm.sys). Boot into Safe Mode (hold Shift while clicking Restart) and uninstall the offending driver. Run sfc /scannow from an elevated Command Prompt. Run DISM /Online /Cleanup-Image /RestoreHealth. Check for BIOS updates from your PC manufacturer. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our Windows Error Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.