http://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-Edition-16.9.2-Release-Notes.aspx

nice

Thanks! Downloading...

Cant Find download link? lol? I only see 16.9.1...

Still, idle clocks bug on 7970 and the report page doesn't load.

Fixed Issues Small amounts of stutter may be experienced when playing or watching cinematic videos in Deus Ex™: Mankind Divided when using AMD CrossFire mode and DirectX®11. uhm no, lol jeez it's awful: http://www.the9quad.com/images/2016/09/21/FLACalculator_2016-09-21_16-44-58.png

AlleyViper Still, idle clocks bug on 7970

So "ditch your gcn 1.0 cards" bug is still there 🙂

F*ck that. We should seriously Twitterbomb them. They will have to at least acknowledge something then. I just asked @CatalystMaker.

Hmm.. My PC keeps hanging during the installation although I can update the driver through device manager. Anyone else experiencing this?

Disconect from network,unplug the cable of your network. Enter in Safe Mode and uninstall the old driver (or else ) with DDU.Use CCleaner,Tuneup Registry cleaner (or else) to clean the registry.Restart. Enter in normal Windows and install the new driver.Restart. Plug the network cable. Enjoy gaming.

F*ck that. We should seriously Twitterbomb them. They will have to at least acknowledge something then. I just asked @CatalystMaker.

Tweet them all together at once, catalystmaker rarely answers... @JonasBeckman Did u examine this Driver? 🤓

I just woke up about a hour ago (The time difference between whenever and here in Sweden usually means driver releases happen a bit after midnight.) but once these are installed I'll do the usual "atiapfxx.exe -r -sys -s test.xml" dump and comparison with 16.9.1-September 13 (Will dump a test.xml file in the syswow or what it was called folder which I then just do a quick comparison with against the previous dump.) EDIT: Also copied over the Vulkan 1.0.26.0 runtime from the Nvidia driver, could take it from the SDK itself but the Nvidia driver was easily extracted with just Winrar instead of having to install a full SDK. :P (Likely won't do much and I only really have two Vulkan games those being Talos Principle and DOOM-4 and none of those would be using the newer SDK, DOOM in particular hasn't had a patch in weeks now so I guess they're either OK with how it works or they're waiting on further DLC content before patching the game again.) EDIT: This was added-> FreeSync (OpenGL freesync support?) Crossfire profile flag changes-> Battleborn Obduction Battle Field 1 (Yeah that's how it's named.) Deus Ex: Mankind Divided F1_2016 Civilization 6 Crossfire profile flag additions-> Dreadnought OpenGL profile additions-> Euro Truck Simulator 2 (?) 0x0804A021 0x00103010 0x00000040 0x04000000 0x00200000 0x00040000 OpenGL profile changes-> False Added to the profiles for Cinnamon, Compiz, Steamcompmgr, Nautilus, Unitygreeter, Metacity, Kwin and GnomeShell (Developer software?) Company of Heroes 2 had two caps added. 0x08008001 0x00841000 (Not exactly sure what MC stands for and I have no idea what the hex value means.) Talos Principle had changes to it's existing MCCaps1 and MCCaps3 flags. DIDE had a profile added (Dead Rising Definitive Edition?) Tomb Raider had a profile added (Rise of the Tomb Raider or Tomb Raider 2013?) That's about it, further down in the .xml there's additions linking these profiles to actual exe names such as Dreadnought being linked to DreadGame-Win64-Shipping.exe which should make it a UE4 game as those usually follow that naming schedule by default. No major changes but the Crossfire flag changes might help with either performance or compatibility (Or both?) for the games they're for although in the case of Deus Ex Mankind Divided I don't know if it'll help for DirectX 12 or if that's now in the hands of the developers when working with this lower-level API. (Might be what is making multi-GPU support lag behind for AMD and Nvidia GPU's in D3D12 if so, can imagine that supporting SLI is different from Crossfire even if the API might help streamline things a bit by standardizing some of this.) OpenGL freesync should be useful too if that isn't already supported, particularly for Linux and well there's a few Windows games using OpenGL over Direct3D also with DOOM(4) being the most recent though AMD's not-quite-stellar OpenGL support makes Vulkan a more attractive choice for that game. 😀 (And unlike DirectX 12 Vulkan isn't tied down to a particular OS either.)

Idle bug still here, got stuck in only couple of min after installing these. Still, tried quite a few games, no problems and everything runs great. Performance clocks works just fine.

F*ck that. We should seriously Twitterbomb them. They will have to at least acknowledge something then. I just asked @CatalystMaker.

Tbf, I don't even know how you guys are having issues, it was solved for me many months ago :/

The issue I was having with the new drivers not recognizing the Club3D 4k60hz adapter on 4K@60hz TVs, has a solution. For people having the same problem as myself with the new 16.9.x drivers (probably very few people here, but I thought I would just mention it anyways), you now have to make sure that you TV is in UHD HDMI deep color mode, in previous driver activating this mode rendered the adapter useless. So i'm guessing AMD must have changed something regarding the chroma with the new drivers.

Fallout New Vegas still crashes to desktop :\

How's the Rise of the Tomb Raider performance? 🙂

Fallout New Vegas still crashes to desktop :\

Won't bother installing this set then, I'll wait till they fix it. :|

Won't bother installing this set then, I'll wait till they fix it. :|

You have a different card...i have no problem on my 380.

You have a different card...i have no problem on my 380.

Tried the new drivers, both Fallout and Fallout:NV still crash. Are you running Windows 10?

Fallout is living up to it's name, falling out straight back to the desktop! Are you sure he issue is driver related, and not system? Some overclocks can cause instability with different drivers, as the drivers can use the card in different ways. It doesn't mean your card or system was 'perfectly stable' with the overclock on older drivers, it just means the unstable part of the graphics card was likely underutilised and newer drivers manage to trip the overclock instability.

It is caused by an access violation (ie: bad pointers value) of a Direct3D 9 call related to the adapter (the graphics card). I checked it with the VS debugger. So it is a driver or a runtime bug (maybe caused by WDDM 2.1, but I am not aware of any changes related to the legacy Direct3D 9 presentation subsystem under the latest WDDM. 16.8 branch drivers works fine..