• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

2500k "clock interrupt on secondary cpu" BSOD

There's a thread in the m/board section with a guy with an Asrock z68 getting the same error, maybe there's something there that'll help - http://forums.overclockers.co.uk/showthread.php?t=18294370

Hi guys anyone else suffering from this problem BSOD " A clock interrupt was not received on a secondary processor within the allocated time interval"

Only happens to owners who wish to use the cpu graphics and not anyone using a discrete graphics card.

Got my replacement board sitting in its box as asrock havent found a cure yet so am thinking of returning board for another make. My first board was giving Bsod 4 times a day and more some times.

So anyone else got this problem solved ?

the gigabyte does not have onboard video.
 
I tried the dynamic V-core and the issue is still there under load, It doesnt change the load voltage as whilst running prime95 now, I am still sitting 0.02v under 1.30v, actually just checked hardware monitor and it fluctuates between 0.03v & 0.02v now, So in fact has made it worse, In bios it shows 1.283v So there is def a issue.

Still, I am sure there must be an answer to this somewhere!?
 
Hi all, Had a strange BSOD about 2hrs ago whilst just browsing on the web "A clock interrupt was not received on a secondary processor with-in the allocated time interval". Now I have had a look around Google and looked at the code for this Bsod and it seems the V-core is too low but what I dont understand is that this has just started to happen?

Could my cpu be faulty? All temps are fine, Ram is all fine and tested with memtest and psu seems to be fine, I do know that that Asrock z68 boards have had this issue though can not find anything on my Gigabyte board with this issue.

I use Hardware monitor and that gives me two readings for the cpu, one is cpu v-core which is @ 1.06v and the other is 1.24v cpu, I also use the intel speedstep and other power saving features via bios.

Only had this cpu/mobo/ram about two months, So I am eager to get this resolved with-out the hassle of RMA.

Any Ideas guy`s would be greatly appreciated.

Im afraid you have the same problem has a lot of us when using the cpu graphics.
 
I tried the dynamic V-core and the issue is still there under load, It doesnt change the load voltage as whilst running prime95 now, I am still sitting 0.02v under 1.30v, actually just checked hardware monitor and it fluctuates between 0.03v & 0.02v now, So in fact has made it worse, In bios it shows 1.283v So there is def a issue.

Still, I am sure there must be an answer to this somewhere!?

think the answer is wait it out for a bios update or replace mobo :( a lot of fiddling 'might' get you there though. have you tried different combos of th DVID to see if you can get the fluctuating numbers closer?
 
think the answer is wait it out for a bios update or replace mobo :( a lot of fiddling 'might' get you there though. have you tried different combos of th DVID to see if you can get the fluctuating numbers closer?

Yeah gonna try playing around with it, to see if I can get it closer, Hopefully I can get a resolution, a bit busy this afternoon so will probably have a play this evening, Thanks for your help Mate, will let you know how I get on!
 
all this SB OCing is turning into a right nightmare for a lot of people. so many models use different option and nothing seems to be very universal. gone are the days of upping the fsb/multi and increasing the vcore (then any minor tweaks to other stuff to go higher).
 
all this SB OCing is turning into a right nightmare for a lot of people. so many models use different option and nothing seems to be very universal. gone are the days of upping the fsb/multi and increasing the vcore (then any minor tweaks to other stuff to go higher).

Yep, I agree the OCing it self is quite easy, but there are too many little things that hamper it.
 
I have managed to get the undervolt to with-in 0.01v, So it is set @ normal volts in bios and -0.55v (1.34v -0.55v=1.284v), It is now reading in hardware monitor 1.27v from 1.28v underload. Still not right but better than was before, Not sure why my board undervolts whilst underload though.

I will just have to take into account the 0.01v when adjusting my voltage.
 
Thought I would post an Image of hardware monitor whilst under load.

Capture2-1.png
 
Nah mate, That had me worried at 1st until I checked Bios and it shows the same reading as the cpu v in hardware monitor, that said though, I have tried every version of cpuz and still get the same reading for core voltage!

the bios will ALWAYS read higher than windows due to it wont run any of the energy saving features.
maybe this is your issue?
 
Back
Top Bottom