• Tracker

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

[CRITICAL PS4] Nasdara – Repeated C0000005 ACCESS_VIOLATION / ENGINE LEVEL Server Crash Loop – v1.30.164200

GeneralCrashErrorServerClient
1

State

Open
Issue key
DZG-1992
Access
Public
Space
DayZ
Project
Stable Feedback
Creator
imonthefloor
Created
Oct 25, 2026
Views
4
Platform
Playstation
What happened?

Issue Summary

Dedicated DayZ PS4 server running dayzOffline.nasdara began repeatedly crashing with the same native engine exception:

C0000005 ACCESS_VIOLATION at 01B52209

A total of 27 crashes were recorded between 23 October 2026 and 24 October 2026.

All 27 crashes report the same exception code and fault address.

Crash List

  1. DayZServer_PS4_x64_2026-10-23_15-52-38.RPT — Crash: 18:03:19.477

  2. DayZServer_PS4_x64_2026-10-23_18-06-33.RPT — Crash: 20:17:15.392

  3. DayZServer_PS4_x64_2026-10-23_20-20-41.RPT — Crash: 22:31:25.520

  4. DayZServer_PS4_x64_2026-10-23_22-34-22.RPT — Crash: 00:45:05.421

  5. DayZServer_PS4_x64_2026-10-24_00-47-53.RPT — Crash: 02:58:29.441

  6. DayZServer_PS4_x64_2026-10-24_03-01-54.RPT — Crash: 05:12:14.660

  7. DayZServer_PS4_x64_2026-10-24_05-14-52.RPT — Crash: 05:22:36.798

  8. DayZServer_PS4_x64_2026-10-24_05-25-27.RPT — Crash: 05:26:15.942

  9. DayZServer_PS4_x64_2026-10-24_05-28-57.RPT — Crash: 05:29:49.414

  10. DayZServer_PS4_x64_2026-10-24_05-32-21.RPT — Crash: 05:33:10.965

  11. DayZServer_PS4_x64_2026-10-24_05-36-27.RPT — Crash: 05:37:16.816

  12. DayZServer_PS4_x64_2026-10-24_05-39-51.RPT — Crash: 05:40:43.138

  13. DayZServer_PS4_x64_2026-10-24_05-45-07.RPT — Crash: 05:45:59.940

  14. DayZServer_PS4_x64_2026-10-24_05-48-59.RPT — Crash: 05:49:49.685

  15. DayZServer_PS4_x64_2026-10-24_06-08-42.RPT — Crash: 06:09:35.236

  16. DayZServer_PS4_x64_2026-10-24_06-13-01.RPT — Crash: 06:13:54.860

  17. DayZServer_PS4_x64_2026-10-24_06-17-00.RPT — Crash: 06:17:51.340

  18. DayZServer_PS4_x64_2026-10-24_06-20-37.RPT — Crash: 06:21:26.871

  19. DayZServer_PS4_x64_2026-10-24_06-24-29.RPT — Crash: 06:25:21.582

  20. DayZServer_PS4_x64_2026-10-24_06-27-55.RPT — Crash: 06:28:44.788

  21. DayZServer_PS4_x64_2026-10-24_06-33-37.RPT — Crash: 06:34:29.421

  22. DayZServer_PS4_x64_2026-10-24_06-37-16.RPT — Crash: 06:38:06.600

  23. DayZServer_PS4_x64_2026-10-24_06-41-29.RPT — Crash: 06:42:18.667

  24. DayZServer_PS4_x64_2026-10-24_06-45-09.RPT — Crash: 06:46:00.667

  25. DayZServer_PS4_x64_2026-10-24_06-49-13.RPT — Crash: 06:50:05.239

  26. DayZServer_PS4_x64_2026-10-24_06-53-47.RPT — Crash: 06:54:37.664

  27. DayZServer_PS4_x64_2026-10-24_06-57-50.RPT — Crash: 06:58:41.573

Common Crash Signature

Every occurrence reports:

ENGINE (F): Crashed

Exception code: C0000005 ACCESS_VIOLATION at 01B52209

Allocator: system

graphics: No

Behaviour / Timeline

There appears to be a clear transition in behaviour.

The first six server instances were able to run for approximately the normal scheduled restart interval before the C0000005 occurred.

After the crash at approximately 05:12 on 24 October, the behaviour changed.

The server started at approximately 05:14:52 and crashed at 05:22:36.

From the 05:25:27 startup onward, the server entered a repeated startup crash loop. Most subsequent instances terminated approximately 50–55 seconds after startup.

The exception remained identical throughout both behaviours:

C0000005 ACCESS_VIOLATION at 01B52209

Persistence Errors Observed

During the affected period, CE also reported failures reading several persistence generations:

storage_20026027\data\dynamic_009.001

storage_20026027\data\dynamic_009.002

storage_20026027\data\building_003.002

Example:

!!! [CE][Storage] Failed to read [Storage] data file "...storage_20026027\data\dynamic_009.001".

However, subsequent RPT output shows CE successfully restoring alternative generations of the affected persistence stores, so it is currently unknown whether these storage errors are a cause, consequence, or unrelated symptom of the crashes.

Additional Observation

During the later startup crash loop, CE progresses through persistence restoration and event/spawner initialization.

Repeated affected startups reach:

[31] VehicleSedan02

[32] VehicleTruck01

[CE][Hive] :: Initializing of spawners done.

The process then terminates with:

ENGINE (F): Crashed

Exception code: C0000005 ACCESS_VIOLATION at 01B52209

No Enforce Script call stack identifying the source of the native access violation is provided.

Additional Script Errors

The logs also contain repeated EffectAreaLoader CreateZones warnings:

[WARNING] :: [EffectAreaLoader CreateZones] :: Cast failed, are you sure your class ( 'Type:' ) inherits from EffectArea and that there are no Typos?

Stack:

scripts/1_Core/proto/endebug.c:92 Function Error

scripts/4_World/classes/contaminatedarea/contaminatedarealoader.c:102 Function CreateZones

scripts/5_Mission/mission/missionserver.c:104 Function OnMissionStart

These errors are included for completeness; I have not established that they are responsible for the native C0000005 crash.

Platform / Mission

Platform: PlayStation / PS4 server executable

Executable shown in logs: DayZServer_PS4_x64

Mission: dayzOffline.nasdara

Map: Nasdara / Badlands

DayZ version: 1.30

Attachments Available

I can provide the complete RPT set covering all 27 crashes, associated script logs, current dayzOffline.nasdara mission files, and persistence/error diagnostics if required.

25.10 2026 02:26:57
Unhandled exception
Program: C:\SERVICES\ni6607389_2_local\dayzps\DayZServer_PS4_x64.exe
Reason: Access violation. Illegal read by 0x7ff70fec2209 at 0x0
SymGetSymFromAddr:487, addr:0x7ff70fec2209
[CDPInitServer]: ??? addr:0x7ff710180e6c
SymGetSymFromAddr:487, addr:0x7ff70fef4404
SymGetSymFromAddr:487, addr:0x7ff70fbced99
SymGetSymFromAddr:487, addr:0x7ff70fa6b7ad
SymGetSymFromAddr:487, addr:0x7ff70fd42b26
SymGetSymFromAddr:487, addr:0x7ff70fe0e0a2
SymGetSymFromAddr:487, addr:0x7ff70fe09bc2
SymGetSymFromAddr:487, addr:0x7ff70fe09615
SymGetSymFromAddr:487, addr:0x7ff70fe095fa
SymGetSymFromAddr:487, addr:0x7ff70fe095fa
SymGetSymFromAddr:487, addr:0x7ff70fe095fa
SymGetSymFromAddr:487, addr:0x7ff70fe095fa
SymGetSymFromAddr:487, addr:0x7ff70fe1733e
SymGetSymFromAddr:487, addr:0x7ff70fe0dfdb
SymGetSymFromAddr:487, addr:0x7ff70fd2e3f5
SymGetSymFromAddr:487, addr:0x7ff70fd2f79e
[CDPInitServer]: ??? addr:0x7ff71024d205
SymGetSymFromAddr:487, addr:0x7ff70fdf466a
SymGetSymFromAddr:487, addr:0x7ff70fdf678e
[CDPInitServer]: ??? addr:0x7ff7101a0f5e
SymGetSymFromAddr:487, addr:0x7ff70fe003f8
SymGetSymFromAddr:487, addr:0x7ff70f94db50
[CDPInitServer]: ??? addr:0x7ff7107ffd0a
[BaseThreadInitThunk]: ??? addr:0x7ffad9b17ad4
[RtlUserThreadStart]: ??? addr:0x7ffada07a8c1
[RtlUserThreadStart]: ??? addr:0x7ffada07a8c1
 
Runtime mode
CLI params: ip 46.251.229.16 port 13200 config serverDZ_Private.cfg limitFPS 100 profiles C:\SERVICES\ni6607389_2_local\dayzps/config dologs  VMErrorMode log_only adminlog  freezecheck 
Reproduction steps
Login Server > Play Till shutdown > server crash upon restart and first connection.
  • Unable to provide storage files for examination or diagnostics due to Nitrados file restrictions.
    Unable to provide further internal diagnostics due to Nitrados file restrictions.

Exact build version (optional)
Version: v1.30.164200
Where did it happen?
Community
Is it modded?
No
Expected result

No crash - corruptions

Reactions

Activity

    about 1 hour ago
  • imonthefloor
    created issueabout 1 hour ago
  • imonthefloor
    changed title toCRITICAL - Root Server Crash (Seperate Engine Crash to local client crash)about 1 hour ago
  • imonthefloor
    changed title to[CRITICAL PS4] Nasdara – Repeated C0000005 ACCESS_VIOLATION / ENGINE LEVEL Server Crash Loop – v1.30.164200about 1 hour ago

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

State

Open
Issue key
DZG-1992
Access
Public
Space
DayZ
Project
Stable Feedback
Creator
imonthefloor
Created
Oct 25, 2026
Views
4