Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

CLOCK_WATCHDOG_TIMEOUT (101) on Asus Maximus VII Hero i7


  • Please log in to reply
5 replies to this topic

#1 FrankMy

FrankMy

  • Members
  • 3 posts
  • OFFLINE
  •  

Posted 30 December 2017 - 08:15 PM

Since a couple of weeks my son is having continous BSODs with CLOCK_WATCHDOG_TIMEOUT on his Gaming PC which is about 3 years old which worked very stable until then.

 

We have reset the mainboard settings to default (no overclocking) and also done a fresh install of Windows 10 which is now a version from early December. Also we've flashed the latest BIOS from Asus.

 

The system runs fine as long as there is no system load. When he puts load on it (or when running Prime 95), the BSOD happens very quickly.

 

I've also run Prime 95 in Safe Mode and there it ran smoothly for 2 hours. When running in normal Windows mode, it crashes after a few seconds / no longer than 2 minutes after start.

 

System Config is here:

  • Asus MAXIMUS VII HERO Intel Z97 So.1150 Dual
  • Intel Core i7 4790K 4x 4.00GHz So.1150 BOX
  • 16GB (2x 8192MB) Corsair Vengeance Pro Series
  • EKL Alpenföhn Brocken 2 Tower Cooler

I've attached some Windows Debugger Dump File Analysis files.

 

Bugcheck analysis tells:

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffa281bff12180, The PRCB address of the hung processor.
Arg4: 0000000000000006, The index of the hung processor.

Once I also got the following error:

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

I'm not quite sure how to best trace down the cause of the error. Any hints for me? Do you think that the CPU may be damaged?

 

Thanks a lot for your help!



BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,011 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:10:12 PM

Posted 30 December 2017 - 08:26 PM

Can you follow these instructions - https://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/ ? No need to create a new topic by the way (referring to step 3) — you already have one here.

 

I'm quite certain that there's a hardware fault with the CPU. When you run Prime95 how hot does the CPU get? To debug a 0x101 we typically need a full dump rather than a minidump, but there may be no point obtaining one in your case...

 

BTW did you turn on Driver Verifier?


Edited by bwv848, 30 December 2017 - 09:07 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 FrankMy

FrankMy
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  

Posted 31 December 2017 - 09:58 AM

Thanks very much for the instructions. I've attached both Sysnative files and Speccy file.

 

 

When running the Prime95 tests, the CPU cores get really hot, core #1 up to 94 C. I've reinstalled the Tower Cooler with new heat paste, but that didn't change the situation. Not sure if this could be related to a CPU error or a fan error?

 

Attached File  CoreTemp-Scr.png   28.89KB   0 downloads

 

I had also done a Driver Verifier test a few days ealier resulting in a BSOD during the Windows boot phase. I need to read through the instructions again and do it again, didn't have the time to do so until now. Not sure if it is needed now since the overheating issues seems to cause the issue.

 

Thanks again for your help!



#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,011 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:10:12 PM

Posted 31 December 2017 - 04:29 PM

Thank you. Feel free to turn off Driver Verifier now — it will be of no use in your case, a hardware-related case.

I've had a look at the dumps in the reports — there were three 0x124s and one 0x101s. I'll only be posting analysis of the latest 0x124 dump, as the older 0x124s are mostly identical and 0x101 minidumps aren't very helpful (particularly your dump).
2: kd> .bugcheck
Bugcheck code 00000124
Arguments 00000000`00000000 ffffc706`58783028 00000000`be000000 00000000`00800400
2: kd> r $bug_param2
$bug_param2=ffffc70658783028
2: kd> !errrec ffffc70658783028
===============================================================================
Common Platform Error Record @ ffffc70658783028
-------------------------------------------------------------------------------
Record Id     : 01d38242fbe0560b
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 12/31/2017 14:39:32 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffc706587830a8
Section       @ ffffc70658783180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffc706587830f0
Section       @ ffffc70658783240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : c3 06 03 00 00 08 10 02 - bf fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffffc70658783240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffc70658783138
Section       @ ffffc706587832c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 2 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0xfffff801daf2aa2d
  Misc.       : 0xfffff801daf2aa2d
2: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 3998
2: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.8, DMIVersion 0, Size=3831]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = 3201
BiosReleaseDate = 01/24/2017
SystemManufacturer = ASUS
SystemProductName = All Series
SystemFamily = ASUS MB
SystemVersion = System Version
SystemSKU = All
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = MAXIMUS VII HERO
BaseBoardVersion = Rev 1.xx
So you can see that the system crashed due to a detected internal timer error as seen from the WHEA error record, which is consistent with all the other 0x124 dumps. And they all occurred when you ran Prime95...
 
Given that the CPU is overheating at 94°C this shouldn't be surprising. Since the system has been running fine for three years, I do suspect that the CPU is faulty, especially after you've replaced the thermal paste and gotten a new cooler. Have you made sure the inside of the case is completely free of dust and other foreign objects? Apart from that I would suggest you post in the Internal Hardware forums for more expert advice https://www.bleepingcomputer.com/forums/f/7/internal-hardware/ it's certainly a hardware related problem.

Edited by bwv848, 31 December 2017 - 04:31 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#5 FrankMy

FrankMy
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  

Posted 02 January 2018 - 12:10 PM

Thanks a lot for your help. I've now found a way how I can get the system run stable - in the Windows power options I limit the max CPU speed to 90% (see below). Since then there have been no crashes, even when running Prime 95. We will have to buy a new CPU at one point, but for the time being this seems to solve the problem.

 

Attached File  2018-01-01.png   34.93KB   0 downloads



#6 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,011 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:10:12 PM

Posted 02 January 2018 - 01:48 PM

You're welcome! Glad you found a temporary solution. I certainly agree with you that you should get a new CPU in the future.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users