Purchased game couple of weeks ago, version 1.46. Played fine for the first few hours. Then all of a sudden would crash a random times showing a memory could not be read error. The error code seems to be random.
{F26550} {F26551} {F26552} {F26553} {F26554} {F26555} {F26556} {F26557} {F26558}
Description
Details
- Legacy ID
- 514168286
- Severity
- None
- Resolution
- Open
- Reproducibility
- Always
- Category
- Game Crash
Always happens, I have uninstalled the game twice with no change, also have changed
and edited profiles, will occur in campaign and scenarios.
I am running an AMD cpu and AMD Radeon GPU. I see other posts with this issue and have tried all attempted steps to find the problem. I do know that I previously had a Nvidia GPU and that the direct X files are from Nivdia, is there a possible conflict with that?
Event Timeline
I can reproduce this bug pretty redundantly by logging into the 69th Infantry Division (http://sixnine.enjin.com/) and using the "FSG Gunner" profile. Setup a mortar bipod/tripod using the ammo truck in the parking lot, assembling the mortar next to the ammo truck. Lob some flares/HE rounds and after awhile, the game crashes. Not sure if a "FSG UAV operator" spotting enemy is also required to reproduce the crashes.
Sometimes I can go for awhile without seeing a crash, but the bug is pretty imminent in that it will eventually appear regardless.
me and a bunch of friends constantly have this problem since 1.46 our favorite game is unplayable we are all running I7 4790Ks and GTX 970s
yeah, mines on anything though both islands, single player, multiplayer everywhere. my game has been unplayable for about a month since the 1.46 update and its so frustrating. :(
As I briefly speculated in my reduplication scenario, it maybe because of using the Artillery Computer map for mortars, as I haven't seen this bug elsewhere within ARMA 3 for the past month(s) until using the mortar with Artillery Computer map.
Is anyone even being assigned to these probably one of the biggest issues in the game as it makes it unplayable for quite a few people and its just being looked over.
Hello, could you please upload your .RPT file here? It can be found in C:\Users\<Name>\AppData\Local\Arma 3\.
@Schultz, let me assure you we are not overlooking the problem. These things are hard to reproduce in our environment and steps to reproduce are different for every user. Thank you for understanding.
Uploaded 4 of the most current .RPT files, I do hope this helps in some way.
Thank you
We need crash dump files from this folder to analyze your problem.
C:\Users\<Name>\AppData\Local\Arma 3\
Can you upload somewhere in winrar package, please?
Archive smaller than 5000 KB can be attached directly to the ticket. For bigger archives, please use some free sharing service and post link here.
How to find correct crashdump file:
Try to make the crash happen
Look into crashdump folder
Upload crashdump with latest date in name (crashdump is rpt + bidmp + mdmp file with same name). Please try to provide as many crashdumps as possible, it helps us investigating the problem in a big way.
Thank you.
Here are 4 of my latest .RPT files https://drive.google.com/folderview?id=0B7PVt5qL7n8Zfm84aElNMHJXbDcxVWx4M1ZVNGpsdTc5aUpvUmw1alhUbjdyVEE5bl9RWlE&usp=sharing
Here is my link to the crash dump files, Thank you
https://drive.google.com/folderview?id=0ByEDgLzOv006fmxyMFlGbGkxeDhXZ3kzUGJ6OF9GRzF6c29PeDVtMUZJdkFhOVQyM0VzZlU&usp=sharing
Within Bug #24041 "Unusual Exit Code and game crash on MP servers" and at Comment #94730 by 10Cwaites on 2015-06-24 01:20, he stated configure the following within the ARMA 3 Launchers Configuration Settings:
- "Disable Launcher's UI hardware acceleration"
- Action after game start: "Close launcher after clicking play"
I can confirm omitting either, and the game will still crash. I've yet to see any crash with the above settings.
Looks like you are experiencing unusual process exits. Please see the following link and try the solutions posted there https://community.bistudio.com/wiki?title=Arma_3_Unusual_process_exit&redirect=no#0xC0000005_-_ACCESS_VIOLATION
Adam: Negative Adam. This bug originates with the ARMA 3 Launcher period. Having users manually reinstalling drivers, downgrading drivers, reinstalling DirectX for a verified bug with the ARMA 3 Launcher are only going to give users further headaches!
Matter of fact the URL & section you reference, I happened upon long ago searching and realized immediately the section referenced (with albeit generic sounding advice) was not the solution for a well kept box or operating system; and knew this bug was very likely originating from within ARMA code itself due to the lack of problems elsewhere within the operating system.
UPDATED: However I will make further note I did recently just install MS Visual Studio Community within the past month. I only started using the ARMA 3 Launcher due to using the execute, TrackIR USB hardware was loosing detection. Using the Launcher, TrackIR USB hardware is no longer lost. Installing MS Visual Studio Community required uninstalling "Visual C++ 2013 Redistributable x86) etc, and letting the MS Visual Studio Community install it's own version else MS Studio Community would not install at all. I'm wondering if others have also installed MS Visual Studio Community?
I've unchecked those ARMA 3 Launcher options (mentioned within Bug #24041) after re-installing (ie. repairing) MS C++ x86 redistributable and haven't seen a crash for the past several hours. Although I've also upgraded from RC to 1.48.
Although some others have experienced crashes and are posting to Bug #24041