BSOD all the time -- Pandora?

[madams4058]

Alright, to begin, I have this nice self-built computer. Recently I've been playing games on it, listening to pandora, and doing work related tasks. Every so often (usually when I'm gaming, but also sometimes when I'm just browsing) it goes to the BSOD. It's done this a lot now. I'm still learning how to read dump files, so I was hoping you guys could help.

Here is my computer information:

Processor: Intel Core i7 2600k
RAM: 8gb
Motherboard: ASUS P8Z68-V LE
Graphics: NVIDIA GeForce GT430 (two cards, one for each monitor. No, they aren't SLI compatible.)
 
And here is my DUMP analysis:
 
 
BugCheck 124, {0, fffffa800a705028, be000000, 800400}
 
Probably caused by : hardware
 
Followup: MachineOwner
---------
 
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800a705028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
 
Debugging Details:
------------------
 
 
BUGCHECK_STR: 0x124_GenuineIntel
 
CUSTOMER_CRASH_COUNT: 1
 
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
 
PROCESS_NAME: SimCity 4.exe
 
CURRENT_IRQL: f
 
STACK_TEXT: 
fffff880`009f4b58 fffff800`04018a3b : 00000000`00000124 00000000`00000000 fffffa80`0a705028 00000000`be000000 : nt!KeBugCheckEx
fffff880`009f4b60 fffff800`03baab03 : 00000000`00000001 fffffa80`06977010 00000000`00000000 fffffa80`06977060 : hal!HalBugCheckSystem+0x1e3
fffff880`009f4ba0 fffff800`04018700 : 00000000`00000728 fffffa80`06977010 fffff880`009f4f30 fffff880`009f4f00 : nt!WheaReportHwError+0x263
fffff880`009f4c00 fffff800`04018052 : fffffa80`06977010 fffff880`009f4f30 fffffa80`06977010 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f4d50 fffff800`04017f0d : 00000000`00000008 00000000`00000001 fffff880`009f4fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f4d90 fffff800`0400be88 : 00000000`00000000 00000000`13c9c1f4 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f4dc0 fffff800`03a9baac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f4df0 fffff800`03a9b913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f4f30 00000000`004a2269 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0018fa58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x4a2269
 
 
STACK_COMMAND: kb
 
FOLLOWUP_NAME: MachineOwner
 
MODULE_NAME: hardware
 
IMAGE_NAME: hardware
 
DEBUG_FLR_IMAGE_TIMESTAMP: 0
 
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
 
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
 
Followup: MachineOwner

Any help would be appreciated. If you need any more information, let me know.

 

[HonorGamer]

If it is pointing to hardware, try updating your graphics drivers:
Drivers - Download NVIDIA Drivers

Also please read the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html and post the files.

 

[writhziden]

It really would help to have the files so we know what we are dealing with on your system...


As to the 0x124 BugCheck code:

BugCheck 0x124

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

Remember to read closely through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html for the crash.
​