CTD's in MP after 1.0.2 patch

After patching BS to 1.0.2 I've had numerous CTD's in multiplayer. It works fine in SP but always crashes after ~15-60 minutes in MP on my rig (spec. below) and wonder if anyone else is experiencing this behaviour?

Core 2 Duo E6850

Gigabyte GA-EX38-DQ6 (Rev 1.1) with F4B BIOS

2 GB Corsair Dominator CM2X1024-8500C5D

Realtek ALC889A High Definition Audio System (Driver version R2.24)

GeForce GTX 260-216 896 MB (Driver version 191.07 WHQL)

Windows XP Pro SP 2 (32-bit) with DirectX 9.0c (February 2010 release)

FLCS & TQS with Digital F22 (Driver Ver: 1.03 SWF22 Hardware Ver: 1.01)

Antec TruePower Trio 550 W PSU

Since it can happen randomly I checked my temperatures but they are well within range while playing DCS:BS...

CPU - core0 max temp 51 °C

CPU - core1 max temp 49 °C

GPU max temp 55 °C

Appreciate any help/input since this has been driving me crazy this weekend while trying to enjoy the Ka-50 on 104th's great server...

Edit: I did a clean 1.00 install then patched to 1.0.2.

/KC

Hey KeyCat, A-10 killer :D

Do you have also CRASH files? Quite many folks around have CTD problems, often with protect.dll and another ones. Maybe you have as same as Mustand has.

Hi Boberro,

Yes, I have saved the crashfiles from BS and here is what Event logger in XP says after one CTD...

Faulting application simulator.exe, version 1.2.1.0, faulting module protect.dll, version 5.70.13.2, fault address 0x00e4ab94.

DCS-20100516-102854.crash (guess this is the correct one?)

# -------------- 20100516-102854 --------------

C:\WINDOWS\system32\kernel32.dll

# E06D7363 at 7C81EB33 01:0001DB33

#

# EAX = 0012EE84

# EBX = 7C36BB92

# ECX = 00000000

# EDX = 00006E6F

# ESI = 0012EF14

# EDI = 0012EF14

# CS:EIP = 001B:7C81EB33

# SS:ESP = 0023:0012EE80 EBP = 0012EED4

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00200206

I have more crashlogs however the reported errors aren't always the same as the one above.

/KC

Similar thing has Mustang, here: http://forums.eagle.ru/showthread.php?t=53874

maybe you will find answer there.

I had problems with protect.dll also, had to reinstall game 3 times and it helped.... however still don't know what caused problem at all.

It's really hard to tell wether we're looking for a bug or a system problem when you have "kernerl32.dll" as the module that crashed.

We're nowehere closer to finding a bug causing these crashes for some of you.

Meanwhile we have to try to figure out if it's your systems.

Personally I havent had any crashes in MP, neither for DCS or FC2, nor for MP client or the MP Server.

So perhaps it's linked to your system, some software or permissions.

Could you please attach a Dxdiag report please?

There's a key to helping you with your DCS:BS - and that is correct information.

 

 

 

So when you post a problem, please attach the following:

• DXDIAG report.
  Use Start->Run: DXDIAG and "Save All Information" for the report. Upload it.
  

Thanks for your input, attached you will find my DxDiag as well as eight BS crash/error logs from this weekend.

I see Mustang has similar issues but with FC2 1.2.1. I never had any stability or CTD issues in FC2 and regulary flew the A-10 for hours and hours on end on 104th server without a hitch and there has been no other changes to my system than applying the patches.

I haven't flown FC2 1.2.1 in MP yet since I was eager to get back in the Shark but I will try that as well later tonight.

/KC

KeyCats DxDiag crash and error files.zip

Crashes happens "anywhere":

- Kernel32.dll, bin\x86\stable\AsyncNet.dll, bin\x86\stable\DXRenderer.dll

You're on Windows XP SP2, and this found in the DxDiag report:

- DirectX Files Tab: The file directx.cpl is an old version

- Nvidia driver 191.07

Unknown factors:

- StickWorks SWF22

I assume you may have a bit of combinations of problems. I would try several things:

- Get SP3 for your Windows XP, important system changes compared to SP2.

- Update the Nvidia driver

- When complete, reinstall the DirectX from here.

Thanks for your input Panzertard!

You're on Windows XP SP2, and this found in the DxDiag report:

- DirectX Files Tab: The file directx.cpl is an old version.

This is just a cpl giving a shortcut in Control Panel and never caused any issues, but sure easy to test removing it but I can assure you it's not the problem.

- Nvidia driver 191.07

Agree not the latest but WHQL and have performed rock solid and without issues in the past but I will update to latest WHQL's just to try when time permitts.

Also if it where the GPU drivers I would assume to experiencing same problems in SP as well?

Unknown factors:

- StickWorks SWF22

Thats my HOTAS (Thrustmaster FLCS & TQS with Digital F22) I've been using for the past ~10 years - old yes but works perfectly fine!

I assume you may have a bit of combinations of problems. I would try several things:

- Get SP3 for your Windows XP, important system changes compared to SP2.

- Update the Nvidia driver

- When complete, reinstall the DirectX from here.

Really can't see how SP3 would fix this MP problems. Agree that I should try with updated nVidia drivers as well as try updating the Realtek sound drivers to the latest and will do after I imaged my system.

Tonight I will try whats suggested in Mustangs thread and ALT-TAB to desktop every ~15 mins

as well as try another server (maybe it is somehow related with my connection to the 104th server, I have ~200 ms ping to that) and see what happens.

/KC

Also if it where the GPU drivers I would assume to experiencing same problems in SP as well?

No, why? Are you flying with the same amount of objects stored in memory, all the same textures, all the same system load?

You're using different API's in Windows, and different devices as well. The sum of whats going on is different.

God, dont we all hate computer systems!

And we who are used to troubleshoot always go for the most obvious problems first:

- SP3 Updates alot of system components for XP, including those who help support DirectX.

- This goes for your CPL as well, when you installed the patch DirectX should have been upgraded. This may or may not include that CPL, Dxdiag finds it problematic enough to report it.

Summary - your system could have been better updated and prepared for a newer DirectX (which includes network components for MP).

And all components in your system is working together - it's all related.

But yes, try the minimize trick - it's good to learn a bit more about this problem. ;)

:thumbup:not to munchkin that SP3 pack has the latest runtime patches and net patches not available to SP2. also your more susceptible to virus's, SP2 with no security updates. makes me a little weary to even be posting to you. your system may be infected much easier than mine. :thumbup:

Again I appreciate your efforts Panzertard but if I have a 100% rock solid system that works perfectly fine with various other games/sims (including previous versions of DCS:BS and FC2) and get problems after installing a patch for one specific sim I tend to suspect something with that new patch at first and not the whole system itself.

This is not saying that the issue can't be related to "something" in my specific OS/system/settings/etc but after reading thru your comments (all in good faith, I'm sure) for others you are pretty quick to blame the users system for anything faulty...

Anyway, bug or not, it's still early days after the BS 1.0.2 patch and if I'm alone with these MP issues indication would be towards my specific system but if others experiencing same/similar problems ED should listen and take action.

Lets wait and see if more users starts to report MP issues and maybe some pattern will emerge... Also think I must try a few other servers as well to see if my problem persists.

/KC

A quick update...

Just done a 60+ minutes Ka-50 test on 51's server and no CTD or other issues.

Fluke or maybe just my lucky day I don't know or maybe this may indicate that my CTD issue experienced this weekend is server/mission related (and Mustang and me seems to both fly primarily on the 104th server so thats a common dominator for both of us)...

I have better connection to the 51's server (~50 ms ping) and there was much less players (~5-10 during my test), more tests will follow...

/KC

Cheers, keep us updated - it would be nice to get a better idea when/why these crashes happens. :)

Just to keep ruling things out I tried 104th again last night with minimum apps/services running (i.e not loading TS etc. and also removed DirectX.cpl just for test) - 19 processes running at OS boot - but no go, got CTD's twice.

Numbers of players (network traffic/chat/events?) seems to play part - I CTD faster if server is crowded, keyword is "seems" since this issue is damn random it's hard to say for sure and I could be wrong.

Also talked with some friends (will try to get them to post here) that tried MP on 104th and in our little "group" 3 out of 5 got same/similar CTD's in FC2/BS while on 104th server.

More tests will follow, hopefully tonight when I get back home...

/KC

Tonight I'm trying ALT-TAB trick and currently 2+ hours and counting on 104th server with 32+ players and no CTD so far - lets hope it continues this way :)

/KC

To bad, same old CTD after about ~2.5 hours but this was the longest MP session I had on 104th server after the patches! I noticed that the player count started to increase from ~20 to ~40 players the last 30 minutes before the crash so...

Ohh well time will tell I guess...

/KC

To bad, same old CTD after about ~2.5 hours but this was the longest MP session I had on 104th server after the patches! I noticed that the player count started to increase from ~20 to ~40 players the last 30 minutes before the crash so...

 

Ohh well time will tell I guess...

 

/KC

Sounds remarkably similar to my situation, around 2 hours i what i can achieve in the 104th mission with regular alt-tab's, but eventually it just succumbs and crashes.

Sounds remarkably similar to my situation, around 2 hours i what i can achieve in the 104th mission with regular alt-tab's, but eventually it just succumbs and crashes.

Yes, I think we are experiencing the same problem here and whats interesting is that we have very different systems - which may rule out GFX driver issues etc...

You run Win 7 - I run Windows XP Pro

You have a ATI GFX card - I have a nVidia

My other two friends (Salsam and RedOne) also flew A-10's for a short while on 104th before they again CTD'ed, this time almost simultaneously (they where in very close proximity to each other)?

They are not active on this forum but I managed to ask Salsam if he could e-mail me the *.crash + error*.* files for comparsion. It's getting to late here now so it have to wait until tomorrow but then I will upload his files here along with their brief systems specifications...

/KC

why dont you guys make a specs list of eachothers machine up to include harddrive make model, and ram.

As promised yesterday I posted Salsams (and one of mine) crashlogs in Mustangs thread over in FC2 section since thats what he flew but I'm pretty sure we are dealing with the same issue in both sims here...

http://forums.eagle.ru/showpost.php?p=907077&postcount=42

/KC

I am having the exact same problem. I kept CTD'ing while flying on the V66th server. At first it only happend when I fired missles or missles where fired at me, but towards the end it would crash when I was coming in to land. All 4 times it crashed during our mission where all at different times. And not 5 mins before our mission, I updated to the new patch. Never had a problem whatsoever before, and it seemed like within minutes of the patch, the game is now unstable.

My Specs:

Win 7 32x

4 Gig DDR3 RAM

ATI 5770 - 1 Gig DDR5

AMD Phenom Black Edition 3.2 Dual Core

DirectX 11

I am having the exact same problem. I kept CTD'ing while flying on the V66th server.

First time I heard it happening on another server than 104th's. Dredge, if you can please also share your crashlog/s and/or details about the server including number of players, mission etc. See Panzertards post for details...

http://forums.eagle.ru/showthread.php?p=738467#post738467

Don't know if this information will help the dev's or anyone else but since I'm most likely busy the rest of the week I post the last set of crashlogs and error message received for reference...

# -------------- 20100517-185359 --------------
C:\WINDOWS\system32\kernel32.dll
# E06D7363  at 7C81EB33 01:0001DB33
#
# EAX = 0013F6C0
# EBX = 76C6EBC8
# ECX = 00000000
# EDX = 00006E6F
# ESI = 0013F750
# EDI = 0013F750
# CS:EIP = 001B:7C81EB33
# SS:ESP = 0023:0013F6BC  EBP = 0013F710
# DS = 0023  ES = 0023  FS = 003B  GS = 0000
# Flags = 00200206

# -------------- 20100517-203434 --------------
C:\WINDOWS\system32\kernel32.dll
# E06D7363  at 7C81EB33 01:0001DB33
#
# EAX = 0013EE54
# EBX = 00000000
# ECX = 00000000
# EDX = 00000000
# ESI = 0013EEE4
# EDI = 0013EEE4
# CS:EIP = 001B:7C81EB33
# SS:ESP = 0023:0013EE50  EBP = 0013EEA4
# DS = 0023  ES = 0023  FS = 003B  GS = 0000
# Flags = 00200206

# -------------- 20100517-214129 --------------
C:\WINDOWS\system32\kernel32.dll
# E06D7363  at 7C81EB33 01:0001DB33
#
# EAX = 0013F6C0
# EBX = 76AB9C48
# ECX = 00000000
# EDX = FF006E6F
# ESI = 0013F750
# EDI = 0013F750
# CS:EIP = 001B:7C81EB33
# SS:ESP = 0023:0013F6BC  EBP = 0013F710
# DS = 0023  ES = 0023  FS = 003B  GS = 0000
# Flags = 00200206

# -------------- 20100518-170034 --------------
C:\WINDOWS\system32\kernel32.dll
# E06D7363  at 7C81EB33 01:0001DB33
#
# EAX = 0013F6C0
# EBX = 703EF028
# ECX = 00000000
# EDX = 7B006E6F
# ESI = 0013F750
# EDI = 0013F750
# CS:EIP = 001B:7C81EB33
# SS:ESP = 0023:0013F6BC  EBP = 0013F710
# DS = 0023  ES = 0023  FS = 003B  GS = 0000
# Flags = 00200206

# -------------- 20100518-202606 --------------
C:\WINDOWS\system32\kernel32.dll
# E06D7363  at 7C81EB33 01:0001DB33
#
# EAX = 0013F7FC
# EBX = 7F61A168
# ECX = 00000000
# EDX = 40006E6F
# ESI = 0013F88C
# EDI = 0013F88C
# CS:EIP = 001B:7C81EB33
# SS:ESP = 0023:0013F7F8  EBP = 0013F84C
# DS = 0023  ES = 0023  FS = 003B  GS = 0000
# Flags = 00200206

# -------------- 20100518-202621 --------------
D:\Games\DCS - Ka-50\bin\x86\stable\AsyncNet.dll
# C0000005 ACCESS_VIOLATION at 03DBBC08 01:0000AC08
#
# EAX = 4F26F53C
# EBX = 00000000
# ECX = 00000000
# EDX = 5C6BF238
# ESI = 5C6BF238
# EDI = 00000000
# CS:EIP = 001B:03DBBC08
# SS:ESP = 0023:5C6BF200  EBP = 00000041
# DS = 0023  ES = 0023  FS = 003B  GS = 0000
# Flags = 00010206

Also at one time only I got the runtime error window before the CTD, see attachment.

/KC

The "pure" kernal32.dll (and AsyncNet.dll) crashes - vs the one's who has "dxrenderer" crashes seems quite different to me.

- Dxrender crash may be more connected to the virtual-world, object behaviour, onscreen representation, errors in textures or objects. (Or drivers perhaps).

- Repeating Kernel32.dll and AsynNet.dll seems more likely to be netcode / windows system oriented - or drivers for that sake.

What we now need to a way to reproduce them - at least quite often - on our own the test-rigs or ED needs to be able to do the same. :)

The funny thing (or sad) is that we have been flying just like you guys, for hours & hours - without such crashes on these servers.

So for us, we are nowhere near getting a method to reproduce the crash.

Anyone able to spot such a key factor missing in our machines compared to yours may give us the edge we need to fight such a crash.

In FC 2.0 with the patch, and connected to a server (with both BS and FC2.0 ) I also got a CTD, saying the 'simulator.exe' file crashed..

In FC 2.0 with the patch, and connected to a server (with both BS and FC2.0 ) I also got a CTD, saying the 'simulator.exe' file crashed..

..and you have nearly the same card as me, except mine's a Sapphire HD3850 AGP 512mb, i'm definately seeing a pattern here.

Heck, we nearly have the same kinda PC, here's my setup:

ASRock 4CoreDual-SATA2 R2.0 Motherboard : Sapphire Radeon HD3850 512MB AGP : Core2Duo E7500 CPU : 2 GB Dual Channel Ram : Acer P235H 23" Monitor : 400GB HD : Enermax 450W PSU