Page MenuHomeFeedback Tracker

0xC0000005 STATUS ACCESS VIOLATION in MP
New, NormalPublic

Description

Very recently began experiencing the above 0xC0000005 STATUS ACCESS VIOLATION error within a few minutes of playing in multiplayer rounds. Sometimes this error prompts as soon as I join the match, and other times it happens anywhere from 5-10 minutes after joining.

Steps taken:
-Verify files
-Reinstall Windows
-Reinstall Arma 3 on SSD
-Reinstall Arma 3 on HDD
-Run 32 bit launcher
-Run dedicated new & old profile parameter
-Disable OneDrive (perhaps OneDrive is locking profile items stored in My Documents or other default OneDrive directories)
-Delete Arma3 folder in My Documents
-Delete Arma3 folder in Appdata > Local
-Delete old profiles, then recreate new profile in Arma3

Details

Severity
Crash
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Category
Error Message
Steps To Reproduce

Join multiplayer match (ex: KOTH by Sa-Matra, select loadout). Perform any of the following:

  1. Lean left/right (wiggle) with default keys q+e, in spawn after selecting loadout
  2. Drive CSAT APC for 800m / ~ 45 seconds from spawn
  3. Reload Katiba GL while in firefight under tower 4
  4. Join game

Event Timeline

This error report was retrieved upon immediately joining in, no loadout selection possible

This error report was retrieved upon joining a different server, walking around for a brief moment and attempting to enter a vehicle. Please advise if you require any additional information / have any insight on how to proceed.

This error report was retrieved upon creating a LAN Warlords match on Tanoa- the game did not go past the map screen / crashed when I pressed continue.

Unfortunately it seems the issue has spanned over to single player- in this current state the game is unplayable. Could not even start single player campaign Steel Pegasus without same error.

Interesting thing of note- I am using Sony Bluetooth headphones (WH-1000XM3):

When I changed my audio output from 'WH-1000XM3 Hands-Free AG Audio' to 'WH-1000XM3 Stereo' I am able to play the Steel Pegasus scenario without issue (was able to proceed 15+ minutes until auto/objective failure). I will try MP later to see if this makes a difference in a multiplayer scenario later and report back. I'm not sure what the difference is between these two outputs but I felt it should be noted regardless :)

More things to report: I was able to play multiplayer and additional single player scenarios without issue with the new output selected; however, when I tried to play Steel Pegasus again this morning I encountered this attached log. I'm not sure what the differences were between last night and this morning but both logs are attached for reference.

I have since booted up the game again and have been able to play without any additional crashes up until this point - providing comment for timeline / reference.