Interactive Troubleshooter

Published: Oct 14, 2026

Corrupted Game Save After a Crash: How to Recover It

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

This interactive diagnostic tree resolves corrupted game save files following abrupt system crashes, power losses, or BSODs. It guides engineers and gamers through isolating interrupted disk I/O buffers, resolving Steam/Epic cloud synchronization conflicts, recovering .bak rolling backups, and reconstructing broken file headers.

Full Diagnostic Tree & Step-by-Step Overview

What specific error behavior occurs when the game attempts to load your save file after the crash?

Game displays explicit 'Load Failed', 'Save Data Corrupted', or 'Data Cannot Be Loaded' error on load menu.
Save slot appears completely empty, missing, or reset to 'New Game' / level 1 progress.
Game hangs on an infinite loading screen or crashes to desktop (CTD) immediately upon selecting the save slot.
Cloud gaming client (Steam Cloud, Epic Games Launcher, Xbox App) reports a 'Cloud Sync Conflict' or overwrote local save files.

What is the physical file state of the save data inside the local directory?

Save file size is exactly 0 KB (zero-byte file corruption caused by mid-write power loss).
Save file contains valid byte size, but secondary `.bak`, `.old`, or `.tmp` files exist in the save folder.
Save file header exhibits byte nullification or corruption when inspected with a text/hex editor.
Game uses JSON/XML-based readable save structures, but the file contains truncated syntax errors.

Recovering Zero-Byte Save Files via Volume Shadow Copies and NTFS Metadata

Solution:

Root Cause: Mid-Write Kernel Panic and File Truncation (Zero-Byte File Corruption)

When a system crashes, suffers a power outage, or experiences a Blue Screen of Death (BSOD) while a game engine is actively executing an I/O write operation, the NTFS file stream is truncated. The operating system allocates the file pointer on disk, but the volatile RAM buffer containing actual game state bytes fails to flush from cache to the storage controller. This results in a 0 KB (zero-byte) file payload that the game's parser immediately rejects as invalid.

Diagnostic Verification:

Navigate to the game's save folder (typically %USERPROFILE%\Documents, %LOCALAPPDATA%, or %USERPROFILE%\Saved Games).

Check the file size of the primary save file (e.g., save01.dat). If Size on disk reads 0 bytes, disk write truncation occurred.

Step-by-Step Fix:

1Check for Shadow Copy Snapshots via PowerShell:

Open PowerShell as Administrator and query active system snapshots:

Get-WmiObject -Class Win32_ShadowCopy | Select-Object DeviceObject, InstallDate, VolumeName

2Extract Prior Version Using Windows File History / Previous Versions:

Right-click the game's save folder > select Properties > navigate to the Previous Versions tab.

Select a restore point dated *before* the crash occurred and click Open.

Copy the intact historical save file from the snapshot folder and paste it into your active save directory.

3Extract via PowerShell Direct Symbolic Link (If Previous Versions tab is unavailable):

Create a symlink to the shadow copy volume:

cmd /c mklink /d C:\ShadowCopy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\

Navigate to C:\ShadowCopy\Users\<Username>\AppData\Local\<GameName>\Saved\SaveGames and retrieve your intact save file.

4Relaunch game and verify state restoration.

Prevention & Long-Term Monitoring:

Enable Windows System Protection / File History on system drives housing user document folders to maintain continuous shadow copy protection.

Restoring Engine-Generated Rolling Backup Files (.bak / .old / .tmp)

Solution:

Root Cause: Primary Save File Corruption with Intact Fallback Backups

Modern game engines (Unreal Engine, Unity, Proprietary engines) implement atomic save mechanisms. During a save operation, the engine creates a new file or renames the prior save file to a backup extension (e.g., save.dat.bak, save.old, save.tmp, or slot0_backup.sav) before overwriting the main file. When a crash occurs, the main save file is corrupted, but the engine's backup file remains completely healthy.

Diagnostic Verification:

Open the game save directory in File Explorer.

Look for files sharing the same base name with extensions such as .bak, .old, .tmp, or timestamped variations (e.g., save_20261014_2200.sav).

Step-by-Step Fix:

1Quarantining Corrupted Files:

Create a temporary backup folder on your Desktop named Corrupted_Save_Backup.

Move the corrupted primary save file (e.g., save.dat) out of the game folder and into the backup folder.

2Renaming the Healthy Backup File:

Locate the most recent backup file (e.g., save.dat.bak or save.tmp).

Rename save.dat.bak to match the exact primary filename expected by the game engine (e.g., save.dat).

3Verifying File Extension Visibility:

Ensure Windows File Explorer is configured to display file extensions: Open File Explorer > View > Show > check File name extensions.

4Launch the game and load the restored slot.

Prevention & Long-Term Monitoring:

Periodically archive save directories manually prior to applying major game patches or mod updates.

Reconstructing Hex File Headers and Fixing EOF Marker Errors

Solution:

Root Cause: Binary Header Corruption and Null Byte Padding

When a system crashes mid-save, the trailing end or leading header bytes of a binary save file may be overwritten with null bytes (0x00) or corrupted block markers. If the magic header sequence (e.g., SAV3, USAV, GVAS for Unreal Engine) or End-of-File (EOF) integrity checks fail, the game binary aborts file reading and flags the save as corrupt.

Diagnostic Verification:

Download and open an official, open-source hex editor like HxD.

Open the corrupted save file alongside a known healthy save file created from a new game slot.

Compare the first 16 to 32 hex bytes (the Magic Number header). If the corrupted file starts with 00 00 00 00 instead of valid ASCII/hex signature bytes, header corruption is present.

Step-by-Step Fix:

1Open Both Files in HxD:

Open corrupted_save.dat and healthy_new_save.dat in HxD.

2Copy Valid Magic Header Block:

Highlight the valid header block from healthy_new_save.dat (typically lines 00000000 through 00000020).

Copy the hex selection (Ctrl + C).

3Overwrite Corrupted Header in Target File:

In corrupted_save.dat, select the corrupted initial null bytes matching the exact length.

Paste write (Ctrl + B) to overwrite the corrupted header without altering overall file length.

4Inspect trailing EOF bytes for unexpected trailing null blocks and save changes.

5Launch game and test loading.

Prevention & Long-Term Monitoring:

Ensure storage drive firmware is updated to avoid write-cache flushing bugs during unexpected system shutdowns.

Repairing Truncated JSON / XML / INI Structured Save Syntax

Solution:

Root Cause: Syntax Parsing Errors in Structured Plain-Text Save Data

Many indie games and modded titles store save states in structured, human-readable formats such as JSON (.json), XML (.xml), or INI (.ini). An abrupt crash truncates the output file stream mid-string, leaving unclosed brackets (e.g., missing closing } or </savestate>), breaking parser deserialization and throwing instant load failures.

Diagnostic Verification:

Open the save file in a code editor like VS Code or Notepad++.

Look for red syntax error highlights or scroll to the absolute end of the file. If the file terminates mid-line without closing tags or brackets, syntax truncation is present.

Step-by-Step Fix:

1Validate File Syntax using Terminal/Code Tools:

For JSON saves, run PowerShell JSON validator:

Get-Content -Path .\corrupted_save.json | ConvertFrom-Json

PowerShell will output the exact line and column number where syntax parsing failed.

2Repair Truncated Formatting in VS Code / Notepad++:

Open the file and navigate to the reported error line.

Add missing closing quotes, trailing commas, or closing object braces (} or ]) to complete the structure validly.

3Re-validate and Save File:

Re-run the PowerShell validation command until no syntax errors are returned.

4Launch game and test loading.

Prevention & Long-Term Monitoring:

Use a developer editor with automatic JSON/XML validation when editing or recovering plain-text save files.

Why is the save slot missing, unlisted, or failing to display in the game menu?

The save index / profile manifest file (`profile.sav` or `saves.ini`) is corrupted or out of sync.
Windows User Account Control (UAC) or Controlled Folder Access redirected save writes to VirtualStore.
The save directory permissions were reset to Read-Only or SYSTEM-only access.
A game patch or update changed the target save directory path or Steam User ID directory.

Rebuilding Profile Manifests and Save Index Metadata Files

Solution:

Root Cause: Profile Index File Desynchronization

Many games keep individual save slot files (e.g., slot1.sav, slot2.sav) organized via a central index manifest file (e.g., profile.bin, save_index.json, or global.dat). When a crash occurs, individual slot data may remain intact, but the index manifest file is reset or corrupted. The game reads the corrupted index, concludes no save slots exist, and shows an empty load menu.

Diagnostic Verification:

Inspect the save folder. Individual slot files (slot01.sav) exist and contain valid multi-megabyte data sizes, but profile.sav or index.dat is 0 KB or missing.

Step-by-Step Fix:

1Backup Active Save Directory to Desktop.

2Regenerate Clean Index Manifest File:

Launch the game and start a New Game.

Save the game immediately in slot 1 and exit the game completely.

The game engine creates a fresh, healthy profile.sav / index.dat file.

3Restore Historical Slot Files:

Copy your original, intact save files (e.g., slot01.sav) from your Desktop backup back into the save folder, overwriting only the slot files while keeping the newly generated profile.sav intact.

4Launch game and verify that slots populate in the load menu.

Prevention & Long-Term Monitoring:

Maintain secondary copies of both slot files and profile index files during modded gameplay sessions.

Retrieving Virtualized Save Files from Windows VirtualStore

Solution:

Root Cause: Windows UAC Virtualization Redirection (VirtualStore)

Older games that attempt to write save data directly to administrative system directories (e.g., C:\Program Files (x86)\<GameName>) trigger Windows User Account Control (UAC) virtualization. Instead of writing to Program Files, Windows silently redirects save writes to a hidden user directory: %LOCALAPPDATA%\VirtualStore. If a system crash breaks UAC hooks or rights elevation, the game searches Program Files, fails to find save data, and reports missing saves.

Diagnostic Verification:

Check if the game is installed under C:\Program Files (x86)\.

Press Win + R, type %LOCALAPPDATA%\VirtualStore, and press Enter.

Step-by-Step Fix:

1Locate Redirected Saves in VirtualStore:

Navigate to %LOCALAPPDATA%\VirtualStore\Program Files (x86)\<GameDirectory>.

2Verify most recent save files exist in this directory.

3Fix Folder Permissions to Prevent Future Virtualization:

Right-click the game's main installation folder under Program Files (x86) > Properties > Security tab.

Click Edit > select Users > check Full Control > click Apply.

4Copy save files directly into the game's expected internal save folder or move the game installation outside Program Files (e.g., C:\Games\).

Prevention & Long-Term Monitoring:

Install legacy PC games outside restricted Windows system directories to avoid UAC virtualization conflicts.

Resetting ACL File Permissions and Controlled Folder Access Safeguards

Solution:

Root Cause: Windows Defender Controlled Folder Access and ACL Lockout

Windows Defender Controlled Folder Access or corrupted Access Control Lists (ACLs) prevent unauthorized apps from writing to %USERPROFILE%\Documents. When a game crashes during write operations, Windows security services may flag the crash event as a ransomware write anomaly, placing an administrative lock on the save directory and rendering save files invisible to the game engine process.

Diagnostic Verification:

Open Event Viewer > Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational.

Search for Event ID 1123 citing blocked access to Document save paths.

Step-by-Step Fix:

1Allow Game Executable in Controlled Folder Access:

Open Settings > Privacy & security > Windows Security > Virus & threat protection.

Click Manage ransomware protection > Allow an app through Controlled folder access.

Add the game's primary executable (.exe).

2Reset Folder ACL Permissions via PowerShell (Admin):

Open PowerShell as Administrator and execute:

icacls "$env:USERPROFILE\Documents\My Games" /reset /t /c
icacls "$env:USERPROFILE\Saved Games" /reset /t /c

3Restart PC and test save file loading.

Prevention & Long-Term Monitoring:

Whitelist custom game launchers and executable paths in Windows Security before launching heavily modded titles.

Relocating Mismatched SteamID / UserID Save Subdirectories

Solution:

Root Cause: SteamID / Platform Profile ID Directory Mismatch

Games distributed through digital platforms (Steam, Epic Games Store, Ubisoft Connect) store saves under user-specific subdirectories named after numeric platform IDs (e.g., C:\Program Files (x86)\Steam\userdata\<SteamID32>\<AppID>\remote). If a platform client update or crash logs you out or switches your account context, the game creates a new empty user ID directory and ignores historical save files sitting in the previous ID folder.

Diagnostic Verification:

Navigate to C:\Program Files (x86)\Steam\userdata\.

Notice multiple numeric folders corresponding to different Steam account IDs.

Step-by-Step Fix:

1Identify Active vs Historical Account Folders:

Open each numeric directory and check modified dates under target <AppID> folders.

2Locate Original Save Data:

Find the folder containing your historical, multi-megabyte save files.

3Copy Save Files to Active Profile Directory:

Copy intact save files from the old SteamID folder to the currently active SteamID folder.

4Relaunch Steam and the game.

Prevention & Long-Term Monitoring:

Note your 32-bit SteamID when managing multi-account gaming rigs to ensure saves are mapped correctly.

What error diagnostic or crash memory dump occurs when attempting to load the corrupted save slot?

Game crashes with Out-of-Memory (OOM) or Access Violation (`0xC0000005`) exception during save parsing.
Game hangs indefinitely due to corrupted physics/entity coordinates or corrupt script references.
Game crashes because installed mods or DLC references present in the save state are missing/corrupted.
Game crashes due to a corrupt DirectX / Vulkan shader cache generated during the crash event.

Fixing Access Violation (`0xC0000005`) Crashes via Save File Trimming

Solution:

Root Cause: Memory Buffer Overflow / Access Violation (`0xC0000005`) During Deserialization

An interrupted save write can write an invalid integer value into array bounds metadata (e.g., declaring an item inventory size of 99999999 items). When the game engine parses the save file on load, it attempts to allocate an absurdly large memory buffer, exceeding system RAM boundaries and triggering an immediate kernel Access Violation (0xC0000005) crash to desktop.

Diagnostic Verification:

Open Event Viewer > Windows Logs > Application.

Look for Error Event ID 1000 citing Faulting application name: <Game>.exe and Exception code: 0xc0000005.

Step-by-Step Fix:

1Download Dedicated Save Editor (if available for target game, e.g., Cyberpunk, Skyrim, Fallout, Borderlands).

2Open Corrupted Save File in Save Editor:

Inspect player status, inventory lists, and active quest buffers.

3Locate Corrupted Integers:

Look for overflow values (e.g., negative numbers, NaN, or extreme integers in item count or coordinate fields).

4Reset Values to Safe Defaults:

Reset inventory counts, clear corrupted pending quest flags, and save modified save file.

5Relaunch game and load corrected slot.

Prevention & Long-Term Monitoring:

For administrative guidance on configuring system crash dump collection, see the Microsoft Official Support Guide.

Resetting Out-of-Bounds Player Coordinates and Physics States

Solution:

Root Cause: Out-of-Bounds Entity Coordinates and Infinite Physics Loops

If a crash occurs while a player character is transitioning levels, falling, or clipping through geometry, the save file records invalid global floating-point vector coordinates (e.g., X: NaN, Y: NaN, Z: -999999). Upon loading, the physics engine attempts to resolve impossible collisions, locking the main execution thread into an infinite loop or hanging indefinitely on the loading screen.

Diagnostic Verification:

Game loading screen music continues playing, but progress bar freezes at 99% or 100% indefinitely.

Step-by-Step Fix:

1Edit Coordinates in Plain-Text / JSON Save Files:

Open save file in Notepad++ or Save Editor.

Search for player vector keys: PlayerPosition, Transform, or Location.

Replace corrupted coordinates (NaN or -999999) with known safe starting coordinates (e.g., X: 0.0, Y: 0.0, Z: 100.0 or starting town coordinates).

2Developer Console Teleport (If game allows loading console prior to render):

Enable developer console in game launch options (-console).

Command player position reset upon load initiation.

3Save file changes and reload.

Prevention & Long-Term Monitoring:

Avoid saving games manually while falling, clipping, or driving high-speed vehicles in open-world game engines.

Re-aligning Missing Mod Dependencies and Master File References

Solution:

Root Cause: Missing Load-Order Mod Dependencies / FormID Corruption

When games with extensive modding support (e.g., Bethesda Creation Engine titles, Witcher 3, Cyberpunk) crash, mod configuration managers (Vortex, Mod Organizer 2) can suffer load-order desynchronization. If a save file contains active pointers to modded items, scripts, or assets that are missing or re-ordered, the game engine crashes upon failing to locate required FormIDs.

Diagnostic Verification:

Open your mod manager (Vortex / MO2).

Check for missing master flags (.esm / .esp warnings) or mismatched load order indices.

Step-by-Step Fix:

1Restore Exact Mod Load Order:

In Mod Organizer 2 / Vortex, restore load order from saved profile backups.

2Purge Orphaned Script Instances via Save Cleaner:

For Creation Engine games, run a dedicated tool like Fallout4 / Skyrim Script Cleaner.

Load save file, select Fix Script Instances, and click Delete Unattached Instances.

3Resave Clean Save File and launch game.

Prevention & Long-Term Monitoring:

Never uninstall active script-heavy mods in the middle of a continuous gameplay play-through.

Purging Corrupted Shader Cache Databases and API Pipelines

Solution:

Root Cause: Corrupted Graphics Shader Compilation Cache

When a system crashes mid-game, compiled DirectX 12 or Vulkan pipeline state object (PSO) shader caches stored on disk become corrupted. When reloading the save, the engine attempts to load cached compiled shaders for the saved location, encounters corrupt binary fragments, and crashes to desktop before rendering the scene.

Diagnostic Verification:

Loading a save file in a small interior location works, but loading a save in a complex open-world scene crashes instantly.

Step-by-Step Fix:

1Clear GPU Vendor Shader Cache Directories:

NVIDIA: Navigate to %LOCALAPPDATA%\NVIDIA\DXCache and %LOCALAPPDATA%\NVIDIA\GLCache > delete all files.

AMD: Open AMD Software > Settings > Graphics > scroll down > click Perform Reset next to Shader Cache.

DirectX Global Cache: Press Win + R, type cleanmgr, select drive C:, check DirectX Shader Cache, and click OK.

2Clear Game Engine Shader Cache:

Navigate to %LOCALAPPDATA%\<GameName> or Documents folder and delete ShaderCache or .PSO folders.

3Relaunch game to force clean shader re-compilation.

Prevention & Long-Term Monitoring:

Clear DirectX shader caches following major GPU driver updates or game engine crashes.

What specific cloud platform synchronization conflict or error exists?

Steam Cloud reports 'Cloud Status: Sync Conflict' or overwrote local save files with older cloud files.
Epic Games Launcher Cloud Sync failed, leaving truncated files in local cache.
Xbox App / Windows Store Cloud Sync stuck at 'Syncing data...' percentage screen.
GOG Galaxy Cloud Backup replaced intact local saves with corrupted cloud snapshots.

Recovering Historical Save Versions from Steam Cloud Remote Storage

Solution:

Root Cause: Steam Cloud Automatic Overwrite of Truncated Save Payloads

When a game crashes, the corrupt 0 KB or malformed local save file is given a newer timestamp by the OS. Upon relaunching Steam, the Steam Cloud client compares file modification dates, assumes the local corrupted file is the desired state, and uploads it to cloud servers, overwriting intact cloud backups.

Diagnostic Verification:

Open a web browser and navigate to the official Steam Cloud Remote Storage portal: https://store.steampowered.com/account/remotestorage.

Step-by-Step Fix:

1Download Intact Saves from Steam Cloud Web Portal:

Navigate to https://store.steampowered.com/account/remotestorage.

Locate target game > click Show Files.

Review listed files and timestamps. Click Download next to historical, intact save files.

2Disable Steam Cloud Synchronization Temporarily:

Open Steam > right-click game in Library > Properties > General tab.

Toggle Keep game saves in the Steam Cloud for [Game] to OFF.

3Replace Local Corrupted Saves:

Copy downloaded files into the local save folder (C:\Program Files (x86)\Steam\userdata\<SteamID>\<AppID>\remote).

4Verify Gameplay and Re-enable Cloud Sync:

Launch game, confirm save loads correctly, exit game.

Re-enable Steam Cloud sync in Properties. Select Upload Local File if a conflict prompt appears.

Prevention & Long-Term Monitoring:

Disable cloud sync on unstable or heavily modded games to prevent automatic cloud contamination.

Restoring Local Manifests in Epic Games Launcher Cloud Sync

Solution:

Root Cause: Epic Games Launcher Local Manifest Staging Failure

The Epic Games Launcher manages cloud saves via local staging manifests located under %LOCALAPPDATA%\EpicGamesLauncher\Saved\Saves. A crash during shutdown corrupts these manifest files, causing the launcher to continuously download broken save revisions from cloud storage.

Diagnostic Verification:

Open Epic Games Launcher > check game card. Status reads *Cloud Sync Failure* or *File Conflict*.

Step-by-Step Fix:

1Disable Epic Cloud Saves:

Open Epic Games Launcher > click Profile Icon (top right) > Settings.

Uncheck Enable Cloud Saves.

2Purge Epic Launcher Cloud Cache:

Navigate to %LOCALAPPDATA%\EpicGamesLauncher\Saved and delete the webcache and Saves folders.

3Restore Local Save File:

Locate local save file under %USERPROFILE%\Documents or %LOCALAPPDATA%.

Swap with a .bak backup file as outlined in Node 202.

4Test game offline, then re-enable Cloud Saves in Epic settings.

Prevention & Long-Term Monitoring:

Maintain manual local backups of saves for games running via Epic Games Launcher.

Resetting Xbox App / Gaming Services Cloud Sync Containers

Solution:

Root Cause: Corrupted Windows Gaming Services Container Index

Games downloaded via Xbox App / Microsoft Store store save data inside restricted system containers under %LOCALAPPDATA%\Packages\<Publisher.Game>\SystemAppData\wgs. When a crash interrupts Microsoft Gaming Services, the container index file (containers.index) becomes corrupted, causing the Xbox app to hang infinitely at *Syncing data 0%*.

Diagnostic Verification:

Launching the game triggers an Xbox popup window stating *Syncing data...* that never completes or throws error 0x80830003.

Step-by-Step Fix:

1Reset Xbox Gaming Services App:

Open PowerShell as Administrator and execute:

Get-AppxPackage *GamingServices* | Reset-AppxPackage

2Clear Local WGS Container Cache:

Navigate to %LOCALAPPDATA%\Packages\<Publisher.GameName_hash>\SystemAppData.

Delete the wgs folder.

3Relaunch Game via Xbox App:

The Xbox App will re-query Microsoft cloud servers and re-download clean container metadata, restoring your cloud save state automatically.

Prevention & Long-Term Monitoring:

Ensure Windows Gaming Services app updates are set to automatic in the Microsoft Store.

Reverting GOG Galaxy Cloud Storage Snapshots

Solution:

Root Cause: GOG Galaxy Offline/Online State Desynchronization

GOG Galaxy maintains local cloud mirrors under C:\ProgramData\GOG.com\Galaxy\storage\cloud. When an offline crash occurs and GOG Galaxy reconnects, it flags local saves as outdated and forces an automatic overwrite from cloud servers.

Diagnostic Verification:

GOG Galaxy displays a notification: *Cloud save synchronization forced rollback*.

Step-by-Step Fix:

1Turn Off GOG Cloud Sync:

Open GOG Galaxy > select game > click Customization button (next to Play) > Manage installation > Configure....

Navigate to Features tab > uncheck Cloud saves.

2Access Local Storage Cache:

Navigate to C:\ProgramData\GOG.com\Galaxy\storage\cloud.

Locate historical save snapshots, copy them to the game's actual Document/AppData save folder.

3Verify gameplay load, then re-enable Cloud saves in GOG settings.

Prevention & Long-Term Monitoring:

Keep GOG Galaxy client updated to maintain stable cloud API handshakes.

Related Diagnostic Guides

System Interrupts High CPU Usage 100% Fix Tree

NVMe SSD Not Showing Full Speed In CrystalDiskMark: PCIe Lane Diagnostic

Windows 11 File Explorer Slow To Load Green Bar Fix

Mechanical Keyboard Some Keys Double Typing: Debounce Diagnostic

AirPods Connected to Windows But Sound Is Low Quality: Hands-Free Profile Fix

Subscribe to StepDiag

Embed Guide on Your Website