Page MenuHomeFeedback Tracker

Arma 3 Launcher Constantly Crashing
Assigned, NormalPublic

Description

So recently my arma 3 launcher has decided to crash constantly without warning. I start up the launcher and crashes anywhere between after 5 seconds of launch and 5 minutes. I also occasionally get a system out of memory exception which is extremely strange since I have 32GB of ram.
Here are the steps I have done to try and fix the issue

  • Deleted the entire game and re-installed (Including the files in my documents and app data)
  • Verify integrity of game cache
  • Removed all anti-virus'
  • Ran steam as an administrator
  • Added" - Safe" to the launcher parameters
  • Restarted my pc about a 100 times
  • Removed all mods

Here are my system specs:
MotherBoard - MSI X99a Gaming 9 ack
CPU - I7 5930k overclocked at 4.0 GHz
Ram - Corsair Vengeance LPX 32 GB 8x4gb DDR4 2666MHZ
GPU - EVGA Geforce GTX 1080 Classified
Sound Card - ASUS Xonar DSX PCIe 7.1
Here is my launcher exception:


Any help with this matter would be really helpful. I have tried every last thing I can think of and have been searching for a fix for over 2 weeks. Arma 3 is my favorite game with over 3k hours of play time and it kills me not being able to play. Thanks in advance.

Details

Severity
Crash
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Operating System Version
10.0.14393.0 (Microsoft Windows NT 10.0.14393.0)
Category
Launcher
Steps To Reproduce

I believe it has something to do with steam mods because it seems to happen when at the bottom it tries to add a steam mod to the launcher

Event Timeline

James184 created this task.Dec 13 2016, 1:37 AM

I have noticed that if I startup my game before the launcher crashes the launcher doesn't crash until after the game closes. Not sure if this is helpful or not.

BISWizard changed the task status from New to Assigned.

Also when I boot the game with a 3rd party program like armasync the game works perfectly fine.

Hello James_Fritz,
could you please attach the complete logs from Launcher and attach them to the issue of feedback tracker? You can either get Launcher to create it from Option / Export Launcher logs to desktop, or gather them manually: http://arma.jiripolasek.com/howtos.html

Here you go

Hello James,
the logs shows that the error occurs rather quickly and is always tied to retrieving the list of running programs (Launcher searches the list for the game). It looks like a good point where to put some diagnostics, I'll update Launcher and send you a diagnostic build to gather more information about the issue.

But I also have two questions:

  1. Do you run an unusually high amount of programs / processes?
  2. Did you disabled the paging file on your computer?
James184 added a comment.EditedDec 15 2016, 5:09 AM

Thank you so much for the continued support.

  1. I wouldn't say an extremely large amount but probably more than the average user. Right now their is 92 running on my pc but that is more than I normally do.
  1. Yes I did.

Try to enable Pagefile. It fixed a problem for me earlier. Thats was some Windows problem, that wndows couldnt really work without a pagefile. I have 16 GB of RAM

Hello James,
TheMasterofBlubb is the most likely right. It is likely that the issue can be fixed by enabling the page file (because the cause would be the memory fragmentation). Could you please give it a try and re-enable the paging file?

Added a 20GB Page file and it still happening. I noticed and confirmed now that it happens everytime the pop comes up at the bottom about a mod being added to the launcher from steam.

Hi James,
could you please upload me a new log to see where the error has moved after adding the page file?

I also tried using the dev branch and performance branch with no success either.

Thank you for the logs, James.
Could you please try this version of Launcher? It's the version from previous release (1.64): http://arma.jiripolasek.com/files/Launcher_138522.zip
It should be enough to unpack it to your desktop, if the installed correctly, it should find it automatically.

That worked great!

Ok, that's great.

But I'd like to ask you for your help. So far I was unable to replicate the issue on our computers and there were lot of changes done between version 1.64 and 1.66 that could cause this either directly or indirectly. Would it be possible for you to test for me a few more version of Launcher?

Absolutely I don't mind at all. Anyway I can help BI I would be a honor. I'll do it as soon as I get home from work

Did you still me to test those other launchers for me? Also should I just use this launcher from now on?

Hello James,
yes, you're safe to use the older Launcher, at least for now. As for the other versions I want to test them before I send them to you, to not bother you needlessly, but my Steam is currently acting up and I'm trying to make it work again.

Okay no problem. If you need any other help feel free to ask. I don't mind at all.

Hello,
could you please try this version: http://arma.jiripolasek.com/files/Launcher_999901.zip ? I believe that I've pinpointed (and fixed) the problem.

James184 added a comment.EditedDec 18 2016, 9:12 PM

I tested it and everything seems to be working fine from what I can see. The only thing I noticed is that it said it was unable to find the arma executable when opening the launcher but I would assume that is because I didn't move it straight into my arma 3 folder and just ran it from my desktop.

Edit:
I copied over the files to my arma folder and it still says the same thing and I can't launch the game. My guess is because I am on the profiling build.

Hi, it's actually my fault, because it's based on the development branch version, so Launcher is expecting the 64-bit executable in the installation folder. I'm sorry, I focused too much on the problem at hand and forgot about this "little" detail. I'll fix it tomorrow first thing in the morning, but you can workaround the error message by copying the arma3.exe as arma3_x64.exe to give Launcher what it expects.

Okay no big deal! Thanks! I will most likely switch back to the dev build anyway because I prefer 64 bit.