Page MenuHomeFeedback Tracker

Server Crash after Update
Reviewed, NormalPublic


After launching the server, the console loads up then crashes.


Operating System
Windows 10 x64
Operating System Version
Windows Server 2016 x64 OS Version 10.0.14393
Steps To Reproduce

Using TADST v3.1.0 server tool to launch the server with mods = crash
Same method but with no mods = crash
Same method above but with no mods, and no battleye = crash
Validate Files = Crash
Installed from new directory = crash
Tried launching the server from arma 3 directory in the steam folder = crash
Even tried running in admin mode = crash

Additional Information

Log file displays this:
Fault address: 29530000 00:29530000 Unknown module
world: Tanoa
Prev. code bytes: DB 48 0F 44 1D 5F 87 88 00 48 8B CB EB 0A FF C8
Fault code bytes: 44 38 11 74 07 48 FF C1 85 C0 75 F2 2B CB 89 4C


Process Name: arma3server_x64.exe : D\Steam\steamapps\common\Arma 3\arma3server_x64.exe
Process Architecture: x64
Exception Code: 0xC0000005
Exception Information: The thread tried to read from or write to a virtual address for which it does not have appropriate access.
Heap Information: Not Present

Event Timeline

Cruisie created this task.Nov 30 2017, 6:35 PM

I can launch the server without TADST, with no config, does not crash.

Cruisie added subscribers: cup, ares.Nov 30 2017, 8:37 PM

I deleted the expanson folder (apex dlc) and got this in the rpt file after the server crashed:

Mods: A3;curator;kart;heli;mark;expansion;jets;argo;orange;tacops;dlcbundle;dlcbundle2;@SW 501st;@501st Map Pack;@ACEX;@Advanced Rappelling;@Advanced Urban Rappelling;@ares Mod - Achilles Expansion;@CBA_A3;@cup Terrains - Core;@cup Terrains - CWA;@cup Terrains - Maps;@Enhanced Movement;@MCC Sandbox 4 - Mission Making The Easy Way;@Operation- TREBUCHET;@Opposition [Maps Pack];@Opposition ACE;@task_force_radio
Distribution: 0
Version 1.78.143717
Fault time: 2017/11/30 12:34:24
Fault address: 52B30000 00:52B30000 Unknown module
world: Malden
Prev. code bytes: DB 48 0F 44 1D 5F 87 88 00 48 8B CB EB 0A FF C8

Fault code bytes: 44 38 11 74 07 48 FF C1 85 C0 75 F2 2B CB 89 4C

auto intit <---- that is broken, disabling it fix the issue

As stated above, autointit removed from parameter line fix the issue for one guy, sadly I'm still having the same issue on my server box - all four servers crash on Dedicated Host Creating

Kirumy added a subscriber: Kirumy.Dec 1 2017, 10:46 AM

Glad to see I'm not the only one having this issue. Anyone got a solution at this time?

To expedite this, I would like to add additional information. I attempted to launch the server with no mods, just vanilla from both the ArmA 3 launcher, tadst and a batch file and had the same issues. I rolled back to a previous version and updated; I still have the same problem.

*Deep, irritated sigh*

Okay, I found the problem. Don't use -netlog.


Yep, disabling netlog seems to work. Another "great" update, another coop cancelled.

Good stuff. Well done Kirumy.
If this update had bought us loads of stuff or fixes, I wouldn't mind, but the last two DLCs have given us a van and broke the servers. What a crock of shit.

Wulf changed the task status from New to Reviewed.Dec 1 2017, 1:11 PM
Wulf added a subscriber: Wulf.


Thank you for the report. I see in your reports a Status Access Violation. Please try these possible solutions:

  • Try joining another server, then rejoin the previous one.
  • Update the graphics card drivers to a newer version.
  • Rollback the graphics card drivers to an older version.
  • Check the temperature of your GPUs and CPUs.
  • Verify the integrity of the game cache using Steam.
  • Re-install DirectX.
  • Uninstall the Visual C++ 2013 Redistributable package (both x86 and x64 version), restart your computer and install the package again (do not use the Repair function).
  • Run a Windows System File Check tool to repair corrupted system files.

We will also have a look at this issue.

This comment was removed by Wulf.

Greetings from ar*e.

Guess our server from Fragnet is going to be having an extended downtime since this game server provider is forcing the -netlog server startup parameter. User can not remove it from the commandline because the GSP is not providing any means to do so.

So it'll be the whole weekend + how many days come the next week when we will be seeing our server up and running again(??)

Yes, found out that -netlog is causing the server to crash, I would say this is a bug.

Wulf added a comment.EditedDec 7 2017, 4:34 PM


There should be a new update with a fix for problems with ports and BattlEye, could you please let us know if the issue still persist?

Thank you.