Hi!
I’m experiencing some clocking issues with driver 570, RTX 5080 and some games, especially Hogwarts Legacy. Somehow the GPU won’t clock above 780 MHz, so performance is very bad.
See the attached screenshot showing mangohud
Also, the GPU sometimes only uses PCIe Gen3, sometimes 5, no idea yet when this happens. Not sure if this is a bios issue of the motherboard or driver issue?
Does anyone have similar issues with a RTX 5080?
Update: This only happens when enabling Nvidia Reflex Low Latency in the graphics settings. Disabling it and it will run just fine…
Reflex is somewhat buggy under proton. Maybe try to create an issue on vkd3d-proton github. It’s possible it’s a driver bug too.
It seems to be a driver bug as vkd3d has no influence on GPU clocks in any way.
Yeah, I saw the response over there which seems like good reasoning…
Probably a driver bug then
Yes, I observe the same issue in Cyberpunk 2077. And using DLSS Reflex cannot be disabled (it is on, greyed out as an option).
Edit: even without DLSS on, this may also happen. This is very erratic and difficult to control (but easy to reproduce).
There are also some weirdness, depending on the proton version, DLSS options are different (but I gather it may be the capability for these proton versions to tell the software DLSS3 is supported). And even after a restart, sometimes the texture quality option (low/high) under DLSS frame generation appears, or not. Same with the frame generation factor (2,3,4X). This is very strange and I suppose this may need a bit of time to stabilise).
As a folow-up: in Cyberpunk, and using proton-ge or experimental or hotfix, the bug only happens when using DLSS Frame generation. With DLSS without frame generation, then freqency and power are boosted (to 2737MHz), even with Reflex enabled. However, restarting the game is necessary after changing these options, which makes testing tedious (especially one cannot skip the intro screens).
FYI I did a bug report on Github: DLSS with Frame generation caps GPU clock to 780MHz with RTX 5080 · Issue #781 · NVIDIA/open-gpu-kernel-modules · GitHub
Has tried to tweak PowerMizer settings? It may be a bug that locks the GPU to lower level of performance. Without overclocking, but just trying to switch from adaptive to maximum performance (this is safe since we do not go above stock limits).
Same thing in Black Myth Wukong.
In Hogwarts Legacy, which will allow you to change settings in game without restarting, this issue can be bypassed by disabling frame generation / relfex, which will immediately cause the GPU to throttle back up to full power, then reenabling frame gen / reflex and the GPU will stay at full power and perform as expected.
However, somethimes after some gaming, at random unforseeable intervals, the GPU will still fall back to this 780 MHz limit and stay there until doing this disable / enable cycle again.
Thanks for the feedback. There is definitely an issue. Interestingly this does not seem to happen in Indiana Jones, but this may be the way DLSS is handled?
Also, there is an nvidia-smi utility with --lock-gpu-clocks=MIN_GPU_CLOCK,MAX_GPU_CLOCK option, maybe it is worth a try? I am wondering if you need to enable the “Coolbits” for overclocking to set those.
Please do not hesitate to add infos to the Github bug report I made.
Thank you all for reporting issue to us, I have filed a bug 5106331 internally for tracking purpose.
Shall try to duplicate issue locally and get back if required any additional information.
Many thanks for filing the bug.
I just found out that some users are reporting clcking issues on Windows too: Question - Frequency problems with new RTX 5080 ? | Tom’s Hardware Forum
So could be linked to being in the early days of the card and drivers, and that these issues will be corrected in the future.
@amrits, @alex.lange: I have some more information that may help scoping the problem. Actually the 780 MHz lock up only happens when restarting Cyberpunk with DLSS frame generation 4X mode activated. If it is set to 2X or 3X, and the game is restarted, then the boost works (2737 Hz). Does this help? Can other people with other games try to set DLSS 2X or 3X in settings?
EDIT: the plot thickens: it may happen during game in 3X after all. However, contrary to 4X, this does not happen immediately, but at some point during play, without reproducibility, as reported by @alex.lange. However with Cyberpunk, once it is locked to 780 MHz there is no coming back, even if settings reduce frame generation (or disabling it), until game is restarted. It is as if there was some throttling happening and then lock down to 780 MHz.
@zebcom I can confirm, that also in Hogwarts Legacy it happens less frequently with framegen 2x (but still happens after some time of gaming). It’s also always present with framegen 3x but during my tests sometimes it was locked to 945 MHz immediately after starting the game and went to 780 MHz shortly after.
Framegen 4x immediately causes it to lock at 780 MHz during game start and throttle up is only possible after the mentioned disable/enable cycle.
@alex.lange: many thanks. Hopefully with all these details this will be solved in the next release.
Thank you all, I was able to repro issue internally with the provided information, engineering team will have a look into it further and share further updates as and when received.
@amrits: Many thanks for the update.
I can replicate this bug in any game with Frame gen. Best example is cyberpunk. If you activate frame gen at x3 or x4 it will lock up the clock at 780 MHz but if you start cyberpunk with x2 frame gen it kinda works but it looks kinda glitchy and buggy but the clock doesn’t lock up. I hope nvidia fixes this with the new driver update.
Also Monster hunter Wilds has the same bug with frame gen on. everything is laggy and glitchy but when i turn it off its all smooth.
Using the same system Ryzen 7 9800x3D | with 5080 RTX | 64 gb ram. I’m on Archlinux based distro if that helps.
This clock bug has existed on 40 series since frame gen was made available for Linux. Why now is Nvidia showing interest in fixing it?
