Shader Compilation Stutter: Why New Games Hitch and How to Fix It
# Shader Compilation Stutter: Why New Games Hitch and How to Fix It
You are exploring a new area. The game runs at a smooth 60 frames per second. Then the screen freezes for half a second. It happens again when a new enemy appears, then again at the next corner. After an hour of play, the hitches fade. The next day, they are gone completely.
That is shader compilation stutter. The game is building small programs called shaders for your exact graphics card and driver, and the game cannot draw the next frame until each one is finished. It is one of the most common causes of hitching in modern PC games, and it has a specific signature. Learn the signature first, then apply the fixes that match it.
This guide explains what is happening in plain language, how to tell shader stutter apart from other kinds of stuttering, and the fixes that actually work. If your game hitches constantly instead of in isolated spikes, or if the problem is low frame rate rather than hitches, start with our broader guide: How to Fix Game Stuttering on PC.
## Topics
– What shader compilation stutter is
– How to tell it is shader stutter
– Why first runs and new areas hitch
– Let the game pre-compile shaders
– Enable Steam shader pre-caching
– Set your driver shader cache size
– Reset the shader cache when it breaks
– Try the DX11 renderer if the game offers one
– NVIDIA Advanced Shader Delivery: the new cloud fix
– When nothing helps
– Frequently asked questions
– Sources
What shader compilation stutter is
Games draw everything on screen with shaders: small programs that handle lighting, materials, shadows, particles, and visual effects. Shaders ship with the game in a generic form. Your PC must compile them into machine code for your exact graphics card and driver version before the game can use them.
On DirectX 12 and Vulkan, the driver builds a pipeline state object, or PSO, for each draw. A PSO bundles the shader with the render state the GPU needs for that specific draw call. The catch is timing. In DX12, PSOs are compiled just in time, the first moment the game needs them. When you walk into a new area and the game encounters an effect it has never drawn before, everything pauses while the driver builds that PSO.
Compilation is a CPU job. While your CPU compiles, your GPU sits idle and the frame waits. The result is one sharp hitch, usually a fraction of a second to a full second, followed by smooth play again. It is not a frame rate problem. It is a frame time spike.
Once a shader is compiled, the result is saved to a shader cache on your disk. The next time the game needs that shader, it loads the cached version instantly. That is why the hitches fade as you play and are gone in later sessions. The cache did its job.
DirectX 11 worked differently. DX11 games pre-compiled their shaders during loading screens, which meant longer waits before playing but smoother gameplay once you were in. DX12 trades that: shorter initial loads, but hitches during play when new shaders appear. Consoles avoid the problem almost entirely because every unit has identical hardware, so developers can precompile everything before the game ships. On PC, the huge variety of GPU and driver combinations makes that impossible, so some compilation has to happen on your machine.
How to tell it is shader stutter
Shader stutter has a signature. Check it before changing any settings, because the fixes in this guide only help if the signature matches.
– Hitches strike when something new appears: a new area, a new enemy, a new weapon, a new visual effect.
– The same spot does not hitch again after you restart the game. The cache took care of it.
– It is worst in the first session after installing the game or updating your graphics driver.
– Your base frame rate is fine between hitches. This is isolated spikes, not constant low performance.
Try this test. Note exactly where a hitch happens, restart the game, and go back to the same spot. If the hitch is gone, it was compilation. If hitches return after you clear the driver shader cache, that also confirms the diagnosis: the game had to compile everything from scratch again.
Now rule out the lookalikes.
– Traversal stutter hitches at the same invisible world boundaries every time, even on repeat visits. It comes from data being loaded into and out of memory as you move, not from shader compilation.
– VRAM stutter is constant hitching, texture pop-in, or severe slowdowns when your graphics settings exceed your card’s video memory. It does not fade after the first session.
– A CPU bottleneck shows up as generally low and uneven frame rate, not as sharp isolated hitches on an otherwise smooth game.
If none of the signatures above match, your problem is a different kind of stutter. Read our broader guide instead: How to Fix Game Stuttering on PC. It covers the other causes in the same step by step order.
Why first runs and new areas hitch
Three things trigger a fresh wave of shader compilation.
First, a new game means an empty cache. Nothing is compiled yet, so the first session does most of the work. Many modern games now show a “Compiling shaders”, “Building shaders”, or “Optimizing game” step on first launch specifically to front-load this.
Second, new content. Even after the first session, a game can surprise you. A new area, a new boss, or a new weather effect can need shaders the pre-compile step never saw. Unreal Engine 5 games are notorious for this, because they use a very large number of shader variants, which makes complete pre-compilation harder for developers.
Third, a driver update invalidates the cache. Shader caches are tied to the driver version that built them. Update your GPU driver and the old cache becomes unusable, so the game compiles everything again. NVIDIA recognized this pain and built Automatic Shader Compilation, a feature that rebuilds the shader cache in the background during idle time after a driver update. Until that rebuild finishes, expect one rough session.
The practical takeaway: after any driver update, give your games one full session to rebuild before you judge performance.
Let the game pre-compile shaders
The single most effective step costs nothing. Let the game’s own pre-compilation finish.
Many modern games compile shaders on first launch. You will see messages like “Compiling shaders”, “Optimizing game”, or “Building shaders”. Do not skip this step. Do not cancel it. Do not alt-tab away from the game while it runs. Titles that do this well include Call of Duty, Fortnite, Destiny 2, Returnal, Hi-Fi Rush, Horizon Zero Dawn, and Atomic Heart.
The step exists specifically to prevent in-game stutter. Yes, it is slow. Yes, it is worth the wait. Play through new areas once without judging performance, and let the cache build over your first two or three sessions rather than judging a game on its very first run.
If the game does not offer a pre-compile step, you still control the most important variable: time. The first sessions will hitch. That is normal and expected. It fades.
Enable Steam shader pre-caching
Steam can download prebuilt shader data from Valve’s servers before you ever launch the game, so your PC does less compiling itself. It is a head start, not a complete fix, but it is free and takes one minute.
1. Open Steam and click Steam in the top-left corner of the client.
2. Choose Settings. Look for Shader Pre-Caching in the left sidebar. In some client builds, the option sits on the Downloads page instead.
3. Tick both options: Enable Shader Pre-Caching and Allow background processing of Vulkan shaders.
4. Click OK, then restart Steam.
5. Let Steam download shader caches for your games before you play.
Know the limits. Steam shader pre-caching mainly helps Vulkan and OpenGL games. DirectX 12 games benefit much less, because their PSOs still need local compilation. And in games that run their own shader pre-compilation at launch, Steam cannot control that step. The game will still compile locally.
Set your driver shader cache size
Your GPU driver keeps its own shader cache, and you can make sure it has room to do its job.
For NVIDIA:
1. Right-click the desktop and open the NVIDIA Control Panel.
2. Go to Manage 3D Settings, then the Global Settings tab.
3. Scroll to Shader Cache Size.
4. Set it to Driver Default or a larger value such as 10 GB. Do not shrink it to save disk space. A small cache means compiled shaders get thrown out and recompiled, which is exactly the stutter you are trying to remove.
5. Click Apply.
For AMD:
1. Open AMD Software: Adrenalin Edition.
2. Go to Settings, then Graphics.
3. Find Shader Cache and make sure it is set to On.
The driver cache lives on your system drive, under folders like DXCache and GLCache for NVIDIA and DxCache and VkCache for AMD, inside your AppData Local folder. A nearly full drive or a slow drive makes cache access worse, so keep the game and your system drive with comfortable free space. Clearing these folders by hand is rarely needed; the next section covers the one case where a reset is justified.
Reset the shader cache when it breaks
Do not clear your shader cache on a schedule. A healthy cache is the thing preventing stutter. Reset it only when something is actually wrong: stutter that never improves on repeat runs in the same areas, or stutter that clearly got worse right after a driver update. Those are signs of a corrupt cache.
Use the route Microsoft supports. Open Windows Settings, go to System, then Storage, then Temporary files. Windows scans and lists categories. Tick DirectX Shader Cache, leave the other boxes alone, and select Remove files. This clears the OS-level shader cache safely.
One warning. After a reset, the next session rebuilds everything from zero. Expect hitches during that session. Play through representative areas of the game once to rebuild the cache, then judge. If the stutter is gone after the rebuild, the old cache was the problem.
If corruption keeps returning, the deeper fix is a clean reinstall of the GPU driver, which also refreshes the driver-level cache. Our full walkthrough covers it: How to Clean Install GPU Drivers with DDU.
Try the DX11 renderer if the game offers one
If a game gives you a choice of graphics API, switching to DirectX 11 can eliminate shader stutter almost completely. DX11 pre-compiles shaders during loading instead of mid-gameplay, so the hitches never happen in the first place.
1. Check the game’s graphics settings for a Renderer or API option and choose DirectX 11.
2. If the game does not offer the choice in its menus, check Steam: right-click the game, choose Properties, and add -dx11 to the Launch Options.
3. Restart the game. Expect longer loading screens as the trade-off.
The cost is real but simple: DX11 loading takes longer, and any DX12-exclusive features are unavailable. For games where shader stutter ruins the experience, that trade is usually worth it. For more on what each graphics setting does, see: PC Graphics Settings Explained.
NVIDIA Advanced Shader Delivery: the new cloud fix
October 2026 brought the biggest development in this space in years. Microsoft’s Advanced Shader Delivery, or ASD, moves shader compilation off your PC and into the cloud.
Here is how it works. Developers capture their game’s shaders into a standardized State Object Database, or SODB, using DirectX 12 and Microsoft’s Agility SDK. Microsoft’s cloud network combines that database with each GPU vendor’s shader compilers and precompiles the shaders for hundreds of thousands of hardware and driver combinations. The result is a Precompiled Shader Database, or PSDB, which is downloaded along with the game, matched to your exact GPU and driver. When the game launches for the first time, the shaders it needs are already sitting in the Windows shader cache. Local compilation is skipped.
NVIDIA added ASD support to GeForce RTX drivers with version 621.01, released in October 2026. NVIDIA says supported games can skip local shader compilation entirely, which removes both the long first-launch compile and the mid-game hitches. Microsoft says the initial pre-compilation step can be reduced by up to 95 percent.
What you need: Windows 11 (version 24H2 is the reported baseline), a DirectX 12 game that supports ASD, driver 621.01 or newer, and the Xbox PC app installed. The initial support covers Gears of War: E-Day and Call of Duty: Modern Warfare 4. Microsoft confirmed the feature also runs on AMD, Intel, and Qualcomm hardware through their own driver updates.
Now the honest limits, because they matter.
– Developers must specifically support ASD. If a studio has not built the SODB for its game, the driver cannot do anything for it. Most of your library will not benefit yet.
– ASD does not fix traversal stutter. That is a memory streaming problem, a different failure with a different cause.
– Unreal Engine 5.8 added engine-level ASD support with a dedicated tool that builds the SODB from a finished game. That should widen adoption, but it still needs each studio to do the work.
– The rollout is brand new. Treat broad promises cautiously until independent testing accumulates.
NVIDIA pairs ASD with its other feature, Automatic Shader Compilation, which quietly rebuilds the shader cache in the background during idle time after a driver update. Digital Foundry notes the two can be used in concert: one handles first launches and supported games, the other handles the post-driver-update rebuild.
If you play a supported game on Windows 11, updating to driver 621.01 or newer and installing the Xbox PC app is worth doing. For everything else in your library, the manual steps earlier in this guide are still the fix.
When nothing helps
Work through these in order if the hitches survive everything above.
1. Verify the game files. On Steam, right-click the game, choose Properties, open the Installed Files tab, and click Verify integrity of game files. Corrupt files can cause hitching that looks like a cache problem.
2. Disable overlays for one test run. Turn off the Discord overlay, Steam overlay, and any GPU tuning overlay completely, then test. Re-enable them one at a time if the stutter stops.
3. Update the game itself. Patches frequently improve shader precaching or fix a specific shader bug.
4. Check your storage. Keep the game on an SSD with plenty of free space. A nearly full or failing drive causes its own hitching.
5. Accept the hardware truth. A faster CPU compiles shaders more quickly, so spikes get shorter, but it does not cure a game that precaches poorly. Shader compilation is fundamentally a CPU task that blocks the GPU, so even fast hardware hitches when the game misses its precaching. Do not buy new hardware to fix shader stutter.
And skip the forum folklore. Shader compilation stutter is CPU-side and disk-side. It is not a VRAM problem. More RAM does not fix it, lowering resolution does not fix it (the GPU is idle during the hitch), and registry tweaks, core parking changes, and aggressive Windows service trimming do not touch the PSO compilation path. Those tweaks circulate because they are generic. They are not shader fixes.
Frequently asked questions
### Why does shader stutter only happen the first time I see something?
Shaders are compiled from generic code into GPU-specific machine code the first time your GPU needs them. After compilation, the result is saved to the shader cache on disk. The next time the game needs that shader, it loads instantly from the cache. No compile, no hitch.
### Why does updating my GPU driver bring the stutter back?
Shader caches are tied to the driver version that built them. A driver update invalidates the old cache, so the game compiles everything again. NVIDIA’s Automatic Shader Compilation rebuilds the cache in the background during idle time after an update, but until that finishes, expect one rough session.
### Is shader compilation stutter the same as traversal stutter?
No. Shader stutter happens once per new shader and never again that session, because the compiled result is cached. Traversal stutter repeats at the same world boundaries every time you cross them. It comes from data being loaded into and out of memory, not from compilation. Fixing one does not fix the other.
### Will a faster GPU fix shader stutter?
Somewhat, but not completely. A faster CPU shortens each spike, because compilation is a CPU job. But shader compilation blocks the GPU while it happens, so even fast hardware hitches when the game fails to precompile. The real fix is better shader caching and precaching, not raw performance.
### Should I clear my shader cache regularly?
No. A healthy cache prevents stutter, and clearing it forces a full rebuild with all the hitches that involves. Clear it only when corruption is suspected: stutter that never improves on repeat runs, or stutter that clearly got worse after a driver update.
### Does Steam shader pre-caching fix it for every game?
No. It mainly helps Vulkan and OpenGL games. DirectX 12 games benefit much less, and in games that run their own shader pre-compilation at launch, Steam cannot control that step. Treat it as a free head start, not a complete fix.
Sources
– NVIDIA driver 621.01 adding Advanced Shader Delivery support: NVIDIA, GeForce Game Ready Driver For Phantom Blade Zero and Call of Duty: Modern Warfare 4 Released – https://www.nvidia.com/en-gb/geforce/news/phantom-blade-zero-nvidia-geforce-game-ready-driver/
– Advanced Shader Delivery system explainer, State Object Database and Precompiled Shader Database: Microsoft DirectX Developer Blog, Introducing Advanced Shader Delivery – https://devblogs.microsoft.com/directx/introducing-advanced-shader-delivery/
– Advanced Shader Delivery reporting, traversal stutter limit, and Automatic Shader Compilation: Digital Foundry, Shader Compilation Stutter Begone – https://www.digitalfoundry.net/news/2026/10/shader-compilation-stutter-begone-nvidias-latest-gpu-drivers-finally-add-advanced-shader-delivery
– Driver 621.01 coverage and AMD and Qualcomm support: Pureinfotech, NVIDIA driver brings faster game loading to Windows 11 – https://pureinfotech.com/nvidia-driver-advanced-shader-delivery/
– Steam pre-caching steps, NVIDIA and AMD cache size steps, cache locations, and the DX11 switch: SmoothFPS, Fix Shader Compilation Stutter on PC – https://smoothfps.com/guides/shader-stutter
– Diagnosis-first framing, driver cache size guidance, and what not to bother with: SavePointGuide, Shader Compilation Stutter: Why It Happens, How to Fix It – https://www.savepointguide.com/post/shader-compilation-stutter-fix-pc.html
– Ordered fix steps, driver cache guidance, and Steam pre-caching scope: DisplayCard Repair, Game Stutters on First Load – https://www.displaycard-repair.com/blog/game-stutters-first-load-shader-compilation-stutter-precompilation-driver-cache/
– Unreal Engine 5 PSO explainer and the cache-clear diagnosis test: Glitchless, Unreal Engine 5 shader compilation stutter: how to fix it – https://www.glitchless.gg/unreal-engine-5-shader-compilation-stutter.html
– Unreal Engine 5.8 Advanced Shader Delivery support: TechSpot, Unreal Engine 5.8 adds support for Microsoft’s Advanced Shader Delivery – https://www.techspot.com/news/114326-unreal-engine-58-introduces-advanced-shader-delivery-support.html
– Clearing the Windows DirectX Shader Cache through Storage settings: Tech-Insider, NVIDIA Shader Cache Size guide – https://tech-insider.org/nvidia-shader-cache-size-set-clear-move-13-steps-2026/
