Page MenuHomeFeedback Tracker

Memory Write Error On Start - Status Access Violation Crash
Closed, ResolvedPublic


{F84919}I am getting a game crash when I start the game with the following mods. I do not get any errors when I unload CUP Terrains. I don't understand how all of a sudden this one mod has out of nowhere started producing a launch crash. I get no crashes when running without mods, or with ANY combination of mods except CUP. I can't understand how running any combination works, but when I try to run this one mod, I get a crash.

Error reads: Arma 3: arma3_x64.exe - Application Error
The instruction at 0x77790944 referenced memory at 0x777da2c4. The memory could not be written. Click on OK to terminate the program.

Crash report is 0xC0000005 - ACCESS_VIOLATION


Operating System
Windows 7
Operating System Version
x64 Ultimate
Game Crash
Steps To Reproduce

Load mods including CUP. Game crash.

Additional Information

Game does not crash when not loading CUP. Makes zero sense to me. I have downloaded CUP from the Steam Workshop and from the main source, both produce the same error.

I have also tried verifying the integrity of the game cache to no avail.

Event Timeline

LtPatterson updated the task description. (Show Details)Oct 8 2017, 6:31 PM
Wulf added a subscriber: Wulf.Oct 9 2017, 2:41 PM


If the mod causes the crashes you might want to contact the creator of the mod that it crashes the game.

Still could you please send us your Arma report?

Here's how to do that:
How to Guide

LtPatterson added a comment.EditedOct 9 2017, 11:52 PM

Here's a link to the .zip of the crash. I asked the mod maker, and a test running just CUP Terrains and Maps was successful. It must be something else. I will continue looking at what mod is breaking the game on launch.

dedmen added a subscriber: dedmen.Oct 10 2017, 8:34 AM

Please disable -noLogs before crashing your game and creating the report.
The devs don't have useful logs if you disable them.

Wulf changed the task status from New to Need More Info.Oct 10 2017, 12:39 PM

As dedmen said please disable -noLogs and crash the game again and send us a report so that we can see what was going on before the crash.

LtPatterson added a comment.EditedOct 12 2017, 12:34 AM

{F85013}My bad! I removed all command line parameters and left only skip logos, static background, world=empty and hyper-threading enabled.

New file attached.

Has someone had a chance to review the new attached log?

Wulf changed the task status from Need More Info to Reviewed.Oct 16 2017, 11:20 AM

I sent the files further to programming just in case. We will see what they can tell us once they get to it.

Crashed somewhere inside graphics component. Only the devs can tell you more specifics.
Did you try completly redownloading CUP yet? There was also a CUP update recently. Good time to redownload everything now. Might be a corrupted model or texture.

LtPatterson added a comment.EditedOct 29 2017, 5:58 AM

Issue fixed by following the last few posts in this thread: related to MSI afterburner. I had to uninstall and install the beta version to get the game to work. I cannot for the life of me understand how the most popular GPU utility in the world caused an obscure crash in Arma, but I would look into what interactions the game has with RivaTuner or Afterburner. Those apps are essential to GPU monitoring and I run them in every game I have ever played in the last 10 years and NEVER had an issue.

Wulf added a comment.Oct 30 2017, 11:42 AM

Ah you are overclocking then that indeed could cause such an issue. Arma does not cope well with overclocking.

Wulf closed this task as Resolved.Oct 30 2017, 11:42 AM
Wulf claimed this task.