Ghz cap at 4.2 ghz when oc'd to 4.8

NickyCWario

Commendable
Jan 23, 2017
6
0
1,510
I have an i5 7600k and an asus z170-p and when I try setting the core ratio in the bios to 48, it boots and works fine but when I check CPU-Z it only shows it going to 4.2ghz under 100% load despite the multiplier being x8-x48?
Is this normal or some sort of failsafe for the cpu, or am I missing something.

Thanks in advance
 

burnhamjs

Commendable
Jan 19, 2017
178
1
1,710
what are your temps? perhaps thermal throttling. If your temps are getting high you may need to drop vcore.

 

NickyCWario

Commendable
Jan 23, 2017
6
0
1,510


My temps got to around 70 degrees celsius and I'm not too sure about the vcore or how to change with that properly but I get how it works, I think it could only have been 1.2-1.3 at most.

 

burnhamjs

Commendable
Jan 19, 2017
178
1
1,710
those temps are fine (as long as it stays below 85C, though i prefer to keep them below 80 during stress testing). Vcore looks fine as well. I like to keep my vcore below 1.35V.

 

NickyCWario

Commendable
Jan 23, 2017
6
0
1,510


So is this just an odd occurrence then and is there a way to more or less force it to go to the higher clock, I have turbo mode on which gets it to 4.2 but without means it only gets to 4.0.
 

burnhamjs

Commendable
Jan 19, 2017
178
1
1,710
Are you trying to overclock by adjusting your turbo ratio or a regular overclock?

I have turbo, speedstep, and c-states disabled when I overclock. Then I set Vcore to 1.35V (and enable enough LLC such that when i monitor Vcore in CPU-Z I don't see any significant drop or boost between idle and stress testing). Then I increase my multiplier one step at a time - run a stress test and see if it passes and temperature remains below 80C. If it passes then I up my multiplier and run again. If the stress test fails then I know I have raised my multiplier too high. If the temps are greater then 80C then I know I have too much Vcore. This is it in a nutshell.

If you have turbo disabled - are you saying you can't set a multiplier 44? (as an example) with a corresponding frequency in CPU-Z of 4.4G

 

NickyCWario

Commendable
Jan 23, 2017
6
0
1,510
Are you trying to overclock by adjusting your turbo ratio or a regular overclock?

I have turbo, speedstep, and c-states disabled when I overclock. Then I set Vcore to 1.35V (and enable enough LLC such that when i monitor Vcore in CPU-Z I don't see any significant drop or boost between idle and stress testing). Then I increase my multiplier one step at a time - run a stress test and see if it passes and temperature remains below 80C. If it passes then I up my multiplier and run again. If the stress test fails then I know I have raised my multiplier too high. If the temps are greater then 80C then I know I have too much Vcore. This is it in a nutshell.

If you have turbo disabled - are you saying you can't set a multiplier 44? (as an example) with a corresponding frequency in CPU-Z of 4.4G

I have turbo enabled most of the time but I'll try it your way since you sound like you at least know where to start with this kind of thing, and I'm doing it by changing the 'cpu core ratio' in my bios.

I have an Asus z170-p with 3017 v. if that helps

Update: No difference, bios clock still doesn't correlate to the cpu-z clock.

 

NickyCWario

Commendable
Jan 23, 2017
6
0
1,510


I had a look into that too but there isn't an option for it anywhere I can find

 

alphadogg123

Distinguished
Jul 14, 2009
83
1
18,665
Try running cpu-z benchmark on the bench tab. You can use this test to calculate the difference between the results at 4.8ghz and stock speeds.
It seems that cpu-z is reporting incorrect numbers on new configs.
 

NickyCWario

Commendable
Jan 23, 2017
6
0
1,510


Yeah I tested that and all the scores no matter what the cpu core ratio in the bios is set to stay borderline exactly the same with scores ranging from about 1932-1936 in the single core score and if I remember correct about 7930-7950 in multi core score.
I can only assume it's due to the motherboard's bios as it classes it as a 'beta build'