1.2.3 Server Crash CTD

[Sov13t]

Started up our dedi server earlier this morning, it crashed.

 

Problem signature:
 Problem Event Name:	APPCRASH
 Application Name:	DCS.exe
 Application Version:	1.2.3.9871
 Application Timestamp:	512bd49f
 Fault Module Name:	Weapons.dll
 Fault Module Version:	1.2.3.9871
 Fault Module Timestamp:	512bcddc
 Exception Code:	c0000005
 Exception Offset:	0000000000011549
 OS Version:	6.1.7601.2.1.0.256.1
 Locale ID:	1033
 Additional Information 1:	6cf0
 Additional Information 2:	6cf097cf0e15fa7ccaf11da3d7a809e3
 Additional Information 3:	c5aa
 Additional Information 4:	c5aaa71a152e9d913ec61e38ef243f61

crash_log_022713.zip

Edited February 27, 2013 by Sov13t

[Sov13t]

Same exact crash again. Seems consistent.

[Hamblue]

Might want to try repair.

Also try another mission after opening and saving in mission editor.

[Wolf Rider]

c0000005 errors, usually indicate a RAM related problem

[Sov13t]

And another one. Server hardware is not the issue.

 

Problem signature:

Problem Event Name: APPCRASH

Application Name: DCS.exe

Application Version: 1.2.3.9871

Application Timestamp: 512bd49f

Fault Module Name: Weapons.dll

Fault Module Version: 1.2.3.9871

Fault Module Timestamp: 512bcddc

Exception Code: c0000005

Exception Offset: 0000000000011549

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: 6cf0

Additional Information 2: 6cf097cf0e15fa7ccaf11da3d7a809e3

Additional Information 3: c5aa

Additional Information 4: c5aaa71a152e9d913ec61e38ef243f61

 

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

 

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

[hendrick48]

So, what is an access violation, a C0000005? This is the translated #GP code the fault handler raises, which the operating system displays as an 'Access Violation', whos numerical form is c thousand 5. Its the operating system telling you that a program has malfunctioned and tried to reference no mans land. It has nothing specific to do with any particular program, or a brand of software, this is straight from the CPU and kernel of the operating system.

 

 

NOW. On to your real question, you are probably seeing a lot of these on your machine, which made you come here in search of answers. You now need to determine which program is throwing the exception. It may be several, thats certainly possible. Use Start->Run Drwtsn32 and see whats in the exception handler log. Use the event viewer, if you prefer. Once you've identified the application that is faulting, the next time it crashes on you, note where it stuck the dump (probably \windows\minidump\3279272.dmp or in C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp) and run it through the dump data analysis tool in my signature, and ill tell you why it blew up, and try to recommend what to do to fix it.

 

Linky...:Google is your friend:... http://www.windowsbbs.com/legacy-windows-os/40538-what-causes-exception-code-c0000005-access_violation.html

[159th_Falcon]

Quite interesting, our 159th Dedi server just had two crashes.

(one yesterday and one today)

And the "problem signature" in windows is exactly the same;

Server/Servman logs in attachment as well as the .crash files

 

Description
Faulting application name: DCS.exe, version: 1.2.3.9871, time stamp: 0x512bd49f
Faulting module name: Weapons.dll, version: 1.2.3.9871, time stamp: 0x512bcddc
Exception code: 0xc0000005
Fault offset: 0x0000000000011549
Faulting process id: 0xa88
Faulting application start time: 0x01ce1638b5da7a61
Faulting application path: C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe
Faulting module path: C:\Program Files\Eagle Dynamics\DCS World\bin\Weapons.dll
Report Id: 0b89e9b4-8363-11e2-824c-001f16fbb7c5

Source
DCS

Summary
Stopped working

Date
‎3/‎3/‎2013 7:55 AM

Status
Report sent

Description
Faulting Application Path:    C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe

Problem signature
Problem Event Name:    APPCRASH
Application Name:    DCS.exe
Application Version:    1.2.3.9871
Application Timestamp:    512bd49f
Fault Module Name:    Weapons.dll
Fault Module Version:    1.2.3.9871
Fault Module Timestamp:    512bcddc
Exception Code:    c0000005
Exception Offset:    0000000000011549
OS Version:    6.1.7601.2.1.0.768.3
Locale ID:    1033
Additional Information 1:    7836
Additional Information 2:    7836ac7694aaa7c528e01a518c6972b9
Additional Information 3:    fe18
Additional Information 4:    fe18e59f2b9b9f89655dcbd4f9c72b84

Extra information about the problem
Bucket ID:    97448757

159th server logs.zip

[hendrick48]

Looks like DCS is what is spitting out this error. I would reseat your ram to be sure. But stability issues have been cropping up.

[104th_Maverick]

We are seeing the same issue on the 104th server. Thanks Frostie for putting me onto this post I didn't see it before.

 

Our crash logs are identical to the crash log posted by Soviet and the window error it generates is the same.

 

I currently have an open thread in the testers section of the forum trying to deal with this bug and I'm getting help on narrowing it down as the current cause is unknown.

 

As soon as we make any headway I will post here to let you guys know!

 

S!

[159th_Falcon]

Good to know Maverick, anything we could do to help you guys nail down the problem?

[104th_Maverick]

I think so yes, but I need to wait until tomorrow when I get feedback from some people before I will know if what I want you to try is going to help or not!

 

Will let you know asap mate

 

Thanks!

[159th_Falcon]

Our server crashed again whit the same error during our squad flight.

Unfortunately i didn't have the change to install Tacview so no new data to process.

 

Good news is though that Tacview is now running and recording on our server so its only a matter of time before we have something to look at.

 

~S~

[joey45]

Could it be CA related?

[104th_Maverick]

No sorry Joey it's not sir. (happens on non CA included missions)

 

If anyone would like to help me get to the bottom of this one, here is how you can help.

 

I need people to either review or send me the tacview tracks of their session in a server that crashed with the above crash log.

 

You will not be able to do this with the Host track, it must be a clients track that is used as IIRC the host track will not work due to the crash.

 

I 'personally' (not ED themselves) think this crash is caused by one of the following:

 

A client shooting another client with a weapon,

A client shooting a ground unit with a weapon,

A client getting shot down by an A2A weapon,

A client getting shot down by a SAM.

 

 

The same crash happens on missions with and without AWACS and Tankers, which is why I think it is something client side. I have also tested the missions we have the crash on in SP and cannot recreate the crash (anyone who can recreate the crash in SP will prove me wrong), which again leads me to believe it is something client side.

 

So please gents, if possible.... get me those tracks and try to find out what is happening in the 10 seconds before the crash happens.

 

If we can get 2 or 3 different people to do this (from different servers) I'm confident we can find the cause within a day or two!

 

Thanks

Edited March 4, 2013 by [Maverick]

[ENO]

Hmmm. I just posted on two crashes in a thread just below this one- not sure if its the same thing but a mission that has never crashed before started to.

 

Ill go back into the server and grab the tacview If its the same crash.

[104th_Maverick]

I noticed that this morning ENO, I don't think the crash logs are the same so it may be a different issue.

 

 

Update from my end.... I've just found out that this crash 'may' also be cause when some AI units (not sure if ground or air yet) are activated. My money is on ground units for now.

 

I will be trying to force this issue in SP all afternoon today, will post if I find anything

[ENO]

Okay- posted it anyway...

 

I'll keep my eye open and if I do see a similar crash in the future I'll post the tacview along with the other files,

[Chippy]

I'm also getting these crashes, I haven't managed to launch DCS once since the update to 1.2.3. I noticed in the crash logs that you guys posted, "weapons.dll" seems to have something to do with it. Once my DCS crashes, I get a debrief that looks like this:

 

 

:noexpression: fuel trucks shooting 30mm rounds? There are literally thousands of weird and random events like this throughout the debriefing.

[BRooDJeRo]

That many fueltrucks being shot at? Or is it just one getting continued fired upon?

[SkateZilla]

that log makes it look like the Fuel trucks are doing the shooting.

[Chippy]

Apparently they were. It even says they shot a couple of SA-19 Grissons, and they even managed to destroy a ZU-23 emplacement according to the debrief :huh:

[SkateZilla]

i imagine it's not supposed to be like that :)

[Chazz Ulric]

Had a crash on the WarHawks server Saturday Night. Su-25 Launched a and hit a SA-10 and Ker-Blamo CTD for all 12 of us on the Server. Sorry no tracks we actually did not think anything of it at the time just a fluke ya know. Now seeing this thread it has me wondering.

[159th_Falcon]

Chazz, Could you check the following plz?

(assuming W vista or 7)

Go to start and in search type

Reliability

 

Then from the results launch the reliability monitor.

 

In it look for the date that the crash occured, and select that date.

 

Then in the bottom halve of the window you should see a number of events, including the crash.

 

right click and select "view technical details"

 

Should give you the error code similar to the ones Soviet and me posted.

 

If it is exactly the same then it could be related, if the error code is different then its an unrelated issue.

[104th_Maverick]

The crash ''appears'' to be linked to the activation of different ground units...eg

 

If you have a Target Group Alpha, with a Target Group Bravo set to activate after Alpha is eliminated, there is a 2 min delay once Alpha get's killed then the server crashes without activating the second group.

 

As I mentioned I cannot recreate this issue in SP, so it is possible it also linked to a client being in the detection range of the next target area that is being activated and any SAM units in that group will detect that client.

 

If anyone who get's the chance to review a track from a server that crashed with this crash ...

 

# C0000005 ACCESS_VIOLATION at CF0E1549 00:00000000

00000000 00000000 0000:00000000

CF0E1549 0073EE60 0000:00000000 ?getPriorityByType@cLauncher@@UEBA?BMAEBV?$cPointe rTemplate@VMovingObject@@@@@Z()+69

CF0DC083 0073EEB0 0000:00000000 ?getTargetPriority@cLauncher@@UEAA?BMAEBV?$cPointe rTemplate@VMovingObject@@@@@Z()+23

CF10D74F 0073EEF0 0000:00000000 ?getMaxTargetPriority@wWeaponSystem@@QEAA?BMAEBV?$ cPointerTemplate@VMovingObject@@@@@Z()+3F

CF118474 0073EF40 0000:00000000 ?getTargetPriority@wWeaponSystemManager@@QEAA?BMAE BV?$cPointerTemplate@VMovingObject@@@@@Z()+64

CF1187A5 0073EF70 0000:00000000 ?check_potentialTarget@wWeaponSystemManager@@QEAA_ NAEAV?$cPointerTemplate@VMovingObject@@@@@Z()+15

CF118ED8 0073EFD0 0000:00000000 ?initialSearchForPotentialTargets@wWeaponSystemMan ager@@IEAAXXZ()+108

CF1194AE 0073F0C0 0000:00000000 ?setAI_ON@wWeaponSystemManager@@UEAAXXZ()+CE

CF1EF6C8 0073F170 0000:00000000 ?setAI_ON@woCar@@UEAAXXZ()+68

CF1D6C3C 0073F2A0 0000:00000000 ?setAI_ON@wcColumn@@UEAAXXZ()+AC

CF1D3AF6 0073F2D0 0000:00000000 ?Control@wcColumn@@UEAANXZ()+26

CF739DCF 0073F310 0000:00000000 ?NextEvent@wWakeupTime@@UEAAXXZ()+2F

D6DD86A1 0073F3A0 0000:00000000

D6DD8B6A 0073F3F0 0000:00000000

C7E5B419 0073F480 0000:00000000

C7E5DEFD 0073F4E0 0000:00000000

C7E77594 0073F510 0000:00000000

C7E7746B 0073F540 0000:00000000

C7F07148 0073F5B0 0000:00000000

C7F08598 0073FAA0 0000:00000000

C7F0B11F 0073FB50 0000:00000000

E0B2167E 0073FB80 0000:00000000 BaseThreadInitThunk()+1A

E0D53501 0073FBD0 0000:00000000 RtlUserThreadStart()+21

 

 

Please confirm that is happens 2 mins after a ground unit has been killed and this activates the trigger to spawn the next target group of vehicles.