Discussion in 'Videocards - AMD Radeon Drivers Section' started by MerolaC, Sep 12, 2019.
Didn't work, gonna try 19.8.2 and see if that helps :[
Surge 2 / Fifa 2020 / Code Vein / This week!
Next week - Ghost Recon!
So new driver soon 19.9.3 this week or 19.10.1 next week.
We are 2 months away from the 'Big One'
are the same of the "Win10-64Bit-Radeon-Software-Adrenalin-2019-Edition-19.9.2-Sep12" ?
Same but with the whql sticker.
The chillenabled registry bug is not fixed.
Yeah if that was reported and replicated early this month then this driver launching on the 9th originally wouldn't have the fix included since the driver would be going through the last bit of testing and be past additional code submissions and this WHQL update is the same code so probably the next driver assuming the bug is fixed and merged into whatever code base is going into testing and finalization for maybe one last September driver or the first October driver whichever it ends up being.
EDIT: Who knows how many different branches and development drivers there are going on over at AMD, it is known from earlier that code and features for the x.12.1 drivers start pretty early for example so it could take a while for these fixes for whatever driver is next in line and still doing code submissions and before testing and final packing and release.
Then there's the other channels like Windows Update say for the 20H1 builds of Win10 and also platforms like the active Linux code submissions and updates although I recall hearing that's a different team or something like that.
Testers would be using some driver variant as well or multiple depending on how things are looking there although for immediate concerns they do occasionally also publish hotfix drivers separate from these beta and WHQL sets though I think it's been a while since one of those came out.
The point is more that ALL 570 cards (no matter which brand) are ignored hence not fixed! Tell me WHY?
... and the following silence here will be ear deafening again.
Relax, your bug is just not so important for AMD. It doesn't hurt you in any way. Just heat and electricity. I used to get this a lot. Solution with other older AMD cards I've owned? vBIOS UPDATE. Go and search if you have the latest. AMD as a processor maker is not responsible for your GPU, the partnered vendor is.
There is no bios update for my rev 1.0 card - only for rev 1.1 cards
again, I am back to 19.4.3 and the card works as supposed and btw my card is just 2 years "old"
So you have tried only changing the driver and it simply stops? If you are entirely sure, that no 3rd party apps are opened or triggering the change in clocks and pciex state, spam AMD to fix this. Also try UVD fix from radeonmod at tweaks section. Also check if ULPS is enabled. I cannot think anything else besides vBios and driver. In my previous gpus it was a hit or miss. In those two years, how many months did you suffer with this bug? In my case I've suffered far more than a year. It is just beyond annoying. Imagine in my PC, it would even cause me weird screen lines...this bug.
There is only AMD Adrenalin installed on my box nothing else (concerning GPU) and nothing oc'ed - the problem exist since 19.5.x hence 4+ months. I am not going to investigate the issue since I got an ol n working driver and all 570 GPUs show this exact problem.
Exact same Gigabyte card too.
OOAHA, apparently an updated driver (from Sep 23) while my 19.9.2 is from Sep 12
Okay, downloading and testing it now.... hope its not just killing my time!
Same crap with this one:
What is the make/model of your monitor?
Maybe because you're running Wattman?
19.4.3 wattman is fine - what's your point?
No problem here on 570:
60 Hz monitor and no hardware acceleration while browsing.
Enjoy your Sapire but it does not help me!
We cannot help you. Nobody can. Format your pc or contact gigabyte. That is the problem with drivers. Drivers are for all. Not for you exclusively. Harsh truth.
As long as there are users with rx570 and downclock works, amd will not acknowledge you. The same thing happened before with older cards. Stop derailing the thread. It is not a driver bug. It is in hardware and os.
Use search in forums, see this happens since gcn 1.0.