General Discussions

[supervargen]

Are you using Adrenalin 18.2.2?

If so, How’s That Driver Working For You?

Problems?

All good?

What's new?

Did it solve a problem?

Tell us plz.

Radeon Software Adrenalin Edition 18.2.2 Release Notes

No fixes at all?? Really AMD? Really???

[locodicegr]

Maybe thats a game Bug.

[locodicegr]

Windows 10 RS3 / R9 380 / Adrenalin 18.2.2.

NO Problems, everything is smooth.

[wetpretzel2]

Lucky you, It is only PUBG that i am having problems with. Fixed the issue of screen image burn in Star Wars Battlefront 2.

[colesdav]

Hi,

Did you take a look at the popup on the Wattman Graph. Does that show the correct temperatures and fan %/ r.p.m. for your cards?
If so, can you add a screenshot to this thread?
I file an AMD Reporting Form about it and point to this link.
If it is a card specific or OS Specific issue that would probably be useful.

Could you please tell me if you can report GPU Power in your performance overlay?

Another thing I noted yesterday about the Performance Overlay for my Sapphire HD 7970 OC 6GB Vapor-X Card.
I was trying to test / monitor the use of GPU VRAM versus Resolution, Antialias settings and Texture settings on Doom and Rise of the Tomb Raider.
The Performance Overlay reports  GPU VRAM UTIL.
Here is an example from testing Doom at 2K on Ultra with AA settings almost at maximum level.

Note:

In the above case the HD7970 OC 6GB Vapor-X card is connected to the motherboard using a PCIe2.0-USB3.0-PCIex16slot "Mining Adapter".
Therefore the reported  FPS is likely lower than I could achieve if the card were connected via Thunderbolt 2 (PCIe2.0x4) or Direcly connected to the Motherboard using  PCIe3.0x16/8/4.
Also note the card is running at default clock and power profile. I can easily overclock this card to at least 1150/1580 with +20% Power setting.
I think the above is pretty good performance for an 'old' card.

If you look at the top right hand of the above image, the performance Overlay reports 6GB of GPU VRAM is in use.

Problem: If I increase AA settings further to completely fill the VRAM then the GPU VRAM UTIL report in the Performance Overlay dissapears.
I think the GPU VRAMUTIL should say "overflow" or "full" or something like that to indicate that it is being monitored and the User may need to reduce their settings.

Another issue. I can only report performance Overlay figures for 1 GPU at a time. So if I run two R9 Nanos in Crossfire I cannot tell what the activity is on the second GPU.

Cheers.

[fr3nki]

Not even one Adrenalin software want to install driver on mine computer all i get is black screen crash during install of display driver part , this also happens on 17 + but after restart or two it menages to install ,17 also crashes during intense gaming , only driver that works totally fine is crimson 16.12.12 ,

I have phenom II x6 1090t,RX 470,Windows 10 x64 (1511 and im not planing to upgrade cos if works awesome for now 3 years )

[jontya]

I've had an issue, mouse input lag/stuttering.

RX 580 8GB

Win 10 (64)

i7-3770k with 16GB

Mouse is a Razer Deathadder with Synapse 2.21 installed (latest version).

First noticed on PUBG but then after further testing found it was happening on the desktop as well as other applications.

Fixed by rolling back to 18.2.1.

I'm happy to provide further information if anyone wants it.

[wetpretzel2]

Is it like I said earlier? going into a fire fight my screen hangs? only does it in game though.

[colesdav]

I retested Radeon Chill on HD7970 /R9 280x/ R9 Nanos yesterday.

I was not expecting it to be improved yet. But there is not even a mention of Chill Performance Limitation on the Release Notes.

To me chill is still broken and needs fixed before it is worthwile using it, especially for those with lower end Freesync monitors (who will likely need Chill to match / improve lower end GPU performance).
 
See: Could AMD please add Keyboard and Mouse input Weighting sliders for for Chill in Adrenalin Driver?

Turning Chill on limits the keyboard only input FPS for me to around 45-55FPS on a wide range of games ... including Doom.

If you can could you please test it and see how it perfoms with your cards/ system?

Thanks.

[wetpretzel2]

My problem with chill is that although it drops the fps down it still runs frequency balls to the wall, so the temps are not really effected, is it something I am doing wrong? The overlay also for some reason keeps on (crashing I think) coming up saying that Radeon client host needs to restart. But don't get me wrong, the in-game performance improvements are defiantly there and noticeable- GOOD DRIVER

[colesdav]

I have run Chill Benchmarks and I definitely see temperature drop on the GPU in certain cases.
The ability to measure the temperature difference you see will depend on Chill Min and Chill Max setting, the game, and the game activity.
People with higher performance/power GPUs will likely see more effect of turning Chill on.

Radeon Chill monitors user keyboard input, and mouse input, so that monitoring activity will incur some compute cost which should be insignificant CPU power increase versus saving on the GPU.

Assuming your GPU can run the game at or near Chill Max FPS normally, with Chill off.
Also assuming the game itself has no built in FPS power saving algorithm implemented in software.

There are three cases to consider.

1. If no activity detected on either then FPS should run at Chill Min.

2. If you move your mouse rapidly for long enough the FPS will go up to Chill Max.

3. In Radeon Chill, If you use any keyboard only input, FPS will rise to ~ (Chill Min + X)  FPS where X depends on the (Chill Max -Chill Min) value.

Unfortunately for me, X is only about 15-25 FPS when Chill Min is 30 FPS, and Chill Max is 60-300 for a large number of games tested.

Therefore Chill impacts gaming FPS performance for keyboard only input with those settings.
In addition there is an inherent time lag to ramp up from Chill Min to Chill Min + X for keyboard only input which the User cannot modify, but it seems acceptable to me.

Case 1 should save save power and drop GPU temps.
Case 2 will not save power but given the wild mouse movement needed to sustain Chill Max for long enough, I cannot think of a game where that is realistic.

Case 3. This will also save power, since with keyboard only input the FPS is only (Chill Min + X) and is  < Chill Max in all cases I tested.

Running Chill benchmark in a repeatable manner can be difficult depending on what you situation you try to measure and what scene in the game you are testing.

I will take a look to see what happens to the GPU Frequency on R9 Nanos in the three cases above.

Cheers.

[mline]

Tested it with my R9 380.

Some features are still buggy. Performance is ok

Most annoying thing is: to many unnecessary features (relive, gallery, overlay) again.

And this is the reason, why i downgrade to 17.11.1

AMD, please focus to drivers, API and documentation (for external developers)

[billy323]

There is an issue with amddvr.exe. When watching a video on YouTube via Firefox the amddvr.exe process will keep the GPU clocks maxed and usage at 100% in a phantom state causing higher than idle temps. Ending this process drops clocks back to idle but it returns if you watch another video. I do not have Relive installed so I am not sure why this process is even running but i think it has to do with the overlay added in Adrenalin.

[kingfish]

It is very easy to fix the issue with amddvr.exe. I don't install Relive either, yet it is installed, and set to 'autostart'.

You run Autorun as Administrator. You uncheck the box by amddvr.exe. Done.

[lostcat]

Systems blanking out and rebooting when playing a WebGL game (it's a hentai game or I'd be more specific) with either 18.2 build.  Don't remember it happening before that.

A10-7850K with or without a 290 in it and an FX-7500.

Had to switch to my NV card to keep playing so can't test further on the desktop at least.

[colesdav]

RE: Systems blanking out and rebooting when playing a WebGL game (it's a hentai game or I'd be more specific)
I think that might actually a deep learning / AI feature of AMD cards and drivers, not a bug.

[vidko]

I'm still having issues with Relive which always stops working as soon as I alt-tab out of any game and back. The only thing that helps is a computer restart which is a real pain in the a**. Running Windows 10 x64 with RX580 8GB.

For me it's a real issue.

[colesdav]

Hi, try setting Record Desktop switch to on in ReLive Recorder. Does that help?

Cheers.

[vidko]

I tried it. The desktop works, but when i alt-tab back into the game still nothing. I also tried 18.2.1 and 18.2.3 same behaviour.

[colesdav]

I just tested Adrenalin 18.2.2. on Windows 10 64 bit recording Rise of Tomb Raider full screen, 4K, Maxed out graphics, in DX12 MultiGPU.
Turned on Desktop Recording.
I can ALT Tab out to desktop (Radeon Settings) and back in to Rise of the Tomb Raider and it all gets recorded fine.
i7-4790K and Dual R9 Nanos installed at the moment.
Maybe it is different in DX11 games ... I can look at that but it will be this evening.
Usual recommendation on this forum would be run DDU, remove all old AMD/Nvidia graphics drivers, reinstall AMD Driver, try again.

Bye

[colesdav]

And thanks for letting me know Adrenalin 18.2.3 is released .

[colesdav]

I do not have Windows 7 OS here. 
I quickly tried running Tom Clancy the Division at 4K in DX11 fresh Windows 7 18.2.2 Driver install running on unsupported Windows 8.1  64bit OS.
Even that allows me to record "The Division", ALT Tab  out to desktop, ALT Tab to Adrenaline GUI, ALT Tab to FireFox, ALT Tab back to Tom Clancy's the Division.
The ReLive Recording recorded everything correctly with no problems.

Even Crossfire DX 11 appears to be running great running this driver on an unsupported version of Windows 8.1 64bit.  
I am uninstalling the driver and reverting back to supported 17.4.4 Crimson ReLive for use on Windows 8.1 64bit.

I will try Windows 7 64bit later.

Bye.

[javierabadie]

Still slow FPS on PES 2018. Last drivers who works well is 17.7.1.

Check on some PCs:

RX 580

RX 480

RX 570

Same on all

[me262schwalbe1]

Computer name: DESKTOP-ENP7QRA
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\WINDOWS
Hardware: Inspiron 5576, Dell Inc., 0JW8XC
CPU: AuthenticAMD AMD FX-9830P RADEON R7, 12 COMPUTE CORES 4C+8G AMD586, level: 21
4 logical processors, active mask: 15
RAM: 7999471616 bytes total

---

Crash Dump Analysis

---

Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

Crash dump directories:

C:\WINDOWS

C:\WINDOWS\Minidump

On Sun 2/25/2018 1:02:59 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022518-9937-01.dmp
This was probably caused by the following module: atikmpag.sys (0xFFFFF80213F4F7E8)
Bugcheck code: 0x116 (0xFFFFA102F4107200, 0xFFFFF80213F4F7E8, 0xFFFFFFFFC0000001, 0x3)
Error: VIDEO_TDR_ERROR
file path: C:\WINDOWS\System32\DriverStore\FileRepository\c0323831.inf_amd64_1212be4b9fe2386c\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR

---

Conclusion

---

One crash dump has been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

[locodicegr]

Update your windows -> DDU -> 18.2.3

[me262schwalbe1]

dam,I didnt expect another one so soon...I have dell support assist on automatic and cannot trust windows updater or device manager...I have to manually look.

[me262schwalbe1]

I have 18.2.1  I tried using the check for updates option in radeon menu and it is not working.I checked there are no updates.

[plumboby]

manually update windows threw device manager its what i do as sometimes windows downloads a heap of packages driver wise & installs the wrong way.Its why i use device manager as you can back track the other drivers for your system to suit & update to the compatible drivers to suit. Windows is hit or miss more mainstream builds i trust it but with Dell builds or Pre builts i use the device manager & manually update to suit just a habbit i use with all builds & repairs i do.

[me262schwalbe1]

Dell just gave me another driver update...I got the driver version 17.7 now...What the hell????18.1  was fine with a few bugs and I was expecting to go forwards not backwards....I was expecting driver version 18.2

[plumboby]

Does happen with pre built like Dell, HP etc. Stick with the newest if they are stable running 18.2.1 drivers atm not to bad on my pesky build.

[rocketman99]

Still crashing regularly in TDR thread. I only play GW2 which is a DX9 game. Crash dump below. As always, clean install new drivers, no Relive or other bits installed. Graphics card is Sapphire RX560.

Microsoft (R) Windows Debugger Version 10.0.15063.468 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 16299 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 16299.15.amd64fre.rs3_release.170928-1534

Machine Name:

Kernel base = 0xfffff801`7ae1d000 PsLoadedModuleList = 0xfffff801`7b184110

Debug session time: Sun Mar  4 15:57:43.639 2018 (UTC + 11:00)

System Uptime: 1 days 1:01:20.307

Loading Kernel Symbols

...............................................................

..Page 23e511 not present in the dump file. Type ".hh dbgerr004" for details

........Page 110f76 not present in the dump file. Type ".hh dbgerr004" for details

......................................................

.......................................................

Loading User Symbols

Loading unloaded module list

....................

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {ffffd00c02c811a0, fffff80b3669f99c, 0, d}

*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys

Probably caused by : atikmpag.sys ( atikmpag+f99c )

Followup:     MachineOwner

---------

6: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

VIDEO_TDR_FAILURE (116)

Attempt to reset the display driver and recover from timeout failed.

Arguments:

Arg1: ffffd00c02c811a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff80b3669f99c, The pointer into responsible device driver module (e.g. owner tag).

Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.

Arg4: 000000000000000d, Optional internal context dependent data.

Debugging Details:

------------------

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  16299.15.amd64fre.rs3_release.170928-1534

SYSTEM_MANUFACTURER:  Dell Inc.

SYSTEM_PRODUCT_NAME:  XPS 8920

SYSTEM_SKU:  07DC

SYSTEM_VERSION:  1.0.7

BIOS_VENDOR:  Dell Inc.

BIOS_VERSION:  1.0.7

BIOS_DATE:  06/05/2017

BASEBOARD_MANUFACTURER:  Dell Inc.

BASEBOARD_PRODUCT:  0VHXCD

BASEBOARD_VERSION:  A01

DUMP_TYPE:  1

BUGCHECK_P1: ffffd00c02c811a0

BUGCHECK_P2: fffff80b3669f99c

BUGCHECK_P3: 0

BUGCHECK_P4: d

FAULTING_IP:

atikmpag+f99c

fffff80b`3669f99c 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CPU_COUNT: 8

CPU_MHZ: e10

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R)  SIG: 5E'00000000 (cache) 5E'00000000 (init)

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  HOMER

ANALYSIS_SESSION_TIME:  03-04-2018 16:55:30.0306

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

STACK_TEXT: 

ffff8287`6dcef6d8 fffff80b`361cce10 : 00000000`00000116 ffffd00c`02c811a0 fffff80b`3669f99c 00000000`00000000 : nt!KeBugCheckEx

ffff8287`6dcef6e0 fffff80b`361cc4e3 : fffff80b`3669f99c ffffd00c`02c811a0 ffff8287`6dcef7e9 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xec

ffff8287`6dcef720 fffff80b`3754cf64 : ffffd00c`02c811a0 ffff8287`6dcef7e9 00000000`0035a4ea ffff8287`6dcef900 : dxgkrnl!TdrIsRecoveryRequired+0x193

ffff8287`6dcef750 fffff80b`375b3921 : ffffd00b`ff29a000 00000000`00000001 ffffd00b`ff29a000 ffffd00b`fd917000 : dxgmms2!VidSchiReportHwHang+0x4c8

ffff8287`6dcef850 fffff80b`3758e823 : 00000000`00000002 00000000`0057f785 00000000`0035a4ea 00000000`00000400 : dxgmms2!VidSchiCheckHwProgress+0x24bb1

ffff8287`6dcef8c0 fffff80b`3752a0bc : 00000000`00000000 ffffd00b`fd917000 00000000`ffffffff 00000000`ffffffff : dxgmms2!VidSchiWaitForSchedulerEvents+0x303

ffff8287`6dcef990 fffff80b`3759cc5f : ffffd00b`fe3bc000 ffffd00b`fd917000 ffffd00b`fe3bc010 ffffd00b`fd917000 : dxgmms2!VidSchiScheduleCommandToRun+0x33c

ffff8287`6dcefa80 fffff80b`3759cc1e : ffffd00b`fd917500 ffffd00b`fd917000 00000000`00000080 fffff80b`3759cb90 : dxgmms2!VidSchiRun_PriorityTable+0x2f

ffff8287`6dcefad0 fffff801`7af33b87 : ffffd00b`fd914700 fffff80b`3759cb90 ffffb980`7b080180 000004ed`bd9bbfff : dxgmms2!VidSchiWorkerThread+0x8e

ffff8287`6dcefb10 fffff801`7af99be6 : ffffb980`7b080180 ffffd00b`fd914700 fffff801`7af33b40 16168230`1a168231 : nt!PspSystemThreadStartup+0x47

ffff8287`6dcefb60 00000000`00000000 : ffff8287`6dcf0000 ffff8287`6dce9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  a05e887139f0ff6cbfa648fbee599294462fd682

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  dc5aed2af84e9387cf37b11e10d0535486fe7aab

THREAD_SHA1_HASH_MOD:  65b26f16328fe41a723c00193723d68b091ef48d

FOLLOWUP_IP:

atikmpag+f99c

fffff80b`3669f99c 4883ec28        sub     rsp,28h

FAULT_INSTR_CODE:  28ec8348

SYMBOL_NAME:  atikmpag+f99c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5a7a3472

IMAGE_VERSION:  23.20.15017.4003

FAILURE_BUCKET_ID:  0x116_IMAGE_atikmpag.sys

BUCKET_ID:  0x116_IMAGE_atikmpag.sys

PRIMARY_PROBLEM_CLASS:  0x116_IMAGE_atikmpag.sys

TARGET_TIME:  2018-03-04T04:57:43.000Z

OSBUILD:  16299

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-02-10 15:34:33

BUILDDATESTAMP_STR:  170928-1534

BUILDLAB_STR:  rs3_release

BUILDOSVER_STR:  10.0.16299.15.amd64fre.rs3_release.170928-1534

ANALYSIS_SESSION_ELAPSED_TIME:  66a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x116_image_atikmpag.sys

FAILURE_ID_HASH:  {e300aa8c-6915-3f37-7957-d2e4fc30a6fd}

Followup:     MachineOwner

---------

[naftali]

THIS IS THE WORST UPDATE, IT WILL JUST CRASH! I WAS FINE WITH 18.2.1 BUT THIS. THIS IS THE REASON WHY EVERYONE GOES FOR NVDIA.

[me262schwalbe1]

ROG Strix GL702ZC user reporting it hasnt crashed yet and it has been several days.

[Ray_AMD]

This is a thread referencing Adrenalin 18.2.2.

There have been several driver releases since then.

If you have an issue, open a new thread on it, making sure you provide all the necessary information.