BSOD playing Bad Company 2

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?

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?

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

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

anomic said:

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.

anomic said:

MvdB said:

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:

HTML Code:

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?

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