AMD Radeon Adrenalin Edition 20.5.1 driver download & Discussion

Both radeon overlay and afterburner/rtss spit out completely random metrics after the computer has been restarted or boot from cold. The only way to resolve this is to perform a factory reset, then things are normal until the next restart. Pretty annoying tbh!

 

Anyone using Win10 2004 yet?

 

I am, no problems so far. On the other hand i rarely have any issues.

 

Been running it since launch day. No problems after reinstalling drivers.

 

No problems as well.

 

I start to feel stupid now.After plugging back GPU and installing back 20.4.2 system is rock solid.

 

Add me to the list, 2004 + 20.5.1 = no issues (except the workaround for VEGA64 and P1 power state to eliminate black screens).

 

Most important is - you have identified the issue

 

Yep, installed on day one along with 20.5.1... no issues so far except that recording bug

 

2004+5.1 working almost* perfectly after clean installing them (regular install after ddu gave me a lot of trouble for some reason).

*known issue for Vegas, huge fps drop when bringing up the metrics overlay...first time ever

 

Hopefully indeed and thank you very much for your time by the way.

 

Anyone else have higher DPC latency with this driver? Latencymon is pegged at almost 500 microseconds at all times and I also experienced some instability in games.

I was pulling my hair out these weekend because I wasn't sure if it was the May Windows update or some kind of bios setting causing it but I finally narrowed it down to the 20.5.1 driver after a clean windows install. Rolled back to 20.3.1 and the latency is back down to 20-80 microseconds.

 

Maybe it improves if Catalyst Settings and the overlay are disabled, unfortunately the software keeps to running in the background and the overlay can only be hidden by default not disabled despite problematic stability and performance reports.

RadeonSoftware.exe can just be terminated it'll do it's thing once it's back up and running again and stay in the background, I'm not sure if it still does that powercfg report about going above recommended values for what it was though comparing with it shut down against running could answer that, I just check the options and check Wattman on boot and then I shut it down.

The overlay itself is amdow.exe and AMDRSServ.exe you'd have to rename them or starting Radeon Settings again will just launch the desktop overlay and the overlay software once more.
C:\Program Files\AMD\CNext\CNext

I don't know why AMD doesn't provide a toggle to properly disable these considering the problem reports, just hiding it from displaying still injects it into other programs and I'm curious if the number of reports on users manually device manager installing the drivers skipping Radeon Settings entirely is related to the overlay but it could just be in part and there's other issues here.


EDIT: Or the device driver itself simply has more delay now and it's something AMD has to look into and fix at some point, also a possibility I suppose and unrelated to overlay or settings software issues.

 

DPC latency concerns are system specific and vendors need logging data from affected machines to look into such reports.

 

in the same way, conflicts are created between the settings in the overlay and from the panel, All setting include wattman, so infinite problems and combinations.
In my opinion and try, the most functional way to "try" to fix some problems is to activate overlarly and set the same settings panel/overlay, when it seems it works disable overlay (disable=hidden)

 

I'm asking because I am able to replicate it very easily simply by installing this driver on a fresh Windows install.

If anyone else wants to check their Latencymon so I know it's only my configuration I'd appreciate it

 

No DPC issues here. LatencyMon was running for more than 10 minutes, Opera with 30+ tabs opened and played one War Thunder battle during measurement.

Spoiler: LatencyMon Full Report

Code:

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for  0:11:59  (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:                                        XINDL
OS version:                                           Windows 10 , 10.0, build: 19041 (x64)
Hardware:                                             Z170-D3H, Gigabyte Technology Co., Ltd., Z170-D3H-CF
CPU:                                                  GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Logical processors:                                   8
Processor groups:                                     1
RAM:                                                  32726 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed:                                   4008 MHz
Measured CPU speed:                                   8 MHz (approx.)

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.



_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs):   135,40
Average measured interrupt to process latency (µs):   2,143854

Highest measured interrupt to DPC latency (µs):       134,10
Average measured interrupt to DPC latency (µs):       0,774734


_________________________________________________________________________________________________________
 REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs):              41,973303
Driver with highest ISR routine execution time:       HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%):          0,007838
Driver with highest ISR total time:                   HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Total time spent in ISRs (%)                          0,008555

ISR count (execution time <250 µs):                   217377
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-999 µs):                0
ISR count (execution time 1000-1999 µs):              0
ISR count (execution time 2000-3999 µs):              0
ISR count (execution time >=4000 µs):                 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs):              133,196856
Driver with highest DPC routine execution time:       ntoskrnl.exe - NT Kernel & System, Microsoft Corporation

Highest reported total DPC routine time (%):          0,013339
Driver with highest DPC total execution time:         Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%)                          0,040357

DPC count (execution time <250 µs):                   874606
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-999 µs):                0
DPC count (execution time 1000-1999 µs):              0
DPC count (execution time 2000-3999 µs):              0
DPC count (execution time >=4000 µs):                 0


_________________________________________________________________________________________________________
 REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.


Process with highest pagefault count:                 none

Total number of hard pagefaults                       0
Hard pagefault count of hardest hit process:          0
Highest hard pagefault resolution time (µs):          0,0
Total time spent in hard pagefaults (%):              0,0
Number of processes hit:                              0


_________________________________________________________________________________________________________
 PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s):                       4,408035
CPU 0 ISR highest execution time (µs):                41,973303
CPU 0 ISR total execution time (s):                   0,492156
CPU 0 ISR count:                                      217352
CPU 0 DPC highest execution time (µs):                84,916667
CPU 0 DPC total execution time (s):                   2,054184
CPU 0 DPC count:                                      747767
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s):                       0,447558
CPU 1 ISR highest execution time (µs):                5,949351
CPU 1 ISR total execution time (s):                   0,000098
CPU 1 ISR count:                                      25
CPU 1 DPC highest execution time (µs):                133,152695
CPU 1 DPC total execution time (s):                   0,037745
CPU 1 DPC count:                                      21223
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s):                       0,583825
CPU 2 ISR highest execution time (µs):                0,0
CPU 2 ISR total execution time (s):                   0,0
CPU 2 ISR count:                                      0
CPU 2 DPC highest execution time (µs):                133,196856
CPU 2 DPC total execution time (s):                   0,071172
CPU 2 DPC count:                                      32808
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s):                       0,455891
CPU 3 ISR highest execution time (µs):                0,0
CPU 3 ISR total execution time (s):                   0,0
CPU 3 ISR count:                                      0
CPU 3 DPC highest execution time (µs):                132,925649
CPU 3 DPC total execution time (s):                   0,025504
CPU 3 DPC count:                                      13383
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s):                       0,565027
CPU 4 ISR highest execution time (µs):                0,0
CPU 4 ISR total execution time (s):                   0,0
CPU 4 ISR count:                                      0
CPU 4 DPC highest execution time (µs):                133,012475
CPU 4 DPC total execution time (s):                   0,036207
CPU 4 DPC count:                                      18162
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s):                       0,446385
CPU 5 ISR highest execution time (µs):                0,0
CPU 5 ISR total execution time (s):                   0,0
CPU 5 ISR count:                                      0
CPU 5 DPC highest execution time (µs):                132,636477
CPU 5 DPC total execution time (s):                   0,016247
CPU 5 DPC count:                                      9576
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s):                       0,543994
CPU 6 ISR highest execution time (µs):                0,0
CPU 6 ISR total execution time (s):                   0,0
CPU 6 ISR count:                                      0
CPU 6 DPC highest execution time (µs):                132,558134
CPU 6 DPC total execution time (s):                   0,038016
CPU 6 DPC count:                                      16730
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s):                       0,511343
CPU 7 ISR highest execution time (µs):                0,0
CPU 7 ISR total execution time (s):                   0,0
CPU 7 ISR count:                                      0
CPU 7 DPC highest execution time (µs):                131,861527
CPU 7 DPC total execution time (s):                   0,0430
CPU 7 DPC count:                                      14957
_________________________________________________________________________________________________________

 

Fully keeping in mind that it should only be run on an IDLE system with nothing open XD

 

OK, I will rerun measuring again with no apps running

 

Thanks @Krteq your latency looks normal.

Here's what mine looks like in case anyone was curious


I'll send a report off to AMD about it. Could be a Polaris thing maybe?