This post is incomplete, but aims to start providing information about what's happening.
Hello,
Since the release of 1.25 some customers are experiencing severe crashes on their DayZ servers (modded) that they didn't have before. So far, I've just started work to try to debug the situation.
For the moment, I'm starting work with this error produced in a crashlog:
Client 1 :
WIN-UTOF1UC2OFH, 28.05 2024 13:50:14 Unhandled exception Program: C:\TCAFiles\Users\****\54\DayZServer_x64.exe Reason: Access violation. Illegal read by 0x7ff76f6a16b8 at 0x50 SymGetSymFromAddr:487, addr:0x7ff76f6a16b8 SymGetSymFromAddr:487, addr:0x7ff76f6a029a SymGetSymFromAddr:487, addr:0x7ff76f6a0189 SymGetSymFromAddr:487, addr:0x7ff76f69fd91 SymGetSymFromAddr:487, addr:0x7ff76f6a52d3 SymGetSymFromAddr:487, addr:0x7ff76f6a5020 SymGetSymFromAddr:487, addr:0x7ff76f3af9db SymGetSymFromAddr:487, addr:0x7ff76f3b6222 [CDPCreateServer]: ??? addr:0x7ff76fb1acdd [CDPCreateServer]: ??? addr:0x7ff76fc78326 [CDPCreateServer]: ??? addr:0x7ff76fc6f584 [CDPCreateServer]: ??? addr:0x7ff76fc71a99 SymGetSymFromAddr:487, addr:0x7ff76f6eb7dd [CDPCreateServer]: ??? addr:0x7ff76fc7958c SymGetSymFromAddr:487, addr:0x7ff76f800c3b [CDPCreateServer]: ??? addr:0x7ff76fdc99e2 [BaseThreadInitThunk]: ??? addr:0x7ffbfc304de0 [RtlUserThreadStart]: ??? addr:0x7ffbfd4fed9b [RtlUserThreadStart]: ??? addr:0x7ffbfd4fed9b
Client 2 :
WIN-43417R2VOB5, 28.05 2024 13:45:48 Unhandled exception Program: C:\TCAFiles\Users\*****\61 - Copie\DayZServer_x64.exe Reason: Access violation. Illegal write by 0x7ff68af04060 at 0x0 SymGetSymFromAddr:487, addr:0x7ff68af04060 [CDPCreateServer]: ??? addr:0x7ff68b555985 SymGetSymFromAddr:487, addr:0x7ff68af10e2a SymGetSymFromAddr:487, addr:0x7ff68af10e69 [BaseThreadInitThunk]: ??? addr:0x7ffeab5b4de0 [RtlUserThreadStart]: ??? addr:0x7ffeac1bed9b [RtlUserThreadStart]: ??? addr:0x7ffeac1bed9b
The crash does not produce an .mdmp and DayZServer_x64.exe does not stop running. This causes the server to freeze until manual action is taken.
I'm going to continue working on this on my side to glean more information, hopefully solve the problem for the customers concerned and provide you with more ways to reproduce the problem.
Best regards