BSOD while watching streams, WHEA_UNCORRECTABLE_ERROR

Hi,

yesterday I removed my old motherboard and CPU to replace it with my new GA-Z77-D3H motherboard and a intel core i5-3570K. Everything seemed to be fine, Windows 7 correctly identified the new motherboard and installed the drivers. I also installed all the drivers from the cd that came with the new motheboard.

Now today I wanted to watch a stream, when suddenly the BSOD appears and the pc restarted a few seconds after the bluescreen. I was surprised but thought it would possibly be just a random malfunction. After the restart, my catalyst-control-center said it couldn't find my ATi 7950, so I reinstalled the 13.4 CCC. Everything was fine after another restart.

But since then, everytime I try to watch a stream, the BSOD reappears and my pc restarts. I already took a look at the dump files with the windows sdk debugger, which gave my something like this:

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: fffffa8009b1a028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000002110a, 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:  
fffff800`00ba8a98 fffff800`03c2ca3b : 00000000`00000124 00000000`00000000 fffffa80`09b1a028 00000000`be200000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`03def443 : 00000000`00000001 fffffa80`07652a60 00000000`00000000 fffffa80`07652ab0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`03c2c700 : 00000000`00000728 fffffa80`07652a60 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`03c2c052 : fffffa80`07652a60 fffff800`00ba8e70 fffffa80`07652a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`03c2bf0d : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`03c1fe88 : 00000000`00000001 fffff800`03e53e80 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`03cd74ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`03cd7353 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff880`049eac61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9cb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x2c61


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

Playing games works like a charm, running FurMark doesnt result in an error either. I attached the zip-file with the information from your tool, I hope that helps to identify the problem. One last thing, I overclocked the cpu with EasyTune 6 to about 4.01 Ghz, but I doubt that's a problem.

Thank you very much!

Lesall said:

One last thing, I overclocked the cpu with EasyTune 6 to about 4.01 Ghz, but I doubt that's a problem.

Thank you very much!

well, that's pretty much sums up everything :\

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8009b46028, fe200000, 21136}

Probably caused by : hardware

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

0: 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.

...........

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

it's stating that your hardware is (on its way to be) busted, more or less

return to your stock settings. Overclocking might seemed cool, but it potentially could jeopardize your whole system, let alone your hardware

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8009b1a028, be200000, 2110a}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware

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

I'm afraid your processor might be giving in
update intelppm.sys just in case:
http://downloadcenter.intel.com/Default.aspx

Adding to cipley's post,

Code:

0: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3468

Overclocking can be a key cause for Stop 0x124's, which are fundamentally a hardware error, I would strongly suggest that you follow these steps How To Clear CMOS (Reset BIOS).

Overclocking will increase the temperature of your hardware dramatically without any adequate cooling, and causes many stability issues with your system.

cipley said:

I'm afraid your processor might be giving in
update intelppm.sys just in case:
http://downloadcenter.intel.com/Default.aspx

Thank you all for the quick answers. I went back to stock settings asap after reading your answer :) Does this mean I already damaged my processor? But I always thought the K-model of the intel chips are designed to be overclocked? One of my friends has the same chip and its overclocked at about 4.4 Ghz, he never ran into any problems.

I will do some testing to verify that it works now. So basically the whole idea of buying a K-model with a motherboard Z77 to be able to overclock was kind of worthless? Is there any explanation why the problem only occured while watching streams? If the overclocking was really that nasty, shouldn't it crash all the time?

Anyway, thank you very much, I will post the results of my testing later.

it could be many thing, but the main suspect here is the current condition of your processor, mainly due to your overclock settings.
after you change back to stock, see if the performance is any better

Been testing streams about an hour or so, no problems at all after changing back to stock settings. Is there any way to find out if my processor took any serious damage from the overclocking? The Intel Update Utility on http://downloadcenter.intel.com/Default.aspx didnt help very much, it had nothing to update for me Instead it shows some crazy stuff about having a driver version of 12.x for my graphic card, which cant be the fact cause my system has never been installed with a version lower than 13.4 of the CCC.

Well, I wont overclock it for the moment, though I really wonder why my processor was in such a bad condition if its meant to be overclocked For the future, is it better to overclock directly through bios settings instead of doing it with tools like EasyTune?

Anway, thanks for the help, definitely a nice forum!

aah, my bad...the .sys file is Windows', so you won't get it anywhere else

How is your machine's cooling system?
When you overclock, the temperature of your machine is rising, it can literally boil the water
That's why there are some aftermarket PC cooling system designed for the overclockers.
Overclocking can be bad, if not being countered with adequate cooling.
Mine for example, a long time ago though, my processor's pin was melted to the motherboard

There are some actions, such as streaming videos, that is CPU intensive, so maybe that's why you get BSOD everytime you stream

Also, overclocking voids your warranty, CMIIW

If you want to attempt overclocking in the future, then do so in smaller increments through the BIOS rather than a third-party program.

Make sure you have adequate cooling methods in place, for example make sure you have enough thermal paste with the heatsinks and CPU, ensure that the fans are working properly or purchase liquid cooling if needed.

Remove any dust from the slots, case vents, and fans etc.

Well, I bought a giant cpu cooler for exactly that reason :) Its not the boxed cpu cooler that is build on my cpu right now. There was already a thin layer of thermal paste at the bottom of the giant cpu cooler, so I thought that would be enough. I have 5 fans blowing air in and out of my case, so I guess thats already fine, but I will try my luck with manual bios settings next time instead of the third party program.

Lesson learned :)

Again, thank you all for the answers, I really appreciate your help!

Welcome, glad to help and be of assistance :)