[1.0.0] Crashed twice, no stack trace
Posted: Sun Sep 13, 2020 7:23 pm
Hi,
My game crashed twice today. I think both time, I had a temporary blueprint (from Ctrl+V) in hand, although I'm not 100% sure about the first time. I didn't think much about the first time, assuming the devs could take a look at the automated crash report, so I didn't save the log file.
I did overclock my memory a bit yesterday (going from 3600MHz to 3733MHz with the same CL timings), but it had no issues passing a memory test which I left running for about 2.5 hours. That was long enough to do 1 pass and a half. I plan on doing another memory test for the full night, just in case and I will report the result here tomorrow. I should note that I didn't experience any crash or unexpected behavior with other software running on my computer (mainly Chrome, Steam and Spotify).
Here is the save file, in case it can help: https://drive.google.com/file/d/1AZet6Y ... sp=sharing. The only thing that might not be super common is the relatively heavy use of signals and circuitry to force the train pathfinding to do better stuff.
I'm only using 2 mods (Power Grid Comb and Dynamic Construction Queue), but I doubt they would be the cause of the crash.
I managed to find the two coredump files, but they seem to be truncated to 2GB (from ~8GB and ~5.7GB) and I cannot get a backtrace from any thread ("Cannot access memory at address ...), so I'm not sure if these files could be useful in any way.
Please let me know if there is anything I can to do help debug this.
My game crashed twice today. I think both time, I had a temporary blueprint (from Ctrl+V) in hand, although I'm not 100% sure about the first time. I didn't think much about the first time, assuming the devs could take a look at the automated crash report, so I didn't save the log file.
I did overclock my memory a bit yesterday (going from 3600MHz to 3733MHz with the same CL timings), but it had no issues passing a memory test which I left running for about 2.5 hours. That was long enough to do 1 pass and a half. I plan on doing another memory test for the full night, just in case and I will report the result here tomorrow. I should note that I didn't experience any crash or unexpected behavior with other software running on my computer (mainly Chrome, Steam and Spotify).
Here is the save file, in case it can help: https://drive.google.com/file/d/1AZet6Y ... sp=sharing. The only thing that might not be super common is the relatively heavy use of signals and circuitry to force the train pathfinding to do better stuff.
I'm only using 2 mods (Power Grid Comb and Dynamic Construction Queue), but I doubt they would be the cause of the crash.
I managed to find the two coredump files, but they seem to be truncated to 2GB (from ~8GB and ~5.7GB) and I cannot get a backtrace from any thread ("Cannot access memory at address ...), so I'm not sure if these files could be useful in any way.
Please let me know if there is anything I can to do help debug this.