Page MenuHomeFeedback Tracker

Application Error : The instruction at 0x00000000 referenced memory at 0x00000000
New, WishlistPublic


Game crash after 30 minutes of play.

Application popup:
DayZ: DayZ.exe - Application Error : The instruction at 0x00000000 referenced memory at 0x00000000. The memory could not be written.

Click on OK to terminate the program
Click on CANCEL to debug the program


Legacy ID
Game Crash
Additional Information

Gigabyte 970A-D3P
AMD FX-8350
AMD Radeon R9 290
16 GB RAM (Corsair Vengeance 1600MHZ)

Event Timeline

SpecialJimmy edited Additional Information. (Show Details)Feb 28 2015, 4:03 AM
SpecialJimmy set Category to Game Crash.
SpecialJimmy set Reproducibility to Random.
SpecialJimmy set Severity to None.
SpecialJimmy set Resolution to Open.
SpecialJimmy set Legacy ID to 169029652.May 8 2016, 9:43 PM

Same problem, same graphics card. Dump file for me is larger than maximum size for file upload on this site.

f3cuk added a subscriber: f3cuk.May 8 2016, 9:43 PM
f3cuk added a comment.Feb 28 2015, 4:55 PM

Okay here is what fixed it for me and the friends i play with.

1.) Right click DayZ on steam
2.) Click on Properties
3.) Click Set launch options
4.) Enter: -malloc=system -maxMem=2047 so it looks like this

Can someone confirm that please...

Tried that, but didn't work out for me. Crashed about half an hour in game.

amask added a subscriber: amask.May 8 2016, 9:43 PM
amask added a comment.Mar 1 2015, 4:08 AM

I use your launch option since today, i do a short session ( 30/45 minutes) and one 3 hours session and crash did not happen.
It's happened every hour before. Maybe it's related.

Viguy added a subscriber: Viguy.May 8 2016, 9:43 PM
Viguy added a comment.Mar 6 2015, 1:27 AM

Same issue here, same version of Dayz. Different hardware. Mine does not happen during gameplay though,(I can play for hours without issue) but consistently when I exit DayZ before I get back to the Steam window.This began on the last update to DayZ for me.

1-eye added a subscriber: 1-eye.May 8 2016, 9:43 PM
1-eye added a comment.Mar 6 2015, 5:15 PM

There is 4 in our group having the same problem. We turned our FPS viewer off and this problem stopped. Hopefully this will work for some of you. This started with us 4 on the last update as well.