1.2.6 Update 2 Server Crashes

[NineLine]

yes it is more stable now.. like 1.2.5, I guess.

 

2x crashes, today and yesterday:

 

Well thats better, but know the focus is still on issues causing MP crashes... so keep the info coming and know we are testing...

[159th_Falcon]

On that note, here's an 159th server crash from today during a squad flight.

I was working, so no idea what was going on in the server at the time of the crash.

1.2.6 U2 crash 1.rar

[redfish]

Three more

 

Three recent crash logs and dump files from the AEF server

CrashLogsnDUMPFiles.zip

[159th_Falcon]

Another crash from the 159th server, see attached.

1.2.6 U2 crash 2.rar

[ENO]

Another firehouse crash. I was feeling lucky there for awhile...

 

 

Problem signature:

Problem Event Name: BEX64

Application Name: DCS.exe

Application Version: 1.2.6.18933

Application Timestamp: 52507409

Fault Module Name: StackHash_232c

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 00000000

Exception Offset: 00000000ffffffff

Exception Code: c0000005

Exception Data: 0000000000000008

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

Additional Information 1: 232c

Additional Information 2: 232cf46ab2010420aa6637d14c4604b7

Additional Information 3: 3341

Additional Information 4: 3341b65378ce4c6ab078e834ccf18abe

crash 10.11.13.zip

[redfish]

CrashLog and DMP file from the AEF server

 

Crash Log and DMP file from AEF server

CrashLog_DMP_File.zip

[redfish]

Crash Log for AEF server

 

Another crash log for AEF server

Another CrashLog and DMP file.zip

[159th_Falcon]

Another one from the 159th server;

***EDIT***

added crash #4

1.2.6 U2 crash 3.rar

1.2.6 U2 crash 4.rar

Edited October 13, 2013 by 159th_Falcon

[Frostie]

<51>Server crash log, dmp file etc.

51st crash log.rar

[ENO]

Was just in TV watching when it crashed on me- weapons.dll.

 

Problem signature:

Problem Event Name: APPCRASH

Application Name: DCS.exe

Application Version: 1.2.6.18933

Application Timestamp: 52507409

Fault Module Name: Weapons.dll

Fault Module Version: 1.2.6.18933

Fault Module Timestamp: 5228d0f9

Exception Code: c0000005

Exception Offset: 0000000000014039

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

Additional Information 1: 6cf0

Additional Information 2: 6cf097cf0e15fa7ccaf11da3d7a809e3

Additional Information 3: 5cb0

Additional Information 4: 5cb05eb878378ac5e0a0875209ad8900

 

 

 

EDIT: Some additional info from someone who was in the server at the time:

I was circling over the target zone at the time, others were RTB or taking off again. One other was entering the TZ and sent out some Anti-Radiation missiles, successful hits. Suddenly the remaining say 5-7 SAMs on RWR went silent. After a minute or so I found them on TGP and then the server stopped. I didn't get any error messages or anything client side. All players were Blue force aircraft.

crash 10.13.13.zip

Edited October 14, 2013 by ENO

[redfish]

Crash Log

 

Another Crash Log

CrashLog and DMP files.zip

[ENO]

Wasn't in there for this one, but one of my regulars was in there and reported that he was in the SU25T working with the anti radiation missiles (again).

 

Sounds like we might have a connection- Anyone else know if their crashes had anything to do with SU25Ts working in a SEAD / DEAD capacity?

crash 10.14.13.zip

[redfish]

Crash Log

 

Another Crash Log

CrashLogs.zip

[redfish]

Crash Logs

 

Two more crash logs

CrashLog.zip

[ENO]

Shouldn't it be the dcs.log- not the old.log which is the mission flown before the dcs.log missiong?

 

Am I mistaken? Figured we needed:

 

dcs.log

crash.log

crash.dmp

 

SLMOD logs I include just in case-

 

Chat log

mission stats

event log

 

If requested:

 

track file

mission / .miz file.

 

To the guys looking at the logs- is there ANYTHING else we need to be providing?

[redfish]

The date time stamp of the dcs.old.log I provide is the same timestamp for the crash and DMP files : eg - 14/10/2013 1:26:49PM across all three files.

[JOKERACTS]

which GPU your server use? processor?

[ENO]

I was under the impression it's made "old" when the new dcs.log is created- Anyway, it'd be nice if someone cleared that up so we're all giving the same data.

[159th_Falcon]

Two more from the 159th server, also some things we have been noticing;

 

Client crashes when assigning a target to mortar units

Server seems to crash whit Combined Arms enabled when a client orders a large number of ground units to move.

(typically all available in the mission)

 

Then a question, i used to be able to see in the logs which player fired what weapon from what aircraft and what he hit.

This was great when someone was suspected of using cheats like R-77 on SU-33.

Or Aim-120 on KA-50's.

 

Though, as of a couple weeks, i am unsuccessful in finding this information in any of the logs.

Anyone has an idea in what log file it should be and why it may not be in there?

1.2.6 U2 crash 6.rar

1.2.6 U2 crash 5.rar

Edited October 15, 2013 by 159th_Falcon
forgot attachments

[sslechta]

Then a question, i used to be able to see in the logs which player fired what weapon from what aircraft and what he hit. This was great when someone was suspected of using cheats like R-77 on SU-33 or Aim-120 on KA-50's.

 

I think sometime in 1.2.5 or 1.2.6 that ED removed that ability. Not sure exactly when it was removed though. I think I used to access this mission screen in game through Shift + ". It was called the Mission Debrief window.

Edited October 15, 2013 by sslechta
Additions

[NineLine]

If you can reproduce the CA issues with track file that would be huge. If I get time I will log on your server and try it myself. Although I dont know if the server will save a track when it crashes, and if the server has been up for a long time its hard for the devs to sift through a 4 hour track....

 

I will make note of your causes and see if the next MP test can try them out...

 

 

Two more from the 159th server, also some things we have been noticing;

 

Client crashes when assigning a target to mortar units

Server seems to crash whit Combined Arms enabled when a client orders a large number of ground units to move.

(typically all available in the mission)

 

Then a question, i used to be able to see in the logs which player fired what weapon from what aircraft and what he hit.

This was great when someone was suspected of using cheats like R-77 on SU-33.

Or Aim-120 on KA-50's.

 

Though, as of a couple weeks, i am unsuccessful in finding this information in any of the logs.

Anyone has an idea in what log file it should be and why it may not be in there?

[159th_Falcon]

Thank's for the info, hopefully someone knows a way of enabling the logging of that data again.

 

Crucial in looking up if anyone is violating any rules.

Also, its the only way to prove someone is abusing CA by shooting down friendly planes.

[sslechta]

Right 159th_Falcon..... We used to use that for any weapons fire on our server so we've been missing that ability.

[159th_Falcon]

If you can reproduce the CA issues with track file that would be huge. If I get time I will log on your server and try it myself. Although I dont know if the server will save a track when it crashes, and if the server has been up for a long time its hard for the devs to sift through a 4 hour track....

 

I will make note of your causes and see if the next MP test can try them out...

 

As you said, track file might be problematic due to server crashing. But it kind of makes sense when you think about it.

(when this occurs its usually Async.dll which i assume has something to do whit synchronisation)

A lot of units moving at once, huge increase in load and the code simply cant keep up.

Throw in some high latency players and the chaos is complete.

(just my ignorant uneducated view on things)

 

Where should i be able to find track files of the server again? Saved Games folder?

[NineLine]

Where should i be able to find track files of the server again? Saved Games folder?

 

Yup, there should be a MP folder in the Track folder...

 

We have noticed some sync issues on our testing, but its trying to figure out of the crash is causing the sync problem or if the sync problem is causing the crash... either way we have had some luck reproducing some of the issues, its a matter of finding the point of the issue(s).