Whenever I try to play the Apex campaign, the game crashes with this error and "The exception unknown software exception (0x0000dead) occurred in the application at location 0x7538c42d."
Description
Details
- Severity
- Crash
- Resolution
- Fixed
- Reproducibility
- Always
- Operating System
- Windows 7 x64
- Operating System Version
- Ultimate (SP1)
- Category
- Game Crash
- Launch Arma 3 through the launcher (Vanilla, no mods)
- Click "APEX PROTOCOL" (Middle selection box)
- Select any mission
- Click Play / Host / Join
Crash with error
RESOLVED
Re-installed the game (twice) and it now works.
- Uninstall the game.
- Make a backup of Arma 3 folder in Documents.
- Delete both Arma 3 folders in Documents and Steam:
\Users\*YOUR USERNAME*\Documents\Arma 3
\Program Files (x86)\Steam\SteamApps\common\Arma 3
- Reboot your PC.
- Run Steam as Admin, download the game.
- Try to run Arma 3 (without mods).
Thanks to Jiri K at the BIS support team :]
Things I've tried:
Deleting and re-installing the whole expansion,
Running the game with the most recent mods I've used,
Moving all mods out of Arma 3 dir,
Validating Steam game cache,
Deleting "functions_f.pbo", "A3.pbo", "functions_f_exp.ebo", "missions_f_exp.ebo", "missions_f_exp_data.ebo",
Event Timeline
Hello,
thank you for the feedback.
Could you please provide some info on how did you manage to resolve your issue?
- Uninstall the game.
- Make a backup of Arma 3 folder in Documents.
- Delete all Arma 3 folders in Documents and Steam:
\Users\*YOUR USERNAME*\Documents\Arma 3
\Program Files (x86)\Steam\SteamApps\common\Arma 3
- Reboot PC.
- Run Steam as Admin, download the game.
- Try to run Arma 3 (without mods).
Wow, so people have to go through all that to fix this error?
Why doesn't Bohemia fix it themselves and let people just play the game instead of leaving the troubleshooting to players.
My girlfriend just wasted 30 euros on this DLC. Last time we spent money on additions for this game.
Right, I have done some more testing.
Whenever I click Play Solo or Host a game Arma 3 crashes with the same message the OP mentioned in the title of this task. The file is where it should be though, and everything else in the game runs as it should.
After the first message I get a second window showing the error code 0x00000dead. I followed the link to see the error codes and this one is not there. I wanted to include the error report file but I got this message saying no configured storage engine.
Running Apex campaign missions on our server gives me no problems though. All works fine. No crashes whatsoever. So at this moment I am fine with playing the campaign that way, but...
I just feel that this sort of issues should be fixed by developers and not force people to uninstall Steam completely. Many people have loads of games on Steam and I think it's ridiculous they have to remove everything just to resolve a tiny issue like this.
IKR. Took me around 30 hours to re-download the game (My internet is beyond terrible) and it didn't work after the first re-install.
Deleting everything to do with Arma 3 sorted the problem out for me.
I actually think that transferring from the Dev build to the stable branch is what caused this (PRE- APEX RELEASE).
Hope your issue gets resolved,
Roxsonix.
@celticalliance
The with the troubleshooting reports is that these bug can happen to all people, to some people, sometimes only to a single person. Every problem can be unique and to find the exact issue, we need the info from them directly, if possible as much as possible.
Why I asked for the workaround? When fixing the issue like this we are not simply trying to find a workaround but we try to change the code to prevent this issue from happening at all. That might take a little bit more time and information about a possible workaround often helps to pinpoint the cause.
Anyway, crashing when hosting the Apex Protocol campaign, some fixes were made and applied in the development branch (will be later added to the Stable/Main). Feel free to switch to that version and check it out.
Thank you all for the feedback and your support, it is appreciated. Should you come across the same issue on development branch or encounter other issue or simply find anything else that might be relevant to the issue, please let me know.
Informing Bohemia this issue is fixed for me in version 1.64. Thank you for the fixes :)