- Aug 25, 2001
- 55,125
- 9,172
- 126
This is interesting. Apparently the "secret sauce" between Ryzen and Radeon, includes undocumented CPU overclocking.
Tom's has an article on it for those of use who prefer print. Sounds like AMD tried to put Ryzen Master into Adrenaline? Seems unnecessary. Also, if it is automatically enabling PBO, doesn't that mean AMD is automatically voiding peoples' warranties?
This is interesting. Apparently the "secret sauce" between Ryzen and Radeon, includes undocumented CPU overclocking.
"The current speculation is that the integration of AMD's Ryzen Master module into the Adrenalin version 22.3.1 ...".That's weird. Which driver build(s) do this? I use Ryzen Master and have a Radeon VII and the drivers haven't activated PBO yet.
Did you ever set PBO to on in the past? Maybe it is auto-OC because AMD thinks, hey, warranty is voided anyway, so what the heck? Let's make people happy!I did not try to tweak and overclock again, I just set it to stock. Just do not have time for tweaking right now.
My warranty is very much void from manual OC. No problems here.Did you ever set PBO to on in the past? Maybe it is auto-OC because AMD thinks, hey, warranty is voided anyway, so what the heck? Let's make people happy!
Lets not have that getting in the way of a good lynch mobbing.
Just a bug. This is not exciting after all.
Yes, the CPU was overclocked prior via PBO.Did you ever set PBO to on in the past? Maybe it is auto-OC because AMD thinks, hey, warranty is voided anyway, so what the heck? Let's make people happy!
A good lynch mobbing is exactly what needs to happen!Lets not have that getting in the way of a good lynch mobbing.![]()
Ryzen Master never installed here so that's not the difference. Since it is a bug, it's probably some weird combination of factors that causes it when the drivers are installed on a Tuesday or something weird like that.Yeah I have 22.3.1 as well. It doesn't happen on my 3900x. Granted I have Ryzen Master installed and use it on a regular basis so it may be that the module disables itself in deference to the full application.
Agreed. Example, I was using a win XP box, that was not even on the internet, and using the same video card and monitor for literally years, my "old games" gaming box. One day the monitor went black. After literally weeks and changing out all the hardware multiple times, I found out that for some reason, under XP, that comination would not work anymore. Under win 10, the monitor worked, but even though it worked on XP for bios, as soon as it loaded XP, it went blank. And the same video card works, but is not installed anywhere right now. So obviously it was win XP drivers that stopped working after some period of time with THAT monitor.Ryzen Master never installed here so that's not the difference. Since it is a bug, it's probably some weird combination of factors that causes it when the drivers are installed on a Tuesday or something weird like that.
Same (22.1.2), and I have yet to see any of this buffoonery.Hmm, good to know about this potential bug. I am still on 22.1.2 I believe on my systems with Radeons, and one of them is Intel based anyway.
Liked for use of buffoonery. My wife or son will get hit with that before the night is over.Same (22.1.2), and I have yet to see any of this buffoonery.
Could be some sort of corruption. If you still have it, boot into VGA mode with F8 at startup and uninstall the driver, then re-install if the monitor comes up.So obviously it was win XP drivers that stopped working after some period of time with THAT monitor.
Disabled. It just means you can toggle it on or off with software tools like Ryzen Master.Normally when the PBO is set to auto in the bios/uefi, is it disabled or enabled?