|28 Mar 2012||#1|
| || |
Rampage IV 3960x BSOD 0X0000124
Have an interesting and am trying to tease it out.
I was overclocking like crazy for 3 days or so (got up to 5000mhz). Anyhow, after all my overclocking I went into Windows for real (not just for benching). I reset all my BIOS settings etc.. etc.. I started getting Unrecoverable_Hardware BSOD's. This was happening every 5 minutes or so. My AMD driver kept resetting so I figured it was driver issues. I used a restore point and the errors occurred within a greater period of time. I then began the hardware portion of my troubleshooting. Actually I first did a flash back of both onboard BIOS'es. Went back into windows, same problem. I switched off the lanes for each of my VGA cards. With all three on, same probem. Each one individually same problem. I have a few RAM kits, tested each individually.
I watched my voltages and temps, they were all high. It is a processor that runs hot, but I am under water. And they usually are in the 20's. Running in the 50's. I reseated the processor, water block etc... No dice.
Okay, here goes. I checked out my voltages in BIOS and all seemed fine. I decided to up the Vcore from the CPU's 1.18 or so to 1.4. Everything has worked fine for 2 days. still works fine right now too. Sleeps fine, everything. Of course, this brought up the wattage and temps at no load. When I run Prime95 core 5 gets up to 91, obviously the Intel thermal sensor kicks. The other cores about 70 or so.
I don't have the minidumps as I just tried to reinstall Windows on my regular HDD, in the process I broke my startup RAID. Which I don't really care about as I am going to be install new vid cards along with a new processor or MOBO.
I can run at full load (even overclock to 4700 and my ram to 2133, it's XMP raating). The RAM taxes the processor more than anything. Another thing that affect core 5. The LGA 2011 CPU's are the RAM controllers too.
The question is do you guys think this is a CPU problem or MOBO problem. IMO it is CPU but I just don't know for sure. It's crap as it is relatively new and I can't RMA it to Intel as it has been overclocked ($1000.00).
|My System Specs|
|28 Mar 2012||#2|
| || |
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's here are some more things you may want to consider.
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" re-installation 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. Otherwise, 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 hadrware troubleshooting steps may, in some cases, void your warranty:
8) Clean and carefully remove any dust from the inside of the machine.
Re seat 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.
|My System Specs|
|28 Mar 2012||#3|
| || |
Thanks for the help. I actually have done everything listed up there. I know (or have read via a couple of people on The Google) that 0x0000124 can also mean a low vcore. My system has been running stable since I upped the Vcore this morning from it's stock 1.18 to1.375. I soon as I go down on the Vcore voltage it crashes. Also, I found that if I disable Intel Side Step (thermal protection) it works just as well. The temps are high and the power is low (or should I say from 20psd to 80psd.). I think, perhaps, that it may be a power issue I have a 1200watt psu snd have determined that i am using around 1300watts. Why this happened after an overclock I just don't know. I ordered a 1500watt PSU from Newegg (overnight of course). So instead of paying 1100.00 for a CPU I have this coming. I am banking this is not a CPU or MOBO issue. If it is I will have a PSU for my Ivy Bridge build next month.
Thank you again!
|My System Specs|
|29 Mar 2012||#8|
| || |
I just did. I did not have my network drivers installed or a patch cable.
I'll run that app and send my specs.
I have a new PSU coming today. I have a 1200w and believe it is too little. According to my calculations i need something like 1300. Or, the capacitors are starting to go one of my raid ssd's doesn't show up if I don't raise my Vcore voltage also (this is new). 1500watts coming today. Maybe that will work. If that does not work, I am thinking it is the MOBO, not the CPU.
Thanks for your help once again!
|My System Specs|
|29 Mar 2012||#9|
| || |
Here we go:
Intel(R) Core(TM) i7-3960X CPU @ 3.30GHz
ASUSTeK COMPUTER INC. RAMPAGE IV EXTREME
BIOS Date: 03/20/12 10:42:52 Ver: 00.18
64.00 GB 63.98 GB (usable RAM)
(1) SAMSUNG SSD 830 Series ATA Device (2) ATA ST1000DM003-9YN1 SCSI Disk Device (3) Intel Raid 0 Volume SCSI Disk Device
(1) AMD High Definition Audio Device (2) High Definition Audio Device (3) AMD High Definition Audio Device (4) AMD High Definition Audio Device
Microsoft Windows 7 Ultimate 64-bit 7600 Multiprocessor Free
|My System Specs|
|Similar help and support threads for2: Rampage IV 3960x BSOD 0X0000124|
|System freeze and STOP:0x0000124 BSOD||BSOD Help and Support|
|BSOD Playing BF3, 0x0000124||BSOD Help and Support|
|BSOD 0x0000124||BSOD Help and Support|
|Semi-random freezes BSOD 0x0000124||BSOD Help and Support|
|Random BSOD, error 0x0000124||BSOD Help and Support|
|BSOD with intensive/moderate CPU usage 0x0000124||BSOD Help and Support|
|Various BSOD - 0x0000124 - 0x000000c5 etc...||BSOD Help and Support|
|Our Sites ||Site Links ||About Us ||Find Us |
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 02:35 AM.