SilentSean Posted December 24, 2014 Report Share Posted December 24, 2014 Since the update, Ive been getting this error: Distribution: 0 Version 1.36.128579 Fault time: 2014/12/24 12:57:34 Fault address: 71E69EFD 01:00018EFD C:\arma3Servers\Spec3 A3Epoch\@EpochHive\epochserver.dll file: epoch (__cur_mp) world: Chernarus Prev. code bytes: 83 C4 04 85 C0 74 09 50 E8 D1 80 02 00 83 C4 04 Fault code bytes: 83 3F 06 8B 45 D0 0F 85 A2 00 00 00 C6 00 00 8B Registers: EAX:00000000 EBX:00B5943C ECX:00B3246C EDX:00B32488 ESI:00A5BF80 EDI:00000000 CS:EIP:0023:71E69EFD SS:ESP:002B:00A5BE5C EBP:00A5BF60 DS:002B ES:002B FS:0053 GS:002B Flags:00010246 I run a dedicated box with Windows Server 2008 R2 DC Edition. Only been getting this since the patch Link to comment Share on other sites More sharing options...
0 Richie Posted December 24, 2014 Report Share Posted December 24, 2014 You replace the old .dll with the new .dll ? Link to comment Share on other sites More sharing options...
0 SilentSean Posted December 24, 2014 Author Report Share Posted December 24, 2014 Yeah, I deleted the hive folder then copied the new one over Link to comment Share on other sites More sharing options...
0 Spec-CrazyG Posted December 26, 2014 Report Share Posted December 26, 2014 now have 2 servers with this issue... no suggestions from anyone, not even devs?.. I'm sure we are not the only ones with this/or seen this issue. Link to comment Share on other sites More sharing options...
0 Santa Posted December 26, 2014 Report Share Posted December 26, 2014 What does your A3Master_xxxxx.log contain? pastebin.com Link to comment Share on other sites More sharing options...
0 MisterT Posted December 27, 2014 Report Share Posted December 27, 2014 paste server,client rpt and check your event logs. Link to comment Share on other sites More sharing options...
0 SilentSean Posted December 28, 2014 Author Report Share Posted December 28, 2014 Apologies for the late reply, been busy the last few days. Here is the server RPT: http://pastebin.com/B1v2ppBq Client RPT and A3Master don't have anything pertaining to the crash Link to comment Share on other sites More sharing options...
0 nedfox Posted December 29, 2014 Report Share Posted December 29, 2014 yours : "C:\arma3Servers\Spec3 A3Epoch\arma3server.exe" -nosplash -nosound -mod=@Epoch;@EpochHive;@AllInArmaTerrainPackLite; "-config=C:\arma3Servers\Spec3 A3Epoch\Spec3A3Epoch\config.cfg" -ip=162.219.28.242 -port=3302 "-profiles=C:\arma3Servers\Spec3 A3Epoch\Spec3A3Epoch\Spec3A3Epoch\" "-BEpath=C:\arma3Servers\Spec3 A3Epoch\Spec3A3Epoch\BattlEye" "-cfg=C:\arma3Servers\Spec3 A3Epoch\Spec3A3Epoch\basic.cfg" -name=Spec3A3Epoch -autoinit -enableHT -exThreads=1 -loadMissionToMemory Fixed : "C:\arma3Servers\Spec3 A3Epoch\arma3server.exe" -config="C:\arma3Servers\Spec3 A3Epoch\Spec3A3Epoch\config.cfg" -ip=162.219.28.242 -port=3302 -profiles="C:\arma3Servers\Spec3 A3Epoch\Spec3A3Epoch\Spec3A3Epoch" -BEpath="C:\arma3Servers\Spec3 A3Epoch\Spec3A3Epoch\BattlEye" -cfg="C:\arma3Servers\Spec3 A3Epoch\Spec3A3Epoch\basic.cfg" -name=Spec3A3Epoch -malloc=system -mod=@Epoch;@EpochHive;@AllInArmaTerrainPackLite The quotes not good ! Also, the HT, threads and other params are not epoch stock. Not needed. Link to comment Share on other sites More sharing options...
0 SilentSean Posted December 30, 2014 Author Report Share Posted December 30, 2014 Those are the exact same parameters I have always used, which were working absolutely fine before the patch. But out of curiosity, I tried those ones, and it still does the same thing. I even moved it to a box where I have another server running fine with no crashes, then I try Chernarus and bam, it crashes again. Link to comment Share on other sites More sharing options...
0 nedfox Posted December 31, 2014 Report Share Posted December 31, 2014 FYI, I'm testing on my test server since we had issues since we introduced AI missions. For now, my focus is on "mounting" static .50 cal guns that missions spawn. When someone gets in, server crashes. if possible, get a test environment up and try to figure out WHEN your server crashes. I will also keep everyone updated here with my findings. Link to comment Share on other sites More sharing options...
0 SilentSean Posted December 31, 2014 Author Report Share Posted December 31, 2014 We are running stock Epoch I have been trying to figure out what is causing the crash. I've been in the server alone, and it doesn't crash on any particular thing. It's crashed when I was in a heli, driving and running in a field etc Link to comment Share on other sites More sharing options...
0 nedfox Posted December 31, 2014 Report Share Posted December 31, 2014 After testing few hours, it's not the mission. FYI, I run a separate batchfile to kill the popup and auto restart : ======================== echo off :start taskkill /f /im werfault.exe timeout 10 goto start ===================== Link to comment Share on other sites More sharing options...
0 SilentSean Posted December 31, 2014 Author Report Share Posted December 31, 2014 We must have different crashes then, because I can run Bornholm without any crashes. I run Arma as a windows service, so I have a custom tool I made to bring it back up if it crashes Link to comment Share on other sites More sharing options...
0 nedfox Posted December 31, 2014 Report Share Posted December 31, 2014 Yeah, firedeamon ftw :) but the batchfile makes sure it restarts even without an admin nearby :) Link to comment Share on other sites More sharing options...
0 SilentSean Posted January 1, 2015 Author Report Share Posted January 1, 2015 It's not firedaemon, it's a little tool I found on these forums somewhere (can't remember where). As for restarting on crash, I wrote a little keep alive program in C# which I have running as a service. It polls every so often checking for the Arma and Bec services, if they are off then it just starts them. No need to do anything on a box reboot either, all the services start with windows :) Link to comment Share on other sites More sharing options...
Question
SilentSean
Since the update, Ive been getting this error:
I run a dedicated box with Windows Server 2008 R2 DC Edition. Only been getting this since the patch
Link to comment
Share on other sites
14 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now