You just bought Death Stranding 2: On the Beach on Steam. The download finishes. You click Play. The screen goes black for a moment—then you’re back on your desktop with no error message. Or maybe the game launches but stutters violently for thirty seconds before freezing. Or it crashes ten minutes in during a cutscene.
Most players immediately blame their GPU driver, their Windows version, or even their hardware. They spend hours reinstalling, tweaking settings, and disabling half their system services. They never try the single most effective first step: verifying the integrity of the game files.
And that is a mistake.
What “Verify Integrity of Game Files” Actually Does
When you install a game through Steam, the client downloads a compressed archive of files, extracts them, and places them in your Steam library folder. Over time, those files can become corrupted. A bad sector on your hard drive. A power outage during an update. A game patch that didn’t apply cleanly. Even a faulty RAM stick can introduce errors during the installation process.
When you tell Steam to verify the integrity of game files, it does two things. First, it compares every single file in the game’s local folder against a manifest stored on Steam’s servers. This manifest contains a cryptographic hash—essentially a digital fingerprint—of every original file. If any local file’s hash doesn’t match, Steam marks it as corrupted or missing. Second, it downloads replacements for any file that failed the check. The result is a game folder that matches exactly what the developer intended for you to run.
This process is not a magic bullet. It does not fix GPU driver conflicts, overheating CPUs, or memory leaks in the engine. But it does directly address a surprisingly common cause of crashes: a single corrupted asset file that the game cannot load. Death Stranding 2 streams massive open-world terrain, character models, and audio files in real time. One broken texture can trip the engine’s error handling and shut down the entire process.
The Most Defensible Position: Start Here, Not With Reinstalls or Driver Updates
Gamers love reinstalling as a fix. It feels definitive. You delete everything, wait an hour for the download, and hope the problem disappears. But a clean reinstall is the same as verifying files—it replaces corrupted files with fresh ones from the server. Except it takes ten times longer and wastes bandwidth on every single file you already had intact. If the problem was caused by one corrupted 50-megabyte asset, you just redownloaded 80 gigabytes to fix it.
Driver updates are worse. Updating your GPU driver can fix specific issues, yes. But it can also introduce new ones. Nvidia and AMD both release drivers that cause stuttering, black screens, or reduced performance in certain titles. Many PC gamers have made the mistake of updating their driver and immediately seeing new crashes that were not there before. Now they have to roll back, spending more time.
Between reinstalling and driver updates, verifying game files takes the least time and carries the lowest risk. On a typical internet connection, a verification run on a game the size of Death Stranding 2 takes between two and ten minutes. It does not delete your save data. It does not change your settings. It does not install anything outside the game’s own folder. And it is the only method that directly repairs the game’s own data.
The reasoning is simple. File corruption is a real, documented cause of crashes in large modern games. Steam’s own support documents list verifying files as the first troubleshooting step for good reason. The chance that it works is high enough to justify the short time investment. And even if it fails to fix your crash, you have eliminated a major variable. That makes every subsequent troubleshooting step faster because you already know the game’s files are pristine.
Why This Beats Other Common Fixes for Death Stranding 2 Crashes
The source material for this article lists eighteen possible fixes. Let’s compare the first few to verifying files.
Restarting your PC and Steam is trivial but almost never fixes a crash that occurs consistently. If the game did not launch before restart, it will not launch after.
Running the game as administrator can solve permission issues, but many modern games do not require admin privileges. It also forces the game to run with elevated rights, which can cause problems with overlay software and Windows security features.
Compatibility mode for Windows 8 or 7 is a legacy workaround for games that were never updated for later Windows versions. Death Stranding 2 is a current-generation title. Forcing an older compatibility mode can actually introduce new incompatibilities with DirectX features.
Disabling full-screen optimizations helps some games that stutter in borderless window mode, but it is a band-aid at best. It does not address corrupted data.
Running SFC scan checks system files, not game files. If your Windows system files are corrupted, that is a separate problem that can cause crashes in any application. But it is not a targeted fix for Death Stranding 2.
All of these are worth trying—after you have verified game files. The one fix that directly replaces broken game data is verifying integrity. Every other fix either changes how the game interacts with Windows, changes your system configuration, or requires you to reinstall the entire game. Only verifying files repairs the game itself without collateral changes.
Acknowledging the Counterargument: “Corrupted Files Are Rare — Waste of Time”
The strongest objection to this position is that file corruption is uncommon. Many PC gamers have played hundreds of games on the same drive and never had a corrupted file. They argue that crashes are almost always caused by outdated drivers, overheating hardware, or Windows configuration issues. Verifying files, they say, is a low-yield step that rarely fixes anything and wastes time better spent on actual solutions.
This is wrong for three reasons.
First, file corruption is more common than most gamers realize. Steam regularly detects corruption during its background verification processes. Large game updates, especially preloads that involve unpacking encrypted archives, are particularly error-prone. A single failed sector on a hard drive can corrupt exactly one file out of ten thousand. The game will crash or fail to launch, and the player will blame the game itself or their hardware. They will never know a file was broken because they never checked.
Second, Death Stranding 2 is a massive, asset-heavy game. The Decima engine loads many small files—textures, shader caches, audio banks—on demand. A corrupted shader file can cause crashes that look exactly like GPU driver instability. Players who update their drivers because they think the crash is GPU-related may actually be chasing a file issue. They waste hours on driver rollbacks and clean installs that do not address the root cause. Verifying files takes five minutes and immediately tells you if that is the problem.
Third, the argument that verifying files is a “waste of time” ignores the cost of not doing it. If you skip this step and jump straight to reinstalling Windows or buying new hardware, you have wasted hours or money. Spending five minutes on a low-effort fix first is not wasteful. It is efficient.
The counterargument holds only if file corruption is zero. It is not zero. It is high enough that Steam prioritizes this fix above almost all others. Dismissing it is an expensive mistake.
Step-by-Step: How to Verify Integrity of Game Files for Death Stranding 2 on Steam
Here is exactly what to do, with no frills.
Open your Steam library. Find Death Stranding 2: On the Beach in your list. Right-click the game entry. Select Properties from the context menu.
In the Properties window, click the Installed Files tab on the left side. You will see a button labeled Verify integrity of game files… . Click it.
Steam will begin scanning every file in the game folder against the server manifest. This process can take anywhere from two to twenty minutes depending on your hard drive speed and the size of the game. You can watch the progress in the Downloads window or just leave it running in the background.
When the scan finishes, Steam will report one of two outcomes. Either “All files successfully validated” or a list of files that failed and were reacquired. If you see the latter, try launching the game immediately. If you see the former, your game files are intact and you should move on to another fix.
Do not skip this step even if you only just installed the game. Installation errors happen. Steam itself sometimes reports a successful install when files were corrupted during extraction. Run the verification regardless.
After verification, launch the game. If it starts and runs without crashing, you are done. If it still crashes, you have eliminated file corruption as the cause and can move to other solutions—updating drivers, disabling overlays, closing background applications, or adjusting in-game graphics settings.
A Note on Launch Options for Death Stranding 2
If verification passes but crashes persist, the source material suggests adding launch options like -dx11codecodecodecodecode, -dx12codecodecodecodecode, or -d3d11codecodecodecodecode in the game’s Steam properties under General. These force the game to use a specific rendering API. Some players report that using DirectX 11 instead of 12 stabilizes the game. This is a reasonable next step after verifying files. But do not skip the verification step and jump straight to launch options. If a corrupted file is causing the crash, launch options will not fix it.
When Verifying Game Files Won’t Help (and What to Try Next)
There are genuine scenarios where verifying game files returns a clean result but the game still crashes. That is normal. File integrity is just one variable in a long list.
What then? Start with the most common crash causes that are not file-related.
Update your GPU driver. Use the official Nvidia or AMD tools, not Windows Update. A clean driver install using DDU (Display Driver Uninstaller) can remove conflicting settings from previous driver versions.
Disable Steam overlay and any other in-game overlays like Discord or GeForce Experience. Overlays inject code into the game process and can cause instability.
Turn off any antivirus or real-time protection for the game folder. Windows Defender is sometimes overzealous with large games. Excluding the Steam library folder from scans can prevent false positives that block file access.
Reduce in-game graphics settings, particularly texture quality and shadow resolution. Death Stranding 2 can use large amounts of VRAM. If your GPU runs out of memory, the game crashes.
If the game still crashes, check your system’s temperature monitoring. Overheating CPUs and GPUs cause crashes that look like software bugs. A quick look at HWMonitor or MSI Afterburner can confirm or rule out thermal throttling.
Finally, consider your storage drive. Death Stranding 2 loads terrain and assets continuously as you traverse its world. If the game is installed on a mechanical hard drive, or even a SATA SSD that is nearly full, the drive’s read speed may drop below what the engine expects. The game can appear to hang or crash when the engine cannot stream an asset in time.
Verifying game files will not fix that. Neither will updating drivers. The only solution is moving the game to a faster drive with enough free space—ideally an NVMe SSD with at least 50 gigabytes of overhead. This is the one nuance that the standard troubleshooting guide overlooks. If you have verified files, updated drivers, disabled overlays, and still see crashes in open-world areas, check your drive.
You might just be waiting on a slow disk.
