Page MenuHomeFeedback Tracker

Crash on startup due to memory access violation
New, NormalPublic


DayZ v0.60.133516 (stable)

This is a rather undeterministic bug. Whenever I startup DayZ, there is a 90% chance of a crash due to memory access violation. It is notable that BattleEye starts before this error occurs. I usually just try starting DayZ up again and again, until it actually starts up.

The three possible error views are as follows:

  1. The instruction at <mem-address> referenced memory at 0x00000000.
  2. The instruction at<mem-address> referenced memory at <mem-adress close to 0x0>.
  3. Invalid memory access.

Here is a screenshot of number 2 referencing 0x08 (in German):

In addition, sometimes the window doesn't even load up properly in the first place and just stays white - without any error message. It doesn't load, but it doesn't crash either.

Logs from appdata and dxdiag:


Operating System
Windows 10 x64
Operating System Version
Game Crash
Steps To Reproduce

I cannot exactly give you any notes on how to reproduce as I can't really influence this particular problem. All I can say is that it behaves seemingly non-deterministic and that I am the only one facing this issue among my friends.

Additional Information

What I have tried by now is reinstalling and deleting configs at my user directory. The game itself seems to start most of the time as the main window opens and visually loads correctly in the background.

May be closely related to:
May be related to:

Event Timeline

Freemanium updated the task description. (Show Details)Jun 20 2016, 4:56 PM
Freemanium edited Additional Information. (Show Details)Jun 20 2016, 5:07 PM
Freemanium edited Additional Information. (Show Details)
Freemanium updated the task description. (Show Details)Jun 20 2016, 5:10 PM

Having THE same issue