New
#1
need help analyzing dmp files
Hello, a friend of mine sent me these dump files - can I get an analysis from someone? Thanks so much.
Hello, a friend of mine sent me these dump files - can I get an analysis from someone? Thanks so much.
Remote assistance is not very effective with a mediate. Information and instructions may get derailed in that case.
CRASH DUMP ANALYSIS: (all the three are identical).
You have asked for analysis, not for any suggestion.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa800ec79028, bf800000, 200401} Probably caused by : GenuineIntel Followup: MachineOwner --------- 2: 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: fffffa800ec79028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000200401, 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: thermald.exe CURRENT_IRQL: f ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre STACK_TEXT: fffff880`0376db58 fffff800`039ffa3b : 00000000`00000124 00000000`00000000 fffffa80`0ec79028 00000000`bf800000 : nt!KeBugCheckEx fffff880`0376db60 fffff800`03592713 : 00000000`00000001 fffffa80`0ec70ea0 00000000`00000000 fffffa80`0ec70ef0 : hal!HalBugCheckSystem+0x1e3 fffff880`0376dba0 fffff800`039ff700 : 00000000`00000728 fffffa80`0ec70ea0 fffff880`0376df30 fffff880`0376df00 : nt!WheaReportHwError+0x263 fffff880`0376dc00 fffff800`039ff052 : fffffa80`0ec70ea0 fffff880`0376df30 fffffa80`0ec70ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c fffff880`0376dd50 fffff800`039fef0d : 00000000`00000008 00000000`00000001 fffff880`0376dfb0 00000000`00000000 : hal!HalpMceHandler+0x9e fffff880`0376dd90 fffff800`039f2e88 : 00000000`00000000 00000000`00000010 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55 fffff880`0376ddc0 fffff800`034797ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff880`0376ddf0 fffff800`03479613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff880`0376df30 fffff800`03471b08 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 fffff880`0dae6638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memmove+0x208 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e} Followup: MachineOwner ---------
But I will suggest the same thing that I suggested to icarus505 here to uninstall Gigabyte bloats.
That seems to have fixed the problem - thanks so much!