Death Stranding 2 Errors: Fix Paths, and When to Ask for a Refund

Cause: The launch build mishandles ray tracing and frame generation during initialisation.

Fix: From the launcher menu before pressing play, turn ray tracing completely off, disable frame generation, and switch anti-aliasing from DLSS/FSR to PICO. Then verify game files and update to the game-ready driver.

Cause: Genuine system or video memory exhaustion, and the Decima engine is unusually sensitive to overclocks.

Fix: Remove any GPU overclock first. Then set a manual Windows page file of 16384 MB initial and 32768 MB maximum on your fastest SSD. Lower the in-game Texture Streaming Pool from Epic/High to Medium, and disable ray tracing if you have under 12GB of VRAM.

Cause: A memory leak — the engine streams open-world data and fails to release it when a high-fidelity cutscene loads.

Fix: Restart the game every two to three hours to clear the cache until a patch arrives. If a specific region consistently crashes, lower cloud quality: volumetric clouds cause GPU spikes during timefall storms.

Cause: A monitor refresh-rate or resolution handshake problem.

Fix: Add -windowed to the Steam launch options to reach the display settings, set the native resolution and refresh rate manually, then switch back to fullscreen or borderless. Disabling fullscreen optimizations also helps.

Cause: WDDM 3.2 changes altered how the game allocates memory and initialises DirectX.

Fix: Enable compatibility mode for Windows 8 plus “Run as administrator” and disable fullscreen optimizations on the executable. Try -dx11 to bypass DX12 shader initialisation. As a last step, set a manual page file of 12288 MB initial / 24576 MB maximum.

Verify game file integrity through your launcher and restart the PC. This clears stuck background tasks and driver hooks, and repairs the corrupt downloads that launch-day server load makes common.

Install the latest GPU driver from the vendor site rather than Windows Update, and choose the clean-install option. Both NVIDIA and AMD ship game-ready drivers for major releases that fix compatibility outright.

Disable Steam, Discord, Xbox Game Bar, GeForce Experience and MSI Afterburner overlays, along with RGB utilities and hardware monitors. These inject code into the game process and are one of the most frequent crash triggers.

Clear the DirectX shader cache from Windows Disk Cleanup and delete the game’s own shader cache folder, then let it rebuild. Corrupted shader caches cause crashes that look like hardware faults.

Remove GPU and CPU overclocks including RAM XMP/EXPO, check temperatures, and if the crash pattern points to CPU instability rather than the GPU, update the motherboard BIOS before assuming your hardware is faulty.

If a fault is acknowledged by the developer as a known issue, say so in your refund request and include the crash pattern. Store refund windows are usually 14 days with under two hours of play, but documented technical faults that make a game unplayable are a valid reason to push past that — attach your crash logs and the steps you already tried.

Include the full error text, when the problem began, whether it followed a patch or driver update, your hardware and driver versions, and the troubleshooting steps already attempted. A refund request with evidence is far more likely to be granted than one without.