The AMD Driver Thread

[LtMatt]

i stopped using afterburner when i noticed it ****s my fps in csgo. Not sure who to blame, amd or afterburner though.
Also to the guy who said not to use DDU because it aint the 90's anymore. When I tried to uninstall the driver using the original AMD uninstaller i would rebouot and crimson would still be in the system tray saying i dont have any AMD driver installed.

Sometimes you need DDU or a program like it.

Kun my dutch friend.

If you are looking for an alternative to MSI AB for an overlay, HWINFO64 works like a dream.

 

[LtMatt]

Just install over the top.

No no no. No! This is not recommended at all, it can cause problems especially when switching from Catalyst to Crimson.



I realise that you are going to reply with but it's never caused me any problems doing it this way.

in a perfect world that works, sometimes it gets messed up.

to my old perv friend Mattholamew, cheers ill try. btw matt we doing a bf3 metro night soon ish with jim chip bass josh the lot etc make sure to be there ill mail ya

Do it Kun, I'll be there. Please give me notice though, not at the last minute.

 

[LtMatt]

At least you know the reply. Although I was talking more with standard installs, not particularly the twice in a lifetime driver "family" switch

7 years lucky then I guess

Consider yourself lucky, buy an extra lottery ticket next week.

It's not uncommon for us to have the odd known issue in our release notes that is caused by people installing one driver over another.

 

[LtMatt]

Hows the ratio look to those bugs induced by knackered installs for using DU?

Especially since windows installs over the top as well...

Never heard of DU, but it's not AMD software that I do know.

Windows 10 has a habit of randomly installing drivers and overwriting existing ones. It causes no end of problems, and as my job is solving problems, I speak from experience.

 

[LtMatt]

AMD Radeon Software Crimson Edition 16.1 for Non GCN Products Release Notes

These drivers are for legacy products and update the legacy Crimson package to 16.1 to incorporate all the latest fixes. Essentially, everything prior to GCN architecture.

Full release notes and download link here.

Spoiler

AMD Desktop Product Family Compatibility ​
AMD Radeon™ HD 5000 Series AMD Radeon™ HD 8000 - 8400 Series
​AMD Radeon™ HD 6000 Series ​AMD Radeon™ HD 7000 - 7600 Series

AMD All-In-One Desktop Product Family Compatibility
AMD Radeon™ HD 7600A Series Graphics AMD Radeon™ HD 6600A Series Graphics
AMD Radeon™ HD 7450A Series Graphics AMD Radeon™ HD 6350A Series Graphic

AMD APU Product Family Compatibility​

AMD Radeon™ HD 8000D Series Graphics AMD Radeon™ HD 8000G Series Graphics
AMD Radeon™ HD 7000D Series Graphics AMD Radeon™ HD 7000G Series Graphics
AMD Radeon™ HD 6000D Series Graphics AMD Radeon™ HD 6000G Series Graphics

AMD Mobility Product Family Compatibility

AMD Radeon™ HD 6000M Series Graphics AMD Radeon™ HD 5000M Graphics

 

[LtMatt]

Individual game profiles regarding crossfire are not saving and not applying again. For example, I know games that if AFR mode is selected for their profile, when in game it should be really bright or really flickery. This is now not happening for those games when I go to test with AFR running on those games from the profiles, 2nd card not running as I can see a 300Mhz core clock on 2nd card. Crossfire is 100% screwed in this version, I still think it's down to the option that's missing in the crossfire section "Enable CrossfireX for applications that have no associated application profile"

Just updated to Radeon Crimson 15.12 and AVG popped up with "General behavioral detection - c:\\Programdata\Launchurl.bat"" After a quick google noticed someone who also installed AMD drivers had this pop up, False positive perhaps?

We're aware of an issue with settings not apply correctly. Look out for the next Crimson driver.

 

[LtMatt]

@AMD Matt, and everyone else.

When someone reports flickering on Freesync, with Catalyst 15.7 and later, especially Crimson 15.12/16.1 please check your DP cable.

Especially if you have XL2730Z the cable that came with the monitor is not DP1.2 but DP1.1 and you have the flickering because of the cable. Throw it away and buy a good DP1.2 compliant cable. (they are not expensive).

Why I say that. Cutting the story short, I received the refurbished replacement monitor last week from BenQ, straight away had bad vertical flickering experiencing (before it became worse), with my "initial" 2730Z.

However I couldn't test anything else with the 295X2 (has only mDP and a DVI) and when decided that I had to try the DVI and buy an mDP to DP cable, the scaller was gone and the monitor needed replacement.


However this time around I decided to try HDMI with the R9 Nano (flickering was there when received the monitor). With HDMI the screen was crystal clear, and no flickering. (Alas without Freesync)
So ordered a new DP cable which received today.

I put it on, and the screen is perfect, with Freesync on. If I put the cable that came with the BenQ monitor, it only works with Catalyst 15.6. Any other drivers and the screen is flickering badly, especially when Freesync is ON.
Same DP cable used on other non freesync monitor but generic, is fine, and has no issues both with Nvidia & AMD GPUs.

AMDMatt knows my complains about the various Catalyst drivers I have raised in here over the best part of 6 months, compared to the 15.6.

Apparently all issues were down to the cable supplied by BenQ, and possibly destroyed also the scaller needing a monitor replacement.

Matt, since you have access to more people than myself, and you have the time, have a look at it. It will save a lot of grievance to AMD who's not fault the flickering with the 2730Z especially, but to the cable supplied by the manufacturer.

Thanks Panos. If you spent some time searching through my posts @ OcuK or even the AMD forums, I'm forever telling people to use certified displayport 1.2 cables. There's a lot of junk DP cables floating round that often come with the display, i see situations like this every day in my job.

I'll check.

How to Choose a DisplayPort Cable, and Not Get a Bad One!
Display Port 1.2 Certified Cables.

Filter the search at the top for Cables.

We recommend people use only cables that are on the Display Port 1.2 certified cable list. Is your cable on there?

I'm currently using one of these, Accell UltraAV B142C-007B DisplayPort to DisplayPort 1.2 Cable with Latches (6.6 Feet / 2m) which is in the list.

Spoiler

I see yours has a minidp connection on one end. Since getting my 295x2 i needed an adapter too, so i again went with an Accell B112B-001B 10 Inches UltraAV Mini Display Port/DisplayPort(f) Adapter - Black pictured below. This is also on the certified list.

Spoiler

Spoiler

I don't have any of the issues you described, so this would be my first port of call.

 

[LtMatt]

@AMDMatt, mate. Accept my apologies, however £470 monitor that is Freesync, you expect the cable been the correct one. Of course a lot of ROG Swifts were shipped with the same cable (Amphenol E326508 ) and people were complaining about flickering with Gsync, especially at Asus and EVGA forums there are many posts!!!!!

And indeed I bought the Accell UltraAV B142C-007B (I have the mDP to DP version of it lurking around also for future use).

@GoogalyMoogaly, read the small prints on the cable and find it's manufacturer spec sheet. Mine was an Amphenol E326508 DP, 6ft also. Others had Accell 6ft DP1.0 or DP1.1 models (varied) in the box.

Which is insane given the cost of the monitor and what was designed to do.

Same monitor same manufacturer.

No worries and i understand. Unfortunately we have no control over what cables are shipped with monitors. It varies from vendor to vendor and as you have noted, they don't always ship the same type of cable. Consistency is a problem. Some have issues, some don't, but if you use a quality cable like Accell then the consistency is there and these types of issues are greatly reduced.

 

[LtMatt]

Hello AMDMatt, is there any ETA on when the core clock issues are going to be fixed at all?

i filled out a bug report as well to try and help out

i have the work around in place using AB which works fine.

I can't and won't give ETA's because things can change quickly, but we're working on it.

 

[LtMatt]

Been browsing the web for ~20mins using non-native 1080p 144Hz and kept seeing the whole screen flicker every now and again.

I then went to check this thread since this afternoon and experienced my first permanent black screen since getting monitor and R9 390 in November, I had to turn off PC and reboot to Windows 10 to get a picture again.

I've now set res to 1440p 144Hz and increased scaling to 150%.

The Benq supplied DP cable is indeed ""E326508 awm style 20276."

Maybe I should swap to HDMI cable?
Wasn't there something about Freesync working over HDMI now, in the most recent Crimson drivers?

It's coming, but it's not here yet. (HDMI FS)

Get the Accell DP 2 meter cable myself and Panos recommended. Fire and forget.

 

[LtMatt]

can anyone with crossfire on latest Crimson driver do me a favour please. Can you tell me what your 2nd card core and memory clocks are doing while on desktop? Mine 2nd card is now showing 0mhz core 0mhz mem when on desktop, my first cards is throttling to 300mhz core and 150mhz core as normal. But, I'm sure on previous drivers both cards would sit at those clocks when on desktop previously.

thanks

That's expected behaviour. Disable ULPS if you want the second GPU to sit at 300/150.

 

[LtMatt]

Matt, come on dude, you think I don't know how ULPS works and that I'd have it enabled running crossfire ULPS is disabled, it always is. This is what I can't understand.

Tried renabling it, disabled it, reinstalled it, still the same.

These Crimsons really have been the worst drivers for me in the last 12 months, pretty unimpressed with them to be honest. Just to many things causing annoying little issues revolving around crossfire.

And disabling ULPS in MSIAB.

Lol, that's your problem then Tony. MSI AB only disbales ULPS for GPU1. Use Trixxx instead to disable ULPS.

 

[LtMatt]

hmmm trixxx comes up with some interesting results when I google it

Checked "EnableULPS" in Registry, that was already disabled with a "0" so no idea why it's doing it.

Do you still run MSIAB alongside Trixxx Matt?

Trixxx is for disabling ULPS, MSI AB is for everything else. After ULPS is off Trixxx is exited and not used until i update drivers.

 

[LtMatt]

I've got a couple of programs that, when running, wake up my second GPU from it's ULPS slumber - specifically NZXT CAM and Creative Sound Blaster's Control Panel.

Is there any way in the AMD software to tell it to exclude these two and leave the GPU asleep for them? Pretty sure the answer's no, but thought it was worth an ask as even leaving them only in the system tray doesn't allow the GPU to sleep.

It's not a huge problem, just annoying when ULPS usually works very well in my setup.

System as in sig, and running Windows 10 64bit.

Not that I'm aware of unfortunately mate.

 

[LtMatt]

I wonder what the chances are for a crossfire profile for the new Tomb Raider next week lol.

You might be surprised.

 

[LtMatt]

I was of the understanding that the initial crimson release (and hotfix) was the last driver release for legacy gpus such as my 6450.

However the latest crimson drivers 16.1 are compatible with my card and I'm currently running them.

They were, but we felt that some bugs present in those drivers had to be fixed. Although pre GCN GPU's have generally reached peak optimisation, we may still release the odd driver to address critical issues on legacy products.

 

[LtMatt]

Can I ask AMD. As 16.1 is called a "hotfix" should you only download this if you are having problems and this hotfix addresses them? Should everyone else stay on 15.12? Or is the practice to always run the latest drivers, hotfix or regular?

16.1 Hotfix fixes some of the bigger issues of 15.12 so i would recommend to upgrade. If 15.12 works fine for you, then stick with it.

 

[LtMatt]

Looking a the techpowerup benchmark, the whole yesterday driver talk was a storm in a teaspoon.
The early german articles tested an early gane rev, TPU teszted the steam version:

Nice, that must be on 16.1.

Update on the next driver.

 

[LtMatt]

need this driver ASAP, sick and tired of seeing this on 16.1 Crimson. Not sure why GPUz is seeing the driver version as 15.8 as I'm on 16.1 but hey ho. Worst driver ever for crossfire.

Spoiler

Matt, come on dude, you think I don't know how ULPS works and that I'd have it enabled running crossfire ULPS is disabled, it always is. This is what I can't understand.

Tried renabling it, disabled it, reinstalled it, still the same.

These Crimsons really have been the worst drivers for me in the last 12 months, pretty unimpressed with them to be honest. Just to many things causing annoying little issues revolving around crossfire.

And disabling ULPS in MSIAB.

That's your problem then Tony. MSI AB only disbales ULPS for GPU1. Use Trixxx instead to disable ULPS.

 

[LtMatt]

AMD Radeon Software Crimson Edition 16.1.1 Hotfix


Hello everyone,

Click here to download the driver.


Highlights of AMD Catalyst™ 16.1.1 Beta Windows Driver

• Performance/Quality improvements and an AMD Crossfire™ profile is available for Rise of the Tomb Raider™
• An AMD Crossfire™ profile is available for Fallout 4

For detailed instructions on how to correctly uninstall or install the AMD Radeon Software Crimson Edition Drivers, please refer to the following support resources:

How-To Uninstall AMD Radeon Software Crimson Edition Drivers from a Windows® Based System
How-To Install AMD Radeon Software Crimson Edition Drivers on a Windows® Based System



Resolved Issues:
Assassin's Creed Syndicate - Building textures may be missing on some AMD Freesync™ displays with VSync enabled
Display corruption may occur on systems with multiple display systems when they have been left idle for some time
Mordheim: City of the Damned – some loading screens may be very dark
Star Wars™: Battlefront – The sky rendering may be corrupted in some situations
Radeon Settings – AMD OverDrive™ Power setting changes on the secondary GPU are not immediately displayed. This is seen only on dual GPU graphics cards, such as the AMD Radeon™ HD 7990 and Radeon™ R9 295x2
Radeon Settings - AMD OverDrive™ clock gauge needles for the secondary GPU may be in wrong position when the system is idle and the secondary GPU is inactive
Some games may experience brightness flickering with AMD FreeSync™ enabled
AMD Radeon Additional Settings window will close if the help button is pressed on Japanese/Korean language setups
Corruption seen in video playback for M2TS format files via Windows® 10 Movie & TV application
Flickering textures experienced in Dota 2 when accessing the "Heroes" menu
Battlefield Hardline – A crash may occur when changing graphics settings from "Ultra" to "High" during gameplay
The screen may turn dark and colors may be corrupted after installing the driver on some AMD Crossfire™ setups
Custom game profiles are reset to defaults after system is restarted
HDMI audio lost when monitor enters sleep mode and are woken up
Black line corruption seen all along the edges of characters and menus in Game of Thrones™



Known Issues:
Fallout 4 - Flickering may be experienced at various game locations with the v1.3 game update and with AMD Crossfire™ enabled. A temporary workaround is to disable AMD Crossfire™.
Far Cry 4 – Stuttering may be observed when launching the game with AMD Freesync™ and AMD Crossfire™ enabled. A temporary workaround is to disable either feature
Flickering may be observed while task switching with AMD Freesync™ enabled
Star Wars™: Battlefront - Some users may experience minor flickering or corruption at different game location or while viewing the in-game cinematics
A few game titles may fail to launch or crash if the Gaming Evolved overlay is enabled. A temporary workaround is to disable the AMD Gaming Evolved "In Game Overlay"
Star Wars™: Battlefront – Corrupted ground textures may be observed in the Survival of Hoth mission
Game stuttering may be experienced when running two AMD Radeon™ R9 295X2 graphics cards in AMD CrossFire™ mode
Assassin's Creed Syndicate – Corruption may be experienced if game is launched with AMD Freesync™ enabled. A temporary workaround is to disable AMD Freesync™
Fallout 4 – Foliage/water may ripple/stutter when game is launched in High/Ultra settings mode
Clock speeds may be seen to fluctuate during gaming on some AMD R9 Fury series products leading to poor performance and/or screen corruption
Just Cause 3 – Frame rates may be forced below 60 fps when VSync is enabled. A temporary workaround is to disable VSync for this game.
The AMD Overdrive™ memory clock slider does not show original clock values if memory speeds are overclocked
Fallout 4 –Thumbnails may flicker or disappear while scrolling the Perk levels page
Rise of the Tomb Raider™ – Game may intermittently crash or hang when launched with very high settings and AA is set to SMAA at 4K resolution
Rise of the Tomb Raider™ – Flickering may be experienced at various game locations when the game is left idle in AMD Crossfire™ mode under Windows 7. A temporary workaround is to restart the game or disable AMD Crossfire™
Star Wars™: Battlefront - Flickering seen on the textured bar on battle/tutorial loading screen



AMD Issue Reporting Form:
This driver release incorporates suggestions received through the AMD Issue Reporting Form. To provide us with your feedback, visit the AMD Issue Reporting Form.