CPU related BSOD - Windows 8 x64

Giorgio

New member
Joined
Aug 18, 2015
Posts
3
Hey there, new here and really need help with this problem I'm having. I suspect that the problem involves my cpu (intel i7-4770k @4.4 ghz overclocked).
I recently started playing Sid-Meier's civilization V with friends, and over a course of a couple hours I hit around 4-5 BSOD's.
However, I get BSOD's in almost all games I play (yet not everytime I play) and the two most frequent errors I see whilst playing games are whea_uncorrectable_error and clock_watchdog_timeout.
Was looking for help to fix my issue, any help will be appreciated.

Here is one of my mini-dumps:


Code:
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.




Loading Dump File [C:\Windows\Minidump\081815-18328-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available




************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*[url]http://msdl.microsoft.com/download/symbols[/url]
Symbol search path is: SRV*C:\SymCache*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is: 
Windows 8 Kernel Version 10240 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10240.16430.amd64fre.th1.150807-2049
Machine Name:
Kernel base = 0xfffff801`2e487000 PsLoadedModuleList = 0xfffff801`2e7ac030
Debug session time: Tue Aug 18 16:21:11.953 2015 (UTC + 1:00)
System Uptime: 0 days 0:11:13.568
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 124, {0, ffffe0019bed7028, bf800000, 124}


Probably caused by : GenuineIntel


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


7: 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: ffffe0019bed7028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.


Debugging Details:
------------------




BUGCHECK_STR:  0x124_GenuineIntel


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


PROCESS_NAME:  CivilizationV_


CURRENT_IRQL:  f


ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre


STACK_TEXT:  
ffffd000`6b26e6f8 fffff801`2e44b94f : 00000000`00000124 00000000`00000000 ffffe001`9bed7028 00000000`bf800000 : nt!KeBugCheckEx
ffffd000`6b26e700 fffff801`2e6da118 : ffffe001`9bed7028 ffffe001`9b0b5950 ffffe001`9b0b5950 ffffe001`9b0b5950 : hal!HalBugCheckSystem+0xcf
ffffd000`6b26e740 fffff801`2e44be3c : 00000000`00000728 00000000`00000007 ffffd000`6b26eb30 00000000`00000000 : nt!WheaReportHwError+0x258
ffffd000`6b26e7a0 fffff801`2e44c19c : ffffe001`00000010 ffffe001`9b0b5950 ffffd000`6b26e948 ffffe001`9b0b5950 : hal!HalpMcaReportError+0x50
ffffd000`6b26e8f0 fffff801`2e44c088 : ffffe001`9b0b4fa0 00000000`00000001 00000000`00000007 00000000`00000000 : hal!HalpMceHandlerCore+0xe8
ffffd000`6b26e940 fffff801`2e44c2c6 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd000`6b26e980 fffff801`2e44c450 : ffffe001`9b0b4fa0 ffffd000`6b26ebb0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd000`6b26e9b0 fffff801`2e5de67b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd000`6b26e9e0 fffff801`2e5de431 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd000`6b26eb20 00000000`013ffa9e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
00000000`0f965984 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x13ffa9e




STACK_COMMAND:  kb


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: GenuineIntel


IMAGE_NAME:  GenuineIntel


DEBUG_FLR_IMAGE_TIMESTAMP:  0


IMAGE_VERSION:  


FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE


BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_cache


FAILURE_ID_HASH:  {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}


Followup: MachineOwner
---------
 
Last edited by a moderator:
Yeah, 99% certain it's your CPU.
If it's under warranty, RMA it.
 
Does the crash occur if you are not running an OC?

Manufacturers only guarantee their products up to the speeds they ship them. Since you are OC'ing there is no guarantee from Intel that the CPU will be stable.

I suggest removing the OC and trying it again. If your computer is then stable the problem was your OC.

I don't believe we have an OC'ing guide here but if it does end up being your OC I suggest you follow a guide to help find stable settings.
 
Does the crash occur if you are not running an OC?

Manufacturers only guarantee their products up to the speeds they ship them. Since you are OC'ing there is no guarantee from Intel that the CPU will be stable.

I suggest removing the OC and trying it again. If your computer is then stable the problem was your OC.

I don't believe we have an OC'ing guide here but if it does end up being your OC I suggest you follow a guide to help find stable settings.

Unless I'm missing something I don't believe the OP is actually overclocking.
I think the 4.4GHz overclock he is referring to is the inbuilt turbo boost mechanism rather than a manual one, unless the OP would like to correct me.
 
Last edited:
You're right, it's not a manual OC. I configured it in BIOS when I got the PC, but I'm unsure whether that will increase the chances of crashing my pc. If it will, please tell me and I'll run a test :D
 
Ah sorry Laxer, it wasn't a manual overclock, and my cpu runs at the factory 'guaranteed' speed. However, I configured the speed in BIOS a while ago, and sort of consider that an overclock :P
 
Perhaps I am wrong but, I would still check it out... :r1:

4770k is only guaranteed up to 3.9GHz (Turboed)
4790k is up to 4.4GHz

So my first question would be if you have the 4770k or 4790k. If it is the 4770k I would suggest going into bios and disabling the overclock and testing. Some motherboard manufacturers have an "Automatic Overclock" option which may be what you referring to in which case it is still an overclock and operating outside of the guaranteed spec by Intel. Usually I get watchdog timeouts when I adjust the Base-Clock too high, for your CPU it should be at 100MHz stock...

Once again, assuming it is an automatic overclock you might find stability if you increase the voltage although I wouldn't go much north of 1.2v
 
Last edited:
Perhaps I am wrong but, I would still check it out... :r1:

4770k is only guaranteed up to 3.9GHz (Turboed)
4790k is up to 4.4GHz

So my first question would be if you have the 4770k or 4790k. If it is the 4770k I would suggest going into bios and disabling the overclock and testing. Some manufacturers have an "Automatic Overclock" option which may be what you referring to in which case it is still an overclock and operating outside of the guaranteed spec by Intel. Usually I get watchdog timeouts when I adjust the Base-Clock too high, for your CPU it should be at 100MHz stock...

Once again, assuming it is an automatic overclock you might find stability if you increase the voltage although I wouldn't go much north of 1.2v

Missed the fact that it is an i7 4770K. My bad, then yeah, it'll be a manual one.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top