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)

Malwarebytes free.

Malwarebytes run and nothing found....sadly.

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!!

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

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!!

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.

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.

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.

Hello,

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

For CPU: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

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

Also, run a dedicated RAM test overnight, using Memtest86. See this guide: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Here is an article on the 101 bugcheck: http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

...Summary of the dumps:

After running Prime95 and Memtest86+ as Jonathan_King recommended, can you Download Core Temp and post the CPU temps?

Have you checked the CPU temp before?
AMD CPUs usually run cool, 59 C is pretty high.

Post using the snipping tool, type 'Snipping Tool' in the start button search box and hit enter.
Select the area and save to a convenient place.

Post it here using the upload as explained: How to Post a Screenshot in Seven Forums
Check if your RAM is in 'Unganged' mode.

Easy way to check is to D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.

Also, go to your BIOS and tell us what the CPU, RAM and North Bridge (NB) voltages are.

Let us know if you have any questions.

Okay, it took a while but I ran the tests suggested and no errors at all...

Any more thoughts? I appreciate the assistance so far...

Check your CPU temps and post the info requested above in post#11.

Okay, here are the temps...

Speedfan is what I used for the temp readings, hope that works for you guys. Its been my best tool in my toolkit for years.
GPU 72C, CORE 62C.

Before I started the load test, GPU was 62C and the CORE was 51C
After I stopped the test it went back down quickly to the starting temps

Memory is in ganged mode.

All voltages are set to auto. I don't overclock anything that is why this is so hard to figure out for me. I could see if I was tweaking...

Anyways, thanks all for the support so far.

What is next?

Is this your CPU?
AMD Phenom™ X4 9500


If it is, check the voltages on the above link, they are 1.10/1.15/1.20/1.25V.

Yours is showing a voltage of 1.312v from CPUZ and Speedfan.


Your max temp is 70 C, from the above link.


Your CPU is running too hot.


Go to your BIOS and change the VCore to 1.20v.


If your system won't run at that voltage then bring it up by 0.02v until it is stable.


You will see much lower CPU temps.
Check it with Core Temp to be sure.

Once the CPU voltage is down to a reasonable level and stable, Run Prime95 and keep Core Temp open and watch the temps until they stabilize.


You might need to change the RAM to 'Unganged' mode, this will make your RAM more stable.

Adding RAM from 2 X 2GB to 4 X 2GB will sometimes require a north bridge voltage bump.
We will look at that next.

Okay two fan units later (antec vcool, antec spot cool - positioned directly over vga heatsink), 1 voltage adjustment to 1.2 v and unganged the memory, here are the results.

Does lower voltage mean slower proc tho? (Sorry for the newbie question...) Seems slower, but maybe its because I have consciously made the changes.

I have not run the load tests tho, that is next...

Lets see if she makes it through the nite without BSOD's!

The Core Speed is how you over clock the CPU, you adjust the voltage to make it stable.

Low voltage will cause it to stop working, too high voltage causes excess heat.

Your CPU speed is the same when you adjust the voltage.


Check in your BIOS for the RAM and NB voltage, post it here.

As much as any avid computer geek hates these words... Underclock your CPU. I have the same CPU/mobo.. setting to auto BSOD to insanity. for some reason It was autoing to 5.5 so CPU-Z said anyway. As far as i am aware its supposed to be 11. anyway I set it up to 6x and I haven't had any Clock_Interupt problems. just an accasional IRQL stop . I'm going to step it up a little bit over the next few days to see how high it will stay stable at..

It took me a little while to weed my problem out, I hate the conclusion. But it's solved..

Just before i found the solution, i broke down and ordered a 9750 since it has no complaints of this problem.. LOL now im debating on going through another journey of taking the water block off (4th time since I've built this computer. And slapping the non problematic CPU in. ^_^

Hope this helps.. Also, keep your cool'n'quiet off, C1E doesnt make a difference. If your not going to virtualize any OS's turn it off to.