Solved BSOD playing Bad Company 2

[anomic]

Phenom II X4 955
MSI 890fx
XFX 6870
4gb Wintec AMPX DDR3
Samsung F3 500gb
Ultra X4 750w PSU
Aftermarket VGA cooler
Aftermarket CPU cooler
WIndows 7 Home 64bit

I get a blue screen every time I play BC2 online for over 30 mins. Never happens right away. Never happens in single player, and never happens in any other game or benchmark. I'm wondering if anyone can decipher my minidump and give me a direction on the action(s) to take to fix this issue.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8005028028
BCP3: 00000000B201A000
BCP4: 0000000000000175
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

 

[JaidynM]

Take a look at the following post and see if it helps.
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

99% of the time, a 124 error is caused by hardware problems. Can you update your BIOS and Chipset drivers? Could you also fill out your System Specs? The following tutorial will help you fill them.
http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

 

[anomic]

Take a look at the following post and see if it helps.
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

99% of the time, a 124 error is caused by hardware problems. Can you update your BIOS and Chipset drivers? Could you also fill out your System Specs? The following tutorial will help you fill them.
http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

System specs are filled out now. The post does help a little, as my CPU and RAM are overclocked. I tested (and continue to test) for 24/7 stability though, multiple programs. ~30 minutes of online BC2 causes a crash? Just a little hard for me to believe is all. I can play single player all day, it's only when playing in online matches.

I know my cooling is adequate, I check my temps in between matches with HWMonitor and gpu never gets over 75 Celsius and the CPU never above 54 Celsius.

The only driver/software not up to date is WIndows 7 Service Pack and my graphics card driver because there is a known bug with BC2 in the latest driver. Service Pack causing a crash? A little far fetched too.

As stated above I test my hardware with Prime95 blend test, memtest86, and the built in memory diagnostic and it checks out fine and prime95 can run indefinitely.

 

[JaidynM]

Do you have the latest patches for the game? I believe there was a V1.5 released sometime in 2009. And I'm assuming you didn't attempt steps 8 & 9 in the post I linked?

Also, when did the problem start occurring? Or was it always present?

 

[anomic]

I just downloaded the game (via STEAM) a week or so ago (give or take a few days) and played single player through twice. Yesterday I felt good enough to take it online and low and behold; crashes.

Nah didn't do 8 and 9. I clean it religiously, and I've got no other hardware to set the bar with, so to speak.

 

[JaidynM]

Right.

Take a look at the below thread. There's a couple of fixes in the first few pages. See if anything from there helps.
EA Forums

And though it will most likely do nothing whatsoever, run an sfc/scannow command in an elevated command prompt. Just in case the problem is related to some damaged or deleted system files. Repeat the command thrice with each one followed by a restart.
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[anomic]

Yes I have heard about too many "fixes" for the BSOD we all seem to experience. "It's punkbuster interfering", "it's my Gigabyte board drivers", "It's MSI Afterburner conflicting" "it's CCC conflicting".

Certain fixes seem to work for certain folks, but for myself none of those have. I was hoping my minidump had some specifics.

 

[JaidynM]

I'm not too good with minidumps so I'll see if I can get a more advanced user to read it.

 

[anomic]

I'm not too good with minidumps so I'll see if I can get a more advanced user to read it.

Thanks you've been a big help. I appreciate it.

To update a little bit, I haven't had a crash at all today (knock on wood). I changed nothing since yesterday, and nothing automatically updated or anything. Strange, consistent crashes at around the half hour mark for two days, and nil today. But I'll update if it happens again.

 

[Jonathan_King]

Hello,

Could you manually upload a MSINFO32 report for us? The jcgriff2 log seems to indicate it was created successfully, but by the time the program finished, the file was gone. Not sure what's going on there.

Enter MSINF032 into the start menu, go to File>Save, and save it as a NFO file. Zip that up and attach it to your next post.

 

[MvdB]

You have an old mouse driver, from 2007, try to find newer for your system here:
Razer Support

Maybe asked before but are you OC-ing?

 

[Dave76]

You mentioned you are OC'ing the RAM, what frequency?

D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

Did you run memtest86+?
How many passes, hours?

 

[anomic]

Update:

After not having a crash all day yesterday with mixed periods of gameplay, it started crashing again last night at around the 30 minute mark again, and again, with no changes to anything.

The NFO file is attached as requested.

Just updated the driver for my mouse, thanks for that. When I plugged it in for the first time, I trusted Windows to find and install the latest, but I guess not.

The ram is only OC'd concerning the timings which are at 7-7-7-20 right now. Stock timings are 9-9-9-24. Stock frequency is 1333 MHz.
Voltages on CPU, and CPU-NB are auto, since I'm not pushing anything and am only using the unlocked multiplier to OC my CPU (x19).
RAM voltage at 1.65.

Will be getting screenshots of CPUz right now.

 

[Lordbob75]

That stop code usually indicates a hardware problem, but here are a few things to try to narrow the problem down:

-Try removing then reinstalling the game
-Run a stress test from Prime95 for a few hours and see if that induces a crash
-Watch your temps while you play, what are you running at (and what is Idle)?
-Try dropping RAM back to stock settings to see if that might fix it
-Run a FurMark stress test to see if the GPU crashes or artefacts (and check temps)

If all that fails or has no effect, then perhaps JKing can lend some insight into it.

~Lordbob

 

[MvdB]

A wrong or faulty keyboarddriver could cause this.... test and see.

 

[anomic]

A wrong or faulty keyboarddriver could cause this.... test and see.

You may be correct. I updated my keyboard driver after the last post I made, and then went to play online. Two hours and no crash. Crazy that something so trivial may have been the culprit. It bothers me that Windows didn't alert me to both my mouse and keyboard drivers being out of date. I had to update both manually.

MvdB, what told you that it may be the keyboard driver causing the crash?

 

[Dave76]

Update:

After not having a crash all day yesterday with mixed periods of gameplay, it started crashing again last night at around the 30 minute mark again, and again, with no changes to anything.

The NFO file is attached as requested.

Just updated the driver for my mouse, thanks for that. When I plugged it in for the first time, I trusted Windows to find and install the latest, but I guess not.

The ram is only OC'd concerning the timings which are at 7-7-7-20 right now. Stock timings are 9-9-9-24. Stock frequency is 1333 MHz.
Voltages on CPU, and CPU-NB are auto, since I'm not pushing anything and am only using the unlocked multiplier to OC my CPU (x19).
RAM voltage at 1.65.

Will be getting screenshots of CPUz right now.

Set the RAM timings back to stock 9-9-9-24, for testing, if the BSoDs stop you can try a few things if you want to tighten the timings, small bump in the CPU-NB should help.
Check and let us know the CPU-NB voltage.

 

[MvdB]

A wrong or faulty keyboarddriver could cause this.... test and see.

You may be correct. I updated my keyboard driver after the last post I made, and then went to play online. Two hours and no crash. Crazy that something so trivial may have been the culprit. It bothers me that Windows didn't alert me to both my mouse and keyboard drivers being out of date. I had to update both manually.

MvdB, what told you that it may be the keyboard driver causing the crash?

Your dump shows what drivers are "on". One of them:

Lachesis.sys     Fri Aug 17 09:48:44 2007 (46C552DC)

is a familiar one. We always check the older ones anyway, but date does not say everything. I know systems to work well with a driver from '96...
Anyway, this one is a known cause if it is old and you have the wrong one (we also need to be careful if a driver is ok with W7 64B if that is the case... )

Anyway, your dump told me + a little experience....

Hope that was it and that you remain stable. A lot of times, depending on system usage, the BSOD cause varies. So if you do get more crashes in the future, please follow up on Dave with your RAM. If, after a couple of days, your happy... please mark the thread solved?

 

[anomic]

A wrong or faulty keyboarddriver could cause this.... test and see.

You may be correct. I updated my keyboard driver after the last post I made, and then went to play online. Two hours and no crash. Crazy that something so trivial may have been the culprit. It bothers me that Windows didn't alert me to both my mouse and keyboard drivers being out of date. I had to update both manually.

MvdB, what told you that it may be the keyboard driver causing the crash?

Your dump shows what drivers are "on". One of them:

Lachesis.sys     Fri Aug 17 09:48:44 2007 (46C552DC)

is a familiar one. We always check the older ones anyway, but date does not say everything. I know systems to work well with a driver from '96...
Anyway, this one is a known cause if it is old and you have the wrong one (we also need to be careful if a driver is ok with W7 64B if that is the case... )

Anyway, your dump told me + a little experience....

Hope that was it and that you remain stable. A lot of times, depending on system usage, the BSOD cause varies. So if you do get more crashes in the future, please follow up on Dave with your RAM. If, after a couple of days, your happy... please mark the thread solved?

Will do. I will play a couple more days and update. Thanks for the help everyone.

 

[Lordbob75]

A note from personal experience: The Razer drivers are a little buggy, but if you uninstall/install the drivers for the Lachesis mouse it might help.

~Lordbob