BSOD 0x00000124 Happens During gaming, Just put New H100i on

Silverxspartan · 14 Oct 2013

Hello, So i had this issue before a couple of months ago and it has gone away for the longest time. The first time i posted here it ended up being an overheating CPU. Since then i have had no issues untill a few days ago. I then thought it was overheating again so i bought the h100i cpu cooler. It bsod tonight while playing World of Warcraft so I have turned down the overclock to see if that fixes it. Attached is grab all application file, hopefully someone can tell me the issue this time. Maybe i gotta buy a new CPU or something.

Thank you in Advance

Arc · 15 Oct 2013

A stop 0x124 is usually a hardware error, and is seems that your hardware is new.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of your PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Let us know the results.
________________________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800ea40028, be000000, 100110a}

*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : GenuineIntel

Followup: MachineOwner
---------

1: 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: fffffa800ea40028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, 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:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f6a58 fffff800`0301ba3b : 00000000`00000124 00000000`00000000 fffffa80`0ea40028 00000000`be000000 : nt!KeBugCheckEx
fffff880`009f6a60 fffff800`031de453 : 00000000`00000001 fffffa80`0ea41d30 00000000`00000000 fffffa80`0ea41d80 : hal!HalBugCheckSystem+0x1e3
fffff880`009f6aa0 fffff800`0301b700 : 00000000`00000728 fffffa80`0ea41d30 fffff880`009f6e30 fffff880`009f6e00 : nt!WheaReportHwError+0x263
fffff880`009f6b00 fffff800`0301b052 : fffffa80`0ea41d30 fffff880`009f6e30 fffffa80`0ea41d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f6c50 fffff800`0301af0d : 00000000`00000004 00000000`00000001 fffff880`009f6eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f6c90 fffff800`0300ee88 : 00000000`00000000 fffff880`009ee180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f6cc0 fffff800`030c646c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f6cf0 fffff800`030c62d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f6e30 fffff880`078a39c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0331bb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x39c2


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
---------