BSOD - Clock Watchdog Timeout - 0x101 - Processor 2 Not Responding?

Question

BSOD - Clock Watchdog Timeout - 0x101 - Processor 2 Not Responding?

Anonymous

Hi,

I am at my wits end with this, so I am reaching out for help with this. Recently, I decided to upgrade my AMD Athlon 64 3200+ processor to an AMD Athlon 64 FX FX-60 (Dual Core) processor; however now I keep getting Blue Screens from time to time. The system will idle forever with no problem, even runs some programs without incident. But, when I stress the CPU with Prime 95, I get a Blue Screen within 5 mins. I also get a Blue Screen when I stream Netflix video (faster with HD). I have done most of the troubleshooting and I have narrowed it down to this. I am getting sporadic blue screen 0x101 CLOCK WATCHDOG TIMEOUT errors and I am NOT getting any response from Processor 2; HENCE the hang up error. I have analyze the dump file with WinDbg.. It verifies Processor 2 is failing 60 clock ticks in, the hang address is fffff880009e6180 and what was being processed when it failed. The wall that I am running into is the file that is crashing the system is UNKNOWN (Module Name & Image Name), !prcb 1 (cannot get PRCB address) and !irql 1 (cannot get PRCB address from processor 0x1). So, since Processor 2 is not reporting anything, I am stuck on how to proceed. How do I move forward and get the information out of Processor 2??? ALL SUGGESTIONS WILL BE WELCOME.. Thanks!

WHAT I HAVE ALREADY DONE:

CPU - FAILS (Prime95 stress test)

Cooling - GOOD

Vcore - GOOD

RAM - GOOD (Ran a 6 hr. Memtest)

Drivers - GOOD (Ran a driver scan with Driver Reviver)

My System:

Window 7

RAM: 4GB

CPU: AMD Athlon 64 FX FX-60

Mobo: K8NNeo4 Series MS-7125 (v3.X) ATX Mainboard

DUMP ANALYSIS:

Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64

Loading Dump File [C:\Windows\Minidump\042914-39062-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************

Response Time (ms) Location

Deferred srv*downstreamstore*http //msdl.microsoft.com/download/symbols

Symbol search path is: srv*downstreamstore*http //msdl.microsoft.com/download/symbols

Executable search path is:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333

Machine Name:

Kernel base = 0xfffff8000300a000 PsLoadedModuleList = 0xfffff8000324e670

Debug session time: Tue Apr 29 14:47:55.266 2014 (UTC - 4:00)

System Uptime: 1 days 4:35:01.625

Loading Kernel Symbols

...............................................................

................................................................

..........................................................

Loading User Symbols

Loading unloaded module list

......

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {60, 0, fffff880009e6180, 1}

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: 0000000000000060, Clock interrupt time out interval in nominal clock ticks.

Arg2: 0000000000000000, 0.

Arg3: fffff880009e6180, The PRCB address of the hung processor.

Arg4: 0000000000000001, 0.

Debugging Details:

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: d

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

STACK_TEXT:

fffff880009a9768 fffff800030dfd5a : 0000000000000101 0000000000000060 0000000000000000 fffff880009e6180 : nt!KeBugCheckEx

fffff880009a9770 fffff80003092ad7 : 0000000000000000 fffff80000000001 0000000000002626 0000000000000002 : nt! ?? ::FNODOBFM::`string'+0x4e2e

fffff880009a9800 fffff800036061c0 : 0000000000000000 fffff880009a99b0 fffff800036223c0 fffff80000000000 : nt!KeUpdateSystemTime+0x377

fffff880009a9900 fffff80003085513 : 00000000398a7bb9 fffff800036223c0 0000000000000000 fffff800030a7e84 : hal!HalpRtcClockInterrupt+0x130

fffff880009a9930 fffff800030be7f9 : fffff800031fbe80 0000000000000001 0000000000000000 0000000000000000 : nt!KiInterruptDispatchNoLock+0x163

fffff880009a9ac0 fffff8000308de0c : 0000000000000000 fffff880009a9bf8 0000000000000000 0000000000000000 : nt!KxFlushEntireTb+0x85

fffff880009a9b00 fffff8000304b489 : 0000000000000010 0000000000000000 fffffa80000320d0 0000000000000010 : nt!KeFlushMultipleRangeTb+0x28c

fffff880009a9bd0 fffff8000304bcd7 : 0000000000001000 000000000000000f 0000000000000000 fffffa80026ffff8 : nt!MiZeroPageChain+0x14e

fffff880009a9c10 fffff8000331fe5a : fffffa800280bab0 0000000000000080 fffffa800280b040 fffff80003079d19 : nt!MmZeroPageThread+0x83a

fffff880009a9d40 fffff80003079d26 : fffff800031fbe80 fffffa800280bab0 fffff80003209cc0 3900350045003800 : nt!PspSystemThreadStartup+0x5a

fffff880009a9d80 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

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

BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_clock_watchdog_timeout_2_proc_analysis_inconclusive

FAILURE_ID_HASH: {f1d742c8-d2bd-7559-9a14-2cd83aa3aa50}

Followup: MachineOwner

0: kd> !prcb 0

PRCB for Processor 0 at fffff780ffff0000:

Current IRQL -- 13

Threads-- Current fffffa800280bab0 Next 0000000000000000 Idle fffff80003209cc0

Processor Index 0 Number (0, 0) GroupSetMember 1

Interrupt Count -- 2842fd7c

Times -- Dpc 00001e14 Interrupt 00008afc

Kernel 005286b8 User 0011f6af

0: kd> !prcb 1

Cannot get PRCB address

0: kd> !irql 0

Debugger saved IRQL for processor 0x0 -- 13

0: kd> !irql 1

Cannot get PRCB address from processor 0x1

0: kd> kv

Child-SP RetAddr : Args to Child : Call Site

fffff880009a9768 fffff800030dfd5a : 0000000000000101 0000000000000060 0000000000000000 fffff880009e6180 : nt!KeBugCheckEx

fffff880009a9770 fffff80003092ad7 : 0000000000000000 fffff80000000001 0000000000002626 0000000000000002 : nt! ?? ::FNODOBFM::`string'+0x4e2e

fffff880009a9800 fffff800036061c0 : 0000000000000000 fffff880009a99b0 fffff800036223c0 fffff80000000000 : nt!KeUpdateSystemTime+0x377

fffff880009a9900 fffff80003085513 : 00000000398a7bb9 fffff800036223c0 0000000000000000 fffff800030a7e84 : hal!HalpRtcClockInterrupt+0x130

fffff880009a9930 fffff800030be7f9 : fffff800031fbe80 0000000000000001 0000000000000000 0000000000000000 : nt!KiInterruptDispatchNoLock+0x163 (TrapFrame @ fffff880`009a9930)

fffff880009a9ac0 fffff8000308de0c : 0000000000000000 fffff880009a9bf8 0000000000000000 0000000000000000 : nt!KxFlushEntireTb+0x85

fffff880009a9b00 fffff8000304b489 : 0000000000000010 0000000000000000 fffffa80000320d0 0000000000000010 : nt!KeFlushMultipleRangeTb+0x28c

fffff880009a9bd0 fffff8000304bcd7 : 0000000000001000 000000000000000f 0000000000000000 fffffa80026ffff8 : nt!MiZeroPageChain+0x14e

fffff880009a9c10 fffff8000331fe5a : fffffa800280bab0 0000000000000080 fffffa800280b040 fffff80003079d19 : nt!MmZeroPageThread+0x83a

fffff880009a9d40 fffff80003079d26 : fffff800031fbe80 fffffa800280bab0 fffff80003209cc0 3900350045003800 : nt!PspSystemThreadStartup+0x5a

fffff880009a9d80 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

0: kd> ~1

Can't switch processors on a kernel triage dump

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

10 answers

Answer 1

Hi,

That Bug_Check is usually either BIOS, low level chipset driver or other drivers, or hardware.

Are you over-clocking at all? If so revert everything back to the manufacturers default or

recommended settings. This could be damage caused by heat.

Well the minidump was no help so that also usually indicates hardware.

Remove ALL power then reseat the cards, memory, and cables.

Could be the processor, the heat sink, or even the compound between them (since it failed

the Prime95 test) or even the motherboard.

Resolving stop (blue screen) errors in Windows 7 - has a section for if you can or can't start Windows.

http://windows.microsoft.com/en-us/windows7/Resolving-stop-blue-screen-errors-in-Windows-7

References to Vista also apply to Windows 7.

Have you added any hardware lately? Main likely culprits are hardware, major drivers, memory, and antivirus/antispyware/security products could be at fault.

BCCode: 101 0x00000101

Bug Check 0x101: CLOCK_WATCHDOG_TIMEOUT

The CLOCK_WATCHDOG_TIMEOUT bug check has a value of 0x00000101. This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

Important Information If You Have Received a STOP Code

If you have received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact information for Microsoft or your computer manufacturerContact Support.

If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft articleResolving STOP (Blue Screen) Errors in Windows.

The following actions might prevent an error like this from happening again:

Download and install updates and device drivers for your computer from Windows Update.
Scan your computer for computer viruses.
Check your hard disk for errors.

Cause

The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

BCCode: 101 0x00000101 <-- read this link

http://www.faultwire.com/solutions-fatal_error/A-clock-interrupt-was-not-received-on-a-secondary-0x00000101-*1254.html?order=date

Hope this helps.

Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right.

Answer 2

Log Name: Application

Source: Application Error

Date: 30/04/2014 14:55:00

Event ID: 1000

Task Category: Application Crashing Events

Level: Error

Description:

Faulting application name: kdbsync.exe, version: 0.0.0.0, time stamp: 0x4f67a718

Faulting module name: amdocl.dll, version: 10.0.1084.4, time stamp: 0x50d225d5

Exception code: 0xc0000005

Fault offset: 0x00057bee

Faulting process id: 0x12c4

Faulting application start time: 0x01cf647bb0214f36

Faulting application path: C:\Program Files (x86)\AMD AVT\bin\kdbsync.exe

Faulting module path: C:\Windows\system32\amdocl.dll

Report Id: 04e41a71-d06f-11e3-883a-0019db276b2f

Try the suggestion in this link:

http://www.winxperts.net/forums/topic/2069-kdbsyncexe-has-stopped-working-fix/

Log Name: System

Source: Microsoft-Windows-DistributedCOM

Date: 30/04/2014 14:54:33

Event ID: 10016

Level: Error

Description:

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID

{C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Solution:

Make sure you’re logged on as an administrator.
Click Start, type regedit in the Search bar, then click regedit.exe

3. In the Registry Editor, press CTRL-F, type {344ED43D-D086-4961-86A6-1106F4ACAD9B} and click “Find Next”.

4. The first result is located in HKEY_CLASSES_ROOT\AppID. This is the key we need.

5. Right-click the key {344ED43D-D086-4961-86A6-1106F4ACAD9B} in the left sidebar, and then press “Permissions…"

6. We first have to change the ownership of the key. The current owner is TrustedInstaller. We have to change the owner to Administrators. Therefor, click Advanced. Then go to the tab Owner, select Administrators, check the box “Replace owner on subcontainers and objects” and press OK.

7. Now that we have changed the ownership to ourself (member of the Administrators group), we can change the permissions on the registry key. In the Permissions window, grant Administrators AND SYSTEM Full Control permissions. Then click OK to confirm the changes. In these 8 steps, we have granted the Administrators and SYSTEM account full permissions to the key HKEY_CLASSES_ROOT\AppID{344ED43D-D086-4961-86A6-1106F4ACAD9B}.

8. Verify that in this key, the value of LocalService is IPBusEnum

9. Click Start, type Component in the Search box, and then click Component Services

10. In the Component Services window, go to Computers –> My Computer –> DCOM Config. Right-click IPBusEnum and click Properties.

11. Go to the tab Security. In the Launch and Activate permissions section, select Customize and click Edit.

12. Select SYSTEM, select the permissions checkbox “Local Launch”. Then click OK to apply the change.

13. Done!

Source: Paolo123 http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/dcom-error-10016-in-event-viewer-windows-7-home/a320103d-6f77-e011-8dfc-68b599b31bf5

Have you had problems updating Windows and hidden any updates?

Log Name: Application

Source: SideBySide

Date: 29/04/2014 05:32:50

Event ID: 63

Level: Error

Description:

Activation context generation failed for "c:\program files (x86)\spybot - search & destroy\DelZip179.dll".Error in manifest or policy file "c:\program files (x86)\spybot - search & destroy\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.

Uninstall and reinstall Spybot S & D.

Please post copies of your dump files as shared files (excluding any more than one month old) to your OneDrive with a link here. I would like to look in more detail at the files in one of the dump files.

Please download and run Driver View and upload a copy of the report it produces to your OneDrive. To get a report on all drivers select Edit, Select All followed by File, Save Selected Items.

http://www.nirsoft.net/utils/driverview.html

Answer 3

Anonymous

Hi, Gerry

Thank you for the reply. Your instructions were very accurate and to the point. Here is the link that you requested:

System Info, System Logs and Event Logs (SHARED FOR ALL)

0 comments

Answer 4

Please provide a copy of your System Information file. Type System Information in the Search Box above the start Button and press the ENTER key (alternative is Select Start, All Programs, Accessories, System Tools, System Information). Select File, Export and give the file a name noting where it is located. Do not place the cursor within the body of the report before exporting the file. The system creates a new System Information file each time system information is accessed. You need to allow a minute or two for the file to be fully populated before exporting a copy. Please upload to your OneDrive (formerly Sky Drive), share with everyone and post a link here. Reports in normal mode preferred. Please say if the report has been obtained in safe mode.

Please upload and share with everyone copies of your System and Application logs from your Event Viewer to your OneDrive and post a link here.

To access the System log select Start, Control Panel, Administrative Tools, Event Viewer, from the list in the left side of the window expand Windows Logs and select System. Place the cursor on System, select Action from the Menu and Save All Events as (the default evtx file type) and give the file a name. Do the same for the Applications log. Do not provide filtered files. Do not clear logs whilst you have a continuing problem.

For help with OneDrive see paragraph 9.3:

http://www.gerryscomputertips.co.uk/MicrosoftCommunity1.htm

Answer 5

Anonymous

Hi,

Thanks for the quick response. No, I am NOT over-clocking at all, everything is set to standard configuration.

0 comments

Share via

BSOD - Clock Watchdog Timeout - 0x101 - Processor 2 Not Responding?

10 answers