Page 1 of 1

[2.0.66] Crash and save corruption "HeatBufferPrototype: long-handed-inserter got bad index"

Posted: Fri Sep 19, 2025 7:31 pm
by koyuze
Playing space age with no mods (besides quality and elevated rails)

The initial crash left me with this message

12352.696 Error HeatBufferPrototype.cpp:172: long-handed-inserter at {185.500, -18.500} got bad index: 761970
12352.696 Error CrashHandler.cpp:643: Received 22

after restarting the game I found that all my auto saves were corrupted as well as my main save.
the message said
52.999 Warning Map.cpp:364: Map loading failed: Corrupt map: unknown quality prototype ID 255. File has likely been corrupted due to failing hardware.
53.228 Error AppManagerStates.cpp:1662: Corrupt map: unknown quality prototype ID 255. File has likely been corrupted due to failing hardware.

and trying the other save files this message came up
63.919 Warning Map.cpp:364: Map loading failed: Invalid bool loaded from input file. File has likely been corrupted due to failing hardware.
64.171 Error AppManagerStates.cpp:1662: Invalid bool loaded from input file. File has likely been corrupted due to failing hardware.

I ran a diagnostic on my computers memory but the system found no issues with my ram.
computer specs:
Windows 10
intel i7-7700
GeForce RTX 2060 12gb
Samsung SSD 870 EVO 2TB
Corsair Vengeance RGB Pro DDR4 3600 16gb (have 4 of these)

Not sure how to repeat crash or corruption. I would like help in identifying if the issue is with my hardware or drivers because I don't want to lose saves to this problem again.

Re: [2.0.66] Crash and save corruption "HeatBufferPrototype: long-handed-inserter got bad index"

Posted: Fri Sep 19, 2025 8:41 pm
by Rseding91
Save corruption like this has virtually always been traced to bad hardware: most commonly failing RAM but also sometimes failing CPUs.

Factorio is not tolerant of failing hardware because it expects things to be correct and failing hardware scrambles things.

I suggest running a memory test, but letting it run longer. And if you’re overclocking your RAM (XMP or equivalent) try disabling that.