Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD "Clock interrupt was not received on a secondary processor"

27 Apr 2014   #1
geared

windows 7 Home Premium 64-bit
 
 
BSOD "Clock interrupt was not received on a secondary processor"

Hi Guys,

Keep receiving the BSOD and the error message states "Clock interrupt was not received on a secondary processor" seems to happen at random times regardless of what I'm doing on the computer.

  • I thought it was the CPU initially so I ran intelburn test three times (standard through to very high) everything went smoothly with CPU reaching temps of 55 degrees.
  • Also ran Sf/scannow in elevated command prompt - no issues there.
  • I don't have anything OC'd.
  • Ran malwarebytes no objects detected
I've read it could be a motherboard issue but no idea how to test it...
Sf attached.Any advice welcome.

Thanks!


My System SpecsSystem Spec
.
27 Apr 2014   #2
Thedoctor44

 

To properly analyse 0x101 bugchecks we need Kernel Memory Dumps instead of minidumps, we'll come to that later on if we can't find anything.

Lets give Prime95 a shot, run it for around 2 hours.
Hardware - Stress Test With Prime95

Note   Note

Like all stress tests it quickly raises your temperature so I recommend using a temperature monitoring software, I use HWmonitor.
You can download it here.

HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
My System SpecsSystem Spec
27 Apr 2014   #3
geared

windows 7 Home Premium 64-bit
 
 

OK thanks - will start it now. I'm assuming I should run blend correct? Rather than small FFTs?
My System SpecsSystem Spec
.

27 Apr 2014   #4
Thedoctor44

 

No, follow the instructions.
Blend isn't necessary most of the time so just go for small FFTs.
My System SpecsSystem Spec
27 Apr 2014   #5
geared

windows 7 Home Premium 64-bit
 
 

OK I just ran it for 2 hours on small FFTs it passed all of the tests.
What would you recommend I try now?
Thanks
My System SpecsSystem Spec
27 Apr 2014   #6
Thedoctor44

 

Lets try Driver Verifier.
Enable Driver Verifier to monitor the drivers.
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

information   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.


warning   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point Manually before enabling DV.


Tip   Tip
  • If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
  • If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.


Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
28 Apr 2014   #7
geared

windows 7 Home Premium 64-bit
 
 

So I changed my crash dump report to kernel, created a restore point and ran driver verifier. Then I restarted the computer and got BSOD straight away and windows failed to start. So I went back to previous restore point and grabbed another SF diagnostic.
Hopefully captured the problem...
Let me know.
Thanks again.
My System SpecsSystem Spec
28 Apr 2014   #8
Thedoctor44

 

The driver that is being blamed is part of Daemon Tools which is a well known cause of blue screens.
You should remove Daemon Tools and find a suitable replacement if necessary.

Code:
Unable to load image \SystemRoot\system32\DRIVERS\dtsoftbus01.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1300 )
My System SpecsSystem Spec
28 Apr 2014   #9
geared

windows 7 Home Premium 64-bit
 
 

awesome thank you for all your help! I've uninstalled it now with revouninstaller. Do you think I should try running dv again? Just to doublecheck?
My System SpecsSystem Spec
28 Apr 2014   #10
Thedoctor44

 

No leave DV off.
Just use your PC normally like how you would if you had no blue screens.
If you get any new crashes upload the dump files.

If you get no crashes and when you feel your issue has been resolved then please mark the thread as solved.

Any more issues let me know
My System SpecsSystem Spec
Reply

 BSOD "Clock interrupt was not received on a secondary processor"




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD a clock interrupt was not received on a secondary processor
Hello,My name is Anderson. First of all,apologies for my info inside the zip file is mixed in with Portuguese,its the language my computer is on. About half a month ago i started getting blue screens while trying to play games,which started to happen more and more often,to anything i did on a...
BSOD Help and Support
BSOD A clock interrupt was not received on a secondary processor
I am getting random BSOD with message "A clock interrupt was not received on a secondary processor within the allocated time interval. I don't even play any games. Normal computer usage. Updated BIOS and graphics to latest releases. All latest Windows updates. I am stuck with this issue and need...
BSOD Help and Support
BSOD 101 - A clock interrupt was not received on a secondary processor
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...
BSOD Help and Support
[BSOD] A clock interrupt was not received on the secondary processor
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...
BSOD Help and Support
Random BSOD "Clock interrupt not received on a secondary processor"
Hey guys! About a month ago I began receiving this bsod. "A clock interrupt was not received on a secondary processor" Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003364180, 0x2) My System Specs: Laptop. Clevo p170hm Mobo: Clevo p170hm CPU: Intel Core i7-2820QM Processor (8M Cache, @2.30 GHz)...
BSOD Help and Support
BSOD A clock interrupt was not received on a secondary processor...
I just had a BSOD with my Clevo W860CU laptop with GTX 285M and 920XM OEM CPU. The BSOD contained this error message: A clock interrupt was not received on a secondary processor within an allocated time What could be the cause of it?
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 16:05.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App