Tracked buildv1.003

Version-stamped guides

Shader Compilation Stutter in The Blood of Dawnwalker — Causes and Fixes

Updated 2026-09-06

On this page

Quick Answer

Sourced 2026-09-06, build 1.003

Short freezes the first time you enter a new area or see a new effect — then smooth on revisit — is the classic signature of DX12 shader compilation. Community guides converge on a short fix list: enlarge the GPU driver's shader cache (10 GB is the repeated figure for NVIDIA), rebuild it after clearing, keep drivers clean-installed, and let the game compile on the main menu after patches. Everything here is community-reported — nobody has benchmarked these claims publicly, and we have not tested them ourselves yet.

The Symptom Pattern: How to Tell It Is Shader Compilation

Not every hitch is a shader problem. Community guides describe a pattern that separates compilation stutter from other performance trouble:

  • The freeze happens the first time you reach a location, meet an enemy type, or trigger an effect — and the same spot runs smoothly afterwards. That one-time nature is the signature.
  • Freezes cluster right after installing a patch or updating your GPU driver, when previously compiled shaders no longer match.
  • Loading into a fresh region produces a burst of short hitches rather than one long stall, and frame pacing recovers within the same session.

If instead the game hitches at regular intervals while sprinting across the map regardless of whether you have been there before, that points to asset streaming (usually a storage-drive problem), not shaders — a different fix page covers that pattern.

The Reported Fix Order

Community sources converge on the steps below, roughly in this order. Each carries its reporting status — nothing on this page has been tested by us.

#StepWhat guides reportStatus
1Set NVIDIA shader cache size to 10 GBThree independent guides name this figure; the default cap can evict The Blood of Dawnwalker's shaders mid-session◐ Sourced — allthings.how, pixelnitro, lagofast
2AMD (Adrenalin): clear the shader cache and let it rebuildReported as the equivalent first step on AMD cards◐ Sourced — allthings.how
3Clean-install your GPU driverRepeatedly cited when stutter began after a driver update◐ Sourced — multiple guides
4After a game patch, wait on the main menu before loading a saveGuides report compilation continues at the menu; entering a save mid-compile produces the worst hitches◐ Sourced — pixelnitro, lagofast
5Verify game files through your launcherStandard hygiene after a patch; cited as ruling out corrupted assets◐ Sourced — multiple guides

Before you delete anything: community reports flag two things worth knowing. Deleting files inside the game's install folder is not part of any guide we would cite — keep deletions to your GPU driver's own cache controls. And after clearing the cache, the first hour of play will stutter more than before, because every shader compiles again from scratch. Judge the result only once that rebuild has settled.

Why This Happens (The Short Version)

The game ships shaders in a form your GPU driver finishes compiling at run time under DX12. First encounter with a new visual — a new region, spell effect, or weather state — triggers a compile burst right as you play, which presents as a brief freeze. A driver-level cache stores the compiled results so later encounters skip the work. Anything that invalidates that cache (game patches, driver updates, a cache size cap too small to hold the game's set) brings the stutter back.

What Did Not Help (Per Community Reports)

  • Disabling driver-level security features (such as Control Flow Guard) circulates on low-credibility sites with no test evidence and contradictory numbers attached. We do not recommend it, and we do not reproduce the claims here.
  • Lowering graphics settings does not address compilation stutter — guides note the freezes persist at Low settings because compilation is not tied to visual quality.
  • One-time cache clears without a driver refresh reportedly help only briefly if a mismatching driver remains installed.

Sources

Every claim on this page is compiled from those public sources — we have not run our own tests yet, and no source we cite has published benchmark data for these fixes. That is exactly why every row above says "reported" instead of "confirmed". Once first-party testing becomes possible, the measured results will replace these entries and the check date on this page will change.

Frequently asked questions