0x0124 Hardware Error BSOD randomly

Hello,
I will try to explain everything I know in as much detail as possible.
First off, my system is running Windows 7 Ultimate x64 which was installed about a year ago. I built the computer in September 2010. In late December 2011 I started getting frequent BSODs while playing video games. I had assumed it was because the computer was running too hot so I started using HWMonitor to check my temperatures and the computer was running extremely hot, around 90 degrees Celsius. I later realized that I had the hardware overclocking switches on my motherboard switched on which was causing the heat issues. Once I flipped them off the temperatures dropped to around 55 degrees.

This is likely the cause of my problems as I probably damaged a part running the computer at those temperatures for the course of at least a month. One day in January my computer refused to turn on and I couldn't figure out why, but pulling the RAM and reinserting it fixed the issue. After this however the DVI port on my graphics card began only outputting in B&W, not a big deal since I always use HDMI but I figured if there was a problematic part causing the BSOD it was likely the graphics card because of this.

I finally finished school for the year and decided to try to figure out which part was causing the issue so that I could replace it. I borrowed a graphics card from a friend and tried swapping it in, but my computer continued to BSOD, although it did seem to take longer to do so. I ran the boot version of memtest for a couple of hours and got no errors but I was planning to run it again overnight at some point to test it further. I might be able borrow a processor from a friend this coming weekend out of a computer I built for him which I could swap in to test the processor. I attached the dump files as per the posting instructions with the exception of the perfmon /report which gave me an error message of "the interface is unknown" if anyone knows why that is then I could attach that file too.

I'm just wondering what tests I can perform to try to figure out what part is causing the issues. If you need any other files I will be happy to try to procure them. Thank you.

The error appears to stem from processor cache failure. While it is memory, it's not memory you can test or replace. You may have indeed damaged the processor core. AMD is not known for throttling on over-temp and will run till they "smoke". You can try a different processor but the motherboard may also be damaged. Try it.

By the way, the error code was 124 - Hardware.

Thanks I'll try swapping out the processor and see how that does. I wish that the BSODs were more procurable on demand so that I could test it easier, but they just happen when they want so what should I use to stress test? Prime95? Are there certain tests on Prime95 that I should do, I've used it before, but just as part of a team, not for stress testing.

Memtest86+ will test the processor cache also. It's part of the processor pipe line to memory.

Follow this tutorial: RAM - Test with Memtest86+

Thanks, I'll give that a go tonight, Newegg is having a sale on a Phenom II X4 955 so I might pick up one of those with a new CPU cooler, but is there any way to test the motherboard?

TychoPsycho said:

... but is there any way to test the motherboard?

Not particularly. You can visually check around the CPU socket for darkened areas but if the board is bad, it will usually just not work. Try the CPU. That's about the best test there is.

In addition to the good suggestions by carwiz, these are my usual recommendations for a 0x124 BugCheck hardware code:

writhziden said:

You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through Stop 0x124 - what it means and what to try and use the following hardware checks to supplement that link.

• If you are overclocking any hardware, please stop.
  
  
• 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). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. 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 Hardware - Stress Test With Prime95 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 CPU stress test using IntelBurnTest
  
  
• 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).
  
  For Part 3: If You Have Errors: 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. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through Stop 0x124 - what it means and what to try for the crash.

Check your BIOS readings for the 5V and 12V rails. HWMonitor may be misreading them.


Security Software: ??? Make sure to install security software. I recommend either of these:

• Microsoft Security Essentials - Free Antivirus for Windows coupled with Malwarebytes. Do not start the free trial of Malwarebytes. Just use the standalone version, update it, and scan your computer once a week with Malwarebytes and with Microsoft Security Essentials.
  
  
• Good and Free system security combination.

After installing your security software, update it, and then run full scans today with each program. Report back the results of the scans.


Make sure to install your Windows Updates.


Update the following driver from your Motherboard Support site:

Code:

L1C62x64.sys Tue Mar 31 23:09:17 2009 (49D2F6FD)

L1C62x64.sys is your LAN driver.


You had a 0x101 BugCheck code: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

Most of your crashes indicate memory problems (possibly an incompatible set of modules?):

• Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

Thanks for all the help writhziden,

I looked at the voltages in my BIOS, they seem to be fine,
CPU Vcore: 1.328v
3.3V: 3.312v
5V: 5.061v
12V: 11.928
I'm using a thermaltake 550w PSU, I'm not sure exactly what model it is.

I've run a Malwarebytes scan, and I'm working on MSE, but I just reinstalled the system this evening so I cant see malware or viruses being an issue yet, I've barely run anything on this system yet. I'll report back on these when they finish.

I installed the LAN driver for my motherboard.

I'm not sure what you mean by incompatible modules of RAM? Could they be incompatible with my new CPU? I've attached the screenshots you asked for from CPU-Z, I have 2 ram slots filled, so the other tabs of SPD show up blank.

Thanks again and congrats on your 9300th post :)