#Game crashes shortly after starting run with X-olotl + Stinger weapon

1 messages · Page 1 of 1 (latest)

keen wigeon
#

Hey, I hopped back into this game just yesterday with a fresh save due to so much new stuff having been added. I played for several hours, with the initial character and Ersa, and then unlocked my third character, X-olotl (hope I'm pronouncing that right - the one that clones itself) - And I also unlocked the Stinger weapon (not sure the exact name, but the third one anyway).

So I picked this new character, and that weapon and started a run in Frozen Pond. About a minute or so, my game crashes. I booted the game up again, and started another run with the same character and weapon, and this time the game crashed in less than 20 seconds (IIRC).

I checked AppData and I have the two crashes under the Crashes folder, with CrashContext.runtime-xml, CrashReportClient.ini and UEMinidump.dmp in each folder. I have enabled the option of sharing data, so I think these have already been sent to you guys, but I'm still reporting this, as it's actively preventing me from playing the game.. I'll upload the memory dumps and crashcontext files from the two crashes here, I think that should be all the info needed? (Note: I prefixed each file with "Crash1-" and "Crash2-")

past breach
#

Hi @keen wigeon , We’re really sorry to hear you’re running into a crash. We totally understand how frustrating that can be — especially when you’re excited to jump back into the game 🙇

Thanks a lot for the info you’ve already shared, that really helps! Could you please compress each of the crash folders into ZIP files so we can take a closer look?

Also, if you’re able to reproduce the issue, it would be super helpful if you could record a short video of it happening and share it here in the thread. Thanks in advance 😉

keen wigeon
keen wigeon
#

Actually the upload limit seems to be 100mb due to boosted server, so I cranked all the framerates and everything down to record, here you are.. The error message is always the same. AMD gives it's own error notification, and another popup about driver timeout.

Note that this only happens with this character (not sure if it's the weapon combination, I haven't tested other weapons, but anyway, here's what you requested) - I can reproduce it every single time, as even now I had to record twice, as the first crash took a bit over a minute and my bitrate was a bit higher, so the recording ended up a bit over 100mb, over the limit, so I had to go crash again, and this time it happened much faster.

keen wigeon
#

If the crash reports don't point out anything obvious, let me know if you want me to try some things like another weapon, another level, etc. - I will test it out once I get around to it. As for now, I will sadly have to avoid this character. That way, perhaps I will encounter a similar crash under other circumstances, which will shed some more light on the issue.