Here's the full message when trying to load the save file:
And in case the image dies, "Corrupt map: unknown asteroid-chunk protoype ID 37379. File has likely been corrupted due to failing hardware."
I am under the impression that this is a similar situation to other posts I've seen, where a single byte was corrupt, and the world might be recoverable.
What did you do?
I was playing factorio on a computer with failing RAM. At the time, I wasn't doing anything too unusual. My character was on nauvis, but I was working on a space platform for about an hour.
What happened?
Due to failing RAM, I imagine some byte corresponding to the ID of an asteroid chunk prototype was corrupted, and so the 3 auto saves as well as the manual save I made all included this corrupt asteroid chunk prototype, resulting in my world becoming unplayable.
What did you expect to happen instead?
At the time I was not aware of my computers failing RAM, so I was expecting my world to be fine when I saved it.
Does it always happen?
I'm going to say this is entirely un-repeatable. Well, attempting to load the world will consistently show this message, but the nature of how my world came into this state is likely not perfectly repeatable. Of course continuing to play with faulty RAM will result in similar issues, and future worlds will more than likely become unplayable as another byte is corrupt down the road. This isn't exactly the kind of issue that can be reproduced intentionally.
Log File
My most sincere apologies, as I think the log file has been overwritten with another log file since the date in which my world became corrupt. Granted, I don't think the log file would do much, given the nature of why my world is corrupt.
Further information
This was on a Space Age world, with quality and elevated rails. No other mods were installed or enabled.
This was on version 2.0.43. The world was corrupt a few months ago, and I recently figured it might be worth asking if it can be recovered.
This was on Windows 10, with DDR4 RAM.
I am getting new RAM, and in the meantime I'll be making more frequent backups.
Dropbox link to the corrupted save file:
link
And one of the autosaves too, for good measure.
Anyway, let me know if this truly is irrecoverable, or if it's a "single corrupt byte" situation. Thanks!
