Why Shader Compilation Causes Stutters in New Games

Why the hitch happens at all

Games ship shaders as portable intermediate code — bytecode such as DXIL — not as the machine language of any particular GPU, because the PC world runs on a zoo of architectures from three vendors and a decade of generations. When the game first asks for a particular pipeline state — a specific combination of vertex, pixel and geometry shaders, blend modes and render target formats — the graphics driver compiles that exact combination into the native code your card understands. The compilation happens on the CPU, usually on one thread, while the frame that needs it waits; the visible result is a fraction-of-a-second freeze that players call shader stutter.

Consoles dodge the problem by being one fixed platform: the developer compiles every shader for that exact GPU and ships the result on the disc. PC developers instead lean on precompilation screens — the 'compiling shaders, 4,312 of 18,207' progress bar — which absorb the worst of the work in bulk up front, and on pipeline state object (PSO) caches that save each compiled pipeline to disk so the second playthrough runs smooth. Games that ship with neither mechanism are the ones that hitch for hours.

The caches that save you — and the cleaning that breaks them

Two layers of caching absorb the pain: the game's own PSO cache and the driver's shader cache, with NVIDIA, AMD and Intel each keeping compiled shaders in folders like DXCache or GLCache under AppData. Aggressive system cleaning that wipes those folders quietly re-imports every stutter you already paid for with your patience.

• Finish the precompile screen: that progress bar is the developer doing the stuttering for you, in bulk, before the game starts
• Leave the driver's shader caches alone — NVIDIA DXCache, AMD DxCache and Intel folders under %LOCALAPPDATA% exist so second encounters load instantly; wiping them restores first-encounter hitching
• Update the GPU driver before a big new release, not during it: a new driver often brings a new compiler version, which invalidates the entire existing cache
• Expect the first hour to be the worst: every new level, weapon or weather effect triggers pipelines nobody has compiled yet; the cache fills and the hitches fade
• Do not trust game boosters and process killers here — compilation is single-threaded CPU work, and freeing RAM changes nothing about it
• If a game ships with no precompile and no PSO cache, that is a developer's decision, not your PC's fault — worth a bug report, not a Windows reinstall

What does not help

Most of the popular advice around shader stutter treats the wrong disease. Lowering settings does not help, because the same pipelines still need compiling — they only get cheaper to render afterwards. Clearing the shader cache as a 'fix' actively makes things worse on every title with a local cache, except in the one legitimate case: a corrupted cache that crashes the game on launch, which is what the game's own clear-cache option exists for. Frame generation cannot mask compile hitches either, since the interpolated frames are built from the stalled one. The honest answer is patience plus an intact cache: let the game warm up once, keep the driver's cache where it is, and on the second playthrough the problem largely stops existing.

Questions and Answers

Read next