DCS 1.2.2 server crash to desktop

Hosting a simple mission, no triggers, with about 5 folks connected (P-51D, A-10C, Ka-50s) when server crashed to desktop ("DCS Stopped Working").

Unfortunately, I don't have more info on what the other clients were doing at the time - I'll get more info from the track file - but wanted to post the .crash log in case it was of any value.

# -------------- 20121111-211943 --------------

# C0000005 ACCESS_VIOLATION at 3FF2C95E 00:00000000
00000000 00000000 0000:00000000 
3FF2C95E 001EF4D0 0000:00000000 
3FEC3CA4 001EF540 0000:00000000 
3FEC238E 001EF6A0 0000:00000000 
3FEB8DFE 001EF6D0 0000:00000000 
F6738721 001EF760 0000:00000000 
F6738BEA 001EF7B0 0000:00000000 
3FF9F029 001EF840 0000:00000000 
3FFA193D 001EF8A0 0000:00000000 
3FFB9684 001EF8D0 0000:00000000 
3FFB9579 001EF930 0000:00000000 
40040498 001EF9A0 0000:00000000 
400418D8 001EFE90 0000:00000000 
400442CF 001EFF40 0000:00000000 
76E5652D 001EFF70 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D
76F8C521 001EFFC0 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

Multiplayer Crash with 1.2.2.7122

I tried several times to startup and taxi on the 104th server last night. My screen always froze before I ever completed my startup. First time seeing this since I updated to 1.2.2.7122. No other changes have been made to the system.

The program DCS.exe version 1.2.2.7122 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.

Process ID: 1360

Start Time: 01cdc058a503171a

Termination Time: 1020

Application Path: D:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe

Report Id:

Description:

A problem caused this program to stop interacting with Windows.

Problem signature:

Problem Event Name: AppHangB1

Application Name: DCS.exe

Application Version: 1.2.2.7122

Application Timestamp: 509a4ed7

Hang Signature: 309b

Hang Type: 2048

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Hang Signature 1: 309ba10c7c90635ccabb66d33040e928

Additional Hang Signature 2: c3f5

Additional Hang Signature 3: c3f5dca76583ebaa14a93c08e9240e2f

Additional Hang Signature 4: 309b

Additional Hang Signature 5: 309ba10c7c90635ccabb66d33040e928

Additional Hang Signature 6: c3f5

Additional Hang Signature 7: c3f5dca76583ebaa14a93c08e9240e2f

I've also had game freeze and the Windows event viewer shows dcs.exe application hang. Also had connection interrupted, both in mp mode on 1.2.2

DCS World is buggy cos I even have to ALT+TAB back to desktop and back to game again for the "connect" button to work in MP. Think it's because the Windows desktop resolution gets changed, which causes Windows 7 to display a message just before the connect screen shows.

Fortunately 1.1.1.1 is very stable in SP and MP modes.

Same problem for me, had that error several times:

# -------------- 20121112-184613 --------------
# C0000005 ACCESS_VIOLATION at 3FD5CFAE 00:00000000
00000000 00000000 0000:00000000 
3FD5CFAE 0015ED20 0000:00000000 
3FCF40D4 0015ED90 0000:00000000 
3FCF27BE 0015EEF0 0000:00000000 
3FCE925E 0015EF20 0000:00000000 
F97A8721 0015EFB0 0000:00000000 
F97A8BEA 0015F000 0000:00000000 
3FDCF4D9 0015F090 0000:00000000 
3FDD1DED 0015F0F0 0000:00000000 
3FDE99B4 0015F120 0000:00000000 
3FDE98A9 0015F180 0000:00000000 
3FE708E8 0015F1F0 0000:00000000 
3FE71D28 0015F6E0 0000:00000000 
3FE7471F 0015F790 0000:00000000 
7710652D 0015F7C0 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D
7744C521 0015F810 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

However, the server is still up (sometimes, often it crashes too), but no one can join the game.

This is from a mission I just ran after the update (the one today)

# -------------- 20121112-200802 --------------

# C0000005 ACCESS_VIOLATION at 4007CFAE 00:00000000

00000000 00000000 0000:00000000

4007CFAE 0012F350 0000:00000000

400140D4 0012F3C0 0000:00000000

400127BE 0012F520 0000:00000000

4000925E 0012F550 0000:00000000

EF238721 0012F5E0 0000:00000000

EF238BEA 0012F630 0000:00000000

400EF4D9 0012F6C0 0000:00000000

400F1DED 0012F720 0000:00000000

401099B4 0012F750 0000:00000000

401098A9 0012F7B0 0000:00000000

401908E8 0012F820 0000:00000000

40191D28 0012FD10 0000:00000000

4019471F 0012FDC0 0000:00000000

77B6F56D 0012FDF0 0001:0001E56D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D

77673281 0012FE40 0001:00032281 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

We have the exact same dll errors on our servers.

Exactly the same for me. I hosted a few servers over the weekend and each one crashed after a while. Had 8 - 12 people in each time.

Cant even load DCS ; mp or sp ; AppHangB1.

What to do?

Please ED put some bug detecting experts on this update.

I've been suffering way too long now from these random crashes .... is it really that hard to find bugs you have just introduced with new code?

degoe we have hit Multiplayer hard and have been striving for the best MP play possible with the current MP code. Be patient and it will come to the community.

Degoe We have posted a bunch of fixes to help minimize the crashes in that 7570 FIX sticky that's in the multiplayer bugs and problems forum- a variety of options exist to help minimize the crashes.

We've been running full time 24/7 throughout the 7570 debacle and I think I have had 2-3 actual server crashes in as many months. Of course, we've had to rip the guts out of some missions and change things around a bit... and modify our .lua configuration in the network config SLIGHTLY... most of those were to resolve connectivity errors- not server crashes.

We are ALL very quick right now to assume that ED multiplayer code is responsible for everything from disconnects to server crashes to russian meteors crashing into the earth- but sometimes this isn't the case. Granted, they're accountable for a great many of the issues- but don't let the assumption that it's MP Code related stop you from ensuring that things are in good shape on your end.

We were getting massive disconnects from the server a few months ago and we toodled along thinking it was because of code. First we thought it was because of wireless (which some part of it probably was), then we thought it was because of the router (which part of it probably was) then after we fixed that I was getting complete service drops- and the tech came in and did some ISP signal tests and found that the hardware throughout the house and at the tie in on in the box at street level was so old he had to redo almost every input connection from there to the router. NOW things are actually rolling very smooth. Sure, we get the occasional disconnect and sometimes people have issues staying connected- that's something we can't do anything about.

Anyway- if you want to have a successful server, it's a LOT of work. You don't just fire up "new server" and let it ride assuming every issue is because ED had a cat walk across a keyboard at some point during a coffee break while they were hashing out the MP code.

Please ED put some bug detecting experts on this update.

I've been suffering way too long now from these random crashes .... is it really that hard to find bugs you have just introduced with new code?

the MP stability issue is top priority.

however, if servers setup missions with the discovered work arounds,you should not be crashing that much.:joystick:

"...assuming every issue is because ED had a cat walk across a keyboard at some point during a coffee break while they were hashing out the MP code."

That is funny shizzle right thar! I don't care who you are.