BSOD playing Battlefield: Bad Company 2

[Satirelol]

Hello everyone. I've never had a problem with a game before nor any kind of instability or anything of the sort. My msconfig startup tab is clean, I just have MSN and MSE along with my keyboard/mouse utilities and that's about it.

Updated any kind of driver (vga, lan, audio, rts, inf chipset, etc) I can think of.
Tried raising Vcore, VTT/QPI voltage, DRAM voltage, GPU voltage.

Still BSOD'ing and nowhere else, always the same 124 error which supposedly hints to a hardware fault if you google around but clearly this is only happening in that game and there is huge topic on EA forums with people having the same issue as me: http://forum.ea.com/eaforum/posts/list/3915/380660.page

That forum offers mostly amateurs fix arounds, so I'm here to find out better on how to get it fixed.

What's weird is that I played the Battlefield 3 Open Beta for 6+ days of constant playing, that game utilizes my CPU cores and GPU MUCH more than BFBC2 ever could. I can loop Heaven Ungine, or play Crysis 2 for hours and yet... no BSOD.

Since then, I've gotten tired of opening the game as I kept crashing always 1h~ into it so I'm not sure if that folder "Windows_NT6_BSOD_jcgriff2" will have the necessary information. However, I have saved the first mini dump from the folder when it started getting annoying and downloaded some app called BlueScreenView and this is what I got:

I have attached below everything, the Windows_NT6_BSOD_jcgriff2 folder as well as BlueScreenView with that minidump that I took out of the Minidump folder a few weeks ago.

 

[zigzag3143]

Hello everyone. I've never had a problem with a game before nor any kind of instability or anything of the sort. My msconfig startup tab is clean, I just have MSN and MSE along with my keyboard/mouse utilities and that's about it.

Updated any kind of driver (vga, lan, audio, rts, inf chipset, etc) I can think of.
Tried raising Vcore, VTT/QPI voltage, DRAM voltage, GPU voltage.

Still BSOD'ing and nowhere else, always the same 124 error which supposedly hints to a hardware fault if you google around but clearly this is only happening in that game and there is huge topic on EA forums with people having the same issue as me: http://forum.ea.com/eaforum/posts/list/3915/380660.page

That forum offers mostly amateurs fix arounds, so I'm here to find out better on how to get it fixed.

What's weird is that I played the Battlefield 3 Open Beta for 6+ days of constant playing, that game utilizes my CPU cores and GPU MUCH more than BFBC2 ever could. I can loop Heaven Ungine, or play Crysis 2 for hours and yet... no BSOD.

Since then, I've gotten tired of opening the game as I kept crashing always 1h~ into it so I'm not sure if that folder "Windows_NT6_BSOD_jcgriff2" will have the necessary information. However, I have saved the first mini dump from the folder when it started getting annoying and downloaded some app called BlueScreenView and this is what I got:

I have attached below everything, the Windows_NT6_BSOD_jcgriff2 folder as well as BlueScreenView with that minidump that I took out of the Minidump folder a few weeks ago.

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[Satirelol]

1) I have tried playing the game OC'd and not OC'd, no difference.
2) My temps are great, gpu load hits perhaps 60c max in crysis (much lower in bfbc2, around 49c) while CPU hits around 50c.
3) Like I said "Updated any kind of driver (vga, lan, audio, rts, inf chipset, etc) I can think of."
4) Motherboard is on the latest BIOS, which is F11 for the GA-P55A-UD3
5) W7 is of course updated to the latest updates.
6) Like I mentioned, I stressed the GPU with Crysis 2/Heaven Ungine loops. I also ran the CPU through Intel Burn test, as well the RAM with MEMTEST
7) Last thing I haven't tried yet, which would be reinstalling the OS.

 

[Satirelol]

Is there anything else I can provide to get some assistance?

 

[zigzag3143]

Is there anything else I can provide to get some assistance?

It is probably a driver. Lets have you run these two tests.

1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[Satirelol]

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 4105

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8006905028
BCP3: 00000000F2000000
BCP4: 0000000000000005
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\101511-12823-01.dmp
C:\Users\Semir\AppData\Local\Temp\WER-20592-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Ok I enabled the verifier, did everything you said. I just BSOD'd while playing, so... what now? where am I supposed to look/what am I supposed to upload?

In any case, here is minidump that I got from this very BSOD andhttp://www.mediafire.com/?p0pdu6tvutrz9tv a new Windows_NT6_BSOD_jcgriff2 folder if it helps:

 

[Satirelol]

Here's some stability proof:
http://i.imgur.com/QiqYn.jpg

I'll try running MEMTEST overnight if that does anything, but this already looks pretty stable to me

 

[zigzag3143]

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 4105

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8006905028
BCP3: 00000000F2000000
BCP4: 0000000000000005
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\101511-12823-01.dmp
C:\Users\Semir\AppData\Local\Temp\WER-20592-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Ok I enabled the verifier, did everything you said. I just BSOD'd while playing, so... what now? where am I supposed to look/what am I supposed to upload?

In any case, here is minidump that I got from this very BSOD and a new Windows_NT6_BSOD_jcgriff2 folder if it helps:

Still not verified. Still pointing to hardware (possibly CPU). Please see the snap shots

go to accessories>cmd>right click and run as admin>

type verifier

Click on list drivers

Click next

What drivers are checked in the right panel?

 

[zigzag3143]

Here's some stability proof:

I'll try running MEMTEST overnight if that does anything, but this already looks pretty stable to me

Any particular reason all four cpus are running at 100%?

Are you overclocking?

 

[Satirelol]

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.

 

[zigzag3143]

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

 

[Satirelol]

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...

 

[zigzag3143]

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.

 

[Satirelol]

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.

 

[zigzag3143]

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.

 

[Satirelol]

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.

 

[saifz]

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