Factorio Forums

**Factorio version:** 2.0.43 (Steam)

**Summary:**
The game sometimes crashes during autosave. Upon restarting and reloading the same save, the game works normally for 30–60 minutes, but eventually crashes again — typically during another autosave.

The error appears to be related to a corrupted `spitter-spawner` entity that has mismatched chunk registration.

**Error log:**
Error UpdatableEntity.cpp:125: updatable entity [name=spitter-spawner, type=unit-spawner(EnemySpawner), position={4.188, 6.813}, ...] should be active on chunk [0, 0] but is active on chunk [60, -45]

**Details:**
- The entity exists physically in chunk `[0, 0]`, but the engine believes it is active in `[60, -45]`.
- When the game tries to update this entity (especially during autosaves or world updates), it crashes.
- Attempting to remove the entity via console (`e.destroy()` or `delete_chunk`) also causes a crash.
- Even putting cleanup code in `script.on_init()` does not help, as the game crashes before Lua logic is even executed.

**Reproduction:**
- Load the attached save.
- Wait 30–60 minutes for an autosave (or play actively).
- Game eventually crashes.
- Restarting the game and reloading works — but the crash will repeat later.

**Attachments:**
- factorio-current.log (from the crash)
- Save file (.zip)

**Mods:**
- space-age
- helmod
- quality
- flib
- rate-calculator
(etc... extracted from save file, let me know if needed in detail)

**Expected behavior:**
- Game should be able to ignore or clean up the corrupted entity gracefully.
- Alternatively, provide a tool or console command to forcibly clear broken entities like this.

Please advise if the save can be fixed manually or if the corruption is fatal. Thank you!

Those are independent issues, this is a hardware problem. If you have not already, update your bios for the raptor lake defect.

Thanks for the advice, updating the BIOS really helped, not a single crash in 3 days