Fix AMD Shader Cache Stutter in DirectX 12 Games

A DirectX 12 game can show a healthy frame rate and still pause when a new effect appears. On an AMD Radeon PC, shader preparation is one possible explanation—but a stutter alone does not prove the shader cache is broken.

Start by letting the game finish any shader preparation, then repeat the same gameplay sequence without clearing anything. If the problem persists and evidence points to a cache issue, try one controlled reset and allow rebuilding before judging the result. Epic’s Fortnite support guidance specifically warns that the first match after clearing its cache can still stutter while shaders compile.

What the Shader Cache Actually Does

DirectX 12 games use pipeline state objects, usually shortened to PSOs, to describe combinations of shaders and rendering state. Preparing an unfamiliar pipeline can take enough time to interrupt frame delivery.

Microsoft’s pipeline-cache example demonstrates how saving compiled PSOs to disk can reduce compilation work on later runs. It also describes using a more general shader while a specialized pipeline finishes compiling—a reminder that the game’s implementation matters.

AMD’s own developer guidance recommends avoiding last-minute PSO compilation and reusing pipelines across sessions. That explains why preserving a working cache is valuable: deleting it removes preparation the system could otherwise reuse.

There also isn’t necessarily one cache controlling everything. Microsoft distinguishes Direct3D-managed, driver-managed, and application-managed caches. Consequently, clearing a Windows cache should not be treated as a guaranteed reset of every game’s pipeline data.

Check the Pattern Before Deleting Anything

Use the following observations to choose your next test. These are troubleshooting clues, not definitive diagnoses.

For a more detailed explanation of these patterns, see our guide to shader compilation stutter versus traversal stutter.

Choose a short, repeatable route or action. Keep the resolution, graphics preset, save location, and rendering API unchanged. Run it again, then restart the game normally and repeat.

A smoother second attempt makes reusable preparation worth investigating. However, previously loaded assets can also help subsequent runs. Treat improvement as evidence to narrow the problem, rather than proof of shader compilation.

Write down exactly what happens. “The first explosion pauses, but the next five do not” is much more useful than “DX12 feels laggy.”

1. Finish the Game’s Shader Preparation

If the game displays a shader-compilation or preparation screen, let it complete before testing. Follow the publisher’s instructions if it provides a dedicated preparation option.

Keep your graphics settings stable during the comparison. Otherwise, you are testing a different workload and may trigger different preparation.

A completed progress bar does not establish that every pipeline needed later is ready. Epic’s Unreal Engine documentation distinguishes pipelines that were never prepared from those queued for preparation but completed too late. Both can contribute to runtime hitches.

That has two practical consequences:

• Waiting in a menu helps only if the game actually performs preparation there.
• There is no reliable universal instruction to “wait ten minutes” or “play three matches.”

Use the game’s own completion indicator and repeatable gameplay observations instead of a fixed timer.

2. Reset AMD’s Shader Cache When There Is a Reason

Consider a reset when the publisher recommends it for your symptom, or persistent problems remain after preparation and controlled retesting.

To use AMD’s built-in option:

1. Close the affected game.
2. Open AMD Software: Adrenalin Edition.
3. Locate Global Graphics.
4. Expand Advanced, if that section is present.
5. Find Reset Shader Cache and use its reset control.
6. Reopen the game, complete any preparation, and repeat your test.

AMD documents this control as deleting stored shader-cache files. Its illustrated interface is based on a particular software version and hardware configuration, so the layout and available options can differ on your PC.

Evaluate the rebuilt result, not just the first run after deletion. Keep a brief record of the first attempt, the repeated attempt, and the result after restarting the game.

If the option is absent, avoid guessing at registry values or deleting similarly named folders. Use the Windows or publisher-supported route where applicable.

3. Clear Windows’ DirectX Shader Cache as a Separate Test

Windows provides a built-in cleanup route for its DirectX shader cache. Microsoft documents that the DirectX cache is integrated with disk cleanup.

Using Disk Cleanup:

1. Close the game and its launcher.
2. Search Windows for Disk Cleanup and open it.
3. Select the Windows drive when prompted, usually C:.
4. Find and select DirectX Shader Cache, if listed.
5. Deselect unrelated categories.
6. Select OK, then confirm deletion.

Microsoft’s cleanup instructions explicitly recommend reviewing selected categories before deleting files. You do not need to include Downloads, the Recycle Bin, or previous Windows installations for this test.

Launch the game again and repeat the same preparation and gameplay sequence.

Do this separately from other changes. If you clear multiple caches, reinstall the driver, and change graphics settings together, you lose the ability to identify which action helped.

If the DirectX cache category is absent, move to the game’s documented troubleshooting instructions rather than improvising a folder-deletion routine.

4. Follow Game-Specific Cache Instructions Where Available

A publisher may document a narrower fix for a particular game.

For example, Epic identifies repeated DirectX shader recompilation as a possible cause of severe Fortnite DX12 stuttering. Its AMD instructions reference the contents of:

%LOCALAPPDATA%\AMD\DxCache

The procedure closes Fortnite and its launcher first, deletes cache contents, and skips files that are in use. Epic also warns that initial gameplay may remain uneven while new shaders compile.

Treat that as Fortnite-specific support guidance, rather than a universal map of every Radeon driver’s cache layout.

For another title, consult its own support page before manually removing anything. Avoid deleting an entire game folder under AppData: cache data may sit alongside settings or saved progress.

If the documented folder does not exist, stop that particular procedure. Its absence is not a reason to delete a different directory with a similar name.

5. Investigate Driver Changes Without Reinstalling Repeatedly

A driver update can change whether existing compiled pipeline data remains usable. Microsoft documents that cached PSO data is specific to the hardware, driver, and machine, including cases where driver-version mismatches invalidate reuse. Renewed preparation after an update therefore does not automatically indicate a faulty installation.

Record the installed driver version and check its release notes for the affected game.

AMD’s troubleshooting guidance recommends checking documented driver issues, applying a relevant workaround, or returning to the last working driver when an unresolved regression is identified. It also lists clean installation as a troubleshooting option for corrupted or problematic driver installations.

Use that sequence deliberately:

• If repeated gameplay becomes smooth, preserve the working setup.
• If the issue persists, compare it with the documented problems for that driver.
• If testing another supported driver, keep your game settings and test route unchanged.

Repeatedly switching drivers and clearing caches makes comparisons harder because each change may introduce fresh preparation work.

6. Check Why the Problem Returns

If gameplay improves but the same preparation problem returns every time you launch, investigate what happens between sessions.

Check whether:

• A cleanup utility is explicitly configured to remove graphics caches.
• A launch script deletes cache files.
• The game or driver changed between tests.
• The publisher documents repeated preparation as a known issue.

Do not assume every “preparing shaders” message means the entire cache has been discarded. Without game-specific evidence, the message alone does not tell you how much work is being repeated.

Also check free space on the Windows and game drives. Microsoft notes that low storage space can affect PC performance. However, there is no universal amount of free space that guarantees a particular game’s shader-cache problems will disappear.

Avoid downloading somebody else’s compiled cache as a shortcut. Hardware- and driver-specific pipeline data is not automatically interchangeable between PCs.

7. Measure the Hitch and Know When to Change Direction

Average FPS can obscure isolated pauses.

At evenly delivered 60 FPS, each frame takes approximately 16.7 milliseconds. A hypothetical 100-millisecond frame interrupts that rhythm even if nearby frames are fast. These figures illustrate frame timing; they are not benchmark results.

AMD Software can display and log performance information, including frame-related metrics, GPU utilization, temperatures, and memory use on supported configurations. Use these readings as context rather than a shader-compilation detector.

For your comparison, record:

• The action or location that triggers the pause.
• Whether it happens on repeated attempts.
• Whether it returns after restarting.
• Whether the duration changes after one troubleshooting step.

If a reset and completed rebuild make no repeatable difference, stop clearing caches.

For persistent problems, test one relevant variable at a time: restore a custom overclock or undervolt to defaults, close unnecessary monitoring utilities, or investigate abnormal temperatures. AMD includes configuration instability, software conflicts, and cooling problems in its broader troubleshooting guidance.

You can also compare a lower graphics workload while keeping the route fixed. If overall FPS improves but the same pause remains, that adjustment has not resolved the specific event you are investigating.

Some remaining hitches require developer attention. Epic’s documentation provides tools to identify missed or late pipeline preparation, showing why consumer-side cache clearing cannot substitute for fixing the game’s scheduling or coverage.

FAQ

Should I clear AMD’s shader cache after every driver update?

No routine reset is necessary simply because the driver changed. Test the updated game first and follow any relevant publisher guidance. Driver changes can already require fresh pipeline preparation; an additional deletion is not automatically beneficial.

Why did stuttering get worse after clearing the cache?

The game may be rebuilding data it previously reused. Epic explicitly notes that Fortnite’s first match after a cache reset can still stutter during compilation. Judge repeated gameplay before deciding the reset failed.

Will a shader-cache reset permanently increase FPS?

Do not expect a guaranteed FPS increase. Caching primarily helps reuse preparation work. Microsoft’s example focuses on reducing repeated compilation and associated rendering interruptions, rather than promising higher performance in every scene.

Can the game still stutter after shader preparation reaches 100%?

Yes. Some required pipelines may be missing from preparation or finish too late. Other pauses may have unrelated causes. A completed preparation screen alone cannot distinguish between those possibilities.

Does a missing AMD reset option mean caching is disabled?

No. AMD states that available controls vary with the system configuration. A missing interface option alone does not establish that the game has no working cache. Check the documentation for your installation and the affected title.

Choose the Next Step From the Result

If repeated gameplay becomes smooth, keep that configuration and preserve its cache. If preparation appears to restart unexpectedly, investigate what changes between sessions. If the same hitch survives a controlled reset and rebuild, move to other causes.

For an unresolved issue, give support the game version, driver version, graphics settings, exact reproduction steps, and your repeated-run observations. That evidence provides a useful starting point for identifying the remaining problem.