• Tracker

    Spaces
    Browse
    Statistics
  • /
  • /Stable Feedback
  • /DZG-2876
Back
1

DayZ crash report — Sakhal, write AV inside the engine (1.30.164289)

BugCrash
1

State

Open
Issue key
DZG-2876
Access
Public
Space
DayZ
Project
Stable Feedback
Creator
tjsneed88
Created
Nov 18, 2026
Views
4
Platform
PC Steam
What happened?

Sakhal: client crashes with a write access violation inside DayZ_x64.exe (+0x12F6998) while terrain/structures stream in — reproducible in vanilla, no mods, no BattlEye

Environment

  • DayZ build: 1.30.164289 (exe timestamp 2026/11/03)

  • OS: Windows 10 Pro 22H2, build 19045.6466

  • GPU: AMD Radeon RX 9070, driver 32.0.31041.1004 (Adreno/Adrenalin 26.x branch)

  • RAM: 32 GB, page file enabled

  • Terrain: Sakhal (dayzOffline.sakhal)

  • Mods: none (vanilla, clean mission, fresh storage)

  • BattlEye: disabled (BattlEye = 0;)

  • Server: local DayZDiag_x64.exe -server, client same build, forceSameBuild = 0

This was reproduced with the diagnostic build on purpose, because the retail client cannot be dumped.

Relation to existing reports

This looks like the same defect as DZG-1321 ("Client crash 0xC0000005 at constant address when many objects stream"), and is consistent with the direction-dependent Sakhal crash in DZG-1430.

Supporting details:

  • No crash_*.log and no .mdmp are written by the retail client; the RPT/error log simply stops. This matches DZG-1321.

  • Lowering Object Detail, Postprocess AA (FXAA off) and Object View Distance did not prevent it on the retail client.

  • No GPU TDR (no Event 4101), no WHEA entry, so this is not a driver timeout.

  • The crash also occurs with BattlEye disabled and with zero mods, so neither anti-cheat nor Workshop content is involved.

Attachments

A 71.5 MB minidump is available on request (too large for the tracker upload). The module offset above is the stable identifier; the absolute address only changes with ASLR.

Reproduction steps

Steps to reproduce

  1. Start a local Sakhal server (vanilla mission, no mods, BattlEye off).

  2. Connect with DayZDiag_x64.exe -connect=<host>:2402 -name=<profile>.

  3. Spawn and look toward the centre of the map / let the nearby structures stream in.

  4. 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.

Exact build version (optional)
—
Where did it happen?
Local / Offline
Is it modded?
No
Expected result
The client stays in world and keeps rendering while the Sakhal terrain and its
structures stream in. Looking toward the centre of the map must not interrupt
the session: no freeze, no termination, no truncated RPT/error log, and the
frame rate may dip but the game continues running. Repeating the same view has
to stay stable.
Public attachments1 file · visible to everyone

DayZDiag_x64_exe_10936.dmp

72 MB

Reactions

Activity

    25 minutes ago
  • tjsneed88
    created issue25 minutes ago

You are not signed in. Please sign in to see more details and to reply.

State

Open
Issue key
DZG-2876
Access
Public
Space
DayZ
Project
Stable Feedback
Creator
tjsneed88
Created
Nov 18, 2026
Views
4