[2.0.72] Factorio keeps crashing after 30 min - 1 hour, even when paused

[SaltBlood]

I am on fulgora, I have all inner planets unlocked and I have gone to and more or less completed: nauvis, vulcanus, and fulgora (havent visited gleba yet).
For whatever reason my factorio keeps crashing in as far as i can tell the exact same way. I have attempted to remediate the issue uninstalling and reinstalling, and using the steam tool "verify integrity of game files".
This is a modded playthrough, but very lightly modded with only some visuals and aquilo freezing mechanics on all planets (Frozen Factory mod).
My best guess would be that something in either the save file or the data stored in C:\Users\"username"\AppData\Roaming\Factorio is corrupted.
I have attached my latest save file, and the last two crash logs.
The save playtime is 400 hours, and I did recently remove my computers C drive, plug it into another computer boot the computer off of my C drive, then put it back into my computer. I do not know if this is relevant, but I thought I would mention it.
If you would like me to attach any other information I would be happy to.
The full modlist (ordered by relevance) is as follows:
base 2.0.72
elevated rails 2.0.72
quality 2.0.72
space age 2.0.72

flib 0.16.5
frozen factory 0.1.1
nixie tubes 2.0.9
factory search 1.14.0
todo list 19.10.0
disco science 2.0.1
better starmap background 2.2.0
visible planets 1.7.0
exfret biter memoirs 1.2.0
honk 5.1.0

[Rseding91]

Thanks for the report. These two crashes are in unrelated pieces of code - both of which execute every single game tick 60 times per second.

That combined with the "after 30 minutes to 1 hour" makes me suspect failing/failed hardware. Most likely RAM but possibly the CPU. If you're overclocking either, try turning that off. Otherwise try running hardware tests and see if it finds anything.

[SaltBlood]

I am starting to suspect that my ram might not be fully seated, going to try reseating it. Thanks for the insight

[SaltBlood]

Ok after extensive stress testing it was most certainly poorly seated ram, thanks for the help!