10-26-2022 05:39 PM - last edited on 03-06-2024 10:12 PM by ROGBot
10-26-2022 06:03 PM
nirurin wrote:
I've tried core-optimiser, I've tried eClk, I've tried +fmax, I've tried 1X, 4X, 8X and 10X scalars...
No matter what I do, the max -effective- clock in hwinfo is always 5650 on my best core.
With all those things added in, it's currently 'requesting' 5975mhz, instead of the previous 5800, but thats irrelevant as the effective clock always seems to be 5650.
Which bugs me lol, cos I've seen a lot of people with at least 5700, if not 5800, using similar cooling to me.
Currently on arctic liquid freezer 2, and my temps even under 230watts never hits 95C, usually more like 85C, so I can't see cooling being the main issue...
(Single core temps only ever get to about 70, if that).
10-26-2022 06:08 PM
Soupladel wrote:
You have not said which board you have and what version of the BIOS you are using.
I am having what appears on the face of it to be the exact same problem, but in my case, all but one of my course are limited to 5.5Ghz boost, with core 0 boosting very occaisonally to 5.765.
I am using the Crosshair X670E Hero motherboard and all BIOS versions after 0705 have the same boosting behaviour, which i have been led to believe is caused by the latest AGESA patch used in the newer versions of my BIOS.
10-26-2022 10:31 PM
nirurin wrote:
Haha, I just came back to the forum, because I had realised this exact thing. I forgot to mention my setup.
Rog Strix e-e, using the 803 test bios, but I was on the latest 'official' bios before that and it seemed to be the same. (So its Agesa1.0.0.3 patch A in both cases I believe?)
10-26-2022 11:57 PM
nirurin wrote:
Haha, I just came back to the forum, because I had realised this exact thing. I forgot to mention my setup.
Rog Strix e-e, using the 803 test bios, but I was on the latest 'official' bios before that and it seemed to be the same. (So its Agesa1.0.0.3 patch A in both cases I believe?)
10-26-2022 11:04 PM
Shamino wrote:
theres no way effective clk = running clk unless the thread/core is busy 100% of the time.
10-26-2022 11:47 PM
Shamino wrote:
then they are doing some work on their core when taking the screenshot