Game Won't Launch? Fixing DirectX and GPU Driver Errors

Game crashes on launch with a DirectX or driver error? Here's what's actually happening and the fix that works.

You double-click the game, the launcher pops up, maybe even the splash screen flashes — then nothing. Or you get a dialog box: "DXGI_ERROR_DEVICE_REMOVED" or "d3d11.dll is missing." Sometimes it's a black screen and a hard crash back to desktop. This almost always happens right after a Windows Update, a GPU driver update, or a fresh game install. Battlefield, Cyberpunk 2077, and older titles like Fallout 4 are famous for it.

What's actually going wrong

DirectX is the middleman between the game and your GPU. When the game asks DirectX for something the driver can't deliver — a feature the driver doesn't expose, a shader model mismatch, or a runtime file that got clobbered — it bails out. The "d3d11.dll is missing" message usually means the DirectX runtime is incomplete. "DXGI_ERROR_DEVICE_REMOVED" means the driver reset mid-render, often from a bad overclock or an unstable power state.

Nine times out of ten, the culprit is one of three things: a half-installed driver (Windows Update loves doing this), a corrupt DirectX runtime, or a game expecting a newer feature level than your GPU or driver provides. Don't bother reinstalling Windows. That's the nuclear option and it rarely fixes anything the steps below won't.

The fix, in order

  1. Check your current DirectX version. Hit Win+R, type dxdiag, hit Enter. On the System tab, look at the DirectX Version line at the bottom. If it says DirectX 12, good. On the Display tab, check the Feature Levels. If your game needs 12_1 and you've only got 11_0, that's your answer — the GPU is too old or the driver isn't reporting correctly.
  2. Do a clean GPU driver install. Not the "express" install. Grab DDU (Display Driver Uninstaller) from Guru3D. Boot into Safe Mode, run DDU, wipe the driver, reboot. Then install the latest driver from NVIDIA, AMD, or Intel directly — never from Windows Update. Windows Update has been shipping stale, broken GPU drivers for years. For NVIDIA, that's GeForce Experience or the manual download page. AMD uses Adrenalin. Intel Arc and Iris Xe use the Intel Driver & Support Assistant.
  3. Reinstall the DirectX End-User Runtime. Microsoft's directx_Jun2010_redist.exe still fixes a shocking number of older games. Yes, it's from 2010. Yes, it still matters. Grab it from Microsoft's download center, run it, point it at a temp folder, then run DXSETUP.exe from inside that folder. It drops the missing d3d9, d3d10, d3d11, d3dcompiler, and XAudio DLLs that newer Windows installs skip.
  4. Verify the game files. On Steam: right-click the game → Properties → Installed Files → Verify integrity. On Epic: Library → three dots → Manage → Verify. On Battle.net: the gear icon → Scan and Repair. This catches corrupted shaders and half-downloaded patches.
  5. Roll back the GPU driver if this started after an update. Device Manager → Display adapters → right-click your GPU → Properties → Driver tab → Roll Back Driver. If that button is greyed out, use DDU and manually install the previous version. NVIDIA and AMD both archive old drivers.
  6. Kill any overclock. MSI Afterburner, EVGA Precision, AMD's own tuning tab — reset to stock. "DXGI_ERROR_DEVICE_REMOVED" is the textbook symptom of an unstable core or memory overclock. If you've got XMP/EXPO enabled and it's marginal, that can cause it too.

If it still won't launch

  • Run as admin. Right-click the .exe → Properties → Compatibility → Run this program as administrator. Some older games need it to write to their own install folder.
  • Check Windows Event Viewer. Windows Logs → Application. Look for a red Error around the crash time. The faulting module name tells you whether it's the GPU driver (nvlddmkm.sys, amdkmdap.sys) or DirectX itself (d3d11.dll, dxgi.dll).
  • Disable overlays. Discord, Steam, GeForce Experience, Xbox Game Bar, MSI Afterburner's RTSS. Any of these can hook into the render pipeline and cause a crash on launch. Disable them one at a time.
  • Try the game in windowed mode. Edit the config file, or launch with -windowed in the Steam launch options. Fullscreen exclusive mode hits a different code path and sometimes sidesteps a broken display mode.
  • Check your PSU and thermals. If the GPU sags under load and resets, that's a hardware problem. HWiNFO64 will show you GPU core voltage and hotspot temps. If the hotspot is hitting 105°C, repaste the card.

One more thing: if the game is from 2005–2012 and you're on Windows 11, install the DirectX 9.0c redist too. Modern Windows ships DirectX 12 but leaves out a bunch of legacy runtime components developers used to bundle. Most "the game just crashes on launch" reports on old titles trace back to this.

Related Errors in Software – Games & Drivers
The Steam servers are too busy Fix "The Steam servers are too busy" error on Windows 11 0x887A0005 Fortnite 'Out of Video Memory' Error (0x887A0005) on Windows 11 Fix Display driver stopped responding and has recovered The Real Fix for "Display Driver Stopped Responding and Has Recovered" Rust black screen on launch — fix it in 5 minutes

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.