Discussion in 'Videocards - AMD Radeon Drivers Section' started by Hilbert Hagedoorn, Feb 3, 2020.
Thanks for the heads up
Big changelog incoming?
I think this is self explanatory
Same hire with downclocking and performance in some old game,no other big issues,but this is
enough.This is not normal,after 4-5 months Navi make 1 year and still cant makes stable drivers.My GPU is 5700xt Nitro+ and in some older game like Diablo 3 my fps is lower than my old 1050ti,on fortnite average fps is good but because of downclocking 1%FPS is terrible and game feels stutters.I know my CPU (4770s) provide me a bottleneck but not so match.I like AMD because they destroy the monopolies of Nvidia and Intel but is not
serious to pay 500 euro and to wait 1 year for stable drivers.
Sorry for bad English.
Have a nice day.
Turn off ULPS (ultra low power state) via msi afterburner and poof problems gone
Let's hope that it will solve more problems than it newly introduces...
Hopefully a huge changelog then
I dont expect a huge changelog, but maybe they found the problem that causing all those issues.
Fingers crossed all goes well.
Finally found a monitor for reading Jonas' replies:
Haha good find! xD
System crash/lock with reboot on my window 10 PC.
My PC-system is a dual boot between:
· macOS Catalina version 10.15.3 (vanilla installation)
· Windows 10 version 1909
· Intel i7 4,2 GHz
· ASUS Ranger VIII bios 3802
· Radeon RX5700 8GB
· Kingston 32GB ram
· Dell P2715Q
My macOS Catalina system is running extremely stable. I have not had any faults whatsoever. I have had the machine running for a week, without turning it off. No lock up, no reboots.
But my windows 10, on exactly the same hardware, is random locking and then rebooting, even when the machine is standing idle by itself. I have not installed any games. I have tried a lot of all the good advise on all forums, but it just keep on random rebooting.
· Turning ULPS off
· Turning HDCP off
· Changing cables
· Using HDMI or DP
· Installing only drivers via “Device Manager” or full package
· Trying all different driver versions (with clean-up between)
· Turning down max clock
· Always with low temperatures
· No gaming
· New clean windows 10 installation
This always gives me the same result, just random lock up with rebooting of my windows 10 machine.
But as my macOS installation runs extremely stable on the same hardware, I’m pretty sure it is the AMD Radeon windows drivers that need some attention and soon.
That black screen bug is NOT causing hard resets.
What is event viewer and dump telling you?
The driver does cause hard resets its just the screen goes straight to black and system restarts almost like losing power instantly
I can reproduce this by running batman AC with vsync off, this is the only game
nothing in event viewer and psu tested ok
Yeah it can either recover, force the user to do a restart if it doesn't recover or if the hotkey to restart the display driver does nothing or you get the third variant that causes the system to restart on it's own similar to the PSU hitting the over current protection.
This particular quirk could be done on Navi on the drivers before 19.8 by overclocking memory on the fly as well but 19.8.1 resolved it and this error here happens even with memory at stock speeds.
EDIT: Hardware acceleration to off in the drivers is the only thing I see missing from the above list too but that's a large amount of software.
(Browser itself, programs like Steam or Discord and what not and media playback software for example.)
Including Radeon Settings itself now that it has a inbuilt browser component so the settings process would have to be terminated if it's that.
EDIT: Also unsure if that third variant (Automatic system shutdown and then reboot.) is 5000 series only or can happen on Polaris and Vega but maybe not and again a pointer towards these errors coming from multiple sources or issues with the drivers whatever is causing it.
AMD already fixed that one before with the memory but it wasn't the only one seemingly.
EDIT: Hah well I guess that Nexus URL wasn't liked ha ha!
And the driver fix for it later on.
Well that particular one at least, plus at least two or three more since for various black screen conditions but it's not resolved fully yet.
EDIT: Suppose the big one is if AMD worked around a hardware fault or not because then these are basically unfixable and can only be worked around which at worst is a endless loop of breaking and fixing a issue that could occur with any number of variables and conditions but then again firmware or micro-code updates are fairly flexible so perhaps once fixed it'll actually hold.
Just like when AMD fixed hardware acceleration!
And then broke it in the very next driver release. Again causing issues with hardware accelerated browsing and as seen also media playback and general software like Adobe.
(Yeah it's a bit repetitive but the number of regressions like that is stupid and should have been found I'd think at least however this stuff is tested.)
Browser seems to be the main one though and there's also been external factors to be fair including Chromium 80.x that seems to have been more sensitive or possibly buggy but that's since been fixed.
And for Firefox it's kinda going back and forth and I think Mozilla and AMD and NVIDIA which also get hit by problems here on occasion keep shifting blame back and forth so eh it's not just the driver side that seems to be problematic.
(Yay another lengthy post but eh it's a complicated issue. ~ )
You know, I've never used HW acceleration on web browsers and the like as I've never noticed any benefit from doing so.Even when the web browser was used for BF3/4 I've keep it off.
Guys, make sure you disable auto-reboot on possible BSOD (that happens if a game ends in black screen, nothing responds and then PC restart automatically) and set Write debugging information to Kernel memory dump.
It can be set in System Properties > Advanced > Startup and Recovery
That way we can possibly investigate the source of the issue and fix it.
Tearing on some sites.
Really? I never noticed.
So, AMD is snooping on us all?
Yea, but isn't terrible.