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!

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

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

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

No, follow the instructions.
Blend isn't necessary most of the time so just go for small FFTs.

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

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

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

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

• 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.

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.

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 )

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?

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 :)