(BSOD) A clock interrupt was not received on a secondary processor within the allocated time interval

reubenno · Jan 21, 2016

Hello,
My PC has been suffering from very infrequent BSODs. The BSOD states that: "A clock interrupt was not received on a secondary processor within the allocated time interval". I have overclocked my 3570K however I am certain that it is stable as I can video edit, run stress tests and game on it without a problem 99.9% of the time. The BSODs seem to happen randomly and can occur without any stress on the CPU (for example on the desktop), as well as in CPU intensive tasks.

I have updated the BIOS to the latest version and made sure that my temperatures are okay.

Does anybody know what could be causing this?

Thanks.

johnbl · Jan 21, 2016

basically some hardware missed a signal because of a timing issue.
most people assume this is cause by the video card timing and it often is but it can also be cause by timing between CPU processors. In particular, I have seen this in many cases cause by USB drivers. mostly USB wireless drivers, that get plugged in, plug and play starts to install the driver on one CPU core, then on another core network activity is queued up waiting for the install to complete. Problem is the plug and play install gets an error and tries again, This goes on for 300 seconds, then the other core just thinks the first CPU core is hung and bugchecks the system with this error code.

happens mostly on windows 7 machine using a certain wireless thumb device because the default driver that shipped with windows 7 was broken.

I have seen this with overclocked systems, where everything was overclocked, the GPU, and CPU and the person was able to resolve it by increasing the clock for the PCI/e bus slightly to match the other overclocking.
(one of the reasons I don't try to help people overclock, too many screwy things to consider)

reubenno · Jan 21, 2016

johnbl :

basically some hardware missed a signal because of a timing issue.
most people assume this is cause by the video card timing and it often is but it can also be cause by timing between CPU processors. In particular, I have seen this in many cases cause by USB drivers. mostly USB wireless drivers, that get plugged in, plug and play starts to install the driver on one CPU core, then on another core network activity is queued up waiting for the install to complete. Problem is the plug and play install gets an error and tries again, This goes on for 300 seconds, then the other core just thinks the first CPU core is hung and bugchecks the system with this error code.

happens mostly on windows 7 machine using a certain wireless thumb device because the default driver that shipped with windows 7 was broken.

I have seen this with overclocked systems, where everything was overclocked, the GPU, and CPU and the person was able to resolve it by increasing the clock for the PCI/e bus slightly to match the other overclocking.
(one of the reasons I don't try to help people overclock, too many screwy things to consider)

Thanks for the reply. I am running Windows 7, I will try upping the PCI/e bus.

HandyTech · Jul 30, 2017

Go Directly into the Bios and Disable Data Execution Prevention, This should solve the problem, It appears to work for me. I have a HP Compaq NC8430 with the same problem.

Search

(BSOD) A clock interrupt was not received on a secondary processor within the allocated time interval

reubenno

Distinguished

johnbl

Polypheme

reubenno

Distinguished

HandyTech

Reputable

TRENDING THREADS

Latest posts

Moderators online

Share this page