BSOD once

[revan89]

Hi,

My system has been up and running without any problems for almost 2 months, and while watching youtube just now got hit by a BSOD.

Here are my specs

Windows 7 64 bit retail
Intel i7 2600K OC to 4.7Ghz @ 1.39V
GSkill 8gb 2133Mhz default timings
2x EVGA GTX 580 Black Ops
Creative SB Titanium HD
Antec HCP 1200W
ASUS P8P67 WS Revolution B3

Also attached the dumps

Thanks

 

[yowanvista]

Dumps indicate the CPU as the cause, please stop any overclocking and see if you get more BSODs with the no overclocks
If you still experience BSODs test your CPU

   Information

Run Prime 95 to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008729028, be200000, 5110a}

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

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: fffffa8008729028, 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:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f2b58 fffff800`03c15a3b : 00000000`00000124 00000000`00000000 fffffa80`08729028 00000000`be200000 : nt!KeBugCheckEx
fffff880`009f2b60 fffff800`037a7563 : 00000000`00000001 fffffa80`087b5a60 00000000`00000000 fffffa80`087b5ab0 : hal!HalBugCheckSystem+0x1e3
fffff880`009f2ba0 fffff800`03c15700 : 00000000`00000728 fffffa80`087b5a60 fffff880`009f2f30 fffff880`009f2f00 : nt!WheaReportHwError+0x263
fffff880`009f2c00 fffff800`03c15052 : fffffa80`087b5a60 fffff880`009f2f30 fffffa80`087b5a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f2d50 fffff800`03c14f0d : 00000000`00000008 00000000`00000001 fffff880`009f2fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f2d90 fffff800`03c08e88 : 00000000`00000002 fffff880`009ea180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f2dc0 fffff800`036985ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f2df0 fffff800`03698453 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f2f30 fffff880`04c02c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0391bb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x2c61


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

 

[revan89]

hmm it's quite strange then that cpu oc is the fault. I've ran overnight intel burn test before without errors, played through demanding games like crysis 2, witcher 2, dirt 3, metro 2033, sc2 all without problems.

 

[yowanvista]

hmm it's quite strange then that cpu oc is the fault. I've ran overnight intel burn test before without errors, played through demanding games like crysis 2, witcher 2, dirt 3, metro 2033, sc2 all without problems.

You might want to reduce the overclock, this might eliminate the BSODs

 

[revan89]

i'll give it a try. thanks loads

 

[revan89]

btw is there a sticky thread which teaches how to self diagnose bsod?

 

[yowanvista]

btw is there a sticky thread which teaches how to self diagnose bsod?

See this thread
http://www.sevenforums.com/crash-lockup-debug-how/26584-configuring-debugging-tools.html