intermittent STOP 0xA error

Hello, Welcome to SF!

Analysis:

Code:

MaxSpeed:     2800
CurrentSpeed: 4009

I highly suggest to stop overclocking as this could be a major cause of these BSODs.

Code:

Universal Serial Bus (USB) Controller	PCI\VEN_1033&DEV_0194&SUBSYS_84131043&REV_03\4&CF85AA7&0&0010	The drivers for this device are not installed.

Go to your Device Manager:

Control Panel -> Device Manager -> Universal Serial Bus Controllers.

Are there any red X's or yellow warning signs?

Code:

NVIDIA High Definition Audio	HDAUDIO\FUNC_01&VEN_10DE&DEV_0018&SUBSYS_10DE0101&REV_1001\5&55CE02E&0&0001	32

Make sure you have the latest NVIDIA drivers: Drivers - Download NVIDIA Drivers I would uninstall your corrent ones, and re-install them.

Code:

DAEMON Tools Lite	"c:\program files (x86)\daemon tools lite\dtlite.exe" -autorun	Don-PC\Don	HKU\S-1-5-21-1890590412-2620226882-2107574820-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Daemon Tools are very well known to cause problems such as BSODs. Please uninstall.

Code:

ASACPI.sys Wed Jul 15 22:31:29 2009 (4A5E9F11)

Even though this driver is mostly up to date, I believe there is a update for it. But this driver is related to Asus ATK0110 ACPI Utility, which is a known BSOD maker in Windows 7. So please either uninstall, or try upddating to latest version here: ASUSTeK Computer Inc. -Support- Drivers and Download

Code:

Probably caused by : hardware

This is blaming your hardware in one of the dump files. So please do the following:

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. 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.
  
  
• 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 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.

Coutesy of: writhziden

Code:

Event[9574]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2012-05-30T05:39:26.236
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Don-PC
  Description: 
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Internal Timer Error
Processor ID: 0

The details view of this entry contains further information.

This shows that it is blaming your processor. So like I said earlier in the post please reset your overclock to default settings so the processor will run like it should. There are 4 of these errors.

After following all of these instructions please post back results.

-Justin

For now do not overclock what so ever. This could be the cause of the BSODs, so for now just leave everything as default. Try searching for updates using Windows Updates.

-Justin