Since 27/07/2016 getting a reference memory followed by a report showing STATUS_ACCESS_VIOLATION error, Arma worked fine the day before
Description
Description
Details
Details
- Severity
- Crash
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Category
- Game Crash
Steps To Reproduce
No Mods
No command line arguments
Additional Information
Troubleshooting I did:
Reinstalled twice
Unsubscribed mods
tried different memory allocators
Insured folder access is correct
ran Arma3.exe withour launcher
Reinstalled gfx drivers
I have a backup of Arma 3 for version 1.60.0.136470, after uninstalling Arma from Steam, and running this Arma3.exe it worked fine.
Event Timeline
Comment Actions
Hello,
thank you for the feedback.
I would ask you to do is to provide us with the crashdumps.
If you are getting crash with vanilla version (without mods) please try to provide crashdumps created without the mods.
To get the crashdump files, please go to the Launcher > Options> Prepare Arma3 troubleshooting report, then save the ZIP file with the report somewhere where you can access it and upload it here.
Or you can look for the crashdumps manually. Crashdump (set of mdmp + rpt + bidmp with same timestamp) files should be located in this directory:
C:\Users\<username>\AppData\Local\Arma 3
Once you have the files in a ZIP, please drag&drop them into the comment box, or (if you encounter any issue with uploading it here) upload them to some free file sharing service (for example Dropbox) and post the link to the files into the comments.
Thank you
Comment Actions
Hi, I cam across a thread somewhere to use the following command line argument -profiles=Profiles, this fixed it for me.
Comment Actions
Hello,
glad to hear that you are able to play.
However the crashdump files I asked for might still come in handy so if it's not too much trouble for you please try to look for the crashdump files. Once you prepare the ZIP file through the launcher please try to check whether the mdmp files are included in it, if they are not look them up manually as mentioned above.
Thank you
Comment Actions
I removed this parameter, and I cant replicate the issue again, not sure what changed. Thanks for the response, but I reckon this issue can be closed.
Comment Actions
Mass closing old issues that are:
- Not relevant anymore
- Probably already fixed
- Missing info and no activity for years