Discussion in 'Videocards - AMD Radeon Drivers Section' started by Hilbert Hagedoorn, Feb 4, 2019.
Yesterday got a freeze then a black screen playing SoTTR with memory timing level 2. So its a no-go with this driver and @Thadeus was right even level 1 have some instability and freezes. I never had issues with last driver just after i updated to this one.
With this driver, I get worse score in Firestrike when overclocking the memory than without.
Same here. There is something wrong with this driver and memory frequency/timings.
Something is wrong full stop. Went from 19.1.1 to this and while Apex Legends was smashing it smoothly with the older driver, this one kept downclocking based off the Hotspot temps. Due to the new Wattman logic it's totally broken and throttles regardless of settings.
Rolled back to 18.11.2, prior to all the destabilised drivers. Rock solid on the OC again now and rock solid performance without crashing drivers. Something that's been plaguing me since 18.12.1.
I reached a similar conclusion, and reverted back to the 19.1.1. WHQL.
They probably still need some time with this new driver family, so might still be tinkering at the moment.
I confirm too. There is a problem with Radeon Settings, which sometimes don't apply timings after (re)booting. I checked it several times using the OclMemBench. Trying to switching timings to auto and back doesn't solve the problem, need to reboot again.
This was my third attempt to get on with Radeon Settings, I had enough. Returned to the previous configuration, install display driver and afterburner, nothing more. I didn't notice any other problems with this driver, works fine. ¯\_(ツ)_/¯
19.2.1 = constant reboots as screen hangs up going into games.
Have gone back to 19.1.1 problem has stopped.
We'll probably get another driver right before Metro on 15th. Hopefuly it will fix some of these issues.
I've not experienced any issues with 19.2.1, but perhaps that's because I only installed the display driver? Also what games are you referring to? Do you have similar issues with other applications?
Edit 1: never mind, I spoke too soon. I spontaneously fired up DOOM, played through a few levels and when I quit the game my monitor seemingly lost input, blacked out for 10 seconds and then came back.
I forgot to mention that my fps would seemingly go up and down at random (causing major stutter) from butter smooth 144hz to well below 60 during cut-scenes and in the menu, but that might as well be a game issue.
And yes, before you say it, I always play my games without v-sync, but I did try to play around with both v-sync (which felt weird) and adaptive sync, which did next to nothing...
Edit 2: went back to 19.1.1 whql and all of my lag/stutter disappeared and my monitor don't lose input when exiting the game; definitely a driver related issue.
Be careful i noticed it does not save user settings sometimes. It kept my overclock but voltage was default for some who knows reasons, no wonder it crashed. Wattman broken.
Memory timings are also broken.
I swtiched back to 19.1.1 and everything works now. AMD fix this crap.
No wonder either here, I had some weird crashes when gaming. I just checked and it's that the voltage isn't saved.
Thanks for the heads up.
It's in the release notes but it's curious to see it applying to Polaris when the Adrenaline 2019 drivers so far have focused mostly on revamping Wattman and other parts for Vega primarily. Well it's clear from the above posts and the number of 580 GPU owners that the drivers do need more work.
Hi guys .
I used DDU restart and install new clean driver 19.2.1 .Gpu Rx vega 56 in stock now. And my problem is new driver not starting main aplication klick and blue circle (windows)rotate ,but main menu not working .I try reinstall 3 times ,and the same result . Maybe windows is problem W 10pro 64 bit ver 18.09 .
Did you use DDU + safe mode?
No i not use safe mode in DDU .Thats important? Waiting for help because try install 19.1.2 and the same problem :main menu not start ,just rotate circle .....
Next step , Safe mode+DDU instalation and the same result .Aplication not start .Again Start windows in safe mode and back to normal windows -and finally work Alright !
THX for help me ! ! !
Naturally now is 19.2.1 tomorow go to play division2 beta , just one day to game.
I have one invite to this test beta ,anyone interest ?
Weird behavior, but since it worked...have fun!
I now this is only beta test,but game start in dx11 in dx12 crash one by one or even not start (frezze).Game with partner is AMD Nad special beta driver to this game .Saad .
I'm playing the game on r9 380 with this driver and everything works good. The only time it crashes on launch is when afterburner is running in background but this can be workarounded and i can make afterburner and the division 2 beta work together.
I run an R9 390 and I can second this result with regard to The Division 2 & DX12. In DX11 Game runs without issue (minor micro stutters when rotating the camera) & just the server disconects to deal with. In DX12, game runs fine up until I exit any safe house/base to the street. Enter the street, game crashes to desktop &* shuts down with no error given. This occurs regardless of core/mem OC or default clocks.
For an AMD supported game this is a devastating display of incompatibility & does not inspire me with confidence that this game will improve on what took them 2 yrs. to fix up in the first game (I've been playing that since alpha days)...
I too have negative performance as soon as I OC vram (in any game & in synthetic bench).
Also of note is the fact that Google chrome constantly hangs when scrolling web pages after a few minutes. Use task manager to kill chrome.exe & computer control is returned without issue (can just relaunch chrome). Kill chrome via the red X (top right of web page) & you can visibly see the screen flash/show tearing & the gpu driver resets itself. In both occurences after relaunch chrome will again start intermittently freezing/releasing after several minutes, regardles of online activity at the time, even Idling gets affected in the same manner.
Solution? DDU'd back to 18.2.1 & things are good again although I have yet to test The Division DX12 with the 18.2.1 driver..
So yeah, AMD getting ahead of themselves a little I think...