|19 Apr 2012||#1|
Random "Blue Screens" BCCode: 124 -- Win7 x64
Hey guys. For the past month or so I've been dealing with random "Blue Screens." The reason why I quote Blue Screens is because that is the type of malfunction Windows says happened, but in actuality there is no blue screen. Sounds skip for a few seconds as the computer locks up and just reboots.
This seems to be happening at complete random times. I'll come home from work and the computer will have rebooted itself, or I will be listening to music, or playing games and it will happen. As far as I can tell there's no rhyme or reason. Some times this happens twice per day, and other times I can go almost 2 weeks without an occurance.
Here's the info that pops up when I log back into Windows:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
OS Version: 6_1_7601
Service Pack: 1_0
My system specs:
Win 7 x64 with all updates.
ASUS M3A78-EM AM2+ Mobo with all firmware updates. Sits at ~35C
AMD Phenom II x6 1090T CPU (not overclocked) which sits at ~25C idle/40C on load
8GB of Corsair DDR2
AMD Radeon 6950 2GB by Sapphire. Sits at ~45C idle and ~60C under load.
625GB Western Digital Caviar Blue's. They sit at ~32C
120GB Crucial M4 SSD (OS drive) with up to date firmware.
I hadn't made any hardware changes for 2 months prior to when this problem started happening.
Things I've tried for troubleshooting:
Disabled/Enabled AMD's Turbo Core feature. Happens both times.
Disabled/Enabled Cool'N'Quiet. Still happens both ways.
Ran Memtest86 for 12 hours and it came back with 0 errors.
Ran Prime95 for several hours to put all 6 of my CPU cores at 100% usage.
I tried to use the memory dump application that was outlined in the sticky for this sub-forum, but I couldn't locate the folder it created. It simply was not in my Documents folder. I instead went ahead and archived my Minidump folder.
Any help would be greatly appreciated!
Edit: While doing the Resource and Performance Monitor I noticed that there is some type of driver conflict with my Video card. I will look into this more after posting. It might have nothing to do with my issue and the problem might not rear it's ugly head for a week or so.
|My System Specs|
|19 Apr 2012||#2|
All of your DMPs point to Stop 0x124 which 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
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 harware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent harware 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.
Stop 0x124 - what it means and what to try
|My System Specs|
|Similar help and support threads for2: Random "Blue Screens" BCCode: 124 -- Win7 x64|
|Random BSOD. | "BCCODE 'a' | STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL"||BSOD Help and Support|
|BCCode 50, random blue screens on new system.||BSOD Help and Support|
|Random "Bad Pool Header" and "System Service Exception" BSODs||BSOD Help and Support|
|Random Blue screens on fresh install, caused by "hal.dll"||BSOD Help and Support|
|Fix Windows 7 "0x0000007F" Blue Screens of Death on PCs with Antivirus||BSOD Help and Support|
|Random Blue Screens Win7?||BSOD Help and Support|
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 20:48.