New
#1
Browsing SF - BSOD
I was browsing SF and clicked a link to antoher thread and got a BSOD 0x124. It may be due to my CPU volts are too low. If someone could check my dump and see what it thinks, I'd be happy.
I was browsing SF and clicked a link to antoher thread and got a BSOD 0x124. It may be due to my CPU volts are too low. If someone could check my dump and see what it thinks, I'd be happy.
There you go - although I'm not sure how weather.exe comes into play. Do you have a weather gadget or similar running?Code:******************************************************************************* * * * 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: fffffa8010370028, 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: Weather.exe CURRENT_IRQL: f STACK_TEXT: fffff880`035dfa58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx 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 ---------
0x124 - Hardware error on Intel so it could be voltages, overheating so it's worth looking at the CPU.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8010370028, be200000, 5110a} Probably caused by : GenuineIntel 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: fffffa8010370028, 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: WIN7_DRIVER_FAULT PROCESS_NAME: Weather.exe CURRENT_IRQL: f STACK_TEXT: fffff880`035dfa58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE Followup: MachineOwner ---------
Gary,
Arc has given me a hand with this one - your CPU appears to be under-clocked. I recommend setting CPU clock-speeds back to default. Please see red text.
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8010370028, be200000, 5110a} 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: fffffa8010370028, 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: Weather.exe CURRENT_IRQL: f STACK_TEXT: fffff880`035dfa58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx 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 --------- 3: kd> !sysinfo cpuspeed CPUID: "Intel(R) Core(TM) i5-2550K CPU @ 3.40GHz" MaxSpeed: 3400 CurrentSpeed: 2200 3: kd> !errrec fffffa8010370028 =============================================================================== Common Platform Error Record @ fffffa8010370028 ------------------------------------------------------------------------------- Record Id : 01cdaf4f7eb0c6a4 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 10/21/2012 8:50:16 Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ fffffa80103700a8 Section @ fffffa8010370180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Generic Flags : 0x00 Level : 2 CPU Version : 0x00000000000206a7 Processor ID : 0x0000000000000006 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ fffffa80103700f0 Section @ fffffa8010370240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000006 CPU Id : a7 06 02 00 00 08 10 06 - bf e3 9a 1f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ fffffa8010370240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ fffffa8010370138 Section @ fffffa80103702c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : GCACHEL2_ERR_ERR (Proc 3 Bank 8) Status : 0xbe2000000005110a Address : 0x0000000209e69980 Misc. : 0x000000d086010086
Thanks to Archie and you Colin.
Those frequency figures are the min and max non-turbo speeds. At stock settings the CPU would down clock to 1600 MHz. I set the min to 2200 MHz. I'll reset the min non turbo to 1600 and see how that goes.
I am currently in the 7th hour of Prime95 and all cores are working.
*08:31 and no issues. thank everyone for the info.
Last edited by Britton30; 21 Oct 2012 at 20:20.