Arma3Server.exe has stopped working - ntdll.dll error
When using arma3server to play test dedicated server missions (using Resistance by KLincheloe) and no mods other than curator and kart; the program stops working either just after i join the sever or before i even launch arma. I recently tried the BIS mission Escape Altis and the dmp files are attached below.
Have checked integrity of install files. Checked I have updated sound files and video drivers (nvidia) and physx.
I have reinstalled all the redist files in the amra 3 install folder (c++, .net and directX)
I have even deleted arma3.exe and arma3server.exe and verified cache again.
I have launched with command line empty and my usual "-nosplash -skipintro".
I have launched the game from within steam. I have checked the mods are loaded in the configure menu under expansions and only A3, Karts, zeus and DLCBundle are showing.
I am getting a server only crash every time i run from 10 seconds to a couple of minutes into opening the program. I can play for hours in MP games with no crashes at all.
I usually run the server using TASDT, but i have also run arma3server.exe with no config file (server.cfg) from the install directory still no success.
To check if it is a HDD issue i have installed arma 3 server from steam on a different drive and allowed all files to download. No success.
I set up the server to include and exclude curator and kart folders and both crash.
I tried leaving the server running with no mission selected and within a few minutes it crashed out as well.
I have done windows memory diagnostics and found no faults with that.
The crash .rpt file names either Kart, A3 or DLCBundle as the mod it cannot cope with and it is always syswos64\ntdll.dll that is the file causing the crash.
filed attached.
.mdmp
.rpt
.bifdmp
I have no issues with running the game itself and this appears to be a recent failure of the arma3server.exe
i have tested on the recent update and although it lasted longer than 10 minutes it still crashed.
I have recently tested -malloc=system and found the same issues as I noticed the server kept using tbb4 {F24864} {F24865} {F24866}