New
#11
One of those crashes mentions your Ethernet driver (CPU STAB TEST). See if updating it helps: RealtekCode:Loading Dump File [D:\Kingston\BSODDmpFiles\DigiCZ\prime95bsod\032412-16926-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16917.amd64fre.win7_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`0305a000 PsLoadedModuleList = 0xfffff800`03296e70 Debug session time: Fri Mar 23 20:52:36.690 2012 (UTC - 6:00) System Uptime: 0 days 1:49:34.736 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8007d99028, be200000, 5110a} Probably caused by : hardware Followup: MachineOwner --------- 6: 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: fffffa8007d99028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value. Arg4: 000000000005110a, 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: prime95.exe CURRENT_IRQL: f STACK_TEXT: fffff880`03101b58 fffff800`03023903 : 00000000`00000124 00000000`00000000 fffffa80`07d99028 00000000`be200000 : nt!KeBugCheckEx fffff880`03101b60 fffff800`031df923 : 00000000`00000001 fffffa80`07705a60 00000000`00000000 fffffa80`07705ab0 : hal!HalBugCheckSystem+0x1e3 fffff880`03101ba0 fffff800`030235c8 : 00000000`00000728 fffffa80`07705a60 fffff880`03101f30 fffff880`03101f00 : nt!WheaReportHwError+0x263 fffff880`03101c00 fffff800`03022f1a : fffffa80`07705a60 fffff880`03101f30 fffffa80`07705a60 00000000`00000000 : hal!HalpMcaReportError+0x4c fffff880`03101d50 fffff800`03022dd5 : 00000000`00000008 00000000`00000001 fffff880`03101fb0 00000000`00000000 : hal!HalpMceHandler+0x9e fffff880`03101d90 fffff800`03016e88 : 00000000`00000000 00000000`43d4ac80 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55 fffff880`03101dc0 fffff800`030c8dec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff880`03101df0 fffff800`030c8c53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff880`03101f30 00000001`409d3466 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 00000000`04dfe420 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1`409d3466 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE Followup: MachineOwner ---------
The Prime95 test: Stop 0x124 - what it means and what to try