New
#1
BSOD all the time -- Pandora?
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:
Code: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.
Last edited by Brink; 19 Jul 2012 at 19:12. Reason: code box