A GPU driver update that tanks your frame rate is almost never a hardware failure. When you see a sudden 30-60% FPS drop immediately after installing a new NVIDIA or AMD driver, the problem is usually one of four things: the shader cache was invalidated and needs to rebuild, the installer silently changed a Windows or NVIDIA/AMD power profile, a game-specific driver profile was reset or overwritten, or the new driver introduced a rendering pipeline change (such as switching a default API) that the game’s engine does not handle gracefully. In Unreal Engine 5 titles, the most visible symptom is frame time spikes that resolve over 5-15 minutes as the engine recompiles PSO caches. In Unity or custom-engine games, the drop tends to be static and consistent from the first frame, pointing more toward a power-state or overlay conflict than a cache issue.
- Likely Causes
- Fix 1: Rebuild the Shader Cache
- Fix 2: Restore the Windows Power Plan
- Fix 3: Toggle Hardware-Accelerated GPU Scheduling
- Fix 4: Restore or Recreate the Game-Specific Driver Profile
- Fix 5: Disable Conflicting Overlays
- Fix 6: Roll Back the Driver
- Fix 7: Clean Install with Display Driver Uninstaller
- Fix 8: Verify PCIe Link Speed
- Fix 9: Re-register the Windows Display Subsystem
- If Nothing Works
- FAQ
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Shader cache invalidated (NVIDIA DXCache, AMD DxCache, Windows D3DSCache all wiped by installer) | FPS starts very low in a new match or area and recovers over 5-20 minutes; check if %LOCALAPPDATA%\NVIDIA\DXCache folder is nearly empty after update | Very easy |
| Windows power plan reset to Balanced by driver installer | Run powercfg /query and look for “PCI Express > Link State Power Management” set to “Moderate power savings” or “Maximum power savings” | Easy |
| Hardware-Accelerated GPU Scheduling (HAGS) toggled by installer | Settings > System > Display > Graphics > Change default graphics settings; check if the toggle state changed after update | Easy |
| NVIDIA/AMD control panel profile reset or missing for your game | Open NVIDIA Control Panel > Manage 3D Settings > Program Settings; check if your game executable is absent or flagged “Use global settings” when it previously had a custom profile | Easy |
| In-game overlay (GeForce Experience, AMD Adrenalin, Discord) hooking conflict | FPS recovers when you disable the overlay; check Windows Event Viewer Application log for “NVStreamSrv” or “RtAudiosrv” errors | Moderate |
| Driver bug specific to new version (known regression) | Rollback fixes it; check NVIDIA release notes under “Fixed” or “Known Issues” | Moderate |
| Corrupted driver installation (partial write, interrupted update) | DDU clean uninstall + reinstall fixes it; Windows Event Viewer shows “nvlddmkm” or “amdkmdag” errors | Advanced |
| PCIe link degraded (GPU falling to Gen1 or x4) | Run GPU-Z, check “Bus Interface” field under load; should read “x16 @ 16.0 GT/s” not “x1 @ 2.5 GT/s” | Advanced |
Fix 1: Rebuild the Shader Cache
How to check
Open File Explorer and navigate to %LOCALAPPDATA%\NVIDIA\DXCache (for NVIDIA) or %LOCALAPPDATA%\AMD\DxCache (for AMD). If the folder is empty or contains fewer than 20 files right after a driver update, the cache was wiped during installation. Launch the game and play for 15 minutes in varied environments. If FPS climbs steadily over that window, cache rebuild is confirmed.
What to do
Do nothing destructive. Simply play the game across different maps or zones for one session. The cache rebuilds automatically. If you want to speed it up, open NVIDIA Control Panel > Manage 3D Settings > Texture filtering – Quality, set to High Quality, and ensure Shader Cache Size is set to “Unlimited” (or at least 10 GB) under Global Settings. For Unreal Engine 5 games specifically, the engine’s own PSO cache lives at %LOCALAPPDATA%\[GameName]\Saved\ShaderPipelineCache\. Delete that folder and let the game regenerate it, which is often faster than waiting for incremental recompilation.
How to undo it
Not applicable. The cache rebuilds itself and has no downside. If you set Shader Cache Size to Unlimited, revert it to 10 GB if you are concerned about disk usage on a small SSD.
Fix 2: Restore the Windows Power Plan
How to check
Open Command Prompt as Administrator and run powercfg /query. Search the output for “Link State Power Management” under “PCI Express.” If it reads anything other than “Off,” the driver installer likely reset your power plan. Also check for the “Ultimate Performance” or “High Performance” plan with powercfg /list.
What to do
Open Control Panel > Hardware and Sound > Power Options. Select “High Performance.” Click “Change plan settings” > “Change advanced power settings.” Expand PCI Express > Link State Power Management and set both “On battery” and “Plugged in” to “Off.” Expand Processor power management and ensure “Minimum processor state” is at least 5% (some games cap below that). If “High Performance” is missing from the list, run powercfg -duplicatescheme e9a4ab83-d546-4c37-8f63-b316677230f9 to restore it.
How to undo it
Switch back to “Balanced” if you prefer lower idle power draw. The change is purely a power plan selection.
Fix 3: Toggle Hardware-Accelerated GPU Scheduling
How to check
Open Settings > System > Display > Graphics > Change default graphics settings. Note the state of “Hardware-accelerated GPU scheduling.” After a driver update, NVIDIA sometimes enables HAGS silently (especially with Game Ready drivers post-531.xx branch), and certain DirectX 11 titles do not handle it well, causing a 10-20% FPS penalty.
What to do
If HAGS is On and you are experiencing drops, turn it Off. If it is already Off and you want to test, turn it On. Reboot after changing this setting — it does not take effect live.
How to undo it
Flip the toggle back and reboot. No files are modified.
Fix 4: Restore or Recreate the Game-Specific Driver Profile
How to check
Open NVIDIA Control Panel > Manage 3D Settings > Program Settings tab. Look for your game’s .exe in the dropdown. If it is missing, the global profile is being applied, which may have changed with the update. Check %APPDATA%\NVIDIA\NVProfile.xml — after a driver update, this file sometimes gets replaced with a blank template that drops per-game overrides.
What to do
Manually add your game executable via the Program Settings dropdown. Recreate any per-game settings you had before (power management mode set to “Prefer maximum performance,” thread optimization, etc.). Alternatively, delete NVProfile.xml and restart the NVIDIA display driver service with net stop NVDisplay.ContainerLocalSystem followed by net start NVDisplay.ContainerLocalSystem, then reconfigure.
How to undo it
Set the program back to “Use global settings” or delete the profile entry from the Program Settings dropdown.
Fix 5: Disable Conflicting Overlays
How to check
Open GeForce Experience (or NVIDIA App in 2026 builds) > Settings > In-Game Overlay and toggle it Off. Do the same in Discord (Settings > Game Overlay > toggle off). Launch the game and check if FPS stabilizes. You can also look at %PROGRAMDATA%\NVIDIA Corporation\NvStreamSrv\ logs for crash entries coinciding with your FPS drops.
What to do
If disabling one overlay restores performance, leave it off for that game or add the game to the overlay’s ignore list. For AMD Adrenalin, go to the Gaming tab > select your game > disable the overlay under the game-specific profile rather than system-wide.
How to undo it
Re-enable the overlay globally or per-game. No files are permanently altered.
Fix 6: Roll Back the Driver
How to check
If the fixes above did not help, check whether the previous driver version resolved the issue. Open Device Manager > Display adapters > right-click your GPU > Properties > Driver tab. Note the “Driver Version” and click “Roll Back Driver” if the button is active.
What to do
Use the Roll Back Driver button in Device Manager, or manually download the prior known-good driver from the NVIDIA/AMD site and install it with the “Perform a clean installation” checkbox ticked. In GeForce Experience or AMD Adrenalin, you can also select “Previous drivers” from the dropdown if you are not rolling back more than two versions.
How to undo it
Reinstall the newer driver once you have confirmed the bug is fixed in a subsequent release. The rollback itself does not remove any game files or user settings.
Fix 7: Clean Install with Display Driver Uninstaller
How to check
Check Windows Event Viewer > Windows Logs > System for repeated “nvlddmkm” Event ID 153 or “amdkmdag” Event ID 160 errors. Frequent entries with “The NVIDIA display driver reset” indicate a corrupted driver stack that a standard reinstall may not fully clear because leftover registry keys and INF files persist.
What to do
Download Display Driver Uninstaller (DDU). Disconnect from the internet or set the Windows update driver installation policy to manual (gpedit.msc > Computer Configuration > Administrative Templates > Windows Components > Windows Update > “Do not include drivers with Windows Updates” set to Enabled). Boot into Safe Mode, run DDU, select “Clean and restart.” Boot back to normal Windows and install the driver fresh.
How to undo it
This is the undo of a corrupted install. If the DDU clean install causes a different problem, you can run DDU again and install a different version, or use System Restore to a point before the DDU run.
Fix 8: Verify PCIe Link Speed
How to check
Download GPU-Z. Launch a game and open the Sensors tab while under load. Look at the “Bus Interface” line. If it reads “x16 @ 16.0 GT/s” you are fine. If it drops to “x4” or “x1” under load, the PCIe link is degraded, possibly caused by a driver update changing power management behavior on the chipset.
What to do
Reboot into BIOS. Navigate to the PCIe configuration section (often under “Advanced” > “PCI Subsystem Settings”). Ensure the slot is set to “Auto” or explicitly to “Gen 4” / “Gen 5” rather than “Gen 1” or “Auto with ASPM.” Disable ASPM (Active State Power Management) for the PCIe slot if your BIOS exposes it separately from the Windows power plan. Also physically reseat the GPU and the 12VHPWR/PCIe power connectors.
How to undo it
Re-enter BIOS and set the PCIe slot back to “Auto.” No OS-level changes were made.
Fix 9: Re-register the Windows Display Subsystem
How to check
If you see DXGI_ERROR_DEVICE_REMOVED errors in the game’s log file (common in Unreal Engine titles at [GameDir]\Engine\Programs\UnrealBuildTool\ or in the game’s own \Logs\ folder with entries like “The graphics device has been removed”), the DXGI subsystem may be in a bad state after a driver update that changed how Windows manages the display adapter handle.
What to do
Run these commands in an elevated Command Prompt: regsvr32 /i /s dxgi.dll, then del %LOCALAPPDATA%\D3DSCache, then reboot. This forces Windows to rebuild the display subsystem cache from scratch with the newly installed driver bindings. The D3DSCache folder is Windows’ own internal cache that sits alongside the vendor caches and can conflict when a driver update changes the shader compilation backend.
How to undo it
No further action needed. The D3DSCache rebuilds on next game launch. The regsvr32 command re-registers an existing system DLL and does not modify version or content.
If Nothing Works
If all nine fixes fail and the FPS drop persists only after the driver update, you are almost certainly hitting a confirmed driver regression. In this case, stay on the last known-good driver version (Fix 6) and monitor the release notes for the next driver iteration. Open a support case with NVIDIA or AMD referencing your GPU model, OS build (winver), and the specific game executable. Include a GPU-Z screenshot, a DxDiag report (dxdiag /out dxdiag.txt in the command prompt), and any Event Viewer entries with “nvlddmkm” or “amdkmdag” in the source field. Vendor support teams escalate cases with confirmed reproductions faster than generic complaints.
FAQ
Why did my driver update install change my power plan?
Both NVIDIA and AMD driver installers call powercfg during installation to ensure the GPU can request maximum performance states from the CPU. This side effect is not always visible in the installer UI. The change persists silently and affects all applications, not just games.
How long does shader cache rebuild take?
Typically 5 to 20 minutes of actual gameplay per unique map or zone. In Unreal Engine 5 games with large open worlds, the first session after a cache wipe can take 30-45 minutes before FPS stabilizes, because the engine compiles PSO entries per material and per draw call combination.
Does deleting the NVIDIA DXCache folder fix anything directly?
It can, but only if the cache is corrupted rather than empty. If your FPS drop started after a driver update and the cache was already large before the update, the installer likely replaced it with a version that conflicts with the old compiled binaries. Deleting %LOCALAPPDATA%\NVIDIA\DXCache forces a clean rebuild. Do this while no games or apps are running, and while the NVIDIA Display Container LS service is stopped.
Will Windows Update automatically reinstall a newer driver over my rollback?
Yes, if the newer driver is pushed through Optional Updates or if you have the “Give me updates for Microsoft products” checkbox enabled in Windows Update settings. To prevent this, set “Do not include drivers with Windows Updates” via Group Policy or registry key HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WUAUOptin\ExcludeWUDriversInQualityUpdate to 1.
