Associate
You're kidding me! Just spent a small fortune to get this baby underwater..... typical.
Just wattman or everything?
Just wattman or everything?
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Everything, it has to be at registry level as MSI Afterburner doesn't help either.You're kidding me! Just spent a small fortune to get this baby underwater..... typical.
Just wattman or everything?
Reproduced, thanks i'll get this looked at.Overclocking is broken from after 19.7.5. You can change HBM clocks but core clocks just don't apply!
I've been running 1800mhz @ 950mv with 1140mhz HBM on recent drivers.
Everything, it has to be at registry level as MSI Afterburner doesn't help either.
There's a new Chipset driver too, so I'd install that's and 19.9.3 and see how you get on.
Reproduced, thanks i'll get this looked at.
Cheers for that Matt! I'd done a report several weeks ago but heard nothing other than an automated email from AMD.Reproduced, thanks i'll get this looked at.
We don't normally respond to bug reports via the reporting form, so that would be expected.Cheers for that Matt! I'd done a report several weeks ago but heard nothing other than an automated email from AMD.
Do you know what the last working driver was?Fingers crossed for a swift resolution
https://videocardz.com/driver/amd-radeon-adrenalin-2019-19-7-5We don't normally respond to bug reports via the reporting form, so that would be expected.
Do you know what the last working driver was?
We don't normally respond to bug reports via the reporting form, so that would be expected.
Do you know what the last working driver was?
Was that using 19.7.5?@Chud_Jenny Just set 1900 core clock in Wattman and seems to apply for me when running benchmarks. Or is it the reporting of the clockspeeds in monitoring that's broke? Showed me peaking at 1881 during the short run of heaven. 19.9.3
Did you make the change via Global WattMan or via Radeon Overlay in game?No, latest drivers. Updated yesterday and seems to be working for me.
That's very interesting to know. So the issue is from within wattman then. As even using MSI Afterbruner the clocks don't stick either.Did you make the change via Global WattMan or via Radeon Overlay in game?
In my testing using the overlay in game works.
Hi Matt, Global Wattman.Did you make the change via Global WattMan or via Radeon Overlay in game?
In my testing using the overlay in game works.
I find at 1800mhz I hold a clock of 1750-1780mhz in game. (All normal) If I input 1900mhz the in game clocks drop slightly around 1740mhz.Well, it may be all isn't well for me either. Whist the clocks appear to hold initially, like when running heaven for 45/50 mins earlier, but then when gaming, on the overlay the clocks are normal, i.e: just shy of 1800 with 99% utilisation. When I stop and check the log, wattman then starts reporting some really odd readings, like spikes of 4000mhz core and 1400 on the hbm. Jumps all over the place. Doesn't affect gaming performance but does the same thing if I run heaven again. Doesn't cause any issue when running heaven. Just odd readings on the log.
All very odd. And annoying!
On the plus side, I had 1901mhz with 1101mv running for ages
Yeah, will do.I find at 1800mhz I hold a clock of 1750-1780mhz in game. (All normal) If I input 1900mhz the in game clocks drop slightly around 1740mhz.
You'd be best installing 19.7.5 if you want to have a play with clocks to give your card a good work out!
Set the display time to 0.25seconds in performance monitoring too. Will get you a better idea of your clocks in game.Yeah, will do.
Will do. What sort of voltage should I be speaking at? What's considered safe max?Set the display time to 0.25seconds in performance monitoring too. Will get you a better idea of your clocks in game.