[2.0.72] Crash loading 2.0.43-3 save "entity->isSetup() was not true"

[Shambala]

Decided to return to Factorio after a break, but my 183-hour save does not load.

11-28-2025, 19-09-55.png (104.01 KiB) Viewed 546 times

Modes listed (I think these are not even mods?) No clue where to start.

Crash log attached.
Save file attached. (If you open it, don't judge me okay?)

[eugenekay]

Since this is a Crash-to-Desktop (not just an Error) it should be placed in the Bug Reports area. The crash occurs with intermediate "Stable" version 2.0.47 or later; reverting all the way back to 2.0.43 allows it to Load. The Space Age expansion is packaged as "Official Mods" to allow you to en/disable it easily, or play a Classic game with Quality / Elevated Rail without the full multi-planet experience.

Factorio crashed. Generating symbolized stacktrace, please wait ...
C:\Users\build\AppData\Local\Temp\factorio-build-FWjsjC\src\Util\ReleaseAssert.cpp(7): ReleaseAssertFailed
C:\Users\build\AppData\Local\Temp\factorio-build-FWjsjC\src\Surface\Surface.cpp(143): Surface::checkConsistency
C:\Users\build\AppData\Local\Temp\factorio-build-FWjsjC\src\Map\Map.cpp(1827): Map::checkConsistency
C:\Users\build\AppData\Local\Temp\factorio-build-FWjsjC\src\Map\MapSetupHelper.cpp(191): MapSetupHelper::MapSetupHelper
C:\Users\build\AppData\Local\Temp\factorio-build-FWjsjC\src\Map\Map.cpp(866): Map::setupEntities
C:\Users\build\AppData\Local\Temp\factorio-build-FWjsjC\src\Scenario\Scenario.cpp(294): Scenario::loadFactory
C:\Users\build\AppData\Local\Temp\factorio-build-FWjsjC\src\Scenario\ParallelScenarioLoader.cpp(190): ParallelScenarioLoader::doLoad
C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30133\include\thread(56): std::thread::_Invoke<std::tuple<void (__cdecl*)(MapInterface,ParallelScenarioLoader *,MapDeserialiser *,enum InputType,InputSource *,MultiplayerManagerBase *,NamedBool<EnableReplayTag>),MapInterface,ParallelScenarioLoader *,MapDeserialiser *,enum InputType,InputSource *,MultiplayerManagerBase *,enum NamedBool<EnableReplayTag>::Enum>,0,1,2,3,4,5,6,7>
minkernel\crts\ucrt\src\appcrt\startup\thread.cpp(97): thread_start<unsigned int (__cdecl*)(void *),1>
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFC8FBEE8D7)
00007FFC8FBEE8D7 (KERNEL32): (filename not available): BaseThreadInitThunk
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFC91BAC53C)
00007FFC91BAC53C (ntdll): (filename not available): RtlUserThreadStart
Stack trace logging done
55.877 Error Surface.cpp:143: entity->isSetup() was not true

The crash occurs inside of Surface.cpp, which implies that there is a Consistency Issue with loading one of the Surfaces. I used /editor mode to delete Surfaces one-by-one to try to narrow down the issue; unfortunately it seems that Nauvis is the source of the issue (which is an un-delete-able Surface). Using a console command I was able to narrow the issue to the North-East section of the Map, and then to an area near Position X=384, Y=-480 / Chunk X=12, Y=-16. The only player-created entity here is a Large Power Pole, which does not seem to be the source of the issue. It is possibly a Corrupt Map decorative entity or Resource Patch?

11-29-2025, 12-26-01.png (1.18 MiB) Viewed 471 times

After Deleting + Regenerating this Chunk the attached save file loads in Version 2.0.72.
/c local surface = game.player.surface; game.player.force.cancel_charting(surface); for chunk in surface.get_chunks() do if (chunk.x == 12 and chunk.y == -16) then surface.delete_chunk(chunk) end end

As with all suspected-data-corruptions, you should run Memtest86 to check for Memory corruption in your system.

Good Luck!

[Loewchen]

It can stay in Technical help for now. If you find a way to reliably corrupt new saves let us know, but so far this is just one save file with that corruption.

[eugenekay]

The suggested "Bug" is not that the Corruption exists to begin with (which is indeed difficult or impossible to reproduce); but the fact that the game Crashes to Desktop instead of Erroring when loading the bad Map data due to a faulty Assert. Eg, the save from 131754 produces a "Corrupt map" Notice:

11-29-2025, 21-37-49.png (18.96 KiB) Viewed 412 times

[Shambala]

First of all, thank you for the help — I really appreciate the time and effort you put into fixing my save. (There were problems with RAM indeed)

I was wondering if there might be any way to resolve the issue without permanently disabling achievements. It's not the end of the world, but it is a bit frustrating, so I wanted to ask in case there's another option I'm missing.