[BSOD] A clock interrupt was not received on the secondary processor

[Veniathan]

Hello people, i just registered in hope for some fixes. This problem appared to me 2 weeks ago. Where my BSOD's were not often at all.

However these other days in the week, they've been happening every 2 - 3 days. But that has also dissapeared. Now i BSOD really often, when ever the computer feels like it.

This started happening as i said 2 weeks ago when i changed my Motherboard and Processor. Because my old one was a AMD 5200+ Dualcore on a M2N-E Asus AM2

They both died at the same time. So i got myself a ASRock N68-S UCC.

But do note that the first four to five days this didnt happen. Everything was fine after changing my hardware. So .. Ive read my minidumps with "whocrashed" and it indicates it is most likely a driver/software problem and NOT hardware.

Yes indeed this is a wall of text, but as a gamer i cannot proceed to enjoy my hobby with a BSOD constantly popping up. Ill post my specs below and all that


CPU: AMD Athlon 64 X2 Dual Core 6000+ 3.0 Ghz
GPU/Video Card: Nvidia 9600 GT
RAM: 4 Gigabyte
Motherboard: ASRock N68-S UCC

My usual temperatures for the CPU are about 35C at idle and 40C - 50C Ingame. Same goes with GPU and just about everything else.

I am running on the latest drivers for all of my components, ive tried rolling back to see if the BSOD's dissapear but nope .. So im guessing it's not those

I compressed the minidump into a rar file and uploaded it. There is a file also called "Additional info" make sure to read it!

It contains important information gathered by "whocrashed"

Thank you in advance guys! Your help will be much appriciated.

P.S: If you need more info on anything, just ask. I want this fixed because im unable to do anything with this problem ..


- the original installed OS on the system?
Answer: Windows Vista Ultimate 64 BIT


- an OEM or full retail version?
Answer: Full Retail


- What is the age of system (hardware)?
Answer: The system is from 2008 itself.


- What is the age of OS installation (have you re-installed the OS?)
Answer: Installed a clean install of Windows 7 after changing hardware.

 

[Veniathan]

I forgot to upload a health report and infact do one.

So i just did the health report and, here you go.

 

[Jonathan_King]

Hello,

I'd suspect this is a hardware problem, so try running the Prime95 test: www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

Run the Small FFTs and Large FFTs tests, and report the results of both.

If Prime95 doesn't show any errors, upload a jcgriff2 report: www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Also, install SP1: windows.microsoft.com/en-US/windows7/learn-how-to-install-windows-7-service-pack-1-sp1

...Summary of the dumps:

[font=lucida console]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Nov  2 01:37:08.109 2011 (UTC - 4:00)
System Uptime: 0 days 4:15:36.062
*** WARNING: Unable to verify timestamp for amdk8.sys
*** ERROR: Module load completed but symbols could not be loaded for amdk8.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
BiosReleaseDate = 03/03/2011
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Veniathan]

Guys, ive been using some bluescreenviewer. Which works similar to whocrashed and WinDbg.

And after going minidump after minidump.. It shows what drives could possibly be causing it. And those files are from all kinds of minidumps all with the 0x101 code. Ill list them.

nvlddmkm.sys
ntoskrln.exe
dxgmms1.sys
storport.sys (Only one minidump had this)

These are the ones marked red, as in "caused by"

 

[Veniathan]

Hello,

I'd suspect this is a hardware problem, so try running the Prime95 test: www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

Run the Small FFTs and Large FFTs tests, and report the results of both.

If Prime95 doesn't show any errors, upload a jcgriff2 report: www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Also, install SP1: windows.microsoft.com/en-US/windows7/learn-how-to-install-windows-7-service-pack-1-sp1

...Summary of the dumps:

[FONT=lucida console]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Nov  2 01:37:08.109 2011 (UTC - 4:00)
System Uptime: 0 days 4:15:36.062
*** WARNING: Unable to verify timestamp for amdk8.sys
*** ERROR: Module load completed but symbols could not be loaded for amdk8.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
BiosReleaseDate = 03/03/2011
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

I ran Prime95 before, and it worked just fine without a problem ..

Now, to the real point. The jcgriff thing always doesnt work, i mean ive created a thread on another forum aswell and it just gets stuck at " Waiting for System info " or something like that.

Ran the thing for 30 minutes, then retried and the same thing happend.

Besides i am unable to install Service Pack 1 via auto update for my Win7. Once its done it fails configurating the update. So it reverts. I dont know why.

There arent much options here as you can see, and im really tired of this problem. Been up an entire day searching around, reading tips on this 0x101 thing. But it leads to no success as far as i can see.

I probably didnt mention but .. I usualy BSOD ingame. Doesnt even have to be a long time. Although when it first started BSODing it would not mind if i was ingame.

 

[Jonathan_King]

Where did you get your copy of Windows 7?

WhoCrashed is based off of Windbg; it is a user-friendly output of a few different Windbg lines. BlueScreenView is a completely different program, and unfortunately not nearly as accurate.

You might try running Prime95 again (all three tests). Otherwise, look into returning your motherboard and CPU and getting new ones.

 

[Veniathan]

Where did you get your copy of Windows 7?

WhoCrashed is based off of Windbg; it is a user-friendly output of a few different Windbg lines. BlueScreenView is a completely different program, and unfortunately not nearly as accurate.

You might try running Prime95 again (all three tests). Otherwise, look into returning your motherboard and CPU and getting new ones.

As i listed in my first reply, when i started the thread.

The first 5 days, the hardware worked fine just like it does now. The hardware itself basicly WORKS fine but these BSOD issues seem to be driver related.

Going back and asking for a new Mobo and CPU would be hard, i didnt actualy get a warranty. Because it wasnt exactly free.

On the other side, i have a friend who has duplicate Windows 7 Retail discs. And this one was unused. So he gave me this one.

There HAS to be something else we can do right?

 

[Jonathan_King]

Did it come with a product key? Is Windows fully activated now?

BlueScreenView and WhoCrashed try to show you what driver is causing the problem, yet their accuracy and usefullness are limited when hardware is the actual cause. In our case, it seems to be almost a certain problem with either the CPU or motherboard,though BIOS could be the cause too. Unfortunately, we cannot test out the last possibility, as no BIOS updates have been released since the version currently installed.

There should be AMD's 3-year warranty on the CPU and AsRock's warranty on the motherboard. Try RMAing them to their respective manufacturer's.

Warranty Services

ASRock > Support > Repair / RMA

 

[Veniathan]

Did it come with a product key? Is Windows fully activated now?

BlueScreenView and WhoCrashed try to show you what driver is causing the problem, yet their accuracy and usefullness are limited when hardware is the actual cause. In our case, it seems to be almost a certain problem with either the CPU or motherboard,though BIOS could be the cause too. Unfortunately, we cannot test out the last possibility, as no BIOS updates have been released since the version currently installed.

There should be AMD's 3-year warranty on the CPU and AsRock's warranty on the motherboard. Try RMAing them to their respective manufacturer's.

Warranty Services

ASRock > Support > Repair / RMA

Yes it does have a product key. But this whole warranty thingy and replacing isnt going to be the choice to fix the problem.

Simple reason why, the hardware cannot be confirmed. I REALLY doubt there is any problem at all with the hardware. Its completely new and up to date aswell.

So replacing hardware and going back and forth would just be .. Pain in the ass as you could say. And personaly i don't have time for it.

Once we are 100% sure that this IS the hardware, then we can actualy replace it.

There were many times way back when i used to have BSOD problems and people just went " Its the hardware its the hardware! " Yet 80% of the time it wasnt.

Ive ran the tests and they are all fine, i have already ran Prime95 2 times the other day.

I also ran the memtest for my RAM. 7 Passes and no problems.

 

[Jonathan_King]

Read here:

http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

 

[Veniathan]

Read here:

http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

If i had a dollar for everytime someone linked me that thread, i'd be rich now.

It does indeed have info, thats for sure.

Ive already checked almost all of these problems and im sure they are not the cause.

On the other hand in this thread right here [BSOD] A clock interrupt on the secondary processor. 0x00000101 - Tech Support Forum

You'll get more info about my problem.

It's been discussed with a Microsoft Professional, he belives it's not the hardware but that its drivers. Although both of your ways of fixing the problems are indeed quite confusing.

Ill try my best on fixing them.

I personaly have to sleep as ive been up almost 2 days tyring to fix this problem and its leading to no avail. Im guessing its easy to fix the problem once you are completely sure what's causing it.

These stress tests and driver verifiers help so little in seing what the cause is, its also VERY VERY time consuming.

And as always. Thank you for the help atleast, Its appriciated.

If you come up with a better solution, im here to discuss. And if i dont get reply withing 24 Hours or 48 Hours ill bump the thread. Thanks again!

 

[Jonathan_King]

Usasma is a very respected BSOD analyst, to be sure. Yet while he showed some drivers to update, he never posted that he thinks the drivers are the cause.

He did mention:

IMO, the inability to install Service Pack 1 is the biggest problem right now.

Try to get that installed. I don't have high hopes for it solving your BSODs, but there's a chance.

Other than that, I have nothing left to say, other than it looks like you have a hardware problem still. If you're positive that neither the motherboard nor the CPU are causing the problem, try changing out your power supply. If that still doesn't work, buy a new CPU.

 

[Veniathan]

Usasma is a very respected BSOD analyst, to be sure. Yet while he showed some drivers to update, he never posted that he thinks the drivers are the cause.

He did mention:

IMO, the inability to install Service Pack 1 is the biggest problem right now.

Try to get that installed. I don't have high hopes for it solving your BSODs, but there's a chance.

Other than that, I have nothing left to say, other than it looks like you have a hardware problem still. If you're positive that neither the motherboard nor the CPU are causing the problem, try changing out your power supply. If that still doesn't work, buy a new CPU.

Once again, i am unable to install the SP1 update.

Anyways, i have a AM2 AMD Dualcore 64 X2 5200+ 2.7 Processor just lying around here. It was on one of my old computers.

I really doubt that the CPU is broken (The current one) but if it is. I would be able to safely replace it with the other one?

 

[Jonathan_King]

You should be able to use your old CPU in that motherboard. It should fit fine at least.

Your best bet is still to RMA the CPU. If it's not defective, they will simply return it to you.

 

[Veniathan]

You should be able to use your old CPU in that motherboard. It should fit fine at least.

Your best bet is still to RMA the CPU. If it's not defective, they will simply return it to you.

Im not going to RMA because i have a change of getting a better CPU at a discount.

I found a AMD Phenom II X6 1055 2.8 GHZ for 140 bucks.

So im getting that one instead .. You were probably right about the defective CPU all along.

 

[ickymay]

are you 110% sure there isn't a bent pin on the cpu ?

 

[Veniathan]

are you 110% sure there isn't a bent pin on the cpu ?

Bent CPU pin? If there was a bent CPU pin it wouldnt be inside the socket.

 

[Jonathan_King]

You should be able to use your old CPU in that motherboard. It should fit fine at least.

Your best bet is still to RMA the CPU. If it's not defective, they will simply return it to you.

Im not going to RMA because i have a change of getting a better CPU at a discount.

I found a AMD Phenom II X6 1055 2.8 GHZ for 140 bucks.

So im getting that one instead .. You were probably right about the defective CPU all along.

My advice to you is to just hang tight for a few days. I still hold that hardware is most likely the cause, but since Usasma and VirGnarus are holding out on a driver/software problem, ride it out with them.

Software fixes are free, while hardware problems require buying new hardware. You might as well stick it out with them until they recommend you replace hardware, and then carry out this plan.

Usasma is a very respected BSOD analyst both here and on TSF, and VirGnarus is excellent at digging through Full Dumps and finding software causes.

 

[Veniathan]

You should be able to use your old CPU in that motherboard. It should fit fine at least.

Your best bet is still to RMA the CPU. If it's not defective, they will simply return it to you.

Im not going to RMA because i have a change of getting a better CPU at a discount.

I found a AMD Phenom II X6 1055 2.8 GHZ for 140 bucks.

So im getting that one instead .. You were probably right about the defective CPU all along.

My advice to you is to just hang tight for a few days. I still hold that hardware is most likely the cause, but since Usasma and VirGnarus are holding out on a driver/software problem, ride it out with them.

Software fixes are free, while hardware problems require buying new hardware. You might as well stick it out with them until they recommend you replace hardware, and then carry out this plan.

Usasma is a very respected BSOD analyst both here and on TSF, and VirGnarus is excellent at digging through Full Dumps and finding software causes.

Thank's for the tip. Much appriciated Jonathan.

Ill hang tight for a few days, even though it gets boring with out playing my favorite games ofcourse ..

Ill wait until they somewhat figure out what the problem is. Then ill try to fix it.

 

[ickymay]

are you 110% sure there isn't a bent pin on the cpu ?

Bent CPU pin? If there was a bent CPU pin it wouldnt be inside the socket.

yes it would and can , I have fixed quite a few systems which suffered strange results especially Bluescreen crashes where one or more pins on the CPU had been bent