Steps to reproduce
Start a local Sakhal server (vanilla mission, no mods, BattlEye off).
Connect with DayZDiag_x64.exe -connect=<host>:2402 -name=<profile>.
Spawn and look toward the centre of the map / let the nearby structures stream in.
Within roughly half a minute of being in world the client stops with no crash dialog.
Repeatability: 2 of 2 attempts crashed this way. The retail client (DayZ_x64.exe, same build, same machine) crashes the same way; Windows only records it as bad_module_info, 0xC0000005, so no user-side dump is possible there.
Crash data (from the minidump)
FieldValueExceptionEXCEPTION_ACCESS_VIOLATION (0xC0000005)OperationwriteFaulting address0x00007FF7B67C6998Faulting moduleDayZDiag_x64.exeModule base0x00007FF7B54D0000Offset in module+0x12F6998 (19,884,440 bytes)Access target0x000000EEA3000000 — invalid, no mappingThread0x2068DumpDayZDiag_x64.exe.10936.dmp, 71.5 MB, WER mini dump
The write target 0xEEA3000000 is not a mapped address; the upper bits look like a corrupted pointer rather than a legitimate object reference.