• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Windows 7 BSOD

Captainpoo

New Member
Joined
Dec 28, 2009
Messages
37 (0.01/day)
System Name Power Muncher.
Processor Intel 2500K @ 4GHZ
Motherboard ASUS Z68
Cooling Arctic cooler 13
Memory Corsair DDR3 1600mhz 2x 4GB modules
Video Card(s) Zotac GTX 560 TI 448
Storage WD 500GB caviar black/ Corsair Force GT SATA3 SSD
Display(s) LG 22" 1920x1080
Case Silverstone PS03 w/ 2 Aerocool Shark (black) Extractor 120mm fans
Audio Device(s) Realtek onboard
Power Supply Corsair 650TX V1 (still going after 3rd PC)
Software Windows 7 64-bit Ultimate
I've been getting this code when i play Bad Company 2. The game locks up and the computer restarts itself.

The code:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA80051DA588
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\031211-15069-01.dmp
C:\Users\Matt\AppData\Local\Temp\WER-25256-0.sysdata.xml
Can anyone help me determine the cause of this?

System info:
Windows 7 64-Bit
1055T (95W) OC to 3.5GHZ (45C max @ 1.38V)
Corsair 1333MHZ 2x2GB Ram
HD 5770 Crossfire
ASUS M4A88T-V EVO
Corsair TX 650W PSU
Realtek ALC892 (Which i am using 5.1)
 
Could be a lot of things.

First, you should check and make sure your temps are all good.
Next, run memtest or equivalent and check the ram.
Back off any OC you are doing and try the game.
Check the timings and voltages on the memory. You may need to manually tweak them.
Check the PSU and make sure all the power levels are good.
Make sure all your drivers and bios are up to date.

Oh and these may help give you some clue:
BlueScreenView v1.31 - View BSOD (blue screen) crash information stored in dump files.
AppCrashView v1.10 - View application crashes (.wer files)
 
Last edited:
Could be a lot of things.

First, you should check and make sure your temps are all good.
Next, run memtest or equivalent and check the ram.
Back off any OC you are doing and try the game.
Check the timings and voltages on the memory. You may need to manually tweak them.
Check the PSU and make sure all the power levels are good.
Make sure all your drivers and bios are up to date.

Oh and these may help give you some clue:
BlueScreenView v1.31 - View BSOD (blue screen) crash information stored in dump files.
AppCrashView v1.10 - View application crashes (.wer files)

Temps are very good. both gpus are 60-65 on bad company 2. cpu is 35c load on default settings.
I factory reset everything in the bios (which is latest bios release)
Psu temps and fan are all good.
gpu and sound drivers are all latest. Everything else is updated from asus driver downloads.

Still got the freeze and system restart after doing these things. Did windows memory diagnostic and that was fine.

i never have this problem on other games, though none are as stressing as bad company.
 
0124 BSOD is memory or memory controller related;)
 
I'll test each stick of ram on bad company 2. It's cheap corsair ram btw (could be getting hot). Could i be using all the 4gb ram up?
 
doubt its pulling all 4GB worth to use it.

Are the volts and timings set correctly in bios? I see you "reset" to defaults, that could mean auto is set. If so thats 1.5V to the ram, and who knows what timings.
 
doubt its pulling all 4GB worth to use it.

Are the volts and timings set correctly in bios? I see you "reset" to defaults, that could mean auto is set. If so thats 1.5V to the ram, and who knows what timings.

I checked the timings and they seem to be the same as the factory defaults corsair have given them. The voltage is 1.5v, just like the factory defaults. I'm going to run Memtest for one hour to see if i get any errors.

CORSAIR 2GB 240-Pin DDR3 SDRAM DDR3 1333 Desktop M... - That is the product. I have two in unganged mode.
 
just an quick test, remove your ram sticks and try the another ram channel in mother board.
 
If the ram passes memtest and individual testing on games, I think it could be my northbridge. It has a self shut down upon reaching 95C for protective purposes.
 
i was gonna say the exact same thing happened to me - and my kingston hyper x ram had gone bad (overnight?) .. anyway, swopping out for crucial ballistix solved my problem
 
Ran memtest for 1 hour and 15 minutes without errors. :S. Not quite sure what the problem may be, but if i get another freeze and restart, im going to inspect my northbridge temperature and see if its hitting 95C.
 
OK, did memtest and passed. Ran bad company 2 and STILL froze and reset.
Put my finger on nortbridge heatsink and it was warm, not scorching hot.
Everything in bios is Auto.
Ran game in administrator and without and both froze within 20-30 mins.
Temps are within normal ranges. GPUs never touch 70C and CPU is 35C load.

Not quite sure what this could mean. I hope my corsair PSU isn't the cause. I'm quite sure a 650TX can handle a 1055t and Xfire 5770s
 
Well, here is a link that will show that a single 5770 puts out at lease 302w of power.

To me, a safe bet of the matter is that it's drawing to much on the psu. Memory is one thing that hits the famous 124, but if you got crossfired/sli system, it can also go across being a psu related issue due to to much power draw from the cards them selves.

I was having the issue with 2 GTX 280's.. The psu was a 750, which was enough via specs and enough amps, but when it had to run at full load, all gpu's going on Grid via the drift racing.. Nope, it would ether 124 myself, or I would lag was there was no tomorrow..

So, if you can get a kill-a-watt and test it, It'll safely show you if the psu isn't being able to handle the system at full load.
 
I have the same problem with bulletstorm and from my research it is a driver problem.I used
260.58 and 260.99 and still have the same problem and i have 1 gtx280sc.Im thing i need to run a older driver could be cuda or physx related,but i will have to research the thought
 
even it's pas test mate , no problem to try it
 
HMM, i'm quite certain the 650tx can handle crossfire 5770's. It does have two 6-pin connectors and is certified xfire and sli ready. I'm going to try more memory tests tomorrow, and perhaps a CPU test.

I worked out, using a psu calculator (extreme.outervision.com/psucalculatorlite.jsp), that my system uses less than 500W of power, due to not so much capacitor aging. I'm also using a belkin surge protector.
 
Last edited:
I raised the voltage on my southbridge supposedly it make noise to the cpu and northbridge,seems to be more stable.
 
OK, i tried using both sticks separately to check if either of them crashed. Both crashed whilst playing bad company 2, with the 124 error on desktop. Not quite sure what it may be. Is there anything else i may try to find out the source of the problem?
Thanks
 
hmm what voltage do you have your ram and CPU at?

All Auto. Before, i had 1.5v on ram and when i had my cpu overclocked, i had that 1.35V (@3.5ghz). Now the cpu is on default speeds and auto voltage, same with the RAM. RAM was set to 1333MHZ speed in bios with default timings of 9-9-9-24. Then suddenly, bad company 2 started crashing. I'm stuck ever since.
 
Just to conclude this problem, i have tested all the methods of hardware error detection i could use. I used Intel burn test for 50 runs, GPU tests and MEMtest. All came back stable. It appears that battlefield bad company 2 is the ONLY game that does BSOD. I may have a problem regarding the game that is triggering the unnecessary BSOD.
 
Possibly follow what instron mentioned above?
 
Just out of curiosity.. Do you have PunkBuster installed?
There have been reports of this interfering with the game..
 
Here is what BlueScreenView makes of it. All other Blue screens are from the same cause (ntoskrnl.exe). I have one other that relates to Atapi (Sata?).
First one:
==================================================
Dump File : 032511-19016-01.dmp
Crash Time : 25/03/2011 16:24:35
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`052df038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a61cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\032511-19016-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7600
Dump File Size : 262,144
==================================================

Second one:

==========================================
Dump File : 031211-15069-01.dmp
Crash Time : 12/03/2011 15:26:12
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`051da588
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : dump_atapi.sys - Is this related to my SATA drive?
Caused By Address : dump_atapi.sys+1d71730
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\031211-15069-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7600
Dump File Size : 262,144
==================================================
 
Back
Top