• 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

teejay73

teejay73

teejay73

Associate
Joined
20 May 2009
Posts
1,118
Location
Essex
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.
 
4ghz on 1.25V is probably your problem, either lower the overclock or increase the voltage a little until it stops.

As for why it's only just started did you test your CPU's stability when you first overclocked it? it could just be a difference in ambient/case temp or something it's been pretty hot recently.
 
mmj_uk said:
4ghz on 1.25V is probably your problem, either lower the overclock or increase the voltage a little until it stops.

As for why it's only just started did you test your CPU's stability when you first overclocked it? it could just be a difference in ambient/case temp or something it's been pretty hot recently.
Click to expand...

Actually my overclock is @ 4.3 ghz though that dont explain why it bsod whilst browsing and running a low clock speed whilst power saving features are enabled. My initial overclock was tested for stability and I ironed out any issues then with 1DAY giving me advice.

Is there a chance that the power features are producing too low a voltage that makes it crap out?
 
It's possible. I tested this once by downloading some free cpu limiting software (it was really comprehensive actually, will try and remember which it was...) to limit the cpu usage of the stress testing prog to some value which kept it from stepping up.

I don't know if this constituted a proper test though, as it steps up way below 100% utilisation.
 
joeyjojo said:
It's possible. I tested this once by downloading some free cpu limiting software (it was really comprehensive actually, will try and remember which it was...) to limit the cpu usage of the stress testing prog to some value which kept it from stepping up.

I don't know if this constituted a proper test though, as it steps up way below 100% utilisation.
Click to expand...

Well I have gone back to stock for now and I am testing prime small fft`s for a few hours to ensure that the system is stable.

After a little searching I found most people @ 4.2 ghz were stable @ 1.28/9v so .3v under that was probably too little volts for my 2500k. We shall see as I am gonna set my 4.2ghz OC at that tomorrow and see what it is like at those volts.
 
I think for sure @ 1.25v was not enough for my cpu and also what I have found out is I am suffering a little v-droop, for example at the moment in bios my cpu v is set to 1.32 and yet whilst running prime95 my volts are @ 1.30v via hardware monitor, I know the software is not an exact science but as soon as I stop prime95, the volts back up to 1.32.

The question is, how can I rectify this v-droop issue :confused:, right now I am just trying to get stable @ 4.2ghz, as I am happy at this point for a 24/7 OC but would like to see my Volts as low as can get them, I think ideally around the 1.28v range would be good as right now my temps are avg 70c across the 4 cores.

Thanks for your input guys! :)
 
joeyjojo said:
I would up it by the smallest increments until it becomes stable, then up one more for good measure.
Click to expand...

Right now it is prime stable for 4hrs at 1.32 but with this V-droop issue, under load it is showing at 1.30v but reverts back to 1.32 when idle, So ideally I would like to solve the V-droop if I can, So I know that the volts are accurate, otherwise at lower volts it might start crapping out under load.

Thanks joeyjojo!
 
is this a gigabyte thing? because my ASRock is lower volts idle and higher underload, which is the way i thought it was meant to be :confused:
have you tried changing the cpu LLC level?
 
paradisiac said:
is this a gigabyte thing? because my ASRock is lower volts idle and higher underload, which is the way i thought it was meant to be :confused:
have you tried changing the cpu LLC level?
Click to expand...

Yep LLC is enabled, you only have the option to enable the LLC on my Mobo and yes I always thought it should be that way too....A bit miffed on this Tbh!
 
yeh had a look through your manual, looks very basic on options :(
whats the 'Dynamic Vcore'?
gigabyte forums said:
Basicly Dynamic VID is the Vcore option to fine tune loadline calibration.
Click to expand...
 
Last edited:
teejay73 said:
yep it is a bit basic, not really looked into the Dynamic Vcore, will have a google and see how to set it.;), hopefully that might point me in the right direction.
Click to expand...

had a google. looks like it might be the answer to the voltage issue. is really hard to find anything conclusive to post though :( but seems lots of people with your mobo are asking for a bios update to give LLC levels.
 
Just found this

Quote:
There's a new Dynamic Vcore option in the Advanced CPU Voltage Settings. To enable it, set the Vcore voltage to "Normal" and then add or subtract the amount needed to reach your target Vcore voltage. For instance, my original Vcore in BIOS was set to 1.2750v. When I set the Vcore to "Normal", it is set to 1.2125v. Therefore, I set the "Dynamic Vcore Voltage" to +.0625v which results in my target voltage of 1.2750 = 1.2125v + .0625.

What this option does is set your idle voltage lower than originally (if you have power savings features enabled). For example, my original CPU-Z idle voltage was 1.248v and now it is 1.104v. The load voltage is unchanged. It's a nice feature to have.
 
paradisiac said:
let us know how you get on with it :)
Click to expand...

Not very well mate, just been into bios and there is no option to enable it, it is set at auto :confused:, there must be a way to enable it unless it is coming in a bios update......F4 bios has been about a bit now and is still the latest Bios for this mobo!
 
teejay73 said:
Not very well mate, just been into bios and there is no option to enable it, it is set at auto :confused:, there must be a way to enable it unless it is coming in a bios update......F4 bios has been about a bit now and is still the latest Bios for this mobo!
Click to expand...

you need to turn the other vcore setting to auto i think.

manual said:
CPU Load-Line Calibration
Enables or disables Load-Line Calibration. Enabling this feature adjusts Vdroop, keeping the CPU voltage more constant under light and heavy CPU load. Disabled sets the CPU voltage following Intel specifications. (Default: Auto)
Note: Enabling Load-Line Calibration may result in damage to your CPU or reduce the useful life of the CPU.
CPU Vcore (The default is Auto.)
Dynamic Vcore(DVID) This option is configurable only when CPU Vcore is set to Normal. (The default is Auto.)
QPI/Vtt Voltage (The default is Auto.)
System Agent Voltage (The default is Auto.)
Click to expand...
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom