Hi there,
Since the 1.27 update, we've received increased reports of players crashing to desktop.
To investigate, we created a Discord channel where players could share their crash logs. We noticed that many reports end with the same error code: 0x7ff725ceba5e at 0xffffffffffffffff.
We have multiple crash logs from affected players showing this same error at the end of the crash log files, and we've also managed to obtain a mini dump. Hopefully, you can help us identify the issue.
Thanks!
mdmp
crash.log
rpt
crashreporter.log
Got a nice update on this!
I managed to replicate multiple client crashes, with the same error code in the crashlog file for multiple clients, in a row and recorded everything. This all happened today, so it's fresh. Hopefully it helps, please let us know if there's anything more we can do to address this issue. It's a major problem for us right now.
Crash 1
Me crashing to desktop.
https://youtu.be/uZPQdcA61GM
crashlog
Crash 2
Me crashing to desktop again.
https://youtu.be/QB2p5sq_Wew
crashlog
Crash 3
Video:
https://youtu.be/r-9Oft8hDfo
In this crash my friend Reu crashes. And the logs provided with the clips are the logs from him.
Reu's crashlog
Crash 4
Video:
https://youtu.be/l25yEl1_nLs
In this video, my friend Priesty crashes at the start, note how there is a pretty strong lag spike happening in the clip at the same time while he did.
Then further in the clip, my other friend Reu crashes again aswell a bit later at 0.26.
Priesty crashlog
Reu crashlog{F5001620}
Thank you for looking into this!
I will copy and paste what i found out:
What i can confirm so far regarding CLIENT crashes, its related to attitional spawned in items (for our server with Dayz Editor loader), reducing spawned in items will lower the risk of client crashes, so it think it has to do something regarding network and network bubbles, most related to networkRangeFar
Why was this ticket merged with https://feedback.bistudio.com/T189322 ? It looks like a completely different issue.