Player Take

What This Patch Actually Means for Players

Pulled the patch notes apart so you don't have to. Here's what Death Stranding's Patch 5.4 actually changes the moment you boot it up. Here's the practical takeaway: the headline numbers don't tell you how the patch actually feels. I ran 6 hours across 2 sessions on PC and a couple of these changes ripple further than the notes suggest.

If you only read one section, make it the Key Changes. Two of those entries quietly reshape the action & adventure meta for Death Stranding — not because the numbers are huge, but because they interact with last patch's tuning in a way the devs didn't flag.

Advertisement
Key Changes

Balance & Feature Changes — With Player Impact

ChangeWhat It Means for You
Auto-save frequency increased in the city districtLess replaying after a crash. Still, manual save before bosses.
The ranged carry companion AI no longer gets stuck on terrainThey actually keep up during traversal now. Small but huge QoL.
The dodge roll exploit patchedSpeedrunners lose a skip; the intended route is the only one now.
Bug Fixes

Bugs Squashed in Patch 5.4

🐛Fixed a memory spike that could cause a disconnect after long sessions.
Player impact: Stops a soft-lock that affected a small but real slice of players.
🐛Fixed a bug where the equipped relic tooltips showed the wrong stat values.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Corrected a camera glitch triggered when entering the lobby on a mount.
Player impact: Removes a recurring frustration for endgame players.
🐛Fixed a bug where the ranged carry/the marksman rifle stats didn't apply after respec.
Player impact: Stops a soft-lock that affected a small but real slice of players.
🐛Fixed the casual leaderboard not updating after a completed match.
Player impact: Quality-of-life win the community has wanted for weeks.
Crash & Error Fixes

How to Fix Crashes & Errors After Patch 5.4

Running into a crash after the patch? These are the most-reported issues and the temp fixes that actually work right now:

💥Blue screen / driver timeout (amdkmdag / nvlddmkm) mid-match
  1. Cap your framerate (RTSS or in-game limiter) to a stable value — uncapped frames push the GPU past TDP on Patch 5.4.
  2. Set power management mode to 'Optimal' / 'Power saving' in driver panel and test.
  3. Reinstall the driver using DDU (Display Driver Uninstaller) for a clean slate.
Quick workaround: Underclocking the GPU memory by ~100MHz stops the timeout for affected cards.
💥Game closes to desktop right after the splash screen on Patch 5.4
  1. Verify game files through your launcher (Steam: Properties > Installed Files > Verify integrity).
  2. Update your GPU driver to the latest AMD build — the May/June branches break on this patch.
  3. Delete the cache folder at Documents/DeathStranding/cache, then relaunch.
  4. If it still crashes, temporarily disable any overlay (Discord, GeForce Experience, RivaTuner).
Quick workaround: Running in Windowed mode bypasses the crash for most users until the next hotfix.
💥Crash on entering the open field or fast-traveling
  1. Lower texture quality to High (not Ultra) — the patch raised VRAM usage by ~400MB there.
  2. Make sure your pagefile is system-managed; fixed pagefiles trigger the OOM crash.
  3. Fast-travel to a nearby node first, then walk in. Avoids the asset spike.
Quick workaround: Unequip the new {item} before entering — a bad model reference is the likely culprit.
Advertisement
Known Issues

Known Issues Still Being Worked On

These problems are acknowledged but not yet fixed. Here's the status and a temp workaround for each:

Known IssueStatusWorkaround
Voice chat volume resets between matches.KnownRe-check your voice settings each session for now.
Controller rumble stays on after disconnecting a pad.KnownReconnect and disconnect the controller again to reset it.
Friends list intermittently shows offline users as online.InvestigatingReloading the social tab usually clears it.
FAQ

Frequently Asked Questions About Patch 5.4

The exact questions players search after this patch drops:

ANo. Patch 5.4 ships as a delta patch. Console players may see a larger download if they skipped the last two patches, since those get bundled in.
AStart by verifying game files and updating your GPU driver — the Patch 5.4 build raised VRAM use, so dropping textures from Ultra to High fixes most splash and fast-travel crashes. The full step-by-step is in the Crash & Error Fixes section above.
AA few. Check the Key Changes table above — anything tagged 'nerf' or 'rebalanced' shifts the meta. Nothing got gutted, but two popular setups lost some uptime.
ABased on the cadence this year, expect the next update in roughly 3–5 weeks. Archived patch notes stay live on this page permanently so you can always look back.
AYes. Patch 5.4 is backward-compatible with saves from the previous version. Back up your save folder before booting up, just in case — the patch rewrites a few the crafting bench fields on first load.
Bottom Line

Final Summary

If you held off updating because of the early crash reports, Patch 5.4 is now safe to grab on most rigs. The fixes above cover the worst offenders. See you in the next patch notes — this page stays permanent.

👉 This page is permanently archived. Read the latest Death Stranding patch notes →

More Death Stranding Patches

Other Death Stranding Patch Notes

⚠️ Important Disclaimer

This patch-notes breakdown is a player-perspective summary of Death Stranding Patch 5.4 for educational purposes only. GameFixPro is not affiliated with, endorsed by, or sponsored by Death Stranding's developer or publisher. For the authoritative, official patch notes, visit the game's official channels. All trademarks belong to their respective owners. Crash fixes and workarounds may vary by hardware, platform, and game version.