I know this error is infuriating—you're mid-battle, everything's smooth, then your screen freezes and you're back at the desktop. Let's fix it.
The Fast Fix: Reset Graphics and Update Drivers
Most DirectX 12 crashes on Windows 11 come down to two things: a stuck GPU state or a driver that doesn't play nice with DX12. Here's the order I recommend, and it works for most people within 10 minutes.
- Restart your PC. Not shutdown and boot—a full restart. On Windows 11, shutdown uses fast startup by default, which can leave GPU drivers in a half-dead state. Hit Start, then Power, then Restart. This alone clears a lot of DXGI_ERROR_DEVICE_REMOVED errors.
- Update your GPU driver. Go to the manufacturer's site—NVIDIA, AMD, or Intel—and download the latest driver for your exact card model. Don't rely on Windows Update; it's often months behind. For NVIDIA, use GeForce Experience or the manual search tool. For AMD, the Adrenalin software handles it.
- Clear the DirectX shader cache. Windows 11 stores compiled shaders to speed up games, but a corrupted cache can crash DX12 apps. Open Disk Cleanup (search for it in Start), select your C: drive, then check "DirectX Shader Cache" and "Delivery Optimization Files." Run it, then restart.
That's the 80% fix. If you're still crashing, move to the next section.
Why This Works
DirectX 12 is a low-level API—it gives games direct access to your GPU's hardware. That's why it performs so well, but it also means a single hiccup in the driver or a stale shader cache can cause the GPU to reset itself, throwing DXGI_ERROR_DEVICE_REMOVED. Restarting clears the driver state, updating the driver patches known bugs, and deleting the shader cache removes any corrupted files that were causing the GPU to hang. It's not magic; it's just resetting the parts that got tangled.
Less Common Variations and Their Fixes
1. Overclocked GPU or Memory
If you've overclocked your GPU or RAM, DX12 will crash faster than a spilled soda on a keyboard. The stability margin shrinks under load. Reset your GPU to stock clocks in MSI Afterburner or your BIOS, and set your RAM to its advertised XMP/EXPO profile—not higher. Test with a demanding game. If the crash stops, you've found the culprit.
2. Power Supply Issues
DX12 games push power draw to the limit. If your PSU is old or underpowered (e.g., 500W for a high-end card), you'll get random crashes that look like driver issues. Check if the crash happens in the first 5 minutes of a heavy scene—that's a power starvation signature. The fix is a new PSU with at least 20% headroom above your system's peak draw. Get a reputable brand like Corsair or Seasonic.
3. BIOS and Chipset Drivers
Sometimes the GPU isn't the problem—the motherboard is. An outdated chipset driver can cause PCIe communication errors that mimic DX12 crashes. Go to your motherboard manufacturer's site, download the latest chipset driver, and install it. Also check for a BIOS update—especially on Ryzen systems, where AGESA updates fix GPU stability.
4. Specific Games with Broken DX12 Modes
Some games have DX12 implementations that are just broken. For example, Red Dead Redemption 2 used to crash constantly on DX12 for many users, and Cyberpunk 2077 had similar issues at launch. If a game crashes repeatedly on DX12 but runs fine on DX11 (if it has that option), the game's DX12 code is the problem, not your PC. Workaround: switch to DX11 mode in the game's settings. It looks slightly different but runs stable.
Prevention: Keep It Stable
Once you've got it fixed, here's how to keep it from coming back:
- Update drivers monthly, but not the day they release—wait a week to see if others report issues on forums.
- Clean your PC's dust. Overheating GPUs crash more often. Use compressed air every 3–6 months, especially if you have pets.
- Cap your frame rate to your monitor's refresh rate. Running at uncapped FPS in menus can push the GPU to 100% and trigger crashes.
- Disable Windows fast startup if you see recurring issues after cold boots. Search "Choose a power plan," click "Choose what the power buttons do," then uncheck "Turn on fast startup." It's fine for most, but it can leave GPU drivers in a weird state.
That's the whole playbook. Start with the restart and driver update, and you'll likely never see this error again. If you do, drop a comment with your GPU model and game—I'll try to point you somewhere specific.