Page MenuHomeFeedback Tracker

Game Crash with windows 8.1 64bit arma3.exe
Need More Info, NormalPublic

Description

Games crashes with this error code OXC0000005 -Status_access_violation only with the 64bit.exe.
32bit arma loads and works flawlessly and ive yet to find a fix for the 64bit version. The 64bit version was working 2 updates ago with no issues at all.

have verified game cache via steam several times checked for errors or missing files in the directory, Reinstalled vc ret 2013.

Details

Severity
Crash
Resolution
Open
Reproducibility
Always
Operating System
Windows 8 x64
Operating System Version
6.3.9600.0
Category
Game Startup
Steps To Reproduce

Everytime you start the game with the lancher in 64bit mode. tested with all custom paramiters on and off no mods

Additional Information

Event Timeline

Qwenthe9tails updated the task description. (Show Details)
Qwenthe9tails renamed this task from Game Crash with windows 8.1 64bit arma.exe to Game Crash with windows 8.1 64bit arma3.exe.Oct 25 2017, 7:42 PM
dedmen added a subscriber: dedmen.Oct 26 2017, 8:53 AM

Your Report Log is useless.
If you use -noLogs and you send us your logs... That won't be useful as they will be empty. Also it doesn't contain any crashdumps.
Please crash it again without "-noLogs -mod= -beservice" and create a new report.

Wulf added a subscriber: Wulf.Oct 26 2017, 10:58 AM

Hello.

As dedmen said please remove -noLogs so that we can see the logs.

Also you might want to try these other possible solutions just in case.

  • Update the graphics card drivers to a newer version.
  • Rollback the graphics card drivers to an older version.
  • Check the temperature of your GPUs and CPUs.
  • Re-install DirectX.
  • Uninstall the Visual C++ 2013 Redistributable package (both x86 and x64 version), restart your computer and install the package again (do not use the Repair function).
  • Run a Windows System File Check tool to repair corrupted system files.
Wulf changed the task status from New to Need More Info.Oct 26 2017, 10:58 AM

Ah my bad i forgot i had no logs turned on, Turned off be and mods and no logs generated the new report here.

It fails right after InitSound - complete I have seen that quite often here. Don't know anything specific about that though.

Just my gut feeling dunno if it might change anything. But worth a try:
remove -cpuCount -exThreads -maxMem -maxVRam and -malloc startparameters.
Basically remove all of them and just run Arma with the defaults it chooses.

Gave it a shot still throwing the same error as before will include log from this test below.

Wulf added a comment.Oct 27 2017, 4:06 PM

Do you have a gamepad connected? If so then try disconnecting it and launch the game.

I just have the keyboard and mouse hooked up, no other peripherals like joysticks or gamepads/controllers.