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 want advice before i buy a new processor


  • Please log in to reply
1 reply to this topic

#1 space_heretic

space_heretic

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:01:28 PM

Posted 20 January 2014 - 04:48 PM

I've been getting a clock_watchdog_timeout periodically and generally when the computer is doing undemanding things ie facebook,web browsing. I've yet to see this bsod while playing any game (crysis 3,rome total war 2)

so heres the dmp file any ideas? i can do the basics like building computers, windows installation but advanced stuff like this is out of my league. Thanks for your guys help any is appreciated

 

Microsoft ® Windows Debugger Version 6.3.9600.16384 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\012014-22734-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff800`dac05000 PsLoadedModuleList = 0xfffff800`daec9990
Debug session time: Mon Jan 20 14:53:39.576 2014 (UTC - 6:00)
System Uptime: 0 days 0:04:48.250
Loading Kernel Symbols
.
 
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
 
..............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 101, {30, 0, ffffd00020880180, 3}
 
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
 
Followup: MachineOwner
---------
 
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
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: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd00020880180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.
 
Debugging Details:
------------------
 
 
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  d
 
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
 
STACK_TEXT:  
fffff800`dc717c58 fffff800`dad76f23 : 00000000`00000101 00000000`00000030 00000000`00000000 ffffd000`20880180 : nt!KeBugCheckEx
fffff800`dc717c60 fffff800`dac5981b : 00000000`00000001 fffff800`daef3180 00000000`00002af3 fffff800`daef3180 : nt! ?? ::FNODOBFM::`string'+0x13d83
fffff800`dc717cf0 fffff800`dac5948c : 00000000`00000001 fffff800`dc717d70 fffff800`dc717e30 fffff800`dae9f920 : nt!KiUpdateRunTime+0x57
fffff800`dc717d30 fffff800`dadd831c : fffff800`daed1378 fffff800`dac5f813 fffff800`daef3180 00000000`0000000c : nt!KiUpdateTime+0x63c
fffff800`dc717f10 fffff800`db38ce5f : ffffd000`20bb98c8 fffff800`daef3180 00000000`00000001 00000000`00000000 : nt!KeClockInterruptNotify+0x5c
fffff800`dc717f40 fffff800`dac9b343 : fffff800`db3d9900 fffff800`dad07cd3 fffff800`00000000 00000000`00000000 : hal!HalpTimerClockInterrupt+0x4f
fffff800`dc717f70 fffff800`dad5412a : fffff800`db3d9900 fffff800`daef3180 00000000`00000000 ffffd000`20bb98c8 : nt!KiCallInterruptServiceRoutine+0xa3
fffff800`dc717fb0 fffff800`dad5450f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`20bb9580 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x11f
 
 
STACK_COMMAND:  kb
 
SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: Unknown_Module
 
IMAGE_NAME:  Unknown_Image
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
IMAGE_VERSION:  
 
FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
 
BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:clock_watchdog_timeout_4_proc_analysis_inconclusive
 
FAILURE_ID_HASH:  {cedafc47-d93f-3b54-5d96-138272e3f754}
 
Followup: MachineOwner
---------
 


BC AdBot (Login to Remove)

 


#2 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:12:58 AM

Posted 20 January 2014 - 11:15 PM

:welcome: to the forum mate.

 

 

Yes, a BSOD 101 is definitely CPU related but it doesn't means CPU should be failed. I have seen this BSOD caused by Overheating, incorrect voltage settings, failed Motherboard etc. It is not possible to diagnose core hardware parts via remote assistance.

 

First we need to the details of your system configuration. To collect that, please post a Speccy snapshot of your system by following http://www.bleepingcomputer.com/forums/t/323892/publish-a-snapshot-using-speccy/


Edited by Anshad Edavana, 21 January 2014 - 12:47 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users