New
#1
BSOD crash
I had a crash for the first time two days ago while I was playing World of Warcraft. I had another last night while watching steaming tv on hulu.com
I had a crash for the first time two days ago while I was playing World of Warcraft. I had another last night while watching steaming tv on hulu.com
Hi and welcome
this one pretty obvious hardware. are you overclocking? running a raid? add ram lately? change your hardware?
Ken J+
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\123009-14570-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c5ae50 Debug session time: Wed Dec 30 04:31:25.287 2009 (GMT-5) System Uptime: 0 days 0:00:07.598 Loading Kernel Symbols ................................................. Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8007d2b748, 0, 0} Probably caused by : hardware Followup: MachineOwner --------- 3: 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: fffffa8007d2b748, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_AuthenticAMD CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`031a86f0 fffff800`02cd7a89 : fffffa80`07d2b720 fffffa80`06bad680 00000000`00000009 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c fffff880`031a8c10 fffff800`02bb9547 : fffffa80`07d2b720 fffff800`02c325f8 fffffa80`06bad680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49 fffff880`031a8c40 fffff800`02b21b95 : fffff800`02c94360 fffffa80`07e4c288 fffffa80`07e4c280 fffffa80`06bad680 : nt!WheapProcessWorkQueueItem+0x57 fffff880`031a8c80 fffff800`02a9c161 : fffff880`0110ae00 fffff800`02b21b70 fffffa80`06bad680 00000538`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25 fffff880`031a8cb0 fffff800`02d32166 : 00000538`00000000 fffffa80`06bad680 00000000`00000080 fffffa80`06b9a040 : nt!ExpWorkerThread+0x111 fffff880`031a8d40 fffff800`02a6d486 : fffff880`02f64180 fffffa80`06bad680 fffff880`02f6efc0 00000538`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`031a8d80 00000000`00000000 : fffff880`031a9000 fffff880`031a3000 fffff880`037b1590 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV Followup: MachineOwner ---------
I'm not overclocking, running raid and I haven't changed any hardware since I installed it. I built the computer beginning of Dec. I updated ASUS EAH5770's drivers recently. My cpu/nb do run pretty hot without overclocking usually between 46-60c.
Last edited by Pfizer; 30 Dec 2009 at 10:38.