Fix SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x0000007E) Windows 11/10

There are two versions of this blue screen, and which one you have changes everything.

In the first, the PC restarts on its own and you land back on the desktop. In the second, Windows crashes every single time it tries to start, loops through Automatic Repair, and never gives you a usable screen. Either way the message is the same: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, stop code 0x0000007E.

The good news is that this is one of the most informative stop codes Windows produces. Unlike a generic crash, it usually tells you — by name — which driver is responsible. Once you know that, the fix is often a single driver update or a one-line command, and your files are never at risk.

What SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x0000007E) means

A system thread is a task the Windows kernel runs in the background on its own behalf. When one of those threads raises an exception that nobody catches, Windows has no safe way to continue — the thread is part of the operating system itself — so it stops the machine rather than risk silent corruption.

In practice, a kernel thread is almost always executing code on behalf of a device driver. So 0x0000007E is usually a driver bug, a driver that was never updated for your Windows version, or a driver that has been damaged on disk.

Reading the four parameters

Microsoft’s bug-check reference documents what each parameter on the blue screen tells you:

The exception codes you will see most often in parameter 1:

• 0x80000002 — STATUS_DATATYPE_MISALIGNMENT: a driver touched data that was not aligned the way the processor requires
• 0x80000003 — STATUS_BREAKPOINT: a driver hit a hard-coded breakpoint or failed assertion and no kernel debugger was attached
• 0xC0000005 — STATUS_ACCESS_VIOLATION: a driver tried to read or write memory it did not own. This is the most common one and almost always points at a specific driver.

Drivers that show up again and again

You do not need to memorise this list — just recognise the pattern:

• nvlddmkm.sys — NVIDIA graphics
• atikmdag.sys / amdkmdag.sys — AMD graphics
• igdkmdn64.sys — Intel integrated graphics
• storahci.sys, iaStorA.sys, e1d65x64.sys — storage and network
• ntfs.sys — the file system driver; often means disk corruption or a failing drive rather than a bug in the driver
• win32k.sys — Microsoft specifically flags this one: it very often indicates a third-party remote-control or screen-sharing program hooking into the graphics stack

Method 1 — Boot into Safe Mode and remove the named driver

Safe Mode loads only the drivers Windows strictly needs. If the PC is stable there and crashes in normal mode, a third-party driver is confirmed as the cause.

1. Force three interrupted boots (hold the power button for 10 seconds as the logo appears, three times) to reach the Recovery Environment, or use one of the other ways in.
2. Go to Troubleshoot → Advanced options → Startup Settings → Restart, then press 5 for Safe Mode with Networking.
3. Open Device Manager, expand Display adapters, right-click your GPU and choose Uninstall device. Tick Delete the driver software for this device if it is offered.
4. Restart normally, then install a fresh driver downloaded from NVIDIA, AMD or Intel — not from Windows Update, and not from a driver-pack site.

If Safe Mode also crashes, the problem is more likely hardware or a core system file. Skip to Method 4 and Method 5.

If you cannot reach Safe Mode: remove the driver from the command line

dism /Image:C:\ /Get-Drivers
dism /Image:C:\ /Remove-Driver /Driver:oem12.inf

Replace C: with your Windows volume as seen from recovery, and oem12.inf with the published name from the first command.

Method 2 — Update firmware, then disable BIOS memory caching and shadowing

This is not filler advice; Microsoft lists it directly in its resolution for 0x0000007E. Outdated ACPI or system firmware is a documented cause, and so is BIOS-level memory caching or shadowing.

1. Visit your PC or motherboard manufacturer’s support page and install the latest BIOS/UEFI update. On branded laptops and prebuilts, use the manufacturer’s updater rather than a generic flash tool.
2. After updating, install the latest chipset driver from the same page.
3. Enter BIOS/UEFI and look for options named Cache, Shadow, Memory Caching or Video BIOS Shadow. Disable them.
4. While you are there, confirm no CPU or memory overclock or XMP/DOCP profile is enabled. If one is, turn it off and test.

Method 3 — Test your memory

If the blue screen names a different driver each time, stop chasing drivers. Randomised crashes with varying symptoms are the classic signature of faulty RAM.

1. Press Win + R, type mdsched.exe and press Enter.
2. Choose Restart now and check for problems.
3. Let the test complete — a full pass with the extended setting is worth the extra time.

Results appear in Event Viewer → Windows Logs → System with the source MemoryDiagnostics-Results. If anything is reported, test each stick individually to find the bad module.

Method 4 — Repair Windows system files

A damaged system file can be the difference between a driver working and crashing. Run DISM first, then SFC:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

If Windows will not start, run them against the offline installation from recovery, replacing C: with the correct volume:

DISM /Image:C:\ /Cleanup-Image /RestoreHealth
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Then check the disk itself, because file-system corruption is both a cause and a consequence of repeated crashes:

chkdsk C: /f

DISM errors such as 0x800f081f or 0x80073712 are fixable — see the DISM and SFC error guide, or the full system-file repair walkthrough.

Method 5 — Read the crash dump and let it name the driver

Guessing is slow. Windows writes a small memory dump to C:\Windows\Minidump on every crash, and that file contains the exact driver that faulted.

• Make sure dumps are enabled: Control Panel → System → Advanced system settings → Startup and Recovery → Settings, and set Write debugging information to Small memory dump (256 KB).
• Use the steps in how to view or share a memory .dmp file to read it.
• Or let the toolkit parse it for you — see below.

If no dump file exists at all, that is itself a clue, and there is a diagnostic that fixes it.

Method 6 — Rule out hardware and recently added software

Microsoft’s guidance here is straightforward: confirm any new hardware is on the compatible list, remove drivers or services you added recently, and run the manufacturer’s hardware diagnostics.

• Unplug everything non-essential — printers, docks, capture cards, external drives, USB hubs.
• Uninstall third-party antivirus and remote-control software temporarily. Security filter drivers and remote-desktop hooks are two of the most common non-obvious causes of 0x7E.
• If you added RAM or an SSD recently, remove it and retest.
• Run the built-in hardware diagnostics — usually accessible by pressing F12 or a vendor-specific key at boot.

The one-click option: find the guilty driver without a debugger

Fix 0x0000007E in three steps

1. Build a rescue USB on any working PC with the toolkit’s Create Rescue USB function, then boot the broken machine from it.
2. Run the environment scan so the toolkit locates your Windows installation, its drives and its crash dumps.
3. Open Analyze & Fix BSOD (or pick SYSTEM_THREAD_EXCEPTION_NOT_HANDLED from the error list) and press Run Selected. It reads the dump, names the driver, and disables or repairs it — then reboots you into a working desktop.

Frequently asked questions

Is SYSTEM_THREAD_EXCEPTION_NOT_HANDLED caused by hardware or software?

Mostly software — specifically a device driver. But faulty RAM, an unstable overclock and outdated firmware produce identical symptoms, which is why the memory test and BIOS update are on this list rather than buried at the end.

The blue screen restarts too fast to read. How do I see the driver name?

Disable automatic restart: Control Panel → System → Advanced system settings → Startup and Recovery → Settings and untick Automatically restart. If Windows will not boot at all, read the dump from another PC or with the toolkit instead.

Can a Windows Update cause 0x0000007E?

Yes. An update can deliver a driver that does not suit your hardware, or leave a pending operation half-applied. Remove the latest quality update from Troubleshoot → Advanced options → Uninstall Updates, or roll the driver back in Device Manager.

Does this stop code mean my drive is failing?

Not usually. If ntfs.sys or a storage driver is named, run chkdsk and check the drive’s SMART health — but 0x7E is far more often a driver than a disk. Confirm before you replace anything: how to check hard disk health.

I fixed it, but it keeps coming back every few days.

Then the driver was never the root cause. Enable small memory dumps so each crash is recorded, and compare two dumps. If the named driver differs each time, suspect RAM, the power supply, or thermals rather than software.

Conclusion

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED is a stop code that hands you the answer if you know where to look. Capture the driver name, confirm it with Safe Mode, remove or update that driver, and clear the two hardware suspects Microsoft calls out — outdated firmware and faulty memory.

If reading a crash dump is more than you signed up for, the VMTechs Boot Repair Toolkit does the analysis offline, names the driver, and applies the repair — even on a PC that refuses to start.

Please follow and like us: