Hello,
To be honest, an AI analyzed this for me. Unfortunately, I'm at a loss. The servers are crashing unexpectedly (without any players) and sometimes multiple times in a row.

Please take a look at my log files; perhaps you'll see something.

I'm very grateful for any help.

---

I am experiencing recurring dedicated server crashes with DayZ 1.29.163451.

The crashes occur during normal dedicated server operation and are difficult to reproduce manually.

Environment

• Windows Server 2022 Standard (64-bit)

• Intel Core i9-14900K

• 128 GB RAM

• Samsung NVMe SSD

I have two independent server instances managed by CFTools Architect, running on a dedicated machine.

Server A - Main Server (88 Mods)

Server B - Test Server (4 Mods)

Both servers crashed independently, sometimes only minutes apart.
I previously reproduced a very similar crash on a separate vanilla Chernarus dedicated server started directly from Steam without mods and without CFTools Architect. Unfortunately, I no longer have the corresponding log files or dump, so I cannot attach independent evidence for that test.

Hardware / System verification

To rule out hardware or operating system problems I performed the following checks:

• Windows Memory Diagnostic → pass

• CHKDSK → no filesystem errors

• SSD SMART status → Healthy

• No WHEA hardware errors

• No hardware-related Windows Event Viewer errors

WinDbg analysis

I analyzed four different crash dumps using WinDbg.

The results are nearly identical.

Common crash signature

• Exception:
  0xC0000005 (Access Violation)

• Failure Bucket:
  INVALID_POINTER_READ_c0000005_DayZServer_x64.exe

• Module:
  DayZServer_x64.exe

• Version:
  1.29.163.451

• Crash Offset:
  DayZServer_x64 +0x2E0E72
  (one dump stops one instruction later at +0x2E0E7B)

• Failure Hash:
  {fa0a711d-8818-27cc-25ee-09a3efe341d0}

The crashing instruction is:
mov rdx, qword ptr [rax+40h]

In multiple dumps:
RAX = 0x0000000000000001

which causes the server to dereference memory address:
0x41

Another dump reaches the next instruction:
mov r10, qword ptr [rdx+B0h]

where RDX already contains an invalid pointer.

The crash location is otherwise identical.

Additional observations

The crashes from both dedicated server instances show:

• identical exception type

• identical failure bucket

• identical failure hash

• identical instruction sequence

• identical crash location inside DayZServer_x64.exe

This suggests that both server instances reach the same native engine code path before crashing.

I cannot determine whether this is caused by the engine itself or by a specific sequence of game events, but the consistency of the crash signature across multiple independent dumps is notable.

Actual result

The dedicated server terminates with an Access Violation (0xC0000005) inside DayZServer_x64.exe.

Attachments

Attached:

• 4 crash dumps (.mdmp)

• 4 WinDbg analysis logs

• corresponding crash logs

• corresponding RPT logs

If additional information or further debugging is required, I will gladly provide it.

Thank you.
Best regards, Chris

1. Start a dedicated DayZ Server

2. Load the mission normally.

3. Let the server run during normal gameplay.

4. The crash occurs randomly after a variable amount of uptime (from approximately 1 minute up to several hours).

5. This also happens when there are no players on the server.

6. The issue has been observed on two independent dedicated server instances.

Frequency:

The problem occurs sporadically and then repeatedly.
Please take a look at the image showing the crash times.

A server with no players and 4 mods crashed 39 times last night.
I reinstalled CF Architect yesterday and rebuilt the DayZ servers - it didn't help.

The dedicated server should continue running normally without crashing.