Page MenuHomeFeedback Tracker

Status Access Violation Crashes
Closed, ResolvedPublic

Description

Hi everyone,

I have been having this issue for the past few days now and have had no luck of my own trying to resolve it. I have tried all of the fixes from the Community Wiki and even reformatted and installed a fresh copy of Windows 10 Pro, but still no luck. I am running no mods, just the base games and some of the DLC. Any help is extremely appreciated and I will be more than glad to give more information as requested. Thanks in advance!

Sincerely,
The Jam Taxi

Details

Severity
Crash
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Operating System Version
Windows 10 Pro - Version 1809 - OS Build 17763.503
Category
Game Crash
Steps To Reproduce

Launch Arma, join a multiplayer server, play for 5-10 minutes, then the game crashes resulting in the Exit Code: 0xC0000005 - STATUS_ACCESS_VIOLATION

Additional Information

Event Timeline

Hi,
game crashes in d3d11 render. It can be caused by graphics drivers, directx or overclocked graphic card. Do you have graphic drivers and directX up to date?

Hi Astaroth,

Thanks for the response! Yes, I have my drivers all up to date. I believe my DirectX is all up to date, but I will uninstall/reinstall all of that again to double check. I will get back to you once this is done (less than 4hrs).

Thanks!

So I reinstalled DirectX via: https://www.microsoft.com/en-us/download/details.aspx?id=8109, and I was able to play for about 20minutes this time before I crashed due to a STATUS_APPLICATION_HANG error.

Attached the new crash log.

Any help on this one would be appreciated too. Thanks Astaroth!

And now I am having this error: Stack Buffer Overflow. :(

Attached new crash log.

Hi,
I checked both new logs but they are without new crashdumps.
Here you can find some solutions for various errors https://community.bistudio.com/wiki/Arma_3_Unusual_process_exit

Thank you Astaroth. I appreciate all of your help! If I find out what is causing it, I will post it in here.

Hi Astaroth, just wanted to give you a little update. I found that the issue was caused due to a Windows Update that apparently had incompatibilities with my hardware. Microsoft put out a patch for the issue and all is well again. Thanks!

Astaroth closed this task as Resolved.Thu, Jun 13, 10:24 AM
Astaroth claimed this task.

Hi,
glad to hear that it works now. Thanks for the info.