Constant CTD during quicksave/load, now save seems broken - Resolved in hardware/BIOS.

[Darksurgeon]

7.10
Unmodified
Queens Herald Start
Kept getting CTD during quicksave/quickload. Updated graphics drivers. Tried reloading save, but not a single ship in the entire universe is moving. The CTD during quicksave and quickload has been an issue for me for a several weeks. I usually verify the game files through steam and it fixes it for a couple days then starts again.

https://filebin.net/oxpxll6gx2kg9r6z

Above link has dxdiag and vulkan info.

[CBJ]

That particular savegame is definitely corrupt, as ships not moving is a typical symptom of that.

Unfortunately it sounds you might be suffering from the known issue with Intel 13th and 14th generation CPUs, in which they cause themselves progressive damage and start having various problems with memory access. Before we jump straight to that conclusion, though, you might want to have a look at this possible issue which another player reported having managed to solve.

[Darksurgeon]

The potential solution you linked doesn't apply to me, but thanks. Is there any way we can absolutely confirm its the CPU? Are there any other possibilities?

[Darksurgeon]

Are there any issues with cloud saves? Was recommended by a steam user to disable them. haven't had a crash yet.

[Darksurgeon]

Never mind. I jinxed it. It just crashed when I tried to quick save, it also crashed when I tried to load back the save game. I have attached the .dmp files below for each instance, just in case that might help diagnose what's wrong.

https://filebin.net/9gzf6ztehhzdg8nw

[CBJ]

Both loading and saving place a particularly heavy load on memory access, which is where the 13th/14th generation Intel CPU problem manifests itself, so I'm afraid that's looking increasingly likely to be the cause. As usual with this issue, the crashdumps are a bit inconclusive; they point to code that couldn't really be expected to crash under any normal circumstances but don't give a clear indication of what actually went wrong.

Note that if the game crashed while saving then the savegame is almost certainly broken, so I don't think the load crash is surprising at all.

[Darksurgeon]

Both loading and saving place a particularly heavy load on memory access, which is where the 13th/14th generation Intel CPU problem manifests itself, so I'm afraid that's looking increasingly likely to be the cause. As usual with this issue, the crashdumps are a bit inconclusive; they point to code that couldn't really be expected to crash under any normal circumstances but don't give a clear indication of what actually went wrong.

Note that if the game crashed while saving then the savegame is almost certainly broken, so I don't think the load crash is surprising at all.

Update: You were right. I updated my MOBO to latest BIOS, then switched out my 14900 for a new one. No problems after 20+ hours. Thanks for your help.

[CBJ]

Good to know. Thanks for reporting back.