Page MenuHomeFeedback Tracker

When joining Altis Life Server Game crashes 100% of the time
Closed, ResolvedPublic

Description

I can start Arma III, but when I try to join an Altis Life Server, the game crashes to desktop every time. {F23970} {F23971}

Details

Legacy ID
430622097
Severity
None
Resolution
Fixed
Reproducibility
Always
Category
Game Crash
Steps To Reproduce

Join Altis Life Server.

Event Timeline

ajbrutico edited Additional Information. (Show Details)
ajbrutico set Category to Game Crash.
ajbrutico set Reproducibility to Always.
ajbrutico set Severity to None.
ajbrutico set Resolution to Fixed.
ajbrutico set Legacy ID to 430622097.May 7 2016, 6:37 PM
ajbrutico edited a custom field.
Bohemia added a subscriber: Crooks.May 19 2014, 2:21 AM

I had this problem as well. Delete all .dll files in the ARMA DLL folder, except the readme. Restart STEAM but do not verify game cache.

Fank added a comment.May 19 2014, 7:02 AM

Could you please upload your crashdumps?
@ajbrutico you can find them under "C:\Users\The Bruticos\AppData\Local\Arma 3" we need the *.mdmp and *.bidmp.

Thank you

Unknown Object (User) added a subscriber: Unknown Object (User).May 7 2016, 6:37 PM
Unknown Object (User) added a comment.May 19 2014, 7:16 AM

seems more of an addon-related crash

Hello,
Thank you for reporting the issue.
We need crash dump files from this folder for solve your problem.
C:\Users\<Name>\AppData\Local\Arma 3\
Can you upload somewhere in winrar package please?
When package will be smaller than 5000k, you can attach it here. When package is bigger, 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 don't extract these files as comments, it makes things very messy.

Thank you.

I believe I uploaded dump files, however deleting the .dlls in the DLL folder as SG_Smokintodd noted seemed to work.

This is not a fix, it is a workaround. Any ideas why this would need to be done in order to play the game?

Hi, we are currently analysing the crashdumps.

Hello,

it seems that some of the dll libraries are corrupted. We are unable to reproducce the problem in our conditions, so I would like to ask you for a cooperation. Please verify your game through Steam, so the dll libraries are downloaded again. ( https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335 )

Then I would like you to try the allocators one by one to determine which cause the crashes (there may be more of them). To do that please:

Create a shortcut of the arma3.exe file.
Select properties of the shortcut (right click)
To the path of the file, add: -malloc=<dll_name>
it should look similar to this: "C:\Program Files (x86)\Steam\SteamApps\common\Arma 3\arma3.exe" -malloc=<dll_name>

Please, replace <dll_name> with following (one for every launch):
tbb4malloc_bi
tbb3malloc_bi
jemalloc_bi
tcmalloc_bi
nedmalloc_bi
custommalloc_bi

If we could determine which of these are causing the crashes, it would be a big help. Thank you very much!

Hi,
we updated the memory allocators, would it be possible to start Arma on Steam Dev branch?
Thank you.

Hello,
are these crashes happening on current Steam Stable 1.20 version?

No I am not having this crash now.

I also have trouble, sometimes it crashes randomly ingame, sometimes it crashes in the loadingscreen. When it crashes in the loadingscreen it is impossible to join back until the server restarts (maybe something weird in the Server Cache). I reinstalled ArmA3 4 times, including twice through Steam and through the complete windows PC version. None of this fixed the issue for me.

Iceman added a comment.Jun 2 2014, 9:35 AM

@Skaronator,

yould you please create another ticket regarding your issue?

Thank you very much!

Alright here: #19049

MadDogX added a subscriber: MadDogX.May 7 2016, 6:37 PM

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.