Rebuild NVIDIA Shader Cache Without Causing More Stutter

The best way to rebuild NVIDIA shader cache is to keep caching enabled, finish the game’s shader preparation, and preserve the results between sessions. If a reset is necessary, clear the relevant cache once, restore caching, and allow rebuilding before evaluating performance.

There is no guaranteed way to delete a shader cache and avoid every first-run hitch. Removing cached work can temporarily make gameplay less smooth. Epic explicitly warns Fortnite players that their first match after a cache reset may still stutter while shaders compile.

Decide Whether You Need to Clear Anything

A shader cache stores previously prepared rendering work. When a game needs a shader or rendering pipeline that is not ready, compilation can delay the frame. Epic’s engineering explanation describes how preparing pipelines earlier allows games to avoid some of those interruptions. Unreal Engine

However, a hitch alone does not establish cache corruption.

Use these situations to choose your next step:

These are troubleshooting directions, not diagnoses.

NVIDIA documents that installing a new driver clears its cache and can cause stuttering during the next game session. Deleting it again immediately gives the game more preparation work to repeat.

If the problem started with a driver change, our guide to fixing shader compilation stutter after an NVIDIA driver update covers that broader investigation.

Try Rebuilding Without Manual Deletion First

Finish the game’s preparation process

Launch the affected game and allow any shader-compilation or optimization indicator to finish. If the developer provides a documented preparation option, use it.

Do not assume that leaving every game at its main menu for ten minutes achieves the same result. Preparation depends on the game’s implementation. Epic’s documentation describes compilation during startup and loading, while also identifying pipelines that may be missed or completed too late.

For your first comparison, keep the driver and graphics settings unchanged. Pick a familiar save or route so you can repeat the same workload.

Treat this as a preparation session. Avoid making several additional “optimization” changes before you have checked whether normal rebuilding helps.

Check NVIDIA Auto Shader Compilation

NVIDIA’s documented Auto Shader Compilation feature rebuilds DirectX 12 shaders after driver updates while the computer is idle. Its announcement specifies GeForce Game Ready Driver 595.97 WHQL or newer; that is the published minimum, not a claim that 595.97 is today’s latest driver.

To check the feature:

1. Open the NVIDIA app.
2. Navigate to Graphics → Global Settings → Shader Cache.
3. Enable Auto Shader Compilation, if available.
4. For an immediate attempt, open the three-dot menu and select Compile Now.

NVIDIA states that newly installed games still need initial shader generation inside the game. ASC should therefore not be treated as a universal replacement for first-launch preparation—or as a promise that every manually deleted cache can be fully reconstructed outside gameplay.

If the control is absent, follow our NVIDIA Auto Shader Compilation missing-option guide before attempting a cache reset.

How to Reset NVIDIA Shader Cache When Necessary

NVIDIA identifies damaged shader-cache files as a possible cause of crashes, reduced performance, and visual artifacts. Those symptoms can justify investigating corruption, but do not prove it.

Its documented manual procedure is:

1. Close games and graphics applications.

2. In NVIDIA app → Graphics → Global Settings, open Shader Cache Size, select Off, and apply.

3. Restart Windows.

4. Open File Explorer and enter %USERPROFILE%\AppData\Local in its address bar.

5. Clear the contents of the following folders where present:

   NVIDIA\DXCache
   NVIDIA\GLCache
   NVIDIA Corporation\NV_Cache

6. Restore the cache setting to Driver Default, apply, and restart again.

Delete the contents of the specified cache folders, not their parent NVIDIA directories. This follows NVIDIA’s published reset workflow.

Before launching the game, confirm that caching is enabled again. Then complete its preparation process and proceed to the comparison below.

What if the folders are missing or files are locked?

A missing folder is a reason to check the instructions for your installation and affected game. Do not create empty cache directories or start deleting similarly named folders elsewhere.

For example, Epic’s current Fortnite instructions also reference a PerDriverVersion\DXCache folder beneath NVIDIA’s local application-data directory. The same instructions tell users to skip files that are currently in use.

That is a game-specific troubleshooting route. It does not mean every NVIDIA system must contain an identical directory layout.

Avoid changing folder ownership or permissions simply to force a cache purge. If the documented locations do not match your installation, stop the deletion step and check the relevant support guidance.

Is Windows DirectX Shader Cache the Same Thing?

Windows-managed DirectX caches, driver-managed caches, and application-managed caches are distinct categories. Microsoft’s shader-cache specification also describes exceptions to what Disk Cleanup can remove.

Consequently, clearing DirectX Shader Cache in Windows should not be described as a guaranteed reset of every NVIDIA and game-specific cache.

If you specifically need to clear the Windows category:

1. Search Windows for Disk Cleanup.
2. Select the Windows drive.
3. Clear unrelated selections.
4. Select DirectX Shader Cache, if listed.
5. Confirm the cleanup.

Microsoft documents selecting file categories individually in Disk Cleanup. Review those selections instead of approving every category automatically.

For troubleshooting, choose the cache layer relevant to the problem. Clearing the Windows cache, NVIDIA cache, and a game’s configuration folders together makes the outcome harder to interpret.

Choose a Cache Size That Can Retain Useful Work

Shader Cache Size controls disk storage, not GPU VRAM. Increasing it does not add graphics memory.

NVIDIA explains that older entries are removed as the cache approaches its capacity limit. A restrictive limit can therefore discard shaders that you still use. Its recommendation is to accommodate the games you play without exceeding available storage.

Start with Driver Default. Consider a larger allowance when your game library and available disk space justify it.

NVIDIA’s cache-reset support article identifies the default as 16 GB at the time of that article’s update. Treat that as a documented value that may change, rather than a permanent specification.

Avoid changing capacity during your initial before-and-after comparison. If you want to investigate cache size, make it a separate test so you can identify which change helped.

Check Whether Rebuilding Actually Improved Stuttering

A fair comparison needs more than one rough first run followed by an impression that things feel better.

The following is a suggested troubleshooting method, not a benchmark result.

1. Record a baseline

Before resetting anything, note:

• The game and driver versions.
• Resolution and graphics settings.
• Whether shader preparation completed.
• The route, save, or encounter being tested.
• Where the noticeable pauses occur.

Choose a sequence you can reproduce without substantial variation. A short single-player route is usually easier to compare than an unpredictable multiplayer match.

2. Separate preparation from evaluation

After rebuilding, run through the chosen sequence once. Label that attempt as the preparation pass.

Repeat it without changing settings. Then close the game normally, reopen it, and repeat the sequence again.

This distinction matters: a smoother second pass is encouraging, while smoother behavior after relaunch provides additional evidence that useful work is being retained. Neither result alone identifies the underlying cause.

3. Compare individual interruptions

If you use a performance overlay, examine frame delivery around the troublesome event. Intel’s PresentMon documentation distinguishes frame-time, displayed-time, and GPU-work metrics, allowing more detailed observation than a single average-FPS value.

For perspective, evenly delivered 60 FPS corresponds to approximately 16.7 milliseconds per frame. A hypothetical 100 ms interruption can be obvious even when the average frame rate remains respectable.

Record whether a hitch:

• Disappears on subsequent passes.
• Becomes shorter.
• Remains at the same location.
• Returns after restarting the game.

Do not treat the shape of a graph as a shader-compilation detector. It shows when delivery became uneven; identifying the responsible subsystem requires more evidence.

4. Keep the comparison controlled

Avoid changing the driver, graphics preset, cache size, and background software together.

If you make four changes and performance improves, you have a working configuration but little understanding of which change mattered. A single-variable comparison gives you a more useful result to preserve or report.

What If the Same Stutter Keeps Returning?

Once a controlled reset and repeated preparation produce no meaningful improvement, stop making cache deletion your default response.

Epic’s PSO documentation distinguishes pipelines that were missed from those that finished preparation too late. It also shows that some hitches have causes unrelated to shader compilation. Player-side cache maintenance cannot correct every scheduling problem inside a game.

Choose the next investigation from the symptom:

These comparisons narrow the possibilities; they do not guarantee a fix.

Our explanation of shader compilation stutter versus traversal stutter provides additional tests for separating first-use effects from repeated movement-related pauses.

FAQ

How long does NVIDIA shader-cache rebuilding take?

There is no universal completion time across games. Use the game’s preparation indicator or the NVIDIA app’s reported status where available. Finishing one preparation phase also does not prove that every pipeline required later has been covered.

Should I clear shader cache after every driver update?

No routine manual reset is necessary solely because you updated a driver. NVIDIA documents cache clearing during driver installation. First allow the game to prepare its shaders and compare subsequent sessions.

Does a larger shader cache guarantee higher FPS?

No. Capacity determines how much compiled work can remain stored. It is not a guaranteed rendering-performance upgrade. Evaluate whether the particular interruptions you are investigating improve, rather than expecting a fixed FPS increase.

Can I copy someone else’s shader cache?

Do not assume it will work. Microsoft describes cached Direct3D 12 pipeline data as specific to the hardware, driver, and machine that produced it. Use the game’s supported preparation or shader-distribution mechanism.

Do I need to uninstall the driver to clear its shader cache?

NVIDIA provides a manual reset procedure, so a full driver uninstall is unnecessary for that task. Its support article also describes a separate cache-only function in DDU; that should not be confused with removing the graphics driver.

Preserve the Result Once Performance Improves

A useful rebuild ends with caching enabled, preparation completed, and repeatable evidence that gameplay improved.

If the same scene becomes consistently smoother, preserve that configuration. If it remains unchanged after a controlled reset, take the recorded versions, settings, and reproduction steps into the next investigation. Repeating the same deletion without new evidence is unlikely to make the diagnosis clearer.