SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x7E): The Crash That Names Its Driver
In plain English
The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED stop code, often shown with 0x7E, usually means a driver or low-level system file crashed hard enough to bring Windows down. On this page, the first thing to check is the driver name on the blue screen itself.
First safe step
Look for the driver file name on the blue screen, a .sys name such as nvlddmkm.sys, and write it down exactly as shown, or take a photo before the PC restarts. One wrong letter can send you toward the wrong fix.
The file name on the screen is the fix list. Start there.
The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED stop code, often shown with 0x7E, usually means a driver or low-level system file crashed hard enough to bring Windows down. On this page, the first thing to check is the driver name on the blue screen itself. If you need the bigger picture on related crashes, start with Blue and Black Screen Stop Codes in Plain English.
This crash is one of the more useful ones because it often names the exact file that failed, usually a .sys driver such as nvlddmkm.sys or rtwlane.sys. Write that name down exactly, or take a photo before the PC restarts. One wrong letter can send you toward the wrong fix.
If your screen does not name any driver file, do not guess. A missing file name often fits better with the 0x0A page for crashes that do not name a driver or the 0x3B page when the screen points to a service or the driver name is missing. If the blue screen started right after Patch Tuesday or another install, jump first to what to do first if the crash started right after an update.
What this stop code usually means and where to look first
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED with code 0x7E means Windows hit an exception inside a system thread and could not recover cleanly. In plain English, a driver or low-level system component tried to do something Windows could not handle, and the blue screen stopped the PC before more damage could happen.
Your first job is simple: look for the exact driver file name on the screen and write it down exactly as shown. If you see a file such as nvlddmkm.sys, rtwlane.sys, or another .sys name, that is usually the best clue on the whole screen.
A named driver usually points to the next fix path. It is a better lead than doing a random reset, changing lots of settings, or guessing which part failed. If the crash began right after a patch or driver install, start with what to do first if the crash started right after an update before you make bigger changes.
If your screen does not name any driver file, stop here and switch to a better match instead of guessing. Use the 0x0A page for crashes that do not name a driver, or use the 0x3B page when the screen points to a service or the driver name is missing. If Windows will not stay up long enough to read the screen or take notes, use Safe Mode when Windows will not stay up long enough to troubleshoot.
1 Read the driver name on screen the right way Free
On most blue screens, the driver clue appears near the stop code text or lower on the screen as a file name such as nvlddmkm.sys. The part that matters is the exact file name, including the letters before .sys. Even a short name is useful, because it often points to one specific graphics, Wi-Fi, audio, storage, or security driver.
Don't copy extra text around it unless it is part of the same file name. The stop code, percentages, and restart message are less helpful here than the exact .sys name. If the screen vanishes too fast to read, a phone photo is fine. A blurry picture that still shows rtwlane.sys is better than guessing from memory.
Write the name down exactly as shown, or take a clear photo before the PC restarts. Watch for common mix-ups like l and I, or 0 and O. If the crash started right after a patch or driver install, also note the date, then use what to do first if the crash started right after an update before making bigger changes.
If you can only catch part of the screen, keep the photo anyway. The next section shows what to do with a named driver file. If your screen never shows one, don't force a match. Use the 0x0A page for crashes that do not name a driver or the 0x3B page when the screen points to a service or the driver name is missing.
2 What to do when the screen names a driver file Free
- If the blue screen names a driver file, start with the newest change first. Restart once, disconnect any hardware you just added, and think about what changed in the last day or two: a driver update, a new USB device, security software, VPN software, or a graphics or Wi-Fi package. If the crash began right after patching, follow what to do first if the crash started right after an update before you change several things at once.
- Next, act on the named driver itself. Open
Device Manager, find the related device, then try the safest option that fits your case:Roll Back Driverif the problem began after a driver update,Update driverif you know the current one is old, orUninstall deviceif the driver was added with new hardware or software. Then restart and test again. - If Windows will not stay up long enough to do that, use Safe Mode when Windows will not stay up long enough to troubleshoot, then remove or roll back the driver there. For laptops and prebuilt desktops, the safest replacement driver usually comes from the PC maker's support page. For a part you installed yourself, such as a graphics card or Wi-Fi adapter, use the hardware maker's official support page. Avoid random driver download sites, even if they claim to match the exact
.sysfile. - If the named file appears to belong to security software, VPN software, audio tools, RGB tools, or motherboard utility software, try removing that program completely and restart before reinstalling anything. If the file points to a Microsoft or system service instead of a clear device driver, or the clue stops making sense once you check it, move to the
0x0Apage for crashes that do not name a driver or the0x3Bpage when the screen points to a service or the driver name is missing.
✓ Crashes gone? You can stop here.
3 If it started after an update, use the update path first Free
If the blue screen started right after Patch Tuesday, a feature update, or an optional driver update, use the update path first. A Windows update does not always break the PC by itself. It often exposes a driver that was already unstable, or it pulls in a device update that does not get along with your hardware.
Start with timing. If the first crash happened the same day as an update, follow what to do first if the crash started right after an update. Keep the driver clue from this page in view while you do that. If your screen names nvlddmkm.sys, rtwlane.sys, or another .sys file, that name still tells you which driver to check first.
If Windows will not stay up long enough to confirm what changed, use Safe Mode when Windows will not stay up long enough to troubleshoot and then check Update history and recent driver changes. That order matters. Confirm the update timing first, then match it to the named driver or device, instead of changing several things at once.
If the crash began after an update but your blue screen never shows a driver file, do not guess from timing alone. Use the 0x0A page for crashes that do not name a driver or the 0x3B page when the screen points to a service or the driver name is missing.
4 When no driver file appears, switch to the right stop-code page
If your blue screen shows SYSTEM_THREAD_EXCEPTION_NOT_HANDLED but does not name any .sys file, this page is probably not your best match. At that point, it is better to stop guessing and switch to the 0x0A page for crashes that do not name a driver.
Use that handoff when the crash still feels driver-related, for example after a device change, a driver install, or a restart loop with no clear file name on screen. If the trouble began right after Windows updating, check what to do first if the crash started right after an update before you change more settings.
Switch instead to the 0x3B page when the screen points to a service or the driver name is missing. That is the better fit when the screen mentions a system service, the crash happens while signing in or opening apps, or the clue on screen does not look like a driver file.
If Windows will not stay up long enough to read anything, start with Safe Mode when Windows will not stay up long enough to troubleshoot, then follow the page that matches what you actually see. A short detour now is faster than trying fixes for the wrong stop code.
5 Try the safest fixes before deeper repair Free
If Windows is still booting well enough, start with the least risky change: remove the newest driver or device software tied to the file name you saw, then restart. If the crash keeps coming back before you can work, use Safe Mode and try the same cleanup there. For a quick route to the right recovery steps, see what to do first if the crash started right after an update.
If the named file points to a graphics, Wi-Fi, audio, VPN, or security driver, uninstall the most recent version of that software first. On laptops and prebuilt desktops, get the next version from the PC maker’s support page before you try a random download site. If the device is a self-installed part, use the hardware maker’s own driver page instead.
When the driver is old rather than new, a newer release often fixes the crash. That is common after a Windows update exposes a weak driver, and it is also why the same file name can keep showing up after a reboot. If Windows will not stay up long enough to do this normally, use Safe Mode when Windows will not stay up long enough to troubleshoot.
Keep the changes small. One driver or one device at a time is enough, so you can tell which fix helped and avoid guessing at the cause.
6 When to stop troubleshooting and get help
If SYSTEM_THREAD_EXCEPTION_NOT_HANDLED keeps coming back with a different .sys name each time, the problem may be deeper than one bad driver. That pattern can point to memory, storage, or another hardware fault that keeps tripping different code paths.
Write down the exact stop code, the driver file name, and the last thing that changed before the crash, such as an update, new hardware, or security software. If you need the next best match, use site search or the main Blue and Black Screen Stop Codes in Plain English page for the closest fit.
The screen message is the clue, not the diagnosis by itself. If the named file keeps changing, that is a sign to look wider instead of chasing one driver name forever.
Frequently asked questions
What if 0x7E happened once and has not come back?
A single crash that does not return does not by itself mean hardware has failed. Note the driver name and the date, then use the PC normally. If it comes back, follow the path for that named driver.
Should I download a replacement for the named .sys file on its own?
No. Do not take a single .sys file from a download site. Get the full driver package from your PC maker first, or from the official hardware maker for a part you installed yourself.
The short version
0x7E is easier to work with than most blue screens because it often leaves a name behind. Write down that .sys file exactly as shown, act on that driver first, and let a missing name send you elsewhere instead of guessing at fixes.
If the crash keeps coming back, or the name changes each time, stop changing drivers and treat the pattern itself as the clue. Note what happened just before it, save your notes, and get help with those details in hand rather than trying one more download.
Different number on screen?
Type it exactly as it appears and get the plain-English answer.
Pop-up telling you to call?
That is a scam. Microsoft never asks you to phone a number.