System Thread Exception Not Handled (0x7E): Fix It, Even in a Loop

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (bug check 0x7E) appears when a system thread raises an error and nothing catches it. Microsoft treats 0x1000007E as the same bug check with the same parameters. System threads are kernel worker threads that Windows and drivers use for background jobs such as starting devices, handling power changes and moving data. No program is involved, which is why this code so often strikes during startup, while drivers initialize.

Microsoft’s advice for it is unusually direct: if the bug check message names a driver, disable or remove that driver. When Windows can identify the file, it appears under What failed and ends in .sys. If nothing is named, or only ntoskrnl.exe, the crash dumps are the next place to look.

The other big clue is timing. A 0x7E that began on the first restart after a driver, Windows or BIOS update very likely comes from that update; a system thread exception not handled after driver update is the clearest case, so roll that driver back first. If the PC can’t stay up long enough to fix anything, as in a system thread exception not handled boot loop, go straight to the Safe Mode and recovery sections below.

Recognize the file on the screen

For anything else, search for the file name on the PC or device maker’s support site. In Safe Mode, you can also search C:\Windows\System32 for the file and read the product name and copyright on its Details tab.

As the Intel Arc case shows, the fix isn’t always the older driver: when the maker has published a version that addresses the crash, update rather than roll back.

No file under What failed?

Check Event Viewer > Windows Logs > System for device or driver errors just before each crash; Microsoft suggests this log for finding the device behind 0x7E. If nothing stands out, use the random crashes section below.

Timing: what changed tells you what to undo

Settings > Windows Update > Update history (on Windows 10, Update & Security > Windows Update > View update history) lists driver updates with install dates, and Reliability Monitor shows them on the same timeline as each crash.

The last row isn’t hypothetical. Microsoft’s article on the July 2024 CrowdStrike incident, KB5042421, describes Windows PCs stuck in a restart loop with 0x50 or 0x7E on the blue screen.

Fix it from Safe Mode

Safe Mode starts Windows with a limited set of drivers, so a third-party driver that crashes normal startup usually stays out of the way. Have your BitLocker recovery key ready first (see where to find your BitLocker recovery key). Then open the Windows Recovery Environment (WinRE): Windows opens it by itself after two failed starts in a row, or hold Shift and select Power > Restart at the sign-in screen. Choose Troubleshoot > Advanced options > Startup Settings > Restart, then press 4, or 5 for Safe Mode with Networking if you’ll need to download a driver.

1. Roll back. In Device Manager, open the device that owns the named file, then Properties > Driver > Roll Back Driver. The button is grayed out when Windows has no earlier driver stored for that device.
2. Or uninstall. Right-click the device, select Uninstall device, tick Attempt to remove the driver for this device (on Windows 10, Delete the driver software for this device) and confirm. Windows falls back to a basic built-in driver where one exists, such as the basic display adapter for graphics.
3. Or disable. For a device you can do without, such as a webcam or card reader, Disable device is the quickest test and easy to reverse.
4. Restart normally. If Windows starts and stays up, install a known-good driver from the PC maker before reconnecting anything else.
5. Stop it coming straight back. Windows Update can reinstall the same driver. Use Settings > Windows Update > Pause updates while you get the fixed version, then resume so security updates keep arriving.

Don’t disable or remove storage controller, chipset or disk encryption drivers this way. Windows may be unable to read its own drive afterward.

Stuck in a loop: Startup Repair and the rollback tools

When even Safe Mode crashes, or the PC cycles between the stop screen and a restart, work through the WinRE tools from least to most disruptive. If WinRE doesn’t open by itself, force it by interrupting startup twice with the power button. Don’t do that while the screen shows Working on updates or Undoing changes with progress still moving: cutting power then can damage system files and make the loop worse.

1. Startup Repair, under Advanced options. It fixes common startup problems without touching your files; if it can’t repair the PC, move on.
2. Uninstall Updates, if the loop began right after Windows Update. Remove the latest quality update first; remove a feature update only if one just installed.
3. System Restore, if a restore point predates the problem. It rolls system files and settings back to that point without touching personal files; apps and drivers installed since then are removed.
4. Remove the driver offline. Open Command Prompt from Advanced options, unlock the drive if BitLocker asks (our automatic repair loop guide shows how), and check that dir C:\Windows finds Windows; if not, find its letter and use that below. dism /image:C:\ /get-drivers lists third-party driver packages, each with a published name such as oem12.inf, a class and a provider. Find the one matching the stop-screen file, such as NVIDIA and Display for nvlddmkm.sys, and remove it with dism /image:C:\ /remove-driver /driver:oem12.inf, using the real number. Microsoft warns that removing a boot-critical package can leave Windows unable to start, so leave storage controller and disk encryption packages alone, and get help if more than one entry could fit.

Quick machine recovery on Windows 11

Windows 11 PCs with Quick machine recovery turned on, the default on Home and unmanaged Pro PCs as of October 2026, also check Windows Update from WinRE for a fix Microsoft has published for widespread boot failures. It helps in a mass incident, not with your particular driver, and Windows 10 doesn’t have it.

Random crashes: read the four values in the dump

When the crashes come at random and no file is named, the four parameters, read in Reliability Monitor or WinDbg as our blue screen of death guide describes, carry more than usual for this code:

If !analyze -v says Probably caused by : ntkrnlmp.exe, the kernel only caught the fault: use the context record (row 4) and look down the stack for the first module that isn’t part of Windows. If several dumps still point nowhere and a memory test passes, Driver Verifier, also in the blue screen guide, can make the faulty driver name itself.

Unlike SYSTEM_SERVICE_EXCEPTION (0x3B), which strikes while the kernel works on a program’s request, 0x7E happens in Windows’ own background threads, so there’s no app to blame. If your crashes alternate between the two codes, our system service exception guide covers the app-triggered side.

Offices: keep one bad driver from stopping every PC

• Pilot updates. Let one or two PCs of each model take driver, BIOS and security-agent updates several days ahead of everyone else. Intune’s driver update policies let you approve drivers per group of devices; they need Intune plus a Windows license that includes Windows Autopatch, such as Microsoft 365 Business Premium or Windows Enterprise E3/E5.
• Decide on Quick machine recovery. It’s off by default once a PC is managed. Admins can turn on cloud remediation and automatic retries through the Recovery CSP, for example from Intune, or with reagentc. Microsoft calls it best-effort and, as of October 2026, limits its test mode to Windows Insider devices, so treat it as a backstop, not your recovery plan.
• Keep BitLocker keys retrievable. Make sure recovery keys are backed up to Microsoft Entra ID or Active Directory and that someone besides the laptop’s user can get at them.

When it’s hardware, and when to stop

Microsoft lists hardware incompatibilities, memory conflicts and IRQ conflicts among the causes of 0x7E, and suggests the PC maker’s hardware diagnostics and any ACPI or firmware updates it offers. Treat it as hardware when:

• Crashes continue in Safe Mode after you’ve removed the named driver.
• The stop screen names a different file each time, or other stop codes start appearing; run a memory test and the PC maker’s diagnostics.
• A newly added part doesn’t list your Windows version as supported.

Before a BIOS or firmware update, back up, suspend BitLocker, plug a laptop into AC power and never interrupt the update: a failed flash can leave the PC unable to start.

Stop and get help if you don’t have the BitLocker recovery key, if the only remaining option is a reset and your backups aren’t current, or if the PC never stays up long enough to work on. A PC stuck in a boot loop needs someone at the keyboard to reach Safe Mode first; if nobody can be there, an on-site visit can be arranged through vetted local partner technicians as a separate paid add-on, where available. Once the PC reaches the desktop, or Safe Mode with Networking where a remote session can be established, this is a typical $59 remote fix: with your approval, a technician finds the driver from the stop screen and dumps, then rolls it back or replaces it while you watch. If it turns out to be hardware, a remote session can help confirm that, but parts aren’t included. See how remote support works.

Common questions

Can I fix SYSTEM_THREAD_EXCEPTION_NOT_HANDLED without losing my files?

Usually, yes. Safe Mode, rolling back or uninstalling a driver, Startup Repair, Uninstall Updates and System Restore all leave your documents alone. Only Reset this PC with Remove everything, or a clean install, erases personal files. If you can reach Safe Mode with Networking, copy anything important to an external drive or cloud storage before trying the more drastic options.

What is the difference between 0x7E and 0x1000007E?

For troubleshooting, nothing. Microsoft documents 0x1000007E as having the same meaning and the same four parameters as 0x7E: a system thread raised an exception that wasn’t handled. You may see either value in Reliability Monitor, Event Viewer or a vendor’s support article, and the same steps apply: identify the driver named, then roll it back, update it or remove it.

Is it safe to rename the .sys file named on the blue screen?

Only for a third-party driver you can live without, and only as a last resort. Renaming the file stops it loading, but if it belongs to storage, disk encryption or security software, Windows may not start at all. Never rename a Windows file such as dxgmms2.sys or ntfs.sys; a third-party driver working with it is the likelier suspect. Uninstalling the device or removing its package with DISM is cleaner. If you do rename one, add .old to the name instead of deleting it, so you can undo it.

Does SYSTEM_THREAD_EXCEPTION_NOT_HANDLED mean my hardware is failing?

Usually not. A specific driver is the most common explanation, especially when the same file appears every time and the crash began after an update. Hardware becomes the likelier cause when crashes continue in Safe Mode, the named file keeps changing, other stop codes appear, or the PC maker’s diagnostics or a memory test report errors.

Will resetting my PC fix SYSTEM_THREAD_EXCEPTION_NOT_HANDLED?

Sometimes, but it’s the slowest fix and not always a lasting one. Reset this PC reinstalls Windows and removes the apps and drivers you installed, yet Windows Update or the PC maker’s update app can deliver the same driver again soon afterward, and a reset can’t fix failing memory or other hardware. Try Safe Mode, the driver rollback and the recovery tools first. If you do reset, copy your files off beforehand, then install the PC maker’s driver for the device that crashed before anything else.

Will Windows Update reinstall the driver I just removed?

It may. Windows Update offers drivers automatically, so the same version can come back within a day. Pause updates in Settings while you install a known-good driver from the PC maker, then resume them. In a business, Intune driver update policies (which need Intune plus a Windows license that includes Windows Autopatch, such as Microsoft 365 Business Premium or Windows Enterprise E3/E5) or the Group Policy setting that excludes drivers from Windows Update give you lasting control across every PC.