Page MenuHomeFeedback Tracker

Dedicated Server Crash
Closed, ResolvedPublic


Server crash - RAR file contains RPTs and dumps for a crash that occurs upon loading a mission (custom mods are used) {F25512} {F25513} {F25514}


Legacy ID
Game Crash
Additional Information

Type: Public
Branch: Stable
Version: 1.38.128937

Version 1.38.128937
Fault time: 2015/02/01 20:12:06
Fault address: 76AE4598 01:00013598 C:\Windows\SYSTEM32\KERNELBASE.dll
file: 16AA-TRN_HR_FEB (__cur_mp)
world: Chernarus
Prev. code bytes: 75 1F 21 4C 24 10 8D 04 24 50 FF 15 2C 63 B9 76
Fault code bytes: 8B 4C 24 54 33 CC E8 11 A7 FF FF 8B E5 5D C2 10

EAX:0280AE90 EBX:00000005
ECX:00000005 EDX:00000000
ESI:0280AF54 EDI:00000001
SS:ESP:002B:0280AE90 EBP:0280AEE8
DS:002B ES:002B FS:0053 GS:002B


note: Minidump has been generated into the file C:\Games\Arma3\Logs\server\arma3server_2015-02-01_10-00-02.mdmp

Event Timeline

LondonLad edited Steps To Reproduce. (Show Details)Feb 1 2015, 9:49 PM
LondonLad edited Additional Information. (Show Details)
LondonLad set Category to Game Crash.
LondonLad set Reproducibility to Always.
LondonLad set Severity to None.
LondonLad set Resolution to Open.
LondonLad set Legacy ID to 4224090797.May 7 2016, 8:12 PM
LondonLad added a subscriber: LondonLad.

Uploaded another v1.38 Server Crash (.zip)

You have a bunch of mods that are conflicting as well. Does it crash if you disable all mods?

as Killzone_Kid says, is it possible to disable the mods you are using?

While we haven't attempted to run it without our set of mods (which was updated). We suspect it is one of the mods that has caused the issue.

The purpose for reporting this is that is crashes the dedicated server exe (blah blah has stopped working).

It was suggested by one of our group members that it seems to be a possible 'clipping' issue with an object 'clipping' on the 'Chernarus' map.

Because its a hard crash of the Dedicated server I think it's worth the BIS Devs taking a look to see if there's anything that can stop the server from 'crashing' and do something different to warn of errors in this instance.

Nailed what the mod issue was...


Seems one of the PBO's (ATLAS_Weapons.pbo) wasn't correct (not the mod makers fault but possibly internally to our group when sorting our mod pack out).

We had to re-pack the ATLAS_Weapons.pbo and include it back into our mod.

This seems to have resolved the problem.

Still I believe this should have a developer look into ways of reporting it into the RPT rather than having the server crash.

Another 1.38 server crash....

File added: arma3server_2015-02-03_12-56-17.rar

Some what related to the above issues reported but in this case with the sig keys.

Sig keys signed for the mod doesn't connect to the steam servers on this Windows 8 Enterprise x64 dedicate server system (but DOES when run from a Windows 7 Enterprise x64 or Windows Server 2008 R2 dedicated server). Weird one. Usually it doesn't provide a crash dump/rpt but in this case I terminated the session 'wait chains' which prodcued the RPT and Dumps.

Crash also occurs in the latest performance exe (1.38_perf_v2)

Crash File attached:

I believe a resign of the keys resolved the issue for the particular mods key which wasn't working/corrupted.

dedmen closed this task as Resolved.May 20 2020, 3:52 PM