Sandustry Keeps Crashing: A Sorted Fix Path
Repeat crashes fall into a few buckets — old-build bugs, memory pressure, mod conflicts, and save damage. The fixes below are ordered by likelihood in week-one reports COMMUNITY.
1. Update Before Anything Else
v0.5.3 fixed a steam/rain simulation memory leak that caused long-session crashes, and v0.5.4 followed with a further hotfix COMMUNITY. If you're on an older build, this alone may be your fix. History in v0.5.3 / v0.5.4 Notes.
2. Read the Crash Log (It's Better Now)
Since v0.5.3, crash logs are much more detailed COMMUNITY. Find the log (Steam app 2764460 VERIFIED local files), read the last entry, and note whether the crash mentions memory, a GPU/overlay, or a mod assembly. That single word decides your next step.
3. Rule Out Memory & Weather Sim
The game's official minimum is 4GB RAM with a DX11-class GPU VERIFIED — but late-game saves with large weather-sim regions want more headroom COMMUNITY. If crashes happen during rain/steam or in late-game saves, shrink the sim area and cap save size (full checklist: Lag & Performance).
4. Disable Mods & Separate Saves
Mods built for an older build can crash on current builds COMMUNITY. Turn them off in the Fluxloader config, test vanilla, and keep modded saves separate from vanilla saves COMMUNITY. More in Install Mods.
5. If It Crashes at Launch, Not Mid-Game
A launch-time crash with an error dialog is a different problem: see Error 0xc0000142. A black screen at launch is also separate: Black Screen.
6. Report With Evidence
If the latest build still crashes, report on the official Discord with: build version, crash log, whether mods are on, and a screenshot of the moment it fails. v0.5.3's richer logs were added specifically to make this useful COMMUNITY.
Don't uninstall and reinstall first. For repeat crashes the order above resolves the overwhelming majority; reinstalling loses your logs and your mod config for nothing.