BSOD playing Bad Company 2, error code 0x00000124

[Zezzer]

Hey guys.

So recently I've been experiencing a BSOD with the above error code, but only in Bad Company 2. I've tried a multitude of fixes, including changing clock speeds/voltages etc, but no dice.

Hopefully you guys can help out..?

My rig is:

Phenom II 955 @ 3.8GHz
Crossfire AMD 6850's
8GB Kingston HyperX RAM
Seasonic 720w PSU
ASUS Xonar Essence STX

Let me know if you need anything else.

Cheers lads

 

[Zezzer]

Nothing?

 

[Arc]

Hello Zezzer.

It is a hardware related bugcheck, stop 0x124.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007611028, b2032000, 175}

Probably caused by : hardware

Followup: MachineOwner
---------

You need to follow the guide http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696.

 

[Zezzer]

Thanks for the reply. I tried most of those things on that list without any success, however I just noticed it seems to be more frequent during Skype calls... Could this have anything to do with it?

 

[Arc]

Might be. Update your network driver, make it sure that you are using the latest version of skype.

 

[Zezzer]

Hmm. Updated EVERYTHING (BIOS, drivers, Skype/other programs) and still occurring. Stress tested everything I could, RAM seems to be okay (got through multiple Windows memory tests) and now I'm at a loss.

Is there anything else I can do?

 

[Arc]

Yes, go to step #9 then.

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed. Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

Stop 0x124 - what it means and what to try.

 

[Zezzer]

Okay. I have tried every single combination of parts in my computer. The only thing I have found is that one GPU will not let the BIOS post, and that the other one /Crossfire as normal results in bluescreens. Could that mean the motherboard is on its way out? :S

 

[Arc]

Motherboard, CPU, GPU, RAM and PSU ... it amy be any of the five. In some cases it may be any other hardware seated in the other ports.

Try changing things other than the motherboard. If all yields the same result, it is the motherboard.

 

[Zezzer]

I've tried changing as much as I can. Something that did strike me as odd was the fact that this random IDE drive I have in my computer (which Windows refuses to read) needs to be plugged in so the BIOS knows to look at my SSD to boot. If its unplugged, it just tries to boot from a CD...

And there's that thing where the GPUs need to be in a certain order to get any form of POST. One GPU just refuses to allow the BIOS to post, but the other one does.

 

[Arc]

By this process, you will be able to identify the culprit hardware. If you fail at the end, let us know ... we will try to assist as much as possible.

 

[Zezzer]

Thanks.

I'm sending in my motherboard sometime soon, hopefully thats the root cause. I'm also running on one 6850, kinda awkward when I dont notice a difference in the majority of games...

 

[Zezzer]

Bumping.

Returning the mobo didn't solve it, nor did Gigabyte find any problem. Everything is stock, no other game except BC2 and BF3 crash like this. Any other suggestions?