BSOD playing Battlefield: Bad Company 2

Satirelol said:

Why wouldn't they be running at 100%? Intel Burn is designed to test CPU stability.
As for the verifier, I already disabled it since that tutorial mentioned I should disable it after a BSOD. So right now the panel is empty.

However, I had everything ticked except "Low Resource Simulation" so it should have worked.

My oversight sorry. I totally zoned out and missed cpu burn. Yes it is supposed to be that way

Honestly, I'm about to just give up this game. I just don't get why this 124 BSOD is so common for this game, as I see a bunch of topics on this forum of people getting the same error as me. I've tried nearly everything so far and it's gotten me nowhere. I'm usually very good at keeping my PC clean, my startup tab in msconfig is technicially empty.

Defragged drive, deleted cache for the game through steam, deleted settings and let the game renew them.
Tested cpu stability, installed new drivers for vga, realtek lan, realtek audio, rts, inf chipset.
Tried raising Vcore, VTT/QPI voltage, DRAM voltage, GPU voltage.
Tried playing overclocked, not overclocked.

I can't think of a single thing that could be wrong except hardware but I can't seem to isolate the issue as my stress tests are showing positive results. Yet everything works just perfect in every other game/application.

Annoying...

Satirelol said:

Honestly, I'm about to just give up this game. I just don't get why this 124 BSOD is so common for this game, as I see a bunch of topics on this forum of people getting the same error as me. I've tried nearly everything so far and it's gotten me nowhere. I'm usually very good at keeping my PC clean, my startup tab in msconfig is technicially empty.

Defragged drive, deleted cache for the game through steam, deleted settings and let the game renew them.
Tested cpu stability, installed new drivers for vga, realtek lan, realtek audio, rts, inf chipset.
Tried raising Vcore, VTT/QPI voltage, DRAM voltage, GPU voltage.
Tried playing overclocked, not overclocked.

I can't think of a single thing that could be wrong except hardware but I can't seem to isolate the issue as my stress tests are showing positive results. Yet everything works just perfect in every other game/application.

Annoying...

Im sure it is. If it is just that game (and you dont BSOD any other time) It may in fact be something wrong in the app.

Here is the driver list, reenabled verifier and rebooted to take a screenshot. Cropped the dropdown menu so they would all fit.

Also, maybe related or not, since a lot of people are reporting realtek problems with the game, is it normal that I have two of these files?



7.048 is the current driver version, no clue what the other 6.0.1.6449 is for. Probably normal though.

Btw, what did you mean by "Still not verified" earlier? Did it just not find any problems with my drivers or did the process not work at all? I basically just repeated what I did earlier, and as you can see the drivers are Loaded so nothing should have went differently.

Satirelol said:

Here is the driver list, reenabled verifier and rebooted to take a screenshot. Cropped the dropdown menu so they would all fit.

Also, maybe related or not, since a lot of people are reporting realtek problems with the game, is it normal that I have two of these files?



7.048 is the current driver version, no clue what the other 6.0.1.6449 is for. Probably normal though.

Btw, what did you mean by "Still not verified" earlier? Did it just not find any problems with my drivers or did the process not work at all? I basically just repeated what I did earlier, and as you can see the drivers are Loaded so nothing should have went differently.

Perfectly normal

Related to Rt64win7.sys 8101E/8168/8169 NDIS 6.20 64-bit Driver from Realtek Corporation

Related to RTKVHD64.sys NVIDIA GeForce 9500M GS.

When verifier is running you can check to make sure it is enabled by typing verifier /query at the cmd prompt. Your last DMP was not enabled.

I did type verifier /query and it prompted a lot of stuff.

Maybe I need better/different instructions because I'm doing exactly as told. Is there a chance that if the problem isn't driver related and it BSOD's for another reason, that the verifier simply doesn't make a report as the problem isn't coming from there?

Also, I ran MEMTEST overnight and it passed 7 tests without any red notices.

i had this error with bc2 once but it ended up being that my cpu oc was not stable. so i upped a little bit (voltage) and have been playing bc2 stable for 6months and more.

0x124 is usually a hardware error so try rulling out stuff that way