Why Games Stutter on a Fast PC Even at High FPS

A high average frame rate and a smooth game are different things. The lurch you feel when you turn a corner is usually not the graphics card running out of power — it is the game building a shader at the moment it first needs to draw something.

Which is why it happens on a machine that benchmarks beautifully, and why it happens in the same places every time on a fresh install.

What is actually happening

Before the GPU can draw anything, the exact combination of shaders and settings has to be compiled into a pipeline state object. Modern APIs want that done in advance. Engines built around older ones often cannot.

A Khronos Group post by a Valve engineer describes the problem in Source 2 exactly: the engine does not know, at the time shaders are provided, “the pairing of shaders across stages, vertex formats, framebuffer formats, depth/stencil state, viewport information, MSAA state, and several others.”

The consequence, in their words: “we delay creation of PSOs until draw time, which can lead to hitches, particularly with a cold pipeline cache.”

A cold cache is the whole story. The first time you see a weapon, an effect, a new area, the work happens then — while you are looking at it.

Why DirectX 11 games felt smoother

Worth knowing, because it explains why this seems to have got worse as hardware got faster.

The same post is candid about it. Direct3D 11 drivers “provide the illusion of compiling entirely with just the shader byte code”, but “there are massive heroics happening inside the drivers to make this so” — background compilation across threads — and even then, D3D11 “cannot guarantee that shader compilation doesn’t happen at draw time.”

Newer APIs handed that responsibility to the game. That is faster when done well, and produces exactly this when it is not. Your hardware is not the variable that changed.

The check, which takes one level

Run the same section twice and watch where it lurches.

• The hitch happens in the same spots on the first run and is gone on the second — shader compilation. The cache is now warm. Nothing is broken.
• It comes back after a driver update — the driver update invalidated the cache. Same cause, and it is expected.
• It happens in the same spots every time, warm or cold — that is asset streaming, not shaders. Usually storage, sometimes memory.
• It is random rather than positional, and matches something else on the machine waking up — background processes.
• It gets worse the longer you play and the fans get louder — thermal throttling, which is a different article.

The distinction that matters: positional-and-once is shaders, positional-and-always is streaming.

What to do now

• Let the shader pre-compilation step finish. When a game offers to compile shaders on first launch or after a driver update, that screen is not a delay before the game — it is the stutter, moved somewhere it does not matter. Do not skip it.
• Play a level through once before judging it. First-run stutter on a game you just installed is close to meaningless.
• Do not lower your resolution to fix it. Resolution is a throughput setting and this is not a throughput problem. It will change your frame rate and not the hitch.
• Do not buy a faster card for this. A faster card compiles a shader marginally faster and still compiles it at draw time.
• Keep the shader cache. Cleanup tools that clear it are undoing exactly the work that made the game smooth.

The fix is arriving from the platform

This is being solved above the level of anything you can configure, which is the right place for it.

AMD describes Advanced Shader Delivery, first shipped on the Ryzen Z Series handhelds including the Xbox ROG Ally (affiliate link to Amazon, opens in a new tab) and Ally X (affiliate link to Amazon, opens in a new tab), as addressing “longstanding issues of shader compilation times and in-game stutter by enabling gamers to download fully compiled shaders tailored for their hardware.”

Compiled elsewhere, downloaded ready, no cold cache. And at GDC 2026, per the same write-up, Microsoft said it is “uniting the ecosystem pieces between game developers, IHVs, and game stores to solve shader compilation on PC going forward”, with new tracing and compilation APIs in the Agility SDK.

So it is a real problem with a named cause and a funded fix — which is a better answer than the one people usually get, that their PC is not good enough.