Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD - Clock interrupt not received on secondary processor


16 Dec 2010   #1

Windows 7 Ultimate x64
 
 
BSOD - Clock interrupt not received on secondary processor

I have had a fairly stable system until I decided to leverage 8gb of ram and 64bit through Windows 7. Now daily or more I get greeted with this consistent error that from reading in the various help sites could be one of a million things.
I have tried:
cleaning extensively with Spybot seek and destroy, avast and Prevx. All programs found some traces of malware and cleaned accordingly (prevx found them, just wants me to pay them for the license to clean it...)
I seem to notice it most when playing music and attempting to download data from the internet. That and almost without fail it will BSOD when I leave it overnight running.
Interestingly enough it does not BSOD when I leave it idle on the login screen.

Please help. Its driving me nuts...

O/S details:
Windows Ultimate 64 bit
Vendor Purchased license
Installed about a year ago
upgraded from vista 32-bit (still on box in dual boot mode)

My System SpecsSystem Spec
.

16 Dec 2010   #2

Windows 7 x86/x64, Server 2008r2, Web Server 2008
 
 

Malwarebytes free.
My System SpecsSystem Spec
16 Dec 2010   #3

Windows 7 Ultimate x64
 
 

Malwarebytes run and nothing found....sadly.
My System SpecsSystem Spec
.


17 Dec 2010   #4

Windows 7 Ultimate x64
 
 

I ran windbg and got some more info...

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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002fd5180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis. (if I can get help with this piece, I can continue to self-diagnose)

MODULE_NAME: nt

FAULTING_MODULE: fffff80002e14000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`031b5d88 fffff800`02e32453 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02fd5180 : nt!KeBugCheckEx
fffff880`031b5d90 fffff800`02e8cde7 : fffff8a0`00000000 fffff800`00000003 00000000`00002710 fffff800`02e80ccc : nt!FsRtlAllocateFileLock+0x14b
fffff880`031b5e20 fffff800`033fa895 : fffff800`0341f460 fffff880`031b5fd0 fffff800`0341f460 fffff8a0`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`031b5f20 fffff800`02e80c33 : fffff800`02ffee80 00000000`00000001 00000000`00000006 fffff8a0`00022008 : hal!HalReturnToFirmware+0xb2d
fffff880`031b5f50 fffff800`02e439ef : fffff880`00fd6324 fffff880`00fd6513 fffffa80`06d6d660 fffff800`02fb8646 : nt!KeSynchronizeExecution+0xce3
fffff880`031b60e0 fffff800`0311b70f : 00000000`00000000 fffff880`031b6700 00000000`00000000 fffff880`03f9a0be : nt!MmSizeOfMdl+0x19f
fffff880`031b6150 fffff800`03182116 : fffff8a0`218f40a8 00000000`0001ff58 fffff880`031b62e0 00000000`00000000 : nt!NtSetInformationToken+0x2957
fffff880`031b62a0 fffff800`031831e5 : fffff8a0`218f40a8 fffffa80`6365734b 00000000`00000000 fffff880`031b6c20 : nt!CcUnpinData+0xf76
fffff880`031b6640 fffff800`02e83993 : fffff880`031b6710 fffff800`02e8293d 00000000`00000001 fffffa80`077e0530 : nt!NtQuerySystemInformation+0x4d
fffff880`031b6680 fffff800`02e7ff30 : fffff880`01007a9c 00000000`00000000 fffff880`031b6844 00000000`00000000 : nt!KeSynchronizeExecution+0x3a43
fffff880`031b6818 fffff880`01007a9c : 00000000`00000000 fffff880`031b6844 00000000`00000000 00000000`00000000 : nt!ZwUnlockFile+0x130
fffff880`031b6820 fffff880`0100756d : fffffa80`077e0530 00000000`00000000 fffff800`20206f49 fffff800`02e8f2a1 : cng!SslDecrementProviderReferenceCount+0x305c
fffff880`031b6be0 fffff800`03180c5d : 00000000`00000000 fffffa80`08973920 fffffa80`08973920 fffffa80`06d56b60 : cng!SslDecrementProviderReferenceCount+0x2b2d
fffff880`031b6c80 fffff800`02e91961 : fffff800`03029500 fffff800`03180c20 fffffa80`06d56b60 00000000`00000000 : nt!ObCreateObject+0x77d
fffff880`031b6cb0 fffff800`03128c06 : 00000000`00000000 fffffa80`06d56b60 00000000`00000080 fffffa80`06d44210 : nt!KdPollBreakIn+0x2b1
fffff880`031b6d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PsCreateSystemThread+0x6f2


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlmp.exe


Help...anyone...please? I don't want to replace my mobo/mem/cpu because windows 7 has issues with it!!
My System SpecsSystem Spec
17 Dec 2010   #5

Microsoft Community Contributor Award Recipient

Windows 7 Ult. x64 Windows 8.1 x64 Ubuntu 12.04 LTS Tri-Boot
 
 

Do you have an HPET option in your BIOS? I'm guessing its set to 32bit?

Another possibility might be defective RAM, or mismatched RAM (since that is the only? change you have made since your system started becoming unstable). Can you list the type, make and speed of your RAM?

Use Speccy to gather the information, and post it back here - free version here http://www.piriform.com/speccy
My System SpecsSystem Spec
17 Dec 2010   #6

Windows 7 Ultimate x64
 
 
updated with speccy

Here is the file, i put it in speccy format, does that work?

Not sure on the CPU setting, but that would be a pretty rookie mistake on my part having a proc emulate 32bit with a 64 os. Course, it would solve my problem and that would be a big score!!
My System SpecsSystem Spec
17 Dec 2010   #7

Microsoft Community Contributor Award Recipient

Windows 7 Ult. x64 Windows 8.1 x64 Ubuntu 12.04 LTS Tri-Boot
 
 

Actually, the 32 bit usually works fine even for 64 bit, but it is soemthing you could try.

Could you save the Speccy information as ASCII (TXT) and upload again?

Thanks.
My System SpecsSystem Spec
17 Dec 2010   #8

Windows 7 Ultimate x64
 
 

Per your request and thanks in advance for your quick replies. I have banging on this for months and its just getting me major ticked that I can't catch it or sort it out.
My System SpecsSystem Spec
17 Dec 2010   #9

Microsoft Community Contributor Award Recipient

Windows 7 Ult. x64 Windows 8.1 x64 Ubuntu 12.04 LTS Tri-Boot
 
 

Mmmm......all your RAM is of the same type, so I don't see issues there.

Do you have hyper-threading turned on in the BIOS by any chance? I have seen similar threads here that point to that too?

I'll see if I can find someone more knowleagble to help you out.

EDIT : once last thing - can you open a Command Prompt, and run the SFC /scannow command to test the integrity of the system file - it can take some time, so be patient with that.
My System SpecsSystem Spec
17 Dec 2010   #10

Windows 7 Professional x64
 
 

Hello,

Could you run a couple of hardware tests? In particular, CPU and RAM.

For CPU: http://www.sevenforums.com/tutorials...t-prime95.html

Run the Blend test, as well as the Small FFTs.

Also, run a dedicated RAM test overnight, using Memtest86. See this guide: RAM - Test with Memtest86+

Here is an article on the 101 bugcheck: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

...Summary of the dumps:
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Dec 16 04:00:56.453 2010 (UTC - 5:00)
System Uptime: 0 days 6:11:31.638
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Dec 15 07:52:24.618 2010 (UTC - 5:00)
System Uptime: 0 days 0:24:05.428
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Bandwidth Moni
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Dec 15 03:00:46.017 2010 (UTC - 5:00)
System Uptime: 1 days 4:22:12.201
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Dec 13 20:30:06.842 2010 (UTC - 5:00)
System Uptime: 0 days 21:53:47.027
*** WARNING: Unable to verify timestamp for TfFsMon.sys
*** ERROR: Module load completed but symbols could not be loaded for TfFsMon.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
My System SpecsSystem Spec
Reply

 BSOD - Clock interrupt not received on secondary processor




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 01:34 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33