Fix DirectX 12 Shader Compilation Stutter on Windows 11

To reduce DirectX 12 shader compilation stutter on Windows 11, start by completing the game’s shader preparation, preserving its working cache, and checking for relevant game or driver fixes. Use a cache reset when there is evidence of a cache problem, then allow preparation to finish before comparing performance.

A powerful graphics card does not guarantee that every required rendering pipeline will be ready when the game needs it. Microsoft’s Direct3D 12 sample demonstrates how caching compiled pipelines helps avoid repeated compilation and associated rendering interruptions.

Why DirectX 12 Games Can Stutter During Shader Compilation

DirectX 12 games use pipeline state objects, usually shortened to PSOs, to describe shaders and other rendering state needed for drawing.

Preparing these pipelines can take time. If the necessary work happens just as the game needs to display an effect, frame delivery can pause.

AMD’s developer guidance recommends avoiding last-minute PSO compilation and reusing pipeline caches across sessions. That explains why completed preparation is valuable—and why deleting a healthy cache can introduce work that had already been done.

Games handle this differently. Some prepare substantial amounts before gameplay. Others prepare additional pipelines as content becomes relevant. Microsoft also demonstrates a fallback approach that uses a general-purpose shader while a specialized pipeline finishes compiling.

The practical result is that two DX12 games on the same PC can behave very differently.

First, Check Whether the Pattern Fits Shader Preparation

A sudden pause does not identify its own cause.

Use these observations to choose a useful comparison:

These are diagnostic clues, not proof.

Repeat the same action or route with unchanged settings. A smoother second attempt suggests that some reusable work helped, but that can include previously loaded assets as well as shader preparation.

Our guide to shader compilation stutter versus traversal stutter explains how to interpret those patterns more carefully.

1. Complete the Game’s Shader Preparation

If the game displays a shader-compilation screen, let it finish before evaluating gameplay. Follow any publisher instructions for preparing or restarting shaders.

Keep your graphics settings stable during the comparison. Otherwise, you are changing the workload you want to investigate.

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

For that reason, avoid assuming that:

• Waiting at every game’s main menu compiles everything.
• Every game needs the same number of minutes.
• One smooth area proves that all later encounters will be smooth.

Use the preparation indicators the game actually provides, then compare repeatable gameplay. If the same problem persists, investigate it rather than waiting indefinitely.

2. Update the Relevant Software and Check Game Files

Before changing settings, record the game version, GPU driver version, and when the problem began.

Check the game’s patch notes for shader-preparation, DX12, or stuttering fixes. Check your graphics driver’s release notes for the specific title.

AMD’s troubleshooting guidance recommends applying documented workarounds and, where an unresolved driver regression exists, considering the last working driver. That is a targeted response to evidence; repeatedly installing different drivers without a controlled comparison makes the result harder to interpret.

Use Windows Update for Windows components

On Windows 11, check Settings → Windows Update and complete relevant pending updates and restarts.

Avoid treating a random “DirectX 12 installer” as a shader-stutter fix. Microsoft explains that DirectX is part of Windows and that modern DirectX updates are delivered through Windows Update. Its older End-User Runtime package does not upgrade the installed Direct3D version.

Verify files when installation damage is plausible

If preparation fails, content is missing, or the problem followed an interrupted installation, use the launcher’s verification function.

For Steam:

1. Right-click the game in your Library.
2. Open Properties.
3. Select Installed Files.
4. Choose Verify integrity of game files.

Steam documents this route for checking the installed game files. Verification can address installation problems, but it should not be described as a guaranteed repair for pipeline-compilation hitches.

3. Preserve Shader Caching and Check Driver Settings

A working cache helps retain preparation between sessions. Inspect any cleaner or launch script that you have explicitly configured to remove graphics-cache files.

Also distinguish a cache reset from leaving caching disabled afterward. Microsoft defines clearing existing data and disabling cache use as separate operations.

NVIDIA GeForce

Check the shader-cache setting available in your installed NVIDIA software. If you disabled it during troubleshooting, complete the documented procedure and restore the recommended setting.

NVIDIA warns that a cache limit that is too small can remove entries your games still need, causing renewed stuttering. It recommends choosing a capacity appropriate for your games and available storage—not assuming one size is best for every PC.

If you need to perform a driver-cache reset, follow our guide to rebuilding NVIDIA’s shader cache without causing unnecessary stutter.

AMD Radeon

AMD Software documents a Reset Shader Cache control under its advanced graphics settings. Available controls and their locations can vary with the software and hardware configuration.

Use it when a reset is justified, then preserve the rebuilt result. Our AMD shader-cache stutter guide explains the Radeon-specific sequence.

For other graphics hardware, use the game publisher’s and GPU manufacturer’s applicable instructions rather than borrowing another vendor’s folder paths.

4. Reset the Appropriate Cache Only When Needed

A reset is reasonable when the publisher recommends it for your symptoms or there is a supported reason to suspect damaged cache data.

NVIDIA states that damaged shader-cache files can cause launch failures, lower performance, or visual artifacts, and provides a procedure for recreating them. That establishes a legitimate troubleshooting use for resetting a cache.

However, “the game stutters” alone does not prove corruption.

Clear Windows’ DirectX Shader Cache

For a controlled Windows cache test:

1. Close the game and launcher.
2. Search Windows for Disk Cleanup.
3. Select the Windows drive when prompted.
4. Select DirectX Shader Cache, if listed.
5. Deselect unrelated categories.
6. Confirm deletion.

Microsoft documents reviewing cleanup categories before removal, and its DirectX specification confirms integration with disk cleanup.

Windows cleanup does not necessarily reset every cache used by a game. Direct3D, graphics drivers, and applications can manage different cached data. Follow the publisher’s procedure if it identifies a particular cache.

After resetting, allow rebuilding. Epic specifically warns that Fortnite’s first match can remain stuttery while new shaders compile after a cache clear.

5. Check Whether Precompiled Shader Delivery Is Supported

Some supported configurations can receive prepared shader data rather than performing all the corresponding compilation locally.

Availability matters here. As of October 2, 2026, Advanced Shader Delivery is still expanding across hardware and games.

Microsoft’s updated AMD announcement lists these requirements for its supported Xbox PC app experience:

• Windows 11 24H2 or newer.
• Supported AMD RDNA graphics.
• AMD Adrenalin 26.6.1 or newer.
• Xbox Gaming Services 37.113.11003.0 or newer.
• A supported game.

Microsoft also identifies “Precompiled shaders installed” as the launch-window message indicating that the feature is working.

Its October 1 announcement describes additional hardware expansion, with the listed Intel and NVIDIA support scheduled for later in October. Do not treat that announcement as confirmation that every compatible GPU already has the feature.

Check the requirements for your specific game, hardware, driver, and storefront. These are requirements for that shader-delivery feature, not general minimum requirements for playing every DX12 game.

6. Understand What Windows Graphics Switches Actually Change

Several Windows settings appear in generic stutter-fix lists, but their documented purpose matters.

Optimizations for windowed games targets compatible DirectX 10 and DirectX 11 games in windowed or borderless modes. Microsoft describes it as changing their presentation model. It should not be presented as a DX12 shader-precompilation switch.

Hardware-accelerated GPU scheduling changes how GPU scheduling is handled. Microsoft’s explanation concerns scheduling efficiency between applications; it does not establish that toggling the feature will prepare a game’s missing shaders.

If a publisher documents a relevant setting workaround, test it. Otherwise, avoid changing several Windows options simply because their names sound performance-related.

Keep each change separate so you can identify whether it affects the particular pause you are investigating.

7. Compare Repeated Runs Before Declaring a Fix

Choose a short sequence that you can reproduce. Keep the driver, graphics settings, rendering API, and starting location unchanged.

Use this suggested comparison:

1. Run the sequence after preparation.
2. Repeat it without clearing anything.
3. Close the game normally.
4. Relaunch and repeat again.

Record where the pause occurs and whether it becomes shorter, disappears, or returns.

If you use a measurement tool, examine frame timing around that event. PresentMon provides frame-presentation analysis and performance-data capture, allowing more detailed comparisons than an average-FPS figure alone.

For perspective, evenly delivered 60 FPS corresponds to approximately 16.7 milliseconds per frame. A hypothetical 100-millisecond frame is a substantial interruption even when surrounding frames arrive quickly. Those figures illustrate timing; they are not benchmark results.

A timing spike tells you that delivery became uneven. Its shape alone does not identify shader compilation as the cause.

When the Remaining Problem Needs a Different Fix

If completed preparation and a justified reset produce no repeatable improvement, stop repeating the deletion.

Look for evidence of another issue: a particular mod, a recent configuration change, overheating, or instability from custom tuning. AMD’s troubleshooting guidance includes software conflicts, cooling problems, and unstable settings among possible system issues.

There are also game-side limits. Epic’s documentation provides tools for identifying missed and late pipeline preparation, illustrating why a developer may need to change what gets prepared or when that work happens.

A useful report includes the exact game and driver versions, graphics settings, save location, reproduction steps, and observations from repeated runs. That gives support something specific to investigate.

FAQ

Why does shader stutter return after a graphics-driver update?

Cached pipeline data can depend on the driver and hardware. Microsoft documents driver-version mismatches for cached PSOs, so previously prepared data may need to be recreated. That does not automatically mean the new installation is broken.

Should I clear the shader cache every time a DX12 game stutters?

No. First complete preparation and compare repeated gameplay. A reset removes reusable work and is most useful when supported by a specific troubleshooting reason.

Can shader stutter remain after the compilation screen reaches 100%?

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

Does a larger NVIDIA shader cache guarantee smoother gameplay?

No. More capacity can help retain useful entries when the existing limit is restrictive, but it does not correct every cause of stutter. Evaluate the same troublesome event before and after changing capacity.

Will Advanced Shader Delivery fix every Windows 11 game?

No. It requires supported hardware, software, game content, and a compatible delivery path. Microsoft’s October 2026 announcement describes an expanding rollout, not universal support for every DX12 title.

Keep the Configuration That Produces a Repeatable Improvement

If preparation resolves the hitch, preserve the working cache. If a documented driver or game fix helps, record the version and settings that worked.

If the pause survives controlled comparisons, move to the next explanation. A repeatable result—or a precise report of the remaining problem—is more useful than another round of unrelated tweaks.