Game worked fine while playing Episode 1 but since I started Episode 2 it crashes almost every time when saving. Error "Arma stopped working". {F24017} {F24018}
Description
Details
- Legacy ID
- 1897491048
- Severity
- None
- Resolution
- Fixed
- Reproducibility
- Random
- Category
- Game Crash
Event Timeline
Hello,
can you please choose Revert from the mission you were playing last? Also, can you confirm this behaviour on version 1.20 (update should be very soon)?
Thank you.
Hi,
choosed Restart for Episode 1, Mission 1 "Signal Lost" and same Problem occured i.e. Crash while first autosave with Error "Arma stopped working". Where do I get Update 1.20?
okay, game updated itself to v1.20, I reverted to Episode 2 Mission 1 "Signal Lost" and game crashed 2 of three times at the very first autosave (right after coming from the beach).
Could you please upload as many crashdumps as possible?
(crashdump is rpt + bidmp + mdmp file with same name)
Thank you.
Okay, the 7z-archive named "Arma 3" contains 3 crashes while autosave Episode 2 Mission 1 right after coming from the beach, Standing Close to a shrine-thing containing a binocular and overlooking the City.
The next Archive "Arma 3 Savecrash" happend after a successfull first autosave in Episode 2 Mission 1. This time i ran more North from shrine-thing when autosave successfully happend but it crashed when I tried to save after I go the Hint by Radio to search the ruins for weapons...
Thank you for the crashdumps, we started analysing them Would it also be possible to upload your profile folder?
C:\Users\<Name>\Documents\Arma 3 - Other Profiles\<Your_profile>
Thank you.
Thank you for the profile folder. The data you sent are currently being analysed, this can take some time. Sorry for inconveniences, have a nice day.
Hello,
we have analysed the crashdumps and found what caused the trouble. Fix was applied, it is distributed in Steam Dev version 124875 and higher and will be brought to Stable in the next update.
Thank you.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.