Overclock.net banner
81 - 100 of 3,089 Posts
Thanks very much for the guide, RobertoSampai!!
Working through your guide now -- haven't built a PC or tried any OC since 2013. Looks like I'm x55 P-Core stable with an AC_LL of 1.09-1.10 and got to the step where I bench all E-Cores at x44. Something I noticed but don't understand is why doing so caused all of my P-Cores to drop to 5.3GHz (and the E-Cores to settle on 4.2GHz) during the Cinebench run. Can you help explain what is going on there? Everything else is configured according to your screenshots up to the "E-Core Overclocking" portion.
 

Attachments

Discussion starter · #82 ·
Thanks very much for the guide, RobertoSampai!!
Working through your guide now -- haven't built a PC or tried any OC since 2013. Looks like I'm x55 P-Core stable with an AC_LL of 1.09-1.10 and got to the step where I bench all E-Cores at x44. Something I noticed but don't understand is why doing so caused all of my P-Cores to drop to 5.3GHz (and the E-Cores to settle on 4.2GHz) during the Cinebench run. Can you help explain what is going on there? Everything else is configured according to your screenshots up to the "E-Core Overclocking" portion.
What MB do you have?
AC_LL at 1.09 to 1.10 is TOO MUCH!
If you have an Asus Z690/Z790 and using LLC#4 (With DC_LL = 1.02) the AC_LL should be around 0.2 to 0.1.
 
What MB do you have?
AC_LL at 1.09 to 1.10 is TOO MUCH!
If you have an Asus Z690/Z790 and using LLC#4 (With DC_LL = 1.02) the AC_LL should be around 0.2 to 0.1.
Yes, sorry, I meant to write 0.09-0.10. Out of 60+ minutes of Cinebench r23 at 0.09 I did see 1 error. And at 0.08 I could not reliably get through the 10 minute run, so I currently have it set at 0.10.
It's a z790 Hero.
Any ideas on why setting the 3 E-Core groups to 44 has that impact on P-Core dropping to 5.3GHz and E-Core dropping to 4.2GHz under load? I don't see HWinfo indicating any sort of throttling.
 
Discussion starter · #84 ·
I've read through it but, to be brutally honest, while I value all the time and effort - it doesn't seem that worthwile for ~60pts single / ~500pts multi in CPU-Z considering all the time needed for tinkering, testing, readjusting.

That's true.... LOLOL.

My intention is to share a little of what I learned over time, trying to condense everything in one place. so people can learn how loadlines and OCTVB work...
I keep my system with all intel limits enabled.
And I usually limit the FPS in games to 120, so I don't heat up my office so much... LOL

But I agree with you... It's a lot of information for little performance...
To get a good score the CPU/MB can be all out of adjustment as long as you have a way to cool the CPU. The best example of this is LN2...
 
Discussion starter · #85 ·
Yes, sorry, I meant to write 0.09-0.10. Out of 60+ minutes of Cinebench r23 at 0.09 I did see 1 error. And at 0.08 I could not reliably get through the 10 minute run, so I currently have it set at 0.10.
It's a z790 Hero.
Any ideas on why setting the 3 E-Core groups to 44 has that impact on P-Core dropping to 5.3GHz and E-Core dropping to 4.2GHz under load? I don't see HWinfo indicating any sort of throttling.
Post some pics of your BIOS settings...
 
Post some pics of your BIOS settings...
You should change the title to "step by step core usage tuning for advanced tweakers".
Many people get daunted by all this work.
 
You should change the title to "step by step core usage tuning for advanced tweakers".
Many people get daunted by all this work.
I think just by being "step by step" it's not only for advanced users. Almost anybody can follow a step-by-step! Taking the time to read and understand the theory is definitely more for the dedicated enthusiast, that's for sure. I'm really impressed by all the explanation put into the guide!
 
Try to set the Pcores to "by core" 58x2-55x8 (stock).
Do you mean the P-Core Ratio Limits? I set the first two to 58 and the rest to 55. After saving the changes, I'm now getting the 4.5GHz on all E-Cores under load, but P-Cores settle on 5.5GHz. Strangely, right at the start of the bench (for just 1 second), six P-Cores apparently clicked up to 5.8GHz? Is that just a polling error from HWInfo?
 

Attachments

Discussion starter · #91 ·
Do you mean the P-Core Ratio Limits? I set the first two to 58 and the rest to 55. After saving the changes, I'm now getting the 4.5GHz on all E-Cores under load, but P-Cores settle on 5.5GHz. Strangely, right at the start of the bench (for just 1 second), six P-Cores apparently clicked up to 5.8GHz? Is that just a polling error from HWInfo?
Now all is working perfectly!

All cores will reach 58x in any time... That's why you see the 58x max frequency in all 8 cores...

If you now set e cores to, let's say 46x4 - 45x16 you will see that all e cores will hit 46x at maximum frequency, but at full load they will run 45x
 
Discussion starter · #93 ·
In the end of the first post, I wrote an explanation of how octvb works...
I know I wrote a lot of things and sometime is not easy to understand... LOL
But basically this is the answer:

When you put full load to the cores... The temps rules downclock all cores to 55x in the 13900k



  • Explaining Asus OCTVB:
I'll try to make OCTVB easy...
Let's use my 12900K manual OCTVB settings and Asus OCTool as an example:

Rectangle Font Parallel Screenshot Number


First line is for only 1 active P-core.
So this line will be used when only 1 core (anyone) is active, and the others are parked or not loaded.
In this condition, If Core temp is < 60 this core will run 57x.
If temp is 60 to 69 this core will run 56x.
If temp is >= 70 this core will run 55x

The second line is for when 2 cores (anyone) are active and the others are sleeping or not loaded.
If temp < 56 these 2 cores will run 57x.
If temp is 56 to 65 these 2 cores will run 56x
If temp is >= 66 these 2 core will run 55x

The third line is for when 3 cores (anyone) are active and the others are sleeping or not loaded.
If temp < 52 these 3 cores will run 57x.
If temp is 52 to 61 these 3 cores will run 56x
If temp is >= 62 these 3 core will run 55x

The fourth line is for when 4 cores (anyone) are active and the others are sleeping or not loaded.
If temp < 66 these 4 cores will run 55x.
If temp is 66 to 75 these 4 cores will run 54x
If temp is >= 76 these 4 core will run 53x

So let's go to the last line....

The last line is for when all cores are active and loaded.
If temp < 72 these 8 cores will run 53x.
If temp is 72 to 81 these 8 cores will run 52x
If temp is >= 82 these 4 core will run 51x
 
Ah, right! So can the adjustments to these OCTVB temperature thresholds only be applied through the windows application, or can they be applied manually within the BIOS? Within the BIOS the values are greyed-out and I don't see a way to unlock them for direct editing.
 
Hi there!

Sharing some results after following first part of the guide:

PCores 5.7
ECores 4.7
Cache 4.6 (Auto)
LLC 4
DC_LL = 1.02
AC_LL = 0.30
IA VR Voltage limit = 1650

~310W (CB R23) ~85° (CPU Package & Core Max)


Any concerns about it? Is it safe to run AC_LL around 0.30?

Will continue testing :)

Blue Azure Font Rectangle Electric blue


Gadget Font Rectangle Screenshot Multimedia
 
Discussion starter · #98 ·
Ah, right! So can the adjustments to these OCTVB temperature thresholds only be applied through the windows application, or can they be applied manually within the BIOS? Within the BIOS the values are greyed-out and I don't see a way to unlock them for direct editing.


If you want to change them in the BIOS you need to use "ENABLE" instead "+1Boost" or "+2Boost".

Manual OCTVB:

OCTVB manual configuration is used when you want to set a specific temperature threshold and a specific "down bin" (ratio offset) for each frequency/core group.
It is a laborious task as each of the fields in the table below must be transcribed into the BIOS.

Rectangle Font Material property Parallel Screenshot


Below the first row of the table (above) is highlighted.
This is the process for setting up a single core.
This configuration will then have to be repeated 7 more times, each with its specific temperature for the group of cores.
The good news is that the Asus algorithm already loads the table in advance, so what we will have to do is just change the temperature value as we wish.
Font Line Screenshot Software Slope
 
Discussion starter · #99 ·
Hi there!

Sharing some results after following first part of the guide:

PCores 5.7
ECores 4.7
Cache 4.6 (Auto)
LLC 4
DC_LL = 1.02
AC_LL = 0.30
IA VR Voltage limit = 1650

~310W (CB R23) ~85° (CPU Package & Core Max)


Any concerns about it? Is it safe to run AC_LL around 0.30?

Will continue testing :)

View attachment 2580462

View attachment 2580463
Try to run the AC_LL as lower as possible...
Lower AC_LL means lower temps and less power and heat... :)
 
81 - 100 of 3,089 Posts