multiplayer client crash and cannot rejoin mission attached

[Devilman]

cause: AI AIRCRAFT LANDS PARKS AND POWERS DOWN.. at full power down lights off client crash to desktop.

 

tested on su-27 and su-24mr

 

test mission is attached reproduced error on 'demand'.

TEST.miz

[AussieM8]

Hi all, Does anyone know if this crash has been acknowledged by the Devs/ED?

 

Windows 7 x64, i7-3770k OC 4.4GHz with Noctua NH-D14 CPU Cooler ,ASRock Z68 Fatal1ty Pro Gen 3

G.Skill Ripjaws 16gig DDR3,, Gigabyte HD7970 GHz Egition 3GB, HOTAS

Warthog,Saitek Combat Pedals and TrackIr 5

Using Deadman's Covers and Metalnwood's extension.

Edited November 13, 2012 by AussieM8

[159th_Viper]

Logs please, Gentlemen.

[JesseJames38]

Just tryed this with Devilman today. Issue is still present. After the AI aircraft shuts down. the clinets are booted "DCS has crashed" as for the Logs. i dont know where they are even located to even send them.

 

Jesse.

[IvanK]

I was getting Multiple client crashes today on line on the 104th server. Others were reporting it as well. No idea as to the cause but this might be it.

 

My logs attached. last mission in this log it didn't crash however.

Logsmpcrash.zip

[JesseJames38]

i Just whent and looked in there. I found no crash log for todays date. last crash log i have was from the 13th of november. this crashed today on the 17th. Log file has not been created.

 

Jesse

[Kuky]

I had crash flying on 104th also, but I got that program was shut down due to system resources (memory) being low... I have 16GB of RAM so that's can't be it, also Grimes was on same server at the time and said he saw many other people gone from 104th server at exact same time as well so it couldn't be me being low on RAM... I had o crash log file.

 

DCS World (and FC3) really have lot of bugs ATM.

[Devilman]

dont mean to dismiss anybodys errors, but the crash that i am reporting here is only on the mission i have posted. i have repoduced the same condition in other missions and once again tonight..

 

i have also ruled out the helicopters do not produce this condition.

 

to reproduce your error to be exact you would need to refly it to the same point and look for a AI airplane landing / and then full power off (lights out)

[Devilman]

here is the attached logs

 

crash logs from clients

 

DCS-20121117-112745.crash from aussiem8 (su-33)

DCS-20121117-112735.crash from scoot (a-10c)

 

log files from host (me)

 

track file of mission

 

original mission

DCS-20121117-112735.zip

[IvanK]

Pretty much cant get On line at all without lock up or crash. Off line no problems. Logs attached as Logscrash.zip

Went back and joined FC2 server without any issues.

Joined Cliffs of Dover On line session no issues.

Joined IL2 On line no issues.

Joined ROF server no issues.

 

All my logs look similar to this with Access Violation and in the last line reference to ntdll.dll:

 

"# -------------- 20121118-071931 --------------

 

# C0000005 ACCESS_VIOLATION at 3F99E28E 00:00000000

00000000 00000000 0000:00000000

3F99E28E 001DF1E0 0000:00000000

3F935924 001DF250 0000:00000000

3F93400E 001DF3B0 0000:00000000

3F9332AE 001DF3E0 0000:00000000

F5F98721 001DF470 0000:00000000

F5F98BEA 001DF4C0 0000:00000000

3FA0FF19 001DF550 0000:00000000

3FA1294D 001DF5B0 0000:00000000

3FA29DD4 001DF5E0 0000:00000000

3FA29CC9 001DF640 0000:00000000

3FAB0A78 001DF6B0 0000:00000000

3FAB1EB8 001DFBA0 0000:00000000

3FAB48AF 001DFC50 0000:00000000

7732652D 001DFC80 0001:0001552D F:\Windows\system32\KERNEL32.dll BaseThreadInitThunk()+D

7745C521 001DFCD0 0001:0002B521 F:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21"

------------------------------------------------------------------------------------------------

 

And looking at both of S77th-Devilmans Crash logs in Post 10 above it looks almost identical to mine same reference to ntdll.dll.

So there is a common issue here on 3 different PC's and different servers (in my case). So I don't think its Mission dependent rather a fundamental issue with DCS/FC3 multi player mode.

 

# -------------- 20121117-112745 --------------

 

# C0000005 ACCESS_VIOLATION at 3FD4E28E 00:00000000

00000000 00000000 0000:00000000

3FD4E28E 0027F1B0 0000:00000000

3FCE5924 0027F220 0000:00000000

3FCE400E 0027F380 0000:00000000

3FCE32AE 0027F3B0 0000:00000000

F8F88721 0027F440 0000:00000000

F8F88BEA 0027F490 0000:00000000

3FDBFF19 0027F520 0000:00000000

3FDC294D 0027F580 0000:00000000

3FDD9DD4 0027F5B0 0000:00000000

3FDD9CC9 0027F610 0000:00000000

3FE60A78 0027F680 0000:00000000

3FE61EB8 0027FB70 0000:00000000

3FE648AF 0027FC20 0000:00000000

7722652D 0027FC50 0001:0001552D C:\Windows\system32\KERNEL32.dll BaseThreadInitThunk()+D

7766C521 0027FCA0 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

 

And from Scoots crash log again in Post 10:

 

# -------------- 20121117-112745 --------------

 

# C0000005 ACCESS_VIOLATION at 3FD4E28E 00:00000000

00000000 00000000 0000:00000000

3FD4E28E 0027F1B0 0000:00000000

3FCE5924 0027F220 0000:00000000

3FCE400E 0027F380 0000:00000000

3FCE32AE 0027F3B0 0000:00000000

F8F88721 0027F440 0000:00000000

F8F88BEA 0027F490 0000:00000000

3FDBFF19 0027F520 0000:00000000

3FDC294D 0027F580 0000:00000000

3FDD9DD4 0027F5B0 0000:00000000

3FDD9CC9 0027F610 0000:00000000

3FE60A78 0027F680 0000:00000000

3FE61EB8 0027FB70 0000:00000000

3FE648AF 0027FC20 0000:00000000

7722652D 0027FC50 0001:0001552D C:\Windows\system32\KERNEL32.dll BaseThreadInitThunk()+D

7766C521 0027FCA0 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

 

EDIT

A 4th PC with Kukys report in post 13 below ... same sort of issue almost identical crash report.

Logscrash.zip

Edited November 18, 2012 by IvanK

[Kuky]

IvanK, I got one of those also:

# -------------- 20121117-065152 --------------

 

# C0000005 ACCESS_VIOLATION at 3F4FE28E 00:00000000

00000000 00000000 0000:00000000

3F4FE28E 0023EEE0 0000:00000000

3F495924 0023EF50 0000:00000000

3F49400E 0023F0B0 0000:00000000

3F4932AE 0023F0E0 0000:00000000

F64E8721 0023F170 0000:00000000

F64E8BEA 0023F1C0 0000:00000000

3F56FF19 0023F250 0000:00000000

3F57294D 0023F2B0 0000:00000000

3F589DD4 0023F2E0 0000:00000000

3F589CC9 0023F340 0000:00000000

3F610A78 0023F3B0 0000:00000000

3F611EB8 0023F8A0 0000:00000000

3F6148AF 0023F950 0000:00000000

76DE652D 0023F980 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D

7738C521 0023F9D0 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

[IvanK]

Keep posting Gents I think we are on to something :)

[ФрогФут]

According to logs, the issue is already fixed and should be included in the next update. Sorry for inconvenience.

[IvanK]

Great news Spasiba

[BIGNEWY]

According to logs, the issue is already fixed and should be included in the next update. Sorry for inconvenience.

 

thanks ФрогФут and the ED team, great news :thumbup:

[ФрогФут]

Just to be sure: is there any A-10C in the mission, used on the crashed server?

[PoleCat]

Yes our 104th missions do contain A-10 AC.

 

Out

[Devilman]

Just to be sure: is there any A-10C in the mission, used on the crashed server?

 

yes the mission that i originaly picked up the error had A-10c, yes those clients crash to desktop.