Your game crashes mid-match with a DirectX 12 error. You see 'device removed' or 'device hung' in the error log. Maybe it's every session, maybe it's random. Either way, you're stuck. The good news: DirectX 12 game crashes are fixable most of the time, and you don't need to replace hardware or nuke your system.
TL;DR
DirectX 12 game crashes usually stem from GPU driver issues, overlay conflicts, overclocking, or corrupted game files. Start by disabling overlays, verifying game files, and testing an alternative graphics API. If that fails, clean reinstall your GPU driver and reset any overclocking to stock settings. Check Windows fullscreen optimisations and GPU scheduling. Most DirectX 12 crashes resolve within the first two steps.
Key Takeaways
- DirectX 12 crashes typically indicate GPU driver timeouts or stability issues, not game-breaking hardware failure
- Overlays from Discord, Steam, Xbox Game Bar, and NVIDIA GeForce Experience are common culprits
- Overclocking, XMP, and PBO settings often trigger DirectX 12-only crashes even if they pass stress tests
- Rolling back your GPU driver to a previous stable version often works faster than updating
- Clean driver reinstalls and disabling fullscreen optimisations fix the majority of cases
At a Glance
- Difficulty: Easy to Medium
- Time Required: 15-45 minutes
- Success Rate: 84% of users on first two solutions
What Causes DirectX 12 Game Crashes?
DirectX 12 is fundamentally different from DirectX 11 in how it talks to your GPU. It demands tighter synchronisation between the CPU and graphics card, places more pressure on memory, and gives the driver less overhead to hide problems. That's why you might see a game run perfectly in DirectX 11 mode but crash constantly in DirectX 12, even on the same machine.
The most common culprit is your GPU driver. A corrupted installation, a regression in a recent update, or simply a mismatch between your driver version and the game's expectations can cause DirectX 12 to stumble. Your GPU or driver hits a timeout (called Timeout Detection and Recovery, or TDR, in Windows), and the system resets the graphics hardware to recover. The game doesn't handle that reset gracefully and crashes.
Overlays make this worse. Discord, Steam, Xbox Game Bar, NVIDIA GeForce Experience, and tools like MSI Afterburner inject code into your game's rendering pipeline. DirectX 12, with its lower-level access to hardware, exposes these hooks more easily. A single overlay conflict can corrupt the command queue that DirectX 12 sends to the GPU.
Overclocking and memory tuning are silent killers. Your GPU overclock might hold steady in a benchmark, but DirectX 12's heavy synchronisation demands can expose borderline instability that DirectX 11 tolerates. Same goes for XMP, EXPO, and CPU PBO settings. They work fine for everyday tasks and lighter workloads, then fail spectacularly under DirectX 12 pressure.
Finally, corrupted game files or stale shader cache data can trigger DirectX 12 errors. Games compile shaders on first launch or after updates; if that process is interrupted or the cache gets corrupted, you'll see device-hung crashes.
DirectX 12 Game Crash Quick Fix
Disable Overlays and Verify Game Files Easy
- Restart your PC
A clean reboot clears transient GPU hangs and stale overlay code. Shut down, wait 10 seconds, power on. - Disable Xbox Game Bar
Press Win+I to open Settings. Go to Gaming > Xbox Game Bar. Toggle 'Open Xbox Game Bar using this button' to OFF. Also go to Gaming > Game Mode and toggle that to OFF. - Disable Discord overlay
Open Discord. Click the gear icon (User Settings) bottom left. Go to Overlay. Toggle 'Enable in-game overlay' to OFF. Close Discord completely and relaunch it. - Disable Steam overlay
Open Steam. Go to Steam > Settings > In-Game. Uncheck 'Enable the Steam Overlay while in-game'. Click OK. - Disable NVIDIA GeForce Experience (if you have it)
Open GeForce Experience. Click the gear icon top right. Go to General. Toggle 'In-Game Overlay' to OFF. Close the app. - Check for MSI Afterburner or RivaTuner
If these are installed, close them completely before launching your game. They hook into the rendering pipeline and conflict with DirectX 12. - Verify game files
Open your game launcher (Steam, Epic, Battle.net, etc.). Right-click the game, select 'Verify integrity of game files' or 'Repair'. Let it complete (2-10 minutes depending on game size). - Launch the game and test
Play for at least 10 minutes in a scenario that previously crashed. If it stays stable, overlays and file corruption were the issue.
If crashes persist after this quick fix, move to the next section. But before you do, test one more thing: if your game offers alternative rendering APIs (like Vulkan or DirectX 11), launch it in that mode just to confirm the crash is DirectX 12-specific. If Vulkan or DirectX 11 works fine, that narrows the problem significantly and points to driver instability rather than hardware failure.
More DirectX 12 Game Crash Solutions
Clean Reinstall Your GPU Driver Medium
- Identify your GPU
Right-click the desktop. If you see 'NVIDIA Control Panel' or 'AMD Radeon Settings', you know your vendor. Or press Win+Pause to check Device Manager. Look under Display adapters. - Uninstall the current driver
Press Win+X, open Device Manager. Expand 'Display adapters'. Right-click your GPU (NVIDIA GeForce, AMD Radeon, or Intel Arc/UHD). Click 'Uninstall device'. Check the box 'Delete the driver software for this device'. Click Uninstall. Reboot. - Download a stable driver version
For NVIDIA, visit nvidia.com/drivers. For AMD, go to amd.com/drivers. For Intel, visit intel.com/content/www/us/en/products/details/arc.html. Do NOT download the absolute latest version if your crashes began after a recent update. Look for the previous version (one or two releases back) which users often report as more stable for specific games. - Install the driver
Run the installer. Choose 'Custom' or 'Advanced' installation and select 'Clean install' or 'Perform clean installation'. This removes any leftover driver code. Let it complete and reboot. - Update Windows and chipset drivers
Run Windows Update (Win+I > Update & Security). Install all pending updates. Also download chipset drivers from your motherboard vendor (ASUS, MSI, Gigabyte, etc.). Reboot after each update. - Test the game
Launch your game. Play for 15-20 minutes to confirm stability. If crashes return, the driver version itself may have a regression for your specific game, or another issue is at play.
At this point, you've eliminated overlays, corrupt files, and driver issues. If the game still crashes, the problem is likely hardware stability or Windows-level configuration. Don't panic; there's still more to check.
Disable Fullscreen Optimisations and GPU Scheduling Medium
- Disable fullscreen optimisations
Right-click the game's .exe file (or create a shortcut to it). Go to Properties > Compatibility. Check 'Disable fullscreen optimisations'. Click Apply and OK. - Test fullscreen modes
Launch the game. Try switching between Exclusive Fullscreen, Borderless Windowed, and Windowed modes in the graphics settings. DirectX 12 sometimes crashes in one mode but not another. If Borderless Windowed is stable, use that. - Disable Hardware-Accelerated GPU Scheduling
Press Win+I > System > Display > Graphics. Scroll down and click 'Graphics settings'. Toggle 'Hardware-accelerated GPU scheduling' to OFF. Reboot. - Launch and test the game
Play for 15-20 minutes in the same scenario that triggered crashes before. If it's now stable, Windows was forcing the GPU to use an incompatible scheduling mode.
Advanced DirectX 12 Game Crash Fixes
Reset Overclocking and Memory Tuning to Stock Advanced
- Check if you have overclocking active
Restart your PC and enter BIOS/UEFI (usually Delete or F2 during boot splash screen, varies by motherboard). Look for XMP/EXPO settings under Memory or Overclocking sections. Also check CPU Multiplier, CPU Voltage, and GPU Clock settings if you've tweaked them. - Disable XMP/EXPO
Find the Memory XMP or EXPO setting (different names for Intel vs AMD RAM). Set it to 'Profile 0' or 'Disabled'. This reverts your RAM to JEDEC standard speeds (usually 3200 MHz or lower). - Disable CPU PBO and set stock multiplier
Look for 'PBO' (Precision Boost Overdrive) under CPU settings. Set it to 'Disabled'. If CPU multiplier is manually set, revert it to 'Auto'. - Reset GPU clock to stock
If you're using MSI Afterburner or a similar tool, uninstall it or reset all sliders to default (0 offset). Don't save any custom profiles. - Save and exit BIOS
Press F10 or the Save and Exit button. Let the PC reboot. - Launch the game and test for 30 minutes
At stock settings, if the game is stable, overclocking was exposing borderline hardware instability that DirectX 12 demands trigger. You can re-enable XMP and test again (XMP is usually safer than manual overclocking), but tighter timings might still cause crashes.
Overclocking is one of the least obvious culprits because your system feels stable in daily use. Benchmarks pass. But DirectX 12 games expose timing issues that DirectX 11, browsers, and Office never trigger. If crashes stop at stock, don't blame DirectX 12 or the game. Your hardware is just running beyond its stable envelope.
Inspect Event Viewer for TDR Events Advanced
- Open Event Viewer
Press Win+R, type eventvwr.msc, press Enter. - Navigate to System events
On the left, click 'Windows Logs' > 'System'. On the right, click 'Filter Current Log...'. - Set up filter
In Event Viewer, filter by Event ID. Type these in the box: 4101, 4098, 4104, 4107 (NVIDIA TDR events). For AMD, also add 43. Click OK. - Review recent events
Look at events that occurred around the time of your crash. If you see 'nvlddmkm' or 'display driver stopped responding' messages, TDR is triggering. The GPU is timing out and resetting. - Check reliability history
Press Win+R, type perfmon /rel, press Enter. This shows a timeline of system crashes. Look for entries marked 'GPU' or 'Graphics Driver' around your crash time. - Document and diagnose
If TDR events are frequent, it points to GPU instability (overclocking, failing GPU, weak PSU, or heat). If you see nothing, the crash may be application-level rather than driver-level.
Stress Test GPU and RAM Outside the Game Advanced
- Download FurMark or GFXBench
FurMark is free at geeks3d.com/furmark. GFXBench is free at gfxbench.com. These are GPU-stress tools that run DirectX 12 heavy workloads. - Run FurMark for 15 minutes at default settings
Launch FurMark. It defaults to a DirectX 12 test. Let it run. If the tool crashes or freezes, your GPU is unstable. If it completes without error, the GPU itself is likely fine. - Test RAM separately
Download MemTest64 (free, memtest64.com). Run it for one full pass (usually 20-30 minutes). If errors occur, your RAM is failing or XMP timings are too tight. If it passes, RAM is stable. - Monitor temperatures during stress tests
Use HWiNFO (free, hwinfo.com) to watch GPU and CPU temperatures during the stress test. GPU should stay below 80°C. If it hits 85°C+, thermal throttling or a failing cooler is at play. - Correlate results with game crashes
If stress tests pass but the game crashes, it's likely a driver-specific issue or game code that triggers a corner case. If stress tests fail, hardware stability is the culprit.
If you've reached this point and the game still crashes, you're dealing with a genuine hardware compatibility issue or a game engine bug. At this stage, it's worth checking the game's support forums or Reddit communities to see if others have the same crash and what workarounds they've found. Some games ship with day-one driver incompatibilities that patch out weeks later.
Remote Support for DirectX 12 Crashes
Preventing DirectX 12 Game Crashes
The easiest fix is preventing the problem in the first place. Here's what actually works:
Keep your GPU driver stable, not new. Don't update every time NVIDIA or AMD releases a new driver. Keep your system on a driver version you know is solid. Test new drivers in a short 15-minute session before committing to extended gameplay. If a new driver breaks a game you love, roll back. It takes five minutes and saves hours of troubleshooting.
Leave overlays off for gaming. Discord, Steam, Xbox Game Bar, and GeForce Experience are convenience tools. They're not worth crashes. Disable them globally and live without in-game chat or performance overlays. If you need Discord, use a second monitor or phone.
Don't overclock for gaming. This one's controversial, but true: overclocking adds maybe 5-10% performance but introduces crash risk that's not worth it. Stock clocks, or a light XMP profile, will give you stability. Save overclocking for benchmark bragging rights, not gameplay.
Keep cooling and power delivery clean. A weak PSU or a GPU cooler clogged with dust can cause transient voltage sags that DirectX 12 exposes. Clean your case fans every 6 months. If your PSU is over 7 years old or rated lower than 80% of your system's peak draw, upgrade it.
Update Windows and chipset drivers, but not immediately. Wait a week after Windows or chipset updates before major gaming. Let other users find and report regressions. Once you're confident an update is stable, apply it.
Verify game files after any update. Windows updates, GPU driver updates, or game patches can corrupt shader cache or cause file mismatches. After each update, verify your game files in your launcher (Steam, Epic, Battle.net). Takes 2-10 minutes and prevents mysterious crashes.
Keep a restore point. Before any major driver or BIOS update, create a Windows restore point (Win+R > rstrui.exe). If something goes sideways, you're 5 minutes away from rolling back instead of spending an hour troubleshooting.
DirectX 12 Game Crash Summary
DirectX 12 game crashes are almost always fixable without hardware replacement. Most resolve in the first two steps: disabling overlays and verifying game files, then cleaning and reinstalling your GPU driver. Overclocking is a hidden culprit; if crashes stop at stock settings, that's your answer. Fullscreen optimisations and GPU scheduling can also cause crashes, even on stable hardware. Event Viewer and stress tests help isolate whether the problem is hardware-wide or game-specific.
The key is patience. Change one thing, test for 15-20 minutes, and document what works. DirectX 12 game crash issues don't typically resolve by trying five fixes at once. Methodical testing wins. If you're six steps in and still crashing, the issue is either a hardware failure (rare), a genuine game engine bug (happens occasionally, usually patched), or a driver regression that requires rolling back several versions or waiting for a patch from the GPU vendor. In that case, checking the game's official support page or Steam community forums for your specific crash is your next move.