ARMA 3 (x64 only) STATUS_ACCESS_VIOLATION crash on every startup
New, NormalPublic

Description

About 4 months ago, I used to be able to run ARMA 3 x64 just fine. However it has begun to crash on startup more a more frequently. At first it was only every 1 in 10 tries it would crash, then it became 1 in 5, and so on until I had to start the game 4 or 5 times before it would run without crashing when it started loading (sounds like hardware fault - but see below).
I have spent months researching every solution I can find relating to startup crashes for x64 bit ARMA on the internet and have tried every solution that was suggested. I really can't face reinstalling windows just to run the x64 version of ARMA as it's the only application (and x64 application) I have installed that doesn't work as intended).

ARMA 3 x32 works every single time without exception, with or without mods and regardless of any parameter changes as x64 used to.
The game will randomly run x64 fine with or without mods and parameters customised (happens about once every 20 tries) and once the game is up and running it runs indefinitely without crashing or any issues.

Here are just some of the things I have tried, I can't remember every single thing though:

  • -Completely reinstalled ARMA 3 from scratch with no mods or parameter settings
  • -Checked my memories health (ram) memtest (was fine)
  • -Individually tested each of my corsair DDR3 4gb Ram sticks and starting up ARMA each time
  • -Underclocked my CPU (GPU has never been OC'd)
  • -Updating graphics card drivers & rolling back drivers
  • -Verified integrity of game cache
  • -Removed all mods
  • -Unsubscribed from all workshop content
  • -Reset all parameters to default
  • -Removed all my profile data
  • -changed various values in the registry that supposedly relate to x64 crashes (after x64 ceased to run not before)
  • -switched to the dev build
  • -Tried launching with or without battleye
  • -Tried launching using battleeye.exe
  • -Creating, removing and editing the nvidia control panel 3d settings for ARMA x64 .exe
  • -Reinstalled direct x
  • -Uninstalled Visual C++ 2013 Redistributable package (both x86 and x64 version), and restarted my computer etc.
  • -CCleaner registry cleaner

Things I have yet to try:

  • De-Fragment PC
  • Run a Windows System File Check tool to repair corrupted system files
  • Reinstall Windows 8.1 (absolute last possible option)

Details

Severity
Crash
Resolution
Open
Reproducibility
Always
Operating System
Windows 8 x64
Operating System Version
8.1 Pro
Category
Game Crash
Steps To Reproduce
  • Start ARMA 3 with x64 selected in parameters in the launcher, and no mods or other parameters selected.
  • ARMA 3 logo with orange loading bar displays over my desktop.
  • The screen then goes black for 2-3 seconds as if it's about to go into the fullscreen loading screen.
  • Then the crash messages pop up and the game closes back to desktop.
Additional Information

Crash log rpt: http://www.mediafire.com/file/p6ecjmu898osqoo/arma3_x64_2018-02-12_18-58-26.rpt

Crash Log Output: http://www.mediafire.com/file/c1qjwbjk75b9628/ArmaReport_Log_20180213T102712_Pete.zip

Error Messages: https://i.imgur.com/GajcLGA.png

System specs:
I5 3570K
GTX 970
16 GB DDR3
250 GB Solid state drive (windows)
1TB internal hard drive (Arma 3)

Pingo created this task.Tue, Feb 13, 6:05 PM
Pingo updated the task description. (Show Details)Tue, Feb 13, 6:12 PM
Pingo changed Operating System Version from 8.1 to 8.1 Pro.
Pingo updated the task description. (Show Details)Tue, Feb 13, 6:32 PM
Pingo edited Additional Information. (Show Details)Tue, Feb 13, 9:14 PM
Wulf added a subscriber: Wulf.Wed, Feb 14, 1:53 PM

Hello.

Thank you for the report. Running a Windows System File Check tool to repair corrupted system files is not a bad idea.

Though according the rpt the game throws the error during detecting your joysticks. Perhaps looking if there are new drivers fro your joysticks isn't bad either. Try disconnecting them if it happens even if they are not connected.

Thanks for the info, I had wondered this as I'd read about driver issues before, and sometimes unplugging stuff from my pc seemed to get it working once or twice. I'll give this a try. Cheers