Page MenuHomeFeedback Tracker

Exit code: 0xC0000005 - STATUS_ACCESS_VIOLATION
Assigned, WishlistPublic

Description

Title crash to desktop after a random ammount of time while playing MP. {F27338}

Details

Legacy ID
3176680936
Severity
None
Resolution
Open
Reproducibility
Random
Category
Game Crash
Steps To Reproduce

Could not reproduce or trigger this crash

Additional Information

Arma 3 Troubleshooting Report

Sorry for the inconvenience.
Please report this on Arma 3 Feedback Tracker (http://feedback.arma3.com). Thanks to you we may fix the issue faster.

----------------------

Process exit

Exit code: 0xC0000005 - STATUS_ACCESS_VIOLATION
Running time: 00:31:35.8956909

----------------------

System information

Date: 2015-11-04 10:16:44 / 2015-11-04 12:16:44 +02
Current dir: E:\Games\SteamLibrary\steamapps\common\Arma 3
Command line: "E:\Games\SteamLibrary\steamapps\common\Arma 3\arma3launcher.exe"
CLR version: 4.0.30319.42000
OS Version: 10.0.10240.0 (Microsoft Windows NT 10.0.10240.0)
OS 64 bit: True
Process 64 bit: False
Culture: en-US
UI Culture: en-US

----------------------

Last game report

Event Timeline

rzarectha edited Additional Information. (Show Details)
rzarectha set Category to Game Crash.
rzarectha set Reproducibility to Random.
rzarectha set Severity to None.
rzarectha set Resolution to Open.
rzarectha set Legacy ID to 3176680936.May 8 2016, 1:03 PM
TutSi added a subscriber: TutSi.May 8 2016, 1:03 PM
TutSi added a comment.Nov 4 2015, 11:29 AM

Look down for other reports, it is assigned.... Why you are creating copies of already reported tickets?

Because each computer is unique, many variables can trigger the same issue. The cost for the tracker is maybe a few houndred kb, but the info can be valuable.

Adam added a comment.Nov 4 2015, 12:41 PM

Exactly what rzarectha stated.

That said. Could you please disable the -nologs parameter and try reproducing the issue again? If the issue occurs again please attach the newly generated dump files here or if they are too big use some file sharing service. Thanks!

Hello Adam, sorry for the delayed answer.

I did read your message as soon as you wrote it.
Sorry for the -nologs, I forgot that i had it disabled for performance improvement.
I unticked it and went in game, i have been ingame on the same server for the last 4 hours and the crash did not occur again.
I will do another test tomorrow trying with the option unticked again and see how it behaves.
Anyway, I am working on getting a proper crash dump for you.

We keep in touch, have a nice evening.

Adam added a comment.Nov 5 2015, 9:38 AM

Awesome. Thanks a lot!

Hi Adam! I am unable to reproduce the crash anymore since i removed the -nologs command. I used to have this crash on two PCs and it never took more than 20 minutes to occur, since I disabled it I have ~ 6 hours played continuously without any problem at all.

Not sure what more to say right now, my suggestion (if you want one) is to have someone test it in-house with -nologs and asserts activated.