Solved BSOD 101 - A clock interrupt was not received on a secondary processor

[ShockBlack]

I built this computer back at the beginning of 2009, and I started getting this same blue screen error, "A clock interrupt was not received...", about once every other week since the beginning of last year, 2011. I investigated it a little here and there but have found no solutions. Unfortunately there isn't a situation that can consistently reproduce this error.

It began as a Windows XP machine, then I upgraded it to the retail version of Windows 7 64bit as soon as Windows 7 was released, and I did a clean install of Windows 7 back in October, 2011. The clean install didn't help.

The only hardware changes were adding an extra stick of RAM, added in the middle of last year, and a new graphics card, which was added a couple months later. These errors were occurring before the hardware changes.

My BIOS is up-to-date and all my drivers are as well. I've done a Memtest over night, which reported no issues, a CPU test with Prime95, which also reported no issues, and a video card test with FurMark for extra measure, no issues there either. So I'm really at a loss...

Attached is my BSOD dump (only going back to October from when I did a clean install) and system file collection along with my system health report and my system specs. Any pointers as to figuring out the culprit of this problem would be greatly appreciated!

 

[scrooge]

maybe bumping your vcore voltage up just a bit will help. or just wait till someone can read the BSOD dump for you.


scrooge

 

[writhziden]

See http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html for information and troubleshooting steps regarding your crashes.

 

[ShockBlack]

See http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html for information and troubleshooting steps regarding your crashes.

That narrows it down. Unfortunately the stress tests tell me there aren't any issues, and attempting to replace parts is really what I was hoping to avoid, unless there's something specific I can replace that will for sure take care of the issue.

maybe bumping your vcore voltage up just a bit will help. or just wait till someone can read the BSOD dump for you.


scrooge

I'm a complete beginner when it comes to overclocking, but from what I read about upping the voltage, it can make the system more stable. If that's the case, I'll certainly give it a try. I used the Intel Desktop Control Center to bump up the voltage from 1.25 to 1.2875 (screenshot attached). I'll leave it at that and report back to let you know if that did the trick.

 

[writhziden]

Did upping the voltage help? If you'd like, I can take a look at your settings and help you with voltage settings if you still need them.

 

[ShockBlack]

You know, upping the voltage really did help. It's been three weeks and I haven't seen a single blue screen error. So thanks, guys! I'll mark this as solved.

 

[writhziden]

Sometimes a small voltage bump is all it takes, especially if you have more than 4 GB of RAM in the system. Glad you got it working. Enjoy!

 

[sw1ft]

My question is how do you bump up the voltage ?
CPU-Z TXT Report
-------------------------------------------------------------------------

Binaries
-------------------------------------------------------------------------

CPU-Z version 1.61

Processors
-------------------------------------------------------------------------

Number of processors 1
Number of threads 8

APICs
-------------------------------------------------------------------------

Processor 0
-- Core 0
-- Thread 0 0
-- Core 1
-- Thread 0 1
-- Core 7
-- Thread 0 7
-- Core 6
-- Thread 0 6
-- Core 2
-- Thread 0 2
-- Core 4
-- Thread 0 4
-- Core 3
-- Thread 0 3
-- Core 5
-- Thread 0 5

Processors Information
-------------------------------------------------------------------------

Processor 1 ID = 0
Number of cores 8 (max 8)
Number of threads 8 (max 8)
Name AMD FX-8150
Codename Zambezi
Specification AMD FX(tm)-8150 Eight-Core Processor
Package Socket AM3+ (942)
CPUID F.1.2
Extended CPUID 15.1
Core Stepping OR-B2
Technology 32 nm
TDP Limit 124 Watts
Core Speed 3926.3 MHz
Multiplier x FSB 19.5 x 201.4 MHz
Rated Bus speed 2416.2 MHz
Stock frequency 3600 MHz
Instructions sets MMX (+), SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, SSE4A, x86-64, AMD-V, AES, AVX, XOP
L1 Data cache 8 x 16 KBytes, 4-way set associative, 64-byte line size
L1 Instruction cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 4 x 2048 KBytes, 16-way set associative, 64-byte line size
L3 cache 8 MBytes, 64-way set associative, 64-byte line size
FID/VID Control yes
Min FID 7.0x
# of P-States 7
P-State FID 0x1A - VID 0x0B - IDD 18 (21.00x - 1.412 V)
P-State FID 0x17 - VID 0x0B - IDD 18 (19.50x - 1.412 V)
P-State FID 0x14 - VID 0x11 - IDD 12 (18.00x - 1.337 V)
P-State FID 0x11 - VID 0x17 - IDD 11 (16.50x - 1.262 V)
P-State FID 0xB - VID 0x22 - IDD 8 (13.50x - 1.125 V)
P-State FID 0x5 - VID 0x2D - IDD 7 (10.50x - 0.987 V)
P-State FID 0x10C - VID 0x35 - IDD 5 (7.00x - 0.887 V)

 

[ShockBlack]

I'm afraid I can't help you with finding out how to up your voltage, but I would suggest creating a new thread as this one is already marked as solved and may get looked over by those that could help you.

I should mention too, as an addendum to this thread, that upping my voltage only mitigated my problem. I still ran into blue screen errors, just less frequently. I finally discovered the true cause of the problem when I put the RAM I was using in my computer that blue-screened into another computer. This other computer was completely unstable on my blue-screening computer's RAM. My RAM was defective, yet stress tests showed no issues, and the blue screen every other week was the only indication that anything was wrong.

So if anyone who's reading this has a similar issue and they're at the point of replacing parts to try to pin down the problem, the RAM is a great place to start. It's very cheap, and if it ends up not being the problem, you get to add more RAM to your computer. If you don't have any more slots, you're not out much and it doesn't hurt to have extra RAM to test your computer with when you run into other hardware problems in the future.