clock interrupt not received secondary processor

armydude · Mar 22, 2011

Recently i just started getting "a clock interrupt was not received on a secondary processor within the allocated time interval." a couple weeks before this error I was getting Not less or equal to bsod because of over heating. I put in a corair h50 and the over heating problem was solved but i think some of the hardware might have been damaged hence this bsod.

The only time it ever bsod is when im in a high end game, graphics, rendering, etc. Simple games that dont require much of my computer rarely ever bsod.

some system specs.

motherboard - m4n72-e
2 nvidia gt 9500
athlon 2x 6400 dual core ( underclocked to 2x 6000 atm to hopefully help some)
2 2 gigs of memory
x64 home premium I believe
this computer has only been vista 64
It came pre-installed

hardware age:
Replaced 1-2 years ago
powersupply
Replaced about 1 year ago
2 nvidia gt 9500 graphic cards
motherboard
Replaced in last few weeks
2 2 gigs of memory. (replaced 1 2 gig and 2 1 gigs, but might add some back into cpu as mine can handle it)
Other than what was replaced ive had this computer for a good few years, with issues here and there.

I'm gonna upload the file you guys wanted in the how to post thing but i must say i dont see hardly any minidumps and i believe this to be just a hardware issue. Any help/links on how to check hardware /drivers would be very much appreciated.

EDIT* I found on the forums a FurMark 1.9.0 and installed / ran it. At first even with sli enabled in nvidia control panel it would not use my 2nd gpu. Starting temps were 50f and 80f, it would 1% the 80f gpu then go back to 0% and then 99% the 50f. I looked at their troubleshooting and found if i rename it to the quake .exe file it would run sli. I did this and it worked making both run at 99%, it also made my 80f gpu hit 100f within a few minutes. Its looking like one of my video cards is over heating, and the only time i use both is for gaming with sli.

kesume · Mar 22, 2011

Hi welcome to the forum.
In view of your BSOD's, I will pass this to one of our members who specialises in BSOD's for his attention.
I ask you please to be patient and wait a while until he becomes available.
Thank you.

richc46 · Mar 22, 2011

Although you do not have any minidump reports that are at all current, your particular problem does sound like hardware. Start with the processor.
This may give you some help

CPU Stress Test www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

If that does not help
We will give you a driver test next, good luck.

armydude · Mar 22, 2011

Well I got some good and bad news, I followed everything in the link you gave me and ran prime95(64bit version) on the first option which is the "Small FFTs". After it ran in the background for about 3 minutes i got the same bsod error. I was surfing the web during this for more info but I doubt it had much effect on this outcome.

EDIT* im gonna run it again to see if the same thing happens, any more help you can post in the mean time will be appreciated.(about 3 mins lol)

richc46 · Mar 22, 2011

If you are getting current BSODs, post the files. The three that you gave me were over a year old.

armydude · Mar 22, 2011

Is there anyway to get info other than the minidump files? I have no new ones in there.

EDIT* I downloaded a program called "Core Temp" to check my cpu during prime95 test, they are both staying at about 45-47 each.

richc46 · Mar 22, 2011

There is no other way to get the information, without the mini dumps
Follow instructions to create a memory dump
How do I use WinDBG Debugger to troubleshoot a Blue Screen of Death? | TechRepublic

armydude · Mar 22, 2011

Wow thanks I didn't realize someone had unchecked it so it never made any minidumps > <.

Here is 2 minidumps i got while trying to reboot after changing the settings.(third reboot worked fine)

richc46 · Mar 22, 2011

You had two reports both the same. Not good. Ill bold the portion that presents the problem

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Mini032211-02.zip\Mini032211-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`02c02000 PsLoadedModuleList = 0xfffff800`02dc6dd0
Debug session time: Tue Mar 22 17:59:26.503 2011 (GMT-4)
System Uptime: 0 days 0:00:27.284
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {61, 0, fffffa60005ec180, 1}
[B]Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE[/B] )
Followup: MachineOwner
---------

With a inconclusive this is all that you can do for now.

Bug Check 0x101: CLOCK_WATCHDOG_TIMEOUT

You will notice toward the end it makes reference to the processor, which I did initially.

armydude · Mar 23, 2011

Well I have some more bad news. While tying to fix this I told it to run chkdsk at restart. Blue screened during it then blue screened every time after loading screen which after I looked up said my hard drive was bad etc etc. I downloaded a recovery disk on my laptop, burned it onto a cd and booted my desktop from there doing chkdsk /f and /r. After that it no longer blue screened but resulted in black screen of death with a moveable cursor.

So if there is any suggestion to get around this just to probably get back to my other blue screen problem lol.

Now i've pretty much accepted the fact I will probably have to reformat everything but id like to copy my hard drive over to an external using the command prompt.

Note: At the black screen keyboard works but cant do sticky keys, ctl alt del, anything. Cant restore, the only thing I can do is the command prompt from the bootable cd.

c:\ is my hard drive
f:\ is my external connected usb

Ive been messing with robocopy and some copy / xcopy.)
One of them gave me the folders under c:\ with the "access is denied." under each other, im going through them again to figure out which(think it was xcopy).
I tried robocopy c: f: /r:0 /w:0 and I get "access is denied."

If all else fails I dont have a problem with losing everything as ive backed up my files I can in no way get back a couple weeks ago with the over heating problem.

I need a way to get past the "access is denied." to be able to simply copy my hard drive over. If there is a better place to post this please tell me so I can go ahead and get on since that i've been going at this day and night trying to solve it.

richc46 · Mar 24, 2011

This may work to get you access
Use Ubuntu Live CD to Backup Files from Your Dead Windows Computer - How-To Geek

armydude · Mar 29, 2011

I reformated my machine, updated all windows update stuff and downloaded nivida drivers to get the control panel for it. Computer was freezing for a few seconds every so often when I would tell it to open documents load something etc. I uninstalled my amd cool and quiet which I heard slows down performance. Doing this did help some but it still freezes a little.

I am getting the same blue screen as before. Note the symbol thing I copy/pasted from the site you gave me the VistaSymbols one. I am gonna run the prime thing for as long as I can but this minidump happen while running it last time I tried.

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

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: dwm.exe
CURRENT_IRQL: d
STACK_TEXT:
fffffa60`0c233b28 fffff800`02028380 : 00000000`00000101 00000000`00000061 00000000`00000000 fffffa60`005ec180 : nt!KeBugCheckEx
fffffa60`0c233b30 fffff800`02065d7a : fffff800`02557460 fffffa60`0c233c50 fffffa60`0c233ca0 fffff800`02557460 : nt! ?? ::FNODOBFM::`string'+0x2de4
fffffa60`0c233b70 fffff800`02534f04 : 00000000`00000000 00000009`00b1387b 00000000`00000000 00000009`00b72bee : nt!KeUpdateSystemTime+0xea
fffffa60`0c233ba0 fffff800`0206553d : fffff800`02187980 00000000`00000001 00000009`00000050 fffffa80`069f58d0 : hal!HalpHpetClockInterrupt+0x8c
fffffa60`0c233bd0 fffff800`0207b321 : 00000000`00000000 fffffa60`0c233d98 00000000`00000001 00000000`00000007 : nt!KiInterruptDispatchNoLock+0x14d
fffffa60`0c233d60 fffff800`0208ac51 : 00000000`00000002 00000000`00000000 fffff800`00000000 fffff880`08779000 : nt!MiFlushTbAsNeeded+0x2b1
fffffa60`0c233e70 fffff800`02079e57 : 00000000`00001820 fffff880`08779000 00000000`00008779 fffffa80`00000000 : nt!MiAllocatePagedPoolPages+0x4c1
fffffa60`0c233f40 fffff800`02146437 : 00000000`00000000 fffffa80`04feb010 00000000`00000000 fffff880`00769aa0 : nt!ExpAllocateBigPool+0xa7
fffffa60`0c234020 fffffa60`0112a3ed : 00000000`00000000 fffffa80`049de2d0 fffffa80`049de2d0 fffffa60`007bcc63 : nt!ExAllocatePoolWithTag+0x767
fffffa60`0c2340f0 fffffa60`010fd794 : fffffa80`04feb010 fffffa60`0c234300 00000000`0000002c 00000000`00000000 : Ntfs!NtfsPrefetchFile+0x5bd
fffffa60`0c234220 fffffa60`010e2145 : fffffa80`04feb010 00000000`00000000 fffffa80`049de2d0 00000000`00000000 : Ntfs! ?? ::NNGAKEGL::`string'+0x14b1a
fffffa60`0c234260 fffffa60`007bae91 : 00000000`00000000 fffffa80`049de2d0 00000000`00000001 fffffa80`04feb010 : Ntfs!NtfsFsdFileSystemControl+0x145
fffffa60`0c234310 fffffa60`007d76e2 : fffffa80`04c8f730 fffffa80`04322050 fffffa80`04c8f700 fffffa60`0c234758 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x211
fffffa60`0c234380 fffff800`022cf8ae : fffffa80`049de601 00000000`00001810 fffffa80`049de628 fffffa80`04c8f700 : fltmgr!FltpFsControl+0x102
fffffa60`0c2343e0 fffff800`022e088a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x5be
fffffa60`0c234510 fffff800`0240bef1 : fffff880`09245ca0 ffffffff`fffdb610 fffffa60`0c234678 fffff800`0240bcc1 : nt!NtFsControlFile+0x56
fffffa60`0c234580 fffff800`0240c36c : fffff880`08776c48 fffffa60`0c234750 00000000`0000000d fffffa60`0c234750 : nt!PfpPrefetchEntireDirectory+0x121
fffffa60`0c234630 fffff800`0240c577 : 00000000`00000000 fffff880`00000000 00000000`00000050 00000000`00000000 : nt!PfSnPrefetchMetadata+0x1cc
fffffa60`0c234730 fffff800`0240c99f : 00000003`49630cd0 fffffa80`046a9040 fffff880`0876e000 00000000`00000000 : nt!PfSnPrefetchScenario+0x137
fffffa60`0c234990 fffff800`0233d201 : 00000000`00000000 00000000`aeabe78b fffffa80`07b43730 00000000`00000000 : nt!PfSnBeginAppLaunch+0x35f
fffffa60`0c234a60 fffff800`022f6851 : fffffa80`04329670 fffffa80`07b43730 fffff880`00000002 fffffa80`14050800 : nt! ?? ::NNGAKEGL::`string'+0x40e20
fffffa60`0c234a90 fffff800`020a977a : fffff800`02185680 00000000`76f065f0 fffff800`022f674c fffffa80`04329670 : nt!PspUserThreadStartup+0x105
fffffa60`0c234ae0 fffff800`020a96ed : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
fffffa60`0c234c20 00000000`76f065f0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
00000000`000efb98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f065f0

STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------

kesume · Mar 29, 2011

Hi,
Thank's for the post, and log read out.
WE will, as ever have someone with suitable expertise look at is soon as practical.
As previous, some members are within a different time zone, so the most suitable person isn't always readily available.
Thank you for your patience.

clock interrupt not received secondary processor

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

Attachments

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer