The Blood of Dawnwalker Keeps Crashing: Find Out When and Fix It

Each timing points at a different layer. Running the wrong checks is why most crash advice feels useless.

1. Before the menu appears

   Startup layer. Verify game files and update the GPU driver before touching in-game settings, because you cannot reach the settings menu yet.

2. While compiling shaders

   Shader layer. The official known-issue entry for this points at a BIOS check. Also close overlays and do not alt-tab during the first launch after a patch.

3. When loading a save

   Save layer. Try an older manual save instead of the newest one. If only one slot crashes, keep that slot and report it rather than deleting it.

4. In a cutscene

   Rendering layer. Lower settings and disable frame generation, then replay from the last save instead of skipping the sequence.

5. At random during play

   Reproduction layer. Note the location and the exact action first. A random crash cannot be fixed without a repeatable case.

These are the checks the patch notes and known-issue posts actually call for, in the order they should be run.

1. Update the game first

   Hotfix 1.0.4 includes stability improvements. Testing a crash on an older build can waste the whole session.

2. Verify the game files

   In Steam: right-click the game, Properties, Installed Files, Verify integrity. A partially downloaded patch is a common startup crash cause.

3. Update the GPU driver

   Shader compilation happens on the driver. An outdated driver can crash exactly at first launch.

4. Check whether your BIOS is up to date

   This is the specific guidance the developer’s known-issue post gives for crashes while compiling shaders. Treat it as a vendor-level check, not a game setting.

None of these steps claims to fix every crash. If the crash survives all four, it needs a reproduction rather than another setting change.

Reported by several players and consistent with how the game is built, but not confirmed by the developer.

1. Let the first shader pass finish

   Do not alt-tab or close the window during shader compilation after a patch. Let it complete once, then reopen the game normally.

2. Disable overlays

   Discord, Steam and capture overlays all hook into the render pipeline and have been reported to trigger crashes on some systems.

3. Remove mods before testing

   A modded install cannot be compared with an official note. Reproduce the crash on a clean install to know whether the mod is involved.

Single reports or causes that have not been confirmed. Try these only after the official checks, and change one thing at a time.

1. Delete the shader cache

   Reported to clear a repeatable shader crash by forcing a full recompile. It is also the fastest way to reintroduce stutter, so expect a slower first session.

2. Turn off frame generation

   Reported to stop crashes and black screens in cutscenes. Not confirmed as a cause.

3. Lower graphics settings before a known heavy scene

   A workaround for one specific repeatable crash, not a general fix. It does not identify the cause.

Do Not Do This First

These actions lose information or progress before you know what is wrong.

• Do not delete the crashing save. Keep it, because it is the reproduction.
• Do not reinstall the game before verifying files and updating the driver.
• Do not change several settings at once and then test.

Other symptom guides

• Crashes →
• Stuttering →
• Controller →
• Quest progress →
• Diagnose saving →