0x0124 BSOD during Win7 install after 4 months of smooth sailing!

[Howard Moon]

Hey guys!

So I sent my Mobo back, and they sent me a brand new one. Installed it just now and..... BSOD

Exact same behaviour as with the old Mobo: BSOD at the start of the Windows installation.

So now I'm thinking it could be either CPU or RAM. RAM seems so unlikely, though. How is it possible that 2 RAM sticks got fried at the exact same time? And why does MemTest say everything is ok?

To make sure it's not the PSU, is it worth playing around with the Vcore etc?

Man this sucks, I really thought swapping the Mobo would fix it

 

[writhziden]

Let's thoroughly check your hardware:

• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing a CPU stress test using IntelBurnTest
  
  
• It is up to you whether you want to try Memtest86+ a third time (I think you ran it twice before?). Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[James7679]

Howard, I am very sorry to hear this, unfortunately there is no real good way to test the individual components if you don't have a second system with the same basic parts to test. The motherboard is where I would have started, you did and are still having the same issues. Are the rest of your components, such as CPU, memory and PSU under warranty? I highly doubt it's your PSU, that Corsair is pretty solid. The next step I would take is sending back the processor and the memory. Again, it's not guaranteed that this is what it is, it's all part of troubleshooting.

Question, do you recall it being an 0x0124 BSOD again?

 

[James7679]

Let's thoroughly check your hardware:

• Monitor temperatures during the following tests.
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  

  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
  • Follow the steps for doing a CPU stress test using IntelBurnTest
• It is up to you whether you want to try Memtest86+ a third time (I think you ran it twice before?). Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

If I am not mistaken, he doesn't have a functional OS.

 

[writhziden]

If I am not mistaken, he doesn't have a functional OS.

Ultimate Boot CD - Overview has some good diagnostic tools to check out.

I believe prime95 can be run through Hiren's boot CD... Hiren

Video memory test: Video Memory stress Test

 

[Howard Moon]

Question, do you recall it being an 0x0124 BSOD again?

Hi James. Yes, it was the same stop code 0x0124. I will check if I can get some RAM from work that I can test. All my components are under warranty so in theory I can send all of them back one by one until the problem is fixed, though that would take a long time

<snip>

Thanks for those steps, Writhziden. However, as James pointed out I have no operating system installed atm. I will use those tools once everything's running though.

 

[Howard Moon]

If I am not mistaken, he doesn't have a functional OS.

Ah, I forgot. He can run all but prime95, Furmark and the Intel test through Ultimate Boot CD - Overview

I believe prime95 can be run through Hiren's boot CD... Hiren

Video memory test: Video Memory stress Test

Ahh nice, I will try those asap. Thanks!

 

[Kaktussoft]

Dear experts, I need your help.

Back in October I built myself a new gaming computer. Hardware specs are as follows:

---
CPU: Intel i5-2500K
Heatsink: Thermaltake Frio
GPU: MSI 560GTX-Ti Twin Frozr II
MoBo: GIGABYTE Z68X-UD3H-B3
RAM: G.Skill Ripjaws 8GB (2x4GB)
HDD: WD 1002FAEX Caviar Black 1TB
DVD: Asus DRW-24B3ST
PSU: Corsair 650TX V2
OS: Windows 7 Home Premium 64bit
---


What Happened

Until three days ago, my computer was running perfectly. I never OC'd it or installed and additional hardware to the one listed above. It has been running for four months without any issues.

Three days ago, I got a Blue Screen (code 0x00000124) with a message that a hardware error had occurred (screenshot). This had been my first ever BSOD with this PC. No CPU-demanding applications were being run at the time of the crash.

When I restarted my PC, and every single restart after that, I would get the exact same BSOD. This would happen either during the Windows7 welcome screen (where you enter login password), or a few seconds after logging in.

I was always able to boot up Windows in safe mode. I tried updating pretty much every single driver, but everything was already up to date. Unfortunately, I didn't save any crash dump files during this time I am sorry for being unable to provide you with a minidump!

I started getting the BSOD even while booting in safe mode! But only sometimes, strangely enough, whereas I would still get the blue screen every single time when booting Windows normally.

I finally decided to do a fresh Windows install. The Windows setup ran successfully, but while booting up for the first time (which is essentially also part of the operating system installation), yes you guessed it.... BSOD!!! Which means that the OS didn't finish installing properly. Now every time I start my PC, after the "loading operating system.." message it gives me a "missing BOOTMGR" error.

I have tried re-installing Windows again a few times, but it always crashes sooner or later. Some times it blue-screens already while extracting the files from the Windows installation DVD.


I am now without a working Operating System and trying to narrow down the faulty piece of hardware which is causing the crashes during Windows installation.


What I have tried

* Removed my graphics card from my PC entirely and used my Mobo's video output. No change, BSOD persists.

* Reset my BIOS to the "failsafe" defaults (even though they were never changed much). No change. I also checked my idle CPU temperatures while in BIOS: everything normal.. 24 degrees max. See screenshots here.

* It was suggested that code 0x0124 on Gigabyte Mobos indicated insufficient Vcore. Tried increased the Vcore from the default 1.24 to 1.35 and QPI/VTT from 1.05 to 1.15. No change.

* Tried booting from a Knoppix 5.1.1 bootable CD (Linux from CD), but it gave me a "can't find filesystem found" error.

* Tried swapping the HDD for another (new) 1.5TB WD Caviar Black. No change.

* Ran MemTest86+ for 8 hours straight (7 passes). No errors were found.

* Tried using only 1 RAM stick at the time. BSOD during Windos installation persisted regardless. Unless both sticks are faulty (unlikely), I think this rules out RAM problem.

* [Update 24.03.2012] Cleaned out entire chassis. Unplugged and re-plugged everything in the Mobo, removed heatsink and CPU, applied new thermal paste, swapped SATA cables for new ones, vacuum cleaned everything. Didn't help.

* Flashed BIOS. Original revision was F3. Tried two different revisions, starting with the F11 (newest one available at the Gigabyte website), then F4. No change.

[Update 30.03.2012]

* Swapped MoBo for a completely new one (same model Gigabyte Z68X-UD3H-B3). Problem persists.



Now what?

I need new ideas on what to try. I would like to determine with certainty where the issue is.

* Keep playing around with Vcore? What values can I (safely) test?

* Please note that I currently have no working Operating System on the machine.

* Due to this, I am unable to provide you with minidump files at the moment. I apologize for this!

THANK YOU FOR YOUR TIME AND EFFORT!

Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR

[This is preliminary documentation and subject to change.]


The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).


Parameters

Parameter 1

0x0​

Parameter 2​

Address of WHEA_ERROR_RECORD structure.​

Parameter 3​

High 32 bits of MCi_STATUS MSR for the MCA bank that had the error.​

Parameter 4​

Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error.​

Cause of error​

A machine check exception occurred.​

These parameter descriptions apply if the processor is based on the x64 architecture, or the x86 architecture that has the MCA feature available (for example, Intel Pentium Pro, Pentium IV, or Xeon).​

 

[Howard Moon]

Hi again fellas,

Ultimate Boot CD - Overview has some good diagnostic tools to check out.

I wasn't able to run any of the CPU diagnostics on this CD. Some compatibility issue I think (screenie here).

I ran a few RAM tests from it, though, including MemTest86+ again. Still no errors found.

I believe prime95 can be run through Hiren's boot CD... Hiren

This CD let me boot "MiniXP", a minimalistic WinXP virtual machine. From there I was able to run Prime95 and several other testing tools. All of them ran without problems. I think I ran Prime95 for 6 hours straight, at a constant 100% CPU load, and it never crashed or found any errors/warnings. Couldn't find a temperature tool on the CD, but from I could tell the CPU barely warmed up.

Video memory test: Video Memory stress Test

This one was included in Hiren's, but I couldn't get it to run. Again some compatibility issue it seemed. However, Video RAM should be fine, since I just replaced the Mobo, right? I've left my GTX 560 out of the machine this whole time.

So I still have no clue where the problem is. Going to try to get some other RAM tomorrow so I can hopefully rule that out.

Thanks a ton for all the help so far guys, appreciate it!

Cheers.

 

[writhziden]

No problem. Let us know how the new RAM goes. Hopefully we can narrow down what is causing this...

 

[James7679]

Howard, we haven't heard back from you, just wondering if you got your issue resolved.

 

[Howard Moon]

Howard, we haven't heard back from you, just wondering if you got your issue resolved.

Hi James!
Thanks for checking back. I sent back my CPU last week and should receive a replacement within the next few days. I'll post the news once I've tried it out

Cheers

 

[Howard Moon]

Hi guys!

GOOD NEWS! I got my CPU replacement yesterday and installed it as soon as I got home and... it works!

No more BSOD during Win7 installation. Finally!

So I guess what I learned from all this is that you can have a defective CPU that still passes all benchmark tools but which crashes during Windows bootup and Windows instalaltion.

Many thanks to all of you for helping me out!

Also, below is a little story about Intel's customer service if you are interested.

===

So I sent Amazon an email saying that my CPU was defective and I wanted to replace it. They wrote back saying no problem, you can send it back to us, and we will send it to Intel for repairs/replacement. It will go faster, however, if you just sent it directly to Intel yourself. So I called Intel and told them the story about my BSODs and so on, and that I had strong reasons to believe that my CPU was defective. What the guy told me kind of shocked me. He said that the failure rate on these processors is so low, it is very hard to believe that my CPU is defective. It is nearly impossible, he said. He told me I was going to have to take my CPU to a shop to have it professionally tested. Naturally, I would have to pay for this test myself (insert outrage here). The shop would then have to give me a written confirmation that the processor is indeed broken, and then I would be able to send the CPU, together with the written proof, back to Intel. At that point I flipped out a little. I mean, the CPU has a 3-year warranty, is only 4 months old, and I am supposed to invest my time and money in doing some test that they should do themselves?

After hanging up the phone I said, screw this, I'm sending it back via Amazon. So I did. One day later I received an email from Amazon: we are very sorry about your defective CPU, here is your money back. O_O And that is why I love them. I simply ordered a new processor, exact same model. I installed it last night, works flawlessly. I almost feel like calling up Intel again: hey, how is this for a written proof you idiots?

/endrant

 

[writhziden]

Understand your frustration, but Intel is mostly right. Processors do not commonly fail without user error involved, i.e. bent/broken pins. However, I still remember the "customer is always right" slogan. Unfortunately, that seems to have been thrown out the window as the economy has dwindled. At least you found a solution to the exchange problem. I've been getting the short end in some deals lately myself, so I know how you felt. Most of my complaints have only been mostly resolved rather than entirely, but that is a whole other can to open, and I do not feel like having worms everywhere.

All in all, I am very happy to see you have a working system again. Enjoy!

 

[James7679]

Howard, I am so glad to hear that you got this resolved. Any component of a PC can present as good, but still be bad. Especially a CPU and GPU. That is why swapping components can be the only way to isolate the problem. So I am glad that you got your baby up and running. Have fun with it and don't be a stranger!

 

[Kaktussoft]

Checking memory is quite easy... write something and read it.... should be the same.

But checking CPU is very difficult. You check it with a program that runs on that cpu! For example he multilipes 8 and 7 and its answer is 999. How should he know this is wrong?

Glad you solved the problem