The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED blue screen sends a clear message, but most users miss it. When a PC halts with stop code 0x1000007E, the screen often flashes a filename like nvlddmkm.sys, atikmdag.sys, or dxgmms2.sys. That tiny string of letters is the kernel’s cry for help—and in the overwhelming majority of cases, it’s pointing straight at a graphics driver problem. Community forums, Microsoft documentation, and third-party repair guides all converge on one finding: GPU and display drivers are the single most common cause of this particular crash. Understanding why unlocks a faster, more reliable fix than guesswork or hardware replacement.

What the stop code actually means

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x1000007E) is a kernel-level crash. It signals that a system thread executed code that triggered an exception—often an invalid memory access—and that exception went unhandled. Because Windows cannot safely continue, it initiates a stop. The filename shown alongside the stop code identifies the driver module that was active when the exception occurred, though it isn’t always the root cause. Still, it’s the strongest clue.

On modern versions of Windows 10 and 11, this error most frequently emerges during graphics-intensive tasks: gaming, video playback, or even hardware-accelerated web browsing. The dxgmms2.sys variant, in particular, is directly tied to the DirectX graphics stack, meaning anything that stresses the GPU can trigger the crash. MiniTool’s Partition Wizard documentation notes that an outdated or corrupted graphics card driver is the primary suspect for dxgmms2.sys BSODs, while faulty RAM, storage issues, or incompatible firmware can also contribute.

The telltale filename: your diagnostic shortcut

When the crash screen appears, jot down the filename. Ignore it and you lose the most valuable piece of evidence.

  • nvlddmkm.sys – NVIDIA graphics driver. A frequent culprit after driver updates or when an older GPU is pushed too hard.
  • atikmdag.sys / atikmdag64.sys – AMD graphics driver. Often crashes when overlays or conflicting utilities are active.
  • igdkmd64.sys – Intel integrated graphics. Common on laptops after a routine Windows update replaces a custom OEM driver with a generic one.
  • dxgmms2.sys – Microsoft’s DirectX kernel subsystem. This file rarely fails on its own; it’s collateral damage from a buggy display driver or a hardware issue that disrupts the graphics pipeline.

Community troubleshooting logs on forums like Tom’s Hardware and Reddit show that users who follow the filename trail are far more likely to resolve the stop error within the first few steps. One r/ZephyrusG14 thread, for instance, tied persistent nvlddmkm.sys crashes to a combination of NVIDIA driver version and power delivery—a reminder that while software is the usual suspect, hardware can masquerade as a driver fault.

Why GPU drivers dominate the blame

Graphics drivers run with kernel-level privileges. Unlike a user-mode application that crashes and closes, a misbehaving graphics driver can corrupt kernel memory or execute an illegal instruction at the highest privilege level, forcing Windows to stop immediately. The dxgmms2.sys file sits at the junction between the driver and DirectX APIs, so when the real culprit—say, nvlddmkm.sys—sends malformed data, dxgmms2.sys often takes the fall. That’s why you’ll see both filenames appear intermittently.

Microsoft’s official System File Checker documentation and community repair guides both emphasize starting with the graphics driver. The steps that follow reflect that consensus, arranged from least invasive to most aggressive.

Step 1: Boot into Safe Mode

Safe Mode loads only essential drivers and services. If the BSOD stops appearing, the cause is almost certainly a third-party driver or utility. Access Safe Mode by interrupting the boot process three times to trigger Automatic Repair, then navigate to Troubleshoot → Advanced options → Startup Settings → Restart → press 4 for Safe Mode. Alternatively, from a working desktop, use Settings → Update & Security → Recovery → Advanced startup. Once in Safe Mode, you can begin repairs.

Step 2: Update, roll back, or reinstall the graphics driver

Open Device Manager (Win + X), expand Display adapters, right-click the GPU, and visit the Driver tab. If the crash started immediately after a driver update, click Roll Back Driver. If that button is grayed out, select Update driver and let Windows search automatically. In many cases, Windows will install a stable version.

When the automatic approach fails, download the driver directly from NVIDIA, AMD, or Intel. For laptops, always check the manufacturer’s website first; OEMs often tune drivers for their specific power and thermal profiles. Tom’s Hardware reports that a clean reinstall of a known-good driver version resolves most nvlddmkm.sys and atikmdag.sys cases without further intervention.

For a completely clean slate, use Display Driver Uninstaller (DDU). Boot into Safe Mode, run DDU to wipe all traces of the current driver, then reboot and install the latest stable package. This step eliminates registry remnants and leftover files that can corrupt a new installation.

Step 3: Run SFC and DISM

Corrupted system files can turn a healthy driver into a crashing one. Open an elevated Command Prompt in Safe Mode or normal mode and execute:

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

DISM repairs the component store; SFC repairs system files. Microsoft recommends running DISM first. If SFC reports unrepairable items, consult Microsoft’s official offline repair guidance. Many community users find this clears dxgmms2.sys crashes that returned despite driver updates.

Step 4: Check disk health

Failing drives and file-system corruption can masquerade as driver bugs. Run chkdsk C: /f /r from an elevated Command Prompt and reboot if prompted. Then use the manufacturer’s SSD utility—Samsung Magician, Crucial Storage Executive, etc.—to check SMART status and update firmware. The original source from MiniTool Partition Wizard specifically links hard disk issues to dxgmms2.sys errors, and field reports confirm that a bad sector on a game drive can trigger reproducible BSODs every time a map loads.

Step 5: Disable overclocking and reset BIOS

CPU, GPU, and RAM overclocks push components beyond validated settings. A single incorrect memory access during a render call can trigger the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED stop. Reset BIOS to factory defaults, disable XMP profiles, and test. The original dxgmms2.sys guide also recommends resetting BIOS configuration as a potential fix, especially if the crash appeared after recent hardware changes.

Step 6: Targeted fixes for dxgmms2.sys

MiniTool’s article details several registry-level workarounds for dxgmms2.sys specifically:

  • Increase TdrDelay: Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers, create or modify DWORD TdrDelay, set Base to Decimal and value to 10. This gives the GPU more time to complete operations before Windows assumes a hang and fires the Timeout Detection and Recovery (TDR) sequence, which can trigger the BSOD.
  • Disable hardware acceleration: Under HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics, set DWORD DisableHWAcceleration to 1. This is a blunt workaround that trades performance for stability, disabling hardware-accelerated rendering for WPF applications.
  • Run DirectX Diagnostic Tool: Type dxdiag in the Start menu, open it, and let it check for DirectX issues. While it rarely fixes the problem alone, it can reveal version mismatches.

These registry tweaks are symptom suppressors, not cures. Use them only temporarily while you identify the root cause.

Step 7: System Restore and advanced diagnostics

If the BSOD started after a recent update or software install, launch System Restore and pick a restore point from before the change. System Restore doesn’t affect personal files but reverts drivers and system settings.

For stubborn cases, enable Driver Verifier (verifier.exe). This tool stresses drivers to force a crash, producing a minidump that can be analyzed in WinDbg or BlueScreenView. The minidump reveals exactly which module caused the exception. Community experts caution that Driver Verifier may trigger additional BSODs during testing—only enable it for diagnostics and disable it once the faulty driver is identified.

Collect minidumps from C:\Windows\Minidump and examine the stack trace. Often the offending driver appears clearly, eliminating guesswork. The original source doesn’t cover this, but community forums consistently rank dump analysis as the definitive method when simpler steps fail.

When hardware is the real enemy

If none of the software fixes hold, hardware becomes the prime suspect. Test RAM with Windows Memory Diagnostic or MemTest86. Test the GPU in another system or swap in a spare. Check PSU voltage stability with a multimeter or a dedicated tester. Anecdotal reports mention faulty DisplayPort cables causing nvlddmkm.sys crashes, and one Reddit thread documented GPU sag on a Zephyrus G14 leading to intermittent dxgmms2.sys stops. These are edge cases but worth a quick check before condemning expensive components.

Prevention and long-term hygiene

  • Keep graphics drivers updated through official channels, not Windows Update alone.
  • Create restore points before any driver change.
  • Use DDU when switching GPU brands or after a major OS upgrade.
  • Maintain regular backups; an in-place repair install preserves files and solves many stubborn corruptions.
  • Monitor storage health with SMART tools and act on warnings before they become BSODs.

The bottom line

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED looks scary, but in practice it’s one of the more cooperative stop codes. The filename on the screen, the stability of Safe Mode, and a methodical driver refresh solve at least eight out of ten cases. The dxgmms2.sys variant, while tied to the DirectX subsystem, almost always heals when the underlying GPU driver is properly reinstalled. Only after software and firmware fixes have been exhausted should hardware bear the blame. Follow the evidence, not the fear.