Solved BSOD every 2-4 hours, STOP 0x00000A

[mattskup316]

I made a thread yesterday which was barried and no one responded or anything! I have a screen shot this time, this STOP 0x00000A keeps happening, and I need to know if it's a bad mobo, because it looks like it wasn't ram, and I bought new ram and placed it in and it's still bad, it seems like all of my slots are bad, no matter which ones I put them in. Here's the picture I took of the errors, it's the same one each time. View attachment 224643

 

[HonorGamer]

You need to be patient. I am sorry that no one replied, but the BSOD Team is swamped.

It's blaming hardware. Do the following steps:

BugCheck 0x124

   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. :warn:WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html and use the following hardware checks to supplement that link.

• If you are overclocking any hardware, please stop.
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• 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 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 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.

​

Coutesy of: writhziden

hamachi.sys Thu Nov 30 14:24:52 [B][COLOR="Red"]2006 [/COLOR][/B](456F3E14)

Drivers before 2009 are known to cause problems. Please update: https://secure.logmein.com/US/support/hamachi2/

After please post back results.

-Justin

 

[mattskup316]

Thanks for responding, The last time I had this problem, I thought it was bad ram, so I bought new ram, and replaced it. It was fine for two days and now it's acting up again, Memtest is showing bad ram, I've tested my ram on a different computer and it's perfectly fine, which goes to make me believe that my ram slots on my mobo right now are bad, because I've tried it every way possible. My harddrive is fine, I tested the last time I had posted here, my GPU is fine, swapped it to another computer and it worked fine without any bsod's or anything, I did swap my ram like I stated above which worked fine on another computer but this one is having problems with it. I can't tell if it's drivers or my mobo, I'm thinking mobo because I had swapped ram back and fourth into different slots, alone, they're both different brands and both different clocks. The weird part is the problem had only started occurring a week after I had been using my system. I'm out of ideas and I just can't figure out if it's my mobo or if it's a faulty driver somewhere, but I'm still thinking mobo.

 

[mattskup316]

I just realized, could incompatible ram be the issue? My Mobo is an ASrock 970 Extreme3 and both sets of ram that I had weren't on the compatible list, could this be the problem?

 

[HonorGamer]

Yes that could be a problem.

-Justin