# Game stuttering at first: shader compilation and cache (2026)

> Game stuttering at first, compiling shaders or hitching after a driver update? Understand the NVIDIA, AMD, Steam and Microsoft shader caches and when clearing them makes sense.

Canonical: https://risefps.com.br/en/blog/jogo-travando-no-comeco-shaders
Last updated: 2026-11-13

Rise team · 2026-11-13 · FPS guides · 5 min

A game that stutters in the first matches, or right after you update your graphics driver, is almost always compiling shaders: translating its graphics effects for your graphics card and saving the result in a cache. In the next matches it reuses what’s already done and the hitches fade. The fix is to let that cache do its work, not to delete it.

## What shader compilation is

Shaders are the small programs that tell the graphics card how to draw light, shadows, smoke and reflections. Before they run, they have to be compiled for your GPU. Microsoft explains that, without precompiled shaders, this happens on a loading screen or at the moment an effect shows up for the first time, during play, and that’s where the stutter comes from. The result is saved in the shader cache, and next time it comes from disk, with no compiling.

- A “compiling shaders” or “optimizing” screen on first launch, sometimes a long one.
- A hitch the first time an effect, a map or a skin shows up, and not the second time.
- Stutter right after a driver or game update that goes away on its own after a few matches.
- High average FPS and still short hitches, even on a good PC.

## Why the game stutters again after a driver update

A compiled shader is tied to an exact combination of game, graphics card and driver. Microsoft says the cache lasts until the driver is updated, because the update invalidates what was stored. So in your first matches on a new driver, it’s normal for the game to compile everything again. A game patch that adds a new map, effect or character also brings shaders your PC hasn’t compiled yet.

## The shader caches that exist today

- NVIDIA driver: in NVIDIA Control Panel › Manage 3D Settings you’ll find Shader Cache Size. Since driver 496.13, it sets how much disk space the driver uses to store compiled shaders.
- AMD driver: according to AMD, the cache speeds up loading and lowers CPU usage because it stores frequently used shaders instead of generating them again. In AMD Software: Adrenalin Edition, Reset Shader Cache sits in the advanced Graphics settings and deletes everything stored.
- Steam: with Shader Pre-Caching turned on in the settings, Steam can download shaders already compiled for your graphics card, when the hardware and driver allow it. Valve says this cuts loading and stutter during the first launches of OpenGL and Vulkan games. DirectX games rely on the driver cache.
- Microsoft’s Advanced Shader Delivery: shaders are compiled in the cloud and downloaded with the game. Since October 2026 it works on AMD, Intel, NVIDIA and Qualcomm graphics, on Windows 11 24H2 or later, in supported games from the Microsoft Store and the Xbox app. Microsoft says Steam and Epic are coming later.

## What to do when a game stutters at first

1. Give the cache time. Play two or three matches before drawing conclusions. If the game has a shader compilation screen, let it finish before you start playing. If the stutter shrinks with each match, the cache was being built.
2. Check that the cache is on in the driver. On NVIDIA, Shader Cache Size shouldn’t be set to Disabled. On AMD, don’t turn off the shader cache.
3. Keep free space on your Windows drive. The driver cache takes up disk space; with a nearly full SSD, there’s less room to store shaders.
4. New driver: wait a few matches before blaming the version. If the stutter stays the same after several matches, then it’s worth trying the previous version, downloaded from the manufacturer’s site.
5. On Steam, keep Shader Pre-Caching on if you play Vulkan or OpenGL titles. Valve notes it uses a little extra bandwidth, because it sends a shader usage report after each session.
6. For Microsoft Store or Xbox app games with Advanced Shader Delivery, Microsoft asks for Windows 11 24H2 or later, an up-to-date driver and the Xbox app installed before you download the game.

> **Heads up: What not to do**
>
> - Clearing the shader cache every week or after every hitch: the game compiles everything again and the stutter comes back with it.
> - Turning off the driver cache to save disk space or because a video told you to.
> - Using a cleaner that wipes the shader cache every time it runs.
> - Rolling back the driver after the first match with stutter, before the cache has been rebuilt.

## When clearing the cache makes sense

Clearing the cache is a diagnostic step, not a routine. It makes sense when the game shows corrupted graphics, crashes at the same loading point every time, or keeps stuttering the same way after many matches, even though the cache has had time to build. After clearing it, the first matches will stutter again while the cache is rebuilt, and that’s expected.

If the stutter never gets better, even after several matches, it probably isn’t shaders. Then the cause is usually temperature, memory, disk or a background program, and it’s worth following the order in the PC stuttering guide. To know whether things improved, measure the 1% low before and after, not just average FPS.

> **In Rise, this is… NVIDIA: 10 GB shader cache**
>
> In Optimizations › More FPS.
>
> Tweak · Rise Basic · Reverts in one click
>
> Turns on the NVIDIA driver shader cache and raises its limit to 10 GB in the global settings, through the driver’s official interface. With more room, the driver throws away fewer compiled shaders when you switch between large games. Requires driver 496.13 or newer. On a small or nearly full SSD, the default is the better choice.

**Read next**

- [PC stuttering in games: what to check, in order](https://risefps.com.br/en/blog/pc-travando-em-jogos)
- [How to measure 1% low and frame time](https://risefps.com.br/en/blog/como-medir-fps-1-low-e-frametime)
- [Fortnite low FPS, lag or stuttering on PC](https://risefps.com.br/en/guides/fortnite/how-to-increase-fps)
- [CS2 stuttering with high FPS](https://risefps.com.br/en/guides/cs2/stutter-high-fps)

## Sources

- [Microsoft, DirectX Developer Blog: Advanced Shader Delivery (2025)](https://devblogs.microsoft.com/directx/introducing-advanced-shader-delivery/)
- [Microsoft, DirectX Developer Blog: Advanced Shader Delivery across hardware (October 2026)](https://devblogs.microsoft.com/directx/advanced-shader-delivery-is-available-now-across-hardware)
- [NVIDIA: driver 496.13 release notes (Shader Cache Size)](https://us.download.nvidia.com/Windows/496.13/496.13-win11-win10-release-notes.pdf)
- [AMD: graphics settings in AMD Software: Adrenalin Edition (Reset Shader Cache)](https://www.amd.com/en/resources/support-articles/faqs/dh3-012.html)
- [Valve: Steam client update with Shader Pre-Caching](https://store.steampowered.com/oldnews/35534)

## Related

- [FPS guides](https://risefps.com.br/en/blog/categoria/guias-de-fps)
- [Blog](https://risefps.com.br/en/blog)