SatisfactorySatisfactory Dedicated Server Keeps Crashing? Causes and Fixes
Satisfactory server crashing on load, mid session or in a restart loop? Read FactoryGame.log, then fix memory, mods, versions or a damaged save.
Updated Oct 7, 2026 · 5 min read
On this page
A Satisfactory dedicated server that keeps crashing is usually running out of memory as the factory grows, running mods that do not match the game version, or loading a damaged or newer save. The server log, FactoryGame/Saved/Logs/FactoryGame.log, names which one in its last lines. Big late game factories need far more RAM than a fresh save, so a server that ran fine for weeks can start crashing without anything else changing.
Step 1: Read the log and crash reports
Look in the server's FactoryGame/Saved/ folder:
| File or folder | What it tells you |
|---|---|
Logs/FactoryGame.log |
The current session. The last lines show what happened just before the crash |
Logs/FactoryGame-backup-<date>.log |
Previous sessions, useful when the server already restarted |
Crashes/ |
Crash reports with a call stack, when the engine managed to write one |
Search the log for Fatal error, Out of memory, Assertion failed and the names of any mods. Note the time of the crash and what players were doing: loading in, placing a blueprint, an autosave, driving a train.
Cause 1: Out of memory
This is the most common cause on long running servers. Memory use grows with the size of the factory: every machine, belt, pipe and train is simulated on the server. Signs:
- The crash happens during load or during an autosave.
- The log mentions running out of memory, or simply stops with no error.
- The host shows memory at its limit just before the crash.
What helps:
- More RAM. Early game saves run comfortably on modest memory, while late game megafactories need much more. The requirements guide has figures by factory size.
- Fewer things to simulate. Remove abandoned test builds, huge belts of items nobody uses, and piles of items left on the ground.
- Regular restarts. A daily restart releases memory that builds up over long sessions.
Cause 2: Mods that do not match
Mods installed with Satisfactory Mod Manager must match the game version, the mod loader version, and the mods on every player's game. After a game update, most mods need an update before they load again, and an outdated mod can crash the server at start.
- Stop the server.
- Move the server's
FactoryGame/Modsfolder somewhere else. - Start the server without mods.
If it starts, add mods back once each has an update for the current game version, starting with the mod loader. Keep server and player mod lists identical. The mods guide covers installing them on a server.
Cause 3: Version and branch mismatch
The server and the save must agree on the game version:
- A save from a newer version will not load on an older server. If someone played the save on the experimental branch, or on an updated PC before the server updated, update the server.
- Experimental and stable are separate. A server on stable cannot load saves made on experimental, and players on one branch cannot join a server on the other. Pick one branch for everyone.
Update the server first, then load the save. The update guide covers the routine.
Cause 4: A damaged save
A crash during an autosave, a full disk or an interrupted upload can leave a save that crashes the server every time it loads. That gives a restart loop: the server starts, loads the session, crashes, and starts again.
Break the loop by loading an earlier save:
- Stop the server so it does not keep restarting.
- Download the save folder as a backup.
- Load the autosave from before the problem, as shown in loading an older autosave.
If every save in the session crashes, the problem is probably not the save. Go back to memory and mods.
Cause 5: Broken server files
After an interrupted update, files can be missing or damaged. Validate the install:
steamcmd +login anonymous +app_update 1690800 validate +quit
1690800 is the Satisfactory Dedicated Server app. On a GamezServers server, type 1 in Repair files on start and restart once. It is slow, so turn it off again afterwards.
Cause 6: Disk full
Saves grow with the factory, and logs and old crash reports pile up. When the disk is full, autosaves fail and the server can crash or write broken saves. Delete old logs and crash reports, and keep a few gigabytes free.
Crashes only at certain moments
| When it crashes | Look at |
|---|---|
| Every autosave | Memory, disk space, save size |
| When a player joins | That player's mods and game version, network timeouts |
| When placing a blueprint | Very large blueprints, mods that add buildables |
| At random after hours | Memory growth, restart the server daily |
Stable hosting for a big factory
On a GamezServers Satisfactory server, you can move up to a bigger plan as the factory grows without losing anything (plan changes are prorated), the log and crash folders are in the file manager, repair runs from a panel setting, and one click backups keep a restore point outside the rotating autosaves. Update on start keeps the server on the same version as players. See Satisfactory server hosting for plans.
FAQ
Where are the Satisfactory server logs?
In FactoryGame/Saved/Logs/ on the server. FactoryGame.log is the current session, and older sessions have dated backup files.
Why does my Satisfactory server crash when loading the save?
Usually not enough memory for the factory's size, outdated mods, or a save from a newer game version. Check the end of the log.
Can a single save keep crashing the server?
Yes, if it was damaged during an autosave. Load an earlier autosave or a backup to break the restart loop.
How much RAM does a late game Satisfactory server need?
Much more than an early save. Check the requirements guide for figures and watch memory use as your factory grows.
Skip the setup. Your own Satisfactory server.
Then $19.99/mo. Just trying it? $5.00 for 3 days