BF:BC2 CTD Very Often

[Baasha]

So over the last few days, I've been getting back to trying vanilla BC2. About 20 minutes in, the game freezes and crashes to desktop (CTD). Sometimes, it does it when I press 'Tab' to check scores but yesterday it crashed just randomly.

The strange thing is, I play Vietnam for a couple of hours straight and there isn't a single hitch. So I'm not sure what's going on (?).

I've tested it out several times and it only crashes when I play vanilla BC2.

Here is the xml crash report:

<?xml version="1.0" encoding="UTF-8"?>
-<report><version>2</version><sessionid>38fb22844dc0f247</sessionid><type>crash</type><sku>ea.dice.RomePC.Cl</sku><createtime>2011-05-04 06:59:22</createtime><buildsignature>602574</buildsignature><systemconfig/><categoryid> 0x62DE96</categoryid><stack> 0x62DE96 0xD42FB7 0x2FFFF 0xD49BAD 0xD5D2CE 0xD5D948 0xD437C0 0xE13E3F 0xD482F0 0x140D4D8 0x97197E 0x63C102 0x76B01725 0x5DD660 0x76A06D91 0x76A06D51 0x76A06CE9 0x76A06D91 0x1546050 0x41A622 0x41A622 0x41B0EF 0x2A9385B 0xE0ACFB 0xE537CA 0xE5A33D 0xD76B61 0xD76B6F 0x76B01725 0x76B01725 0x63C6B9 0x51DCEB 0x76B01136 0x51DEF9 0x1699234 0x1699234 0x1699234 0x75360849 0x1699234 0x5198FE 0x5198FE 0x155FA10 0x521056 0x155FA34 0xA493E8 0x14D9A58 0x735729BB 0x155FA10 0x73578CED 0x73572A47</stack><threads/><screenshot/><memdump/><contextdata>registers: Edi 0973a090, Esi 00000000, Ebx 00000000, Edx 00000000, Ecx 0d1bb350, Eax 1bf104a8 Ebp 0e91fa50, Eip 0062de96, Esp 0e91fa40</contextdata></report>

Here are the settings in settings.ini:

[WindowSettings]
Width=8100
Height=1600
Fullscreen=true
RefreshRate=59.972
VSync=false
[Sound]
Quality=high
VoipEnable=true
SpeakerCount=0
[Graphics]
Effects=high
Soldiers=high
Vehicles=high
Overgrowth=high
Undergrowth=high
StaticObjects=high
Terrain=high
Shadows=high
Bloom=true
HSAO=false
MSAA=1
Water=high
MainQuality=custom
Texture=high
DxVersion=11
Aniso=4
Detail=high
RenderAheadLimit=2
Fov=55

Can someone help me with this? Are others having similar/same issues in BC2? I play Bulletstorm as well and there are no issues whatsoever with that game so I know it's specific to vanilla BC2.

 

[Bill Brasky]

Have you manually updated punkpuster? Verified game files? Updated video card drivers?

http://www.evenbalance.com/index.php?page=support-bc2.php

 

[Baasha]

Have you manually updated punkpuster? Verified game files? Updated video card drivers?

http://www.evenbalance.com/index.php?page=support-bc2.php

Thanks for that.

I just updated the PunkBuster service.

I won't be playing until later today but I will test it out and see if that was the issue. FWIW, my old PunkBuster service was version 0.968 or something like that and the new one is version 3.4! LOL.. so yes, updating it must definitely help.

 

[gonzal13]

Are you overclocked? Is your ram running at other than rated speeds? Have you run memtest86?

 

[43st]

Turn off MSI Afterburner before playing.

 

[Bill Brasky]

Turn off MSI Afterburner before playing.

Definitely something to try, but FWIW I leave Afterburner on while gaming and everything is fine. Just saying it's not always the culprit.

 

[Zargon]

you arent running eyefinity are you?

 

[gonzal13]

you arent running eyefinity are you?

Width=8100
Height=1600


Just guessing, but I think thats a yes?

 

[Baasha]

Guys,

Thanks for the advice but there isn't much luck here.

I updated PunkBuster to the latest version and tried playing and it seemed fine for about 20 mins and then it crashed to desktop again. :thumbsdown:

I am overclocked (4.41GHz on a 990X) but my GPUs are NOT OC'd (2x GTX-590s @ 630MHz).

I am running NVidia Surround at 8100x1600 but I have no issues with Vietnam, Bulletstorm, Dead Space 2, TF2, etc. etc. So I know it's some issue specific to Vanilla BC2.

This is so frustrating.

Any other suggestions?

Please help!

 

[bunnyfubbles]

I've owned BC2 and Vietnam as soon as they came out and is by far my most played game within the past year. I could probably count the number of crashes or incidents I had with the game on one hand...that is until about a week or two ago when I started getting more CTDs in that extremely short span than I had ever experienced in the year preceding that.

The only thing different was I had updated my drivers. At first I thought it might be a combination of drivers + SLI but I recently moved from 2x GTX470s to a single GTX580 and occasionally still get a CTD

it doesn't happen to me as nearly often as it is happening to you but I'd wager that it is driver related and that you're exacerbating the problem by running 4x GPUs and such an extreme resolution.

btw, what kind of setup results in 8100x1600

 

[duragezic]

You definitely need to try running everything at stock. I know when you have an overclock that works fine in tests and in all your games, but sometimes there is that one game that just doesn't like it.

It's probably not going to fix it but I don't think you can ever really troubleshoot a crash without first running everything at stock speeds.

 

[ader098]

Bfbc2 is very sensitive to cpu overclocking, try lowering your oc to 4.2ghz
and see if the ctd's stop.

 

[imaheadcase]

I'm going to guess the OP you tried disabling surround, and one GPU only to rule that out?

I would venture a guess that is the problem, as with most games.

 

[bunnyfubbles]

Bfbc2 is very sensitive to cpu overclocking, try lowering your oc to 4.2ghz
and see if the ctd's stop.

I've run BC2 on 3 different rigs with 3 different CPUs and 3 different GPUs (plus an SLI option) spanning from 8GB of DDR2 to 24GB of DDR3 and have never had a problem with any sort of issue related to overclocking

I had a Q9450 @ 3.4GHz + Radeon 5850 @ 900MHz, no reoccurring problems

I had an i7 930 @ 4GHz + GeForce GTX470 @ 750MHz, no reoccurring problems

(even had a stint in between with 2x SLI GTX470s)

I now have an i7 2600K @ 4.8GHz + GeForce GTX580 @850MHz, again, no reoccurring problems, at least not until the latest driver came out.

That being said, I am (along with many ATers) not the average overclocker in that I don't settle for "stable enough", I make sure my overclocks pass the most grueling stress tests for hours on end, ie 12-24+

I also don't push my hardware too far because there's always a point of extremely diminishing returns. An extra couple MHz for several hundred watts more just isn't worth it. For instance I can actually hit 5GHz on my 2600K with voltage and temps that really won't kill the CPU before I ultimately replace it with a Bulldozer or SandyBridge-E, but to get there it will burn so much more power under load with the extra voltage required to ensure stability, and the performance just isn't worth it to me for what is nothing other than bragging rights. The same is true of my other CPUs and GPUs - I could easily hit 1GHz+ on my 5850 (especially with my Accelero S1 + 120mm fan) but again it just wasn't worth it IMO.

I really have never seen a game or other program that would be unstable after my rig passed my stress testing.

If the OP is in the same boat as I am with his hardware testing I really think its far more likely its a software conflict, likely with the drivers.

 

[Zargon]

Width=8100
Height=1600


Just guessing, but I think thats a yes?

LOL yeah, either I was mostly asleep or he added all that info AFTER my post. either is a viable theory

I know eyefinity + bc2 after the last patch = CTD for me

 

[gonzal13]

Guys,

Thanks for the advice but there isn't much luck here.

I updated PunkBuster to the latest version and tried playing and it seemed fine for about 20 mins and then it crashed to desktop again. :thumbsdown:

I am overclocked (4.41GHz on a 990X) but my GPUs are NOT OC'd (2x GTX-590s @ 630MHz).

I am running NVidia Surround at 8100x1600 but I have no issues with Vietnam, Bulletstorm, Dead Space 2, TF2, etc. etc. So I know it's some issue specific to Vanilla BC2.

This is so frustrating.

Any other suggestions?

Please help!

Because you confirmed you are overclocking. I think you should test your memory and cpu for errors. Do you know how to do this?

I had problems with BC2 inexplicably CTD'ing like you and I found it was that my ram timings were off. I changed one setting and then I've never had a crash again.