Port Royal not utilizing GPU Core Clocks

[[STG] Dante]

I've ran this benchmark hundreds of times. I recently found a more reliable way to undervolt & o.c. my 3080. However for some reason Port Royal goes to a lower voltage, like .915v, when my card is set and uses 1.050v on every other application and benchmark. The Core clock also doesn't increase from idle it stays around 1830mhz vs the 2100+mhz i'm testing. I should also note this has never been an issue for me in the past, same software & gpu.

[Migz - DH]

I suspect that Jarnis will tell you something about how the benchmark does not change anything with your system, that it just uses what the system gives it to produce results, that the benchmark was not changed recently, and if the benchmark gives you strange results, you should probably check your system for issues.

As an aside, I just reran Port Royal with my 3080 and got a score of 12607 with my everyday overclock. http://www.3dmark.com/pr/2565403

(edit, typo)

[UL_Jarnis]

Yep. You are effectively asking why NVIDIA driver and the card firmware does what it does. We don't know. The benchmark just renders stuff. It has no control over the card. If in doubt, DDU wipe the drivers and reinstall and try again.

Note that if you are undervolting, the card can do odd things when it tries to keep itself from outright crashing. Port Royal is on the heavy side as far as test loads go and it activates parts of the card that are not used in many games. It is not at all unusual that an undervolt that is stable on some old school DX11 load suddenly acts all wonky under Port Royal or Speed Way. 30- and 40-series cards drop their clocks when they hit the power limits, which they commonly do under heavy benchmark loads.

[Migz - DH]

Sorry for typoing your name, Jarnis. Forgive me!!

[[STG] Dante]

Originally posted by UL_Jarnis:

Yep. You are effectively asking why NVIDIA driver and the card firmware does what it does. We don't know. The benchmark just renders stuff. It has no control over the card. If in doubt, DDU wipe the drivers and reinstall and try again.

Note that if you are undervolting, the card can do odd things when it tries to keep itself from outright crashing. Port Royal is on the heavy side as far as test loads go and it activates parts of the card that are not used in many games. It is not at all unusual that an undervolt that is stable on some old school DX11 load suddenly acts all wonky under Port Royal or Speed Way. 30- and 40-series cards drop their clocks when they hit the power limits, which they commonly do under heavy benchmark loads.

I found the issue. It was with msi afterburner. For some reason if you start from a - negative offset on core clocks before overclocking the port royal benchmark sits at that base negative offset. I guess it's just not going to work for benchmarking.