This error started to happen after I moved my arma 3 installation to a different drive. What happens is I would start the arma 3 launcher and then it would load in the background for about 30 seconds then it would crash with this error System.OutOfMemoryException. This only happens with the launcher if I launch the game from the .exe file then it launches just fine but without the launcher I can't use mods.
Description
Details
- Severity
- Crash
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Operating System Version
- 1703
- Category
- Launcher
I can reproduce this by just starting the launcher.
Here is the log file.
And here is the dxdiag.
Event Timeline
Hello kitfox,
could you please send met all Launcher logs? http://arma.jiripolasek.com/howtos.html
Hello and thank you for helping me on this here is the zip folder of the logs{F57155}
Could you please try to start it in the safe-mode and disable HW acceleration for Launcher? https://arma3.com/launcher/troubleshooting
When did you upgraded to Windows 10 Creators Update? Are you experiencing any issues with the other programs?
I tried staring it in safe mode and disabling HW acceleration but it gave me the same error
just with the safe mode parameter listed. I upgraded to windows 10 creator last week so far there have been no problems with other programs and this update.So any reason why you haven't replied in a week. pls I want to be able to play arma on this computer again.
Hello kitfox,
we're still trying to make some sense out of the error, but unfortunately it points to the core of .NET Framework (so deep that we can't reverse engineer it to see what could possible go wrong) and we haven't been able to find out any similar issues anywhere on the internet.
I've send a few questions regarding that to friends at Microsoft, but for now the cause might be anything from simple file corruption to a bug in the new .NET Framework 4.7 (which is installed in Creators Update by default).
It appears that the latest windows update has fixed the issue. What I think happened is that the because I had installed the creators update in its early stages some of the file probably got corrupted which is what broke the launcher.