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.

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.

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.

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

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

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}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
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.