Page MenuHomeFeedback Tracker

Game crash: The instruction at 0x016f56cb referenced memory at 0x00000000.
Assigned, WishlistPublic


Game crash with error :

The instruction at 0x016f56cb referenced memory at 0x00000000. The memory could not be written. Launcher detected Arma3 was closed unusually. Exit code 0xC0000005 - STATUS_ACCESS_VIOLATION. {F27009}


Legacy ID
Game Crash
Steps To Reproduce

Running a scenario with following mods AiATP, CAF aggressors, RHS Escalation and Reshmaan Province. Oddly the scenario works fine in the editor but crashes when played in SP or MP.

Event Timeline

RickOShay set Category to Game Crash.
RickOShay set Reproducibility to Sometimes.
RickOShay set Severity to None.
RickOShay set Resolution to Open.
RickOShay set Legacy ID to 2283789112.May 8 2016, 12:41 PM
Adam added a comment.Sep 10 2015, 1:50 PM

Hello, we are sorry you are experiencing issues with our game.
Could you please export your game log files from the launcher?

Steps on how to export logs from ARMA 3 Launcher:

  1. Start ARMA 3 Launcher
  2. Click the Hamburger menu tab in the launcher (Top right corner. Next to Options (Cog wheel icon) and Minimize Button)
  3. Drop down menu will appear
  4. Select: Prepare Arma Troubleshooting error and save those files
  5. A notification will pop up with the name of the generated file

Please note that the files might take a while to collect.

Attach the generated files to the ticket. If the files are too big please use some free file sharing service.

Also, please check if your page file is enabled and how big the page file is.

How to check your page file:

  1. Go to control panel
  2. Select System
  3. Select Advanced System settings in the left menu
  4. In the new popup window select Advanced and and Click settings under Performance
  5. New window will pop up. Select advanced again and check the Virtual memory tab
  6. The total paging file size for all drives number represents your page file size.

Is your hardware overlocked (CPU,GPU and RAM mainly)

Lastly, we are preparing a special .EXE of the game with extended logging capability so we can identify the problem faster and with more accuracy.
Would you be able to play the game with mentioned .EXE so we can find fix for the issue faster?
This helps us investigating your problem in a big way.

Thank you for your feedback!

Ok here are the files. Page file is managed by Windows. No over clocking.

I am more than happy to use the .EXE to help you resolve the issue

sp00kz added a subscriber: sp00kz.May 8 2016, 12:41 PM

I'm running into a similar crash, No OC. My log is too large to upload.

I'm guessing this has to do with a mod, has only been occurring since the last arma3 patch. This error occurs (memory crash referencing 0x00000000) to multiple people using this set of mods. (rhs/ace3/tfar++)

16gb ram, 16gb (system managed size) page file on D:

Adam added a comment.Sep 11 2015, 9:43 AM

does the crash happen when mods are not used?

Adam added a comment.Sep 11 2015, 10:38 AM

Also could you please attach the mission where it is crashing?

Please let me know if I'm hijacking this ticket and need to create anew.

I have not played arma3 recently without mods, my only interesting note is that this did not seem to happen on a second server with a similar modset that did not have vehicle respawn configured. I will see if I can get ahold of this pbo as it's not cached on my machine.

I am not an experienced map maker, here is the simple mpmission I was running using arma3server on the same system as the fully connected client.

The most reliable way I was able to reproduce this bug was to spawn an aircraft (rhs or stock, seemed to occur faster with rhs) and fly around for <5 minutes.

located mission where crashing did not occur, if this helps:

@spOOkz - well spotted! The cause of the crash is vehicle respawn.

Excellent, let me know if I can help any further