You just installed a new graphics driver, and now your games are falling apart. Maybe the game crashes to the desktop the moment you click Play, or it freezes mid-match and kicks you back to Windows without an error. Sometimes you get a hard full-system crash: the screen goes black, the audio stutters or loops, and the PC reboots on its own. Other times the symptoms are subtler — texture flickering, stuttering that wasn’t there yesterday, or DirectX error pop-ups like “D3D device lost” in games that ran perfectly fine before the update.
The good news: this is one of the most common and most fixable problems in PC gaming. A driver update touches the exact software layer your games rely on, so when something goes wrong, it goes wrong immediately and obviously. The bad news is that people often panic and start reinstalling Windows or RMA-ing hardware when a ten-minute rollback would have solved everything. Work through the fixes below in order — they’re sorted easiest-first, and most readers are back in-game within the first three steps. There’s no urgent data-loss risk here in most cases, but crashes mid-save can corrupt game files, so don’t keep relaunching a crashing game over and over.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Corrupt or incomplete driver installation | Crashes started immediately after updating; Device Manager shows a warning icon on your GPU | Easy |
| Bad driver release (buggy new version) | Crash reports mention the driver file (e.g., nvlddmkm.sys or atikmdag.sys); forum threads report the same version failing | Easy |
| Old driver settings carried over incorrectly | You used custom profiles (overclocks, forced settings) that persisted across the update | Easy |
| Overlay or monitoring software conflict | Crashes stop when you disable overlays (Discord, GeForce Experience/NVIDIA App, Steam, MSI Afterburner, Radeon Software) | Easy |
| Unstable GPU overclock or factory OC colliding with new driver voltage/clock behavior | Crashes only under load; you have an OC applied in Afterburner or the card is a factory-overclocked model | Moderate |
| Windows update paired with the driver update | Settings > Windows Update > Update history shows an OS update installed the same day | Moderate |
| Corrupted game files exposed by driver change | Only one game crashes; others run fine | Easy |
Fix 1: Restart Properly First
What causes it
Driver installers frequently defer critical steps until reboot. NVIDIA, AMD, and Intel installers all prompt for a restart, and skipping it leaves mixed old and new driver components in memory — a classic recipe for instant crashes.
How to check
Ask yourself: did you actually reboot after installing the driver? If Windows Fast Startup was involved, you may have “shut down” without a true restart. Press Win + X, select Shut down or sign out, and hold Shift while clicking Shut down for a full shutdown.
What to do
Click Start, select the Power icon, and click Restart (not Shut down — Restart bypasses Fast Startup, Shut down does not). Then launch the game again.
How to undo it
Nothing to undo — a restart is always safe.
Fix 2: Disable Overlays and Background Software
What causes it
Overlays hook directly into the game’s rendering process. When a driver update changes how the game draws frames, overlay hooks that worked fine yesterday can crash the game instantly.
How to check
Close everything non-essential: Discord (User Settings > Activity Settings > Game Overlay > toggle off Enable in-game overlay), the NVIDIA App or AMD Radeon Software (disable In-Game Overlay in each app’s settings), Steam (Settings > In Game > uncheck Enable the Steam Overlay), MSI Afterburner/RivaTuner, and any RGB or recording software.
What to do
Disable each overlay, then test the game. To keep things clean, open Task Manager (Ctrl + Shift + Esc) and end background tasks for these apps so nothing re-hooks automatically.
How to undo it
Re-enable each overlay one at a time to find the culprit; once identified, update that app — overlay apps ship compatibility patches for new drivers within days.
Fix 3: Roll Back the Driver
What causes it
Some driver releases are simply buggy for specific GPU generations. If a clean driver from an earlier version worked, using it again is a legitimate long-term fix, not a workaround.
How to check
Press Win + X and choose Device Manager. Expand Display adapters, double-click your GPU, and open the Driver tab. Note the Driver Version and Driver Date. If “Roll Back Driver” is grayed out, Windows no longer has the previous copy stored, and you’ll need the installer method below.
What to do
On the same Driver tab, click Roll Back Driver if available, pick a reason, and restart. If it’s grayed out, download the previous driver directly from the GPU vendor’s site (NVIDIA, AMD, or Intel), then use their installer and choose the clean/factory-reset installation option, which wipes old settings.
How to undo it
Simply install a newer driver again later once the issue is patched in a future release.
Fix 4: Clean Reinstall the Driver with DDU
What causes it
Upgrading drivers on top of old ones can leave leftover files, registry entries, and stale shader caches that conflict with the new version. A truly clean install eliminates this whole category of problem.
How to check
If crashes persisted through a rollback or a normal reinstall, assume leftovers are involved. There’s no single confirmation — this step is cheap enough to just do.
What to do
Download Display Driver Uninstaller (DDU) and the driver package you want ahead of time. Disconnect from the internet (so Windows Update can’t auto-install a driver mid-process). Boot into Safe Mode (hold Shift while clicking Restart, then Troubleshoot > Advanced options > Startup Settings > Restart, then press 4). Run DDU, select your GPU type and brand, and click Clean and restart. Back in Windows, run the driver installer, choosing Custom installation and checking Perform a clean installation (NVIDIA) or the factory reset option (AMD).
How to undo it
Reconnect to the internet and let the installer set your preferred options. Reapply any display settings (resolution, refresh rate, HDR) since a clean install resets them.
Fix 5: Reset Your GPU Settings and Remove Overclocks
What causes it
Overclocks and undervolts tuned on an old driver can become unstable on a new one, because driver updates change clock behavior, voltage curves, and power management. Even factory-overclocked cards can stumble when a new driver raises default clocks or shifts boost behavior.
How to check
Open MSI Afterburner (or the NVIDIA App / AMD Radeon Software performance tab) and look for any Core Clock, Memory Clock, or voltage offsets that aren’t at zero. Undervolt curves set in the Afterburner curve editor (Ctrl + F) also count.
What to do
Reset everything to stock: in Afterburner, click the reset (circular arrow) button and disable Start with Windows so it doesn’t reapply. In the NVIDIA App, remove any per-game profiles. In AMD Radeon Software under Performance > Tuning, click Reset to defaults. Then test. If crashes stop, re-add your overclock in small increments later, testing each step.
How to undo it
Reapply your saved overclock profile once you’re on a stable driver, starting with smaller offsets than before.
Fix 6: Verify Game Files
What causes it
Repeated crashes mid-write can corrupt game files, and a driver change can expose files that were already borderline. This is especially common with games that compile shaders on first launch.
How to check
If only one game crashes while others run fine, this is almost certainly your issue.
What to do
In Steam: right-click the game in your Library, choose Properties > Installed Files > Verify integrity of game files. In the Epic Games launcher: click the game’s three-dot menu > Manage > Verify. On GOG Galaxy: Manage installation > Verify / Repair. For the Xbox app, use the game’s page > three-dot menu > Manage > Files > Verify and repair.
How to undo it
Nothing to undo — verification only replaces damaged or missing files.
Fix 7: Clear Shader Caches
What causes it
Both Windows and the GPU vendors cache compiled shaders tied to a specific driver version. When the driver changes, stale caches can cause crashes, especially during scene transitions in DirectX 12 and Vulkan titles.
How to check
Crashes that happen after a few minutes of play, during loading, or when entering new areas point at shader cache problems.
What to do
In the NVIDIA Control Panel: Manage 3D settings > Global settings > Shader Cache Size > set to Disabled, click Apply, restart, then set it back to Driver default. In AMD Radeon Software: Gaming > Graphics > set Reset Shader Cache to Enabled, launch the game once, then switch it back. Also clear per-game caches — for example, delete the shadercache or pc folders inside a Steam game’s install directory if the game documents them, and clear the Windows DXCache by deleting the contents of %LOCALAPPDATA%\D3DSCache.
How to undo it
Restoring the settings as described above is the undo; caches rebuild automatically the first time you play each game.
Fix 8: Check for Conflicting Windows Updates and Pause Driver Auto-Updates
What causes it
Windows Update sometimes delivers its own graphics driver alongside or shortly after your manual install, and the two installs can stomp on each other. OS updates landing the same day can also change behavior the new driver wasn’t tested against.
How to check
Go to Settings > Windows Update > Update history and compare dates with your driver install (check the Driver tab in Device Manager). If a driver appears there that you didn’t install manually, that’s your conflict.
What to do
Pause updates for up to 5 weeks via Settings > Windows Update, then perform one clean DDU reinstall of your chosen driver while paused. To reduce future interference, use the vendor’s own app (NVIDIA App or AMD Radeon Software / AMD Software: Adrenalin Edition) for driver updates instead of relying on Windows. Advanced users can also set a group policy or registry setting to prevent Windows Update from offering drivers, but pausing is usually enough.
How to undo it
Resume updates from the same Windows Update page once the driver situation is stable.
If Nothing Works
If you’ve done a clean DDU reinstall, tested stock clocks, verified files, and cleared caches and crashes continue, it’s time to widen the net. First, check whether the crashes coincide with actual hardware stress: run a stress test and monitor temperatures with a free tool like HWiNFO64. If your GPU exceeds safe temperature ranges (roughly, sustained temps above the mid-80s °C under load) or the crash reproduces in a stress test and not just games, the driver update may be coincidental — thermal issues, failing PSU delivery under transient load, or insufficiently seated power cables can all surface right when a new driver raises power draw. Reseat GPU power connectors, confirm your PSU wattage meets the card’s requirement, and clean dust from fans and heatsinks. Second, test the drive and RAM quickly: run Windows Memory Diagnostic (mdsched.exe from the Start menu) and check the drive’s health status in the manufacturer’s tool. Third, if the GPU is older, a driver branch that drops optimization support for your architecture can genuinely degrade stability — in that case, staying on the last well-supported driver long-term is a valid answer, and you should stop chasing every new release. Finally, if crashes happen system-wide (browsers, video playback), test the card in another PC if possible or contact the manufacturer’s support, as persistent crashes across drivers and games point to failing hardware rather than software.
FAQ
Should I always update my GPU drivers right away?
No. The safest habit is to update when a new game you play recommends it, when a fix note mentions a game you play, or when a security advisory lands. Otherwise, waiting a week or two lets other users surface buggy releases first. If you update and everything breaks, roll back and wait for the next release.
Is DDU really necessary, or is the “clean installation” checkbox enough?
For most people, the vendor’s built-in clean-install option is enough. DDU earns its keep when the checkbox method didn’t fix the problem, when you’re switching between NVIDIA, AMD, or Intel cards, or when crashes have persisted across multiple driver versions — it strips leftovers that installers miss.
Why does only one game crash after the driver update?
Different games use different rendering APIs and driver features. A new driver can break DirectX 12 or Vulkan titles while leaving older DirectX 11 games untouched, or clash with one game’s anti-cheat or shader pipeline. Verify that game’s files and clear its shader cache specifically — per-game problems are almost always solvable.
Will rolling back the driver hurt anything?
No. Rolling back just puts a known-good earlier version back on your system. You’ll miss any new-game optimizations from the newer driver, and some very recent games may warn you that your driver is old, but stability and performance in everything else will be unaffected. You can update again whenever the next release arrives.
