Sign in with
Sign up | Sign in
Your question
Solved

BSOD BCCode: 124

Last response: in Windows 7
Share
March 17, 2013 6:04:11 PM

I have recently been experiencing a lot of blue screens. It usually happens when i start up a game. below is my BSOD info
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA80077FD028
BCP3: 00000000FE200000
BCP4: 0000000000021136
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

PC SPECS= i5 3.4 ghz 3570k
pny gtx 660ti 2gb
2x4gb corsair vengence ram
asus p8 z77-v LX mobo
asus monitor



Any help would be appreciated.
I really want to fix these blue screens

More about : bsod bccode 124

March 17, 2013 6:14:17 PM

increase CPU vcore should solve it :) 
m
0
l
a b $ Windows 7
March 17, 2013 6:21:35 PM

Bug Check 0x124 is WHEA_UNCORRECTABLE_ERROR

It is almost always down to a hardware issue.


- Remove any over-clocking you may have.
- Install HWMonitor and check your temperatures aren't getting high. Run Prime95 to heavily stress the CPU.
- Download MemTest and burn the iso to a CD/DVD. Use this to test your RAM. Let it run for a good few hours.
- If your motherboard has on-board graphics try using those (just as a test).
- Update all hardware drivers to their newest versions.
m
0
l
Related resources
Can't find your answer ? Ask !

Best solution

a b $ Windows 7
March 17, 2013 6:29:16 PM

Here is a troubleshooting guide from a Microsoft MVP on the matter...



Stop 0x124 is a hardware error
If you are overclocking try resetting your processor to standard settings and see if that helps.
If you continue to get BSOD here are some more things you may want to consider.
This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).

Stop 0x124 - what it means and what to try
Synopsis:

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.


Generic "Stop 0x124" Troubleshooting Strategy:

1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.

2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.

3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.

4) Update the motherboard BIOS according to the manufacturer's instructions.
Their website should provide detailed instructions as to the brand and model-specific procedure.

5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.

6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing.
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:

8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.

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.

Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
Share
a b $ Windows 7
March 17, 2013 6:29:31 PM

make sure your new mb has the newest bios bug fixes. check with cpu-z that your ram is running at it right speed. (spd tab). in the bios make sure xmp profile is turned on and your running the mb in standard mode speed. with some ram when you run it in performace mode it changes the ram/cpu bus timing and causes issues.
m
0
l
March 17, 2013 7:15:22 PM

imomun said:
increase CPU vcore should solve it :) 


increase vcore? elaborate please
m
0
l
March 18, 2013 3:38:28 AM

Kunal Mahajan said:
imomun said:
increase CPU vcore should solve it :) 


increase vcore? elaborate please


casper1973 already elaborate this though

Let me make Long story short. :) 

BSOD BCCode: 124 usualy a hardware issue can happen for overheating, driver conflict/issues corrupted file etc increase/decreasr voltage often resolves but not always.

If your overclocking 3570k you can enable more voltage to see if it ressoves, also enable PLL Overvoltage for 4.4GHz and more

Next candidate Memory. Full memtest to see if any module has developed fault.

Normally this should get read of the issue unless the problem is elsewhere.

Theres some similar threads already exist that you might want to look


http://www.tomshardware.co.uk/forum/67693-63-bsod-mins-...

http://www.tomshardware.co.uk/forum/364158-28-years-bso...

Thanks
m
0
l
March 30, 2013 1:46:49 PM

Ya guys sorry for my late reply( been busy lately). But updateing the bios and graphics drivers seemed to do the trick. Thanks to all the people that helped.
m
0
l
!