AMD Radeon Adrenalin Edition 18.6.1 Driver download & Discussion

Please submit a bug report because this has been an issue since the 18.5x series and, it seems, Win7 users.

I first reported it in the 18.5.2 thread here:
AMD Radeon Adrenalin Edition 18.5.2 Driver - Download & Discussion

 

Win7... rly... Try with win10, tinfoil hat and all (j/k).

MS already left Win7 to die, dont expect those bugs to be fixed.

 

Windows 7 & XP is the future!! /s

 

Wow, neither of us said anything about Win7 being superior to Win10.

 

In its own way W7 is superior to W10. But Gaming PCs should better all run W10. And show on steam survey, that gamers are ready for next step in software engineering. Otherwise we'll be stuck in DX11 4-Core CPU era.
With only occasional DX12/Vulkan game.

 

This is directly from AMD_Matt in AMD Forums about UVD BUG:

We were not able to reproduce this issue. We tested on a clean build of Windows 10/7, fully updated no other software installed (aka MSI Afterburner which is known to cause this issue) other than the latest driver and the clock speeds behave as they should.

Another comment:

We will take another look at the issue if we get more reports.
If anyone experiences this issue, please provide a summary of your issue and your can provide your full system specs, as well reproduction steps.

 

Here some history...

 

MSI AB causing the issue!? HAHAHAH.

 

Matt said it..i have no idea man, they probably tested in house..i dont think he is talking without testing.

 

Meanwhile he removed the MSI AB parenthesis on that post. Still, it's good to see them willing to take a look at the issue again.
In the past I've had good experience with the driver team solving problems after constructive feedback to amdmatt, so I took a shot at it on the thread.

 

Why exactly do you need that?
I have both AMD and Nvidia cards, and I can assure you that adding supports means 99.9% of the times nothing at all.
They (Amd and nvidia) usually just add a profile for the game, which is useful mostly for laptop users.
On Nvidia side of things, they sometimes add 3d vision support or sometimes better SLI support, but overall regarding performance, support for: tags for both nvidia and AMD means a BIG ZERO performance boost except when they specify it, like in this driver for vermintide 2.

This stuff of game ready drivers or Support for, it's mostly just pure marketing.
Also Vampyr it's an Unreal Engine 4 games, so basically I'm expecting that they aren't going to work on specific improvements for the game, but instead they will try to find possible improvements on other Unreal Engine 4 games that are more crowded like overwatch or PUBG/ fortnite, since improvements on those games can also translate to other Unreal Engine 4 games, since many things inside UE4 is shared across games.
Anyway Unreal Engine 4 will always perform better on nvidia, possible due to a huge colaboration that always existed between Nvidia and Epic.
Cheers

 

Here some Test w/ Vega 64 XTX LC:
It is Gain

"AMD claims 9% performance improvement with 18.6.1 drivers with Vega Series and Rx 480/580 so putting it too the test."

 

i assume they don't know how their cards works OR the game il not well written/programmed

 

You cannot compare unknown AMD RTG with famous CD Projekt Red and the best game RPG type ever made in history aka Witcher 3. They do not know how to write drivers since previous decades. For this matter respect only goes to the game maker not ATI.

 

It's easier to put the blame on others, than solving it yourself.

 

First of all Matt is using AB, and testing and reproduce bugs reported by us, so he can tell the team properly whats the problem...

Not like some threads i see on the AMD forums like "HEY AMD - change brightness and color .That is worse and poblem.Please solve.''
Like seriously? Nice bug report.

Anyway...lets not put the gun on his head for saying something like this.

Cheers.

 

The thing is that it has almost become a habit/meme by some "helper" users to point MSI AB as guilty for everything on a lot of threads in the official forums, mostly on unrelated and blatant driver problems. A classic example would saying that MSI AB is guilty for the CGN 1.0 because when applying an OC with it, the card doesn't respond to it and is stuck on UVD states. Only because AB is being used (on other affected systems too) and makes the problem obvious, it's "surely" guilty. /s

Last time I remember MSI AB being anything related to "UVD", was when the OC interface on drivers changed without any notice to AIBS that have their own OC tools (was it on driver 17.7.2?) and then apps using the official OC mode stuck the card on low clocks when applying a OC. IIRC this was promptly corrected by Unwinder after AMD was requested for the new SDK, and even then AMD reverted those changes one or two drivers later.

 

https://www.phoronix.com/scan.php?page=article&item=windows10-w10priv-wsl&num=1
Proud of my DX12 exclusive botnet. Tbh I would love to go back to 7 and get more vulkan games.

 

If you have More that 10 for Game profiles
My New Tweak will be interesting Time Savior

Make CNTweak.Reg file and edit + Copy/Paste:

Tweak to your liking,
TIP: also you can Run: Regedit and see the Values in Decimal not HEXa

"MaxFramerateDefault"=dword:00000046 [70FPS/Hz]
"MinFramerateDefault"=dword:00000040 [64FPS/Hz]

==
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\AMD\Chill]
"ChillLevelDefault"=dword:00000002
"MaxFramerateDefault"=dword:00000046
"MinFramerateDefault"=dword:00000040
"MaxFramerateRange"=dword:00000064
"MinFramerateRange"=dword:0000001e
"ProfileEnableDefault"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\AMD\CN]
"UA_Enabled"=dword:00000001
"Benchmark"="false"
"PreloadDelay"=dword:000000c8
"UnloadDelay"=dword:000000c8

 

Flicker on the screen produced by any application that uses AMD's Virtual Super Resolution (VSR) including vsr resolution on windows desktop

Flicker is also present when secondary screens are enabled
the error is present in Adrenalin Edition 18.6.1

Previous drivers such as Radeon Software version 18.4.1 are not affected by this problem

s.o: win 10
my gpu is amd 7950 with bios 280
monitor samsung bx 2350