ArmaReport_Log_20170929T130013_stan123.zip22 MBDownload
Details
Details
- Severity
- Crash
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 7
- Category
- Game Crash
Additional Information
Related Objects
Related Objects
Event Timeline
Comment Actions
Looks like steam overlay crash. Callstack doesn't match. But final crash location matches.
Comment Actions
how can i disable overlay without delete or rename file(coz it is not work, if i make it right)?
Comment Actions
one thing.If i start the game with settings "start the game 32 bit" game will start well.What the problem can be with 64 bit version?
Comment Actions
The problem is not Arma. It's Steam.
Steam will try to repair that file if it detects that it is missing. It is probably doing that while you start Arma. Even though overlay is disabled and it shouldn't do that Steam still does it.
They pushed a update to that file 3 days ago. Shortly before the crashes started to appear everywere.
you could create a dummy file with the same name and write-protect it so that Steam cannot overwrite it.
Comment Actions
The fix would be Steam fixing their GameOverlayRenderer64.dll. I didn't check if it got an update yet.
This is essentially a Steam Bug not Arma.
Comment Actions
Just before you open arma in steam, delete "GameOverlayRenderer64.dll" from steam directory.One way to start Arma 3 64 bit that i now know
Comment Actions
Ok, good to know. :)
Just in case the problem would occur again, could you download the development version of Arma 3 and through the Diag Exe version, could you recreate the crash and send dumps from that? Thanks. :)