Page MenuHomeFeedback Tracker

Arama 3 Troubleshooting 0x0000DEAD
Closed, ResolvedPublic

Description

C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe

"C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe" -nobenchmark -mod

Original output filename: Arma3Retail_DX11
Exe timestamp: 2016/12/07 10:50:01
Current time: 2017/02/19 00:43:35

Type: Public
Build: Stable
Version: 1.66.139586

Allocator: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\dll\tbb4malloc_bi.dll

  • Loaded addons ---

Details

Severity
None
Resolution
Open
Reproducibility
Random
Operating System
Windows 7
Category
General
Steps To Reproduce

please help

Additional Information

i need halp

Event Timeline

Getting this one every 5th pass or so.... most of mine are 0xC0000005 Violation Access.. been going on for days now.. I have played the game at most 5 hours in 4 days, half of this was on other people's servers.. So far the only thing I have found to fix the issue for 2-3 is Uninstall everything.. literally.. steam included. Then using your registry cleaner of choice and killing anything it pulls up without bothering to look at the what if scenario.. Finally.. if you are like me and like to mess with mods and use the tools.. The instant I install the largest tool set for arma3 the error begins, even if it has only been 2 minutes post reinstall..

Good Luck.. I am sure that I will be killing my server and dumping this game considering you can search back for 2 years and find these errors, they blame GFX card. Frag'd Drive.. and so on.. READ THE REPORT, it has zero to do with it.. The bottom line seems to be that the launcher is not saving its callin code properly and it is dialing into the MS mess using either the wrong pattern, date, or any number of things. .

Alwin claimed this task.Feb 20 2017, 4:59 PM
Alwin changed the task status from New to Reviewed.

Hi,

Can I ask you about your crash dumps please? We´ll need your troubleshooting report folder to investigate your issue.

Thank you very much.

@Astaroth hi :)
Please close this ticket as obsolete

Astaroth closed this task as Resolved.Wed, Jun 12, 3:03 PM

Strange that I didn't get notification of the request for crash dumps, but over a year later I got the notification of things being resolved/obsolete and closed lol. I don't know that I would say that this issue has ever been "resolved".. Perhaps that is, in part, due to there being so many variations of the overall crash, or perhaps due to the majority of people rarely have this error happen more than a few times in the life of a computer.

I can't say that I solved the issue, but I did exactly as I said.. killed my servers and dropped the game until 2 months ago. The issue started once again a couple of days ago and I made some seemingly unimportant param changes that has so far stopped there being any other problems.

the launcher had my system listed with 6 cores, no special actions for extra cores/threads, half of the actual gfx mem total listed, and windows select for the maloc type. I changed those settings to more "correct" amounts (8 core, all 3 of the boxes checked for core usage, hyper threading, set the gfx mem to a max of 3/4 total mem,