New
#1
BSOD (SF Diagnostics Tool is Not Working)
Hi I d/l SF diagnostics, but, it freezes up, so I have uploaded the .DMP file in a zipped folder.
Hi I d/l SF diagnostics, but, it freezes up, so I have uploaded the .DMP file in a zipped folder.
Hello Mate,
It's possible that the something is blocking the tool. Well it's OK. Seems like the dump file is pointing to intelppm.sys i.e. Microsoft Intel processor drive. Which may not be your problem. Here what you can try
- Run SFC /SCANNOW Command - System File Checker
- Update your chipset drivers(Motherboard drivers)
Run Hardware Diagnostic Hardware Diagnostic | Captain Debugger . Also follow this article Stop 0x124 - what it means and what to try
Bugcheck:
Code: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: fffffa800b474028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000400405, 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: System CURRENT_IRQL: f STACK_TEXT: fffff880`01fb8b58 fffff800`01a25a3b : 00000000`00000124 00000000`00000000 fffffa80`0b474028 00000000`fa000000 : nt!KeBugCheckEx fffff880`01fb8b60 fffff800`01be8b03 : 00000000`00000001 fffffa80`0ad8a8f0 00000000`00000000 fffffa80`0ad8a940 : hal!HalBugCheckSystem+0x1e3 fffff880`01fb8ba0 fffff800`01a25700 : 00000000`00000728 fffffa80`0ad8a8f0 fffff880`01fb8f30 fffff880`01fb8f00 : nt!WheaReportHwError+0x263 fffff880`01fb8c00 fffff800`01a25052 : fffffa80`0ad8a8f0 fffff880`01fb8f30 fffffa80`0ad8a8f0 00000000`00000000 : hal!HalpMcaReportError+0x4c fffff880`01fb8d50 fffff800`01a24f0d : 00000000`00000008 00000000`00000001 fffff880`01fb8fb0 00000000`00000000 : hal!HalpMceHandler+0x9e fffff880`01fb8d90 fffff800`01a18e88 : 00000000`00000000 fffff880`01fb0180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55 fffff880`01fb8dc0 fffff800`01ad9aac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff880`01fb8df0 fffff800`01ad9913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff880`01fb8f30 fffff880`0310d9c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 fffff880`01fd8c98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x39c2 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 ---------