Radeon Software Crimson Edition 16.9.2 Release Notes

cageymaru

Fully [H]
Joined
Apr 10, 2003
Messages
22,092
Radeon Software Crimson Edition 16.9.2 Release Notes
Radeon Software Crimson Edition 16.9.2 Release Notes

Article Number: RN-WIN-RADEONCRIMSON16.9.2
Radeon Software Crimson Edition is AMD's revolutionary new graphics software that delivers redesigned functionality, supercharged graphics performance, remarkable new features, and innovation that redefines the overall user experience. Every Radeon Software release strives to deliver new features, better performance and stability improvements.

Radeon Software Crimson Edition 16.9.2 Highlights

Support For:

  • Forza Horizon 3™
New AMD CrossFire profile added for DirectX® 11:

  • Dreadnought
Fixed Issues

  • Intermittent mouse cursor corruption may be experienced on some Radeon RX 400 Series graphics products.
  • Flickering display may be experienced on portrait Eyefinity display configurations when launching or exiting DirectX®12 applications.
  • Ashes of the Singularity™ may experience an application crash when Multi-GPU is enabled in DirectX®12.
  • Upgrading from a previous Radeon Software Crimson Edition version may cause user settings in Radeon Settings to reset to defaults.
  • Intermittent crash may be experienced in Mozilla Firefox while doing video playback on some Radeon RX 400 Series graphics products.
  • Radeon Settings may sometimes experience an "application has stopped" error after modifying game profiles on Windows 10 Anniversary Addition.
  • A small amount of corruption may be experienced in the lower right hand corner of the display on some Radeon HD 7000 series products when playing Deus Ex™: Mankind Divided.
  • 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.
  • HDMI® Audio may be lost after resuming from standby on Windows 10 Anniversary Edition.
  • Flickering may be experienced in Rocket League on Radeon RX 400 Series graphics products when running in AMD CrossFire mode.
Known Issues

  • A few game titles may fail to launch, experience performance issues or crash if the third party application "Raptr" has its game overlay enabled. A workaround is to disable the overlay if this is experienced.
  • Counter-Strike™: Global Offensive may experience intermittent stutter on Radeon R9 380 Series graphics products in AMD CrossFire mode.
  • Rise of the Tomb Raider may experience an application crash when changing the resolution from in-game menus when running DirectX®12. Users can restart the game to complete the resolution change.
  • OpenCL™ version information may display incorrectly or may display random characters in Radeon Settings.
  • Radeon RX 460 may fail to resume from sleep mode and require a system restart when connected through AMD XConnect™ Technology.
  • While using or having Radeon WattMan open in Radeon Settings while in AMD CrossFire mode, the secondary/slave GPU clocks will increase to their highest state.
  • Overwatch™ may experience flickering character models while in the hero selection menu or during gameplay in AMD Crossfire mode.
  • Paragon may experience flickering while using AMD FreeSync technology and AMD CrossFire mode in conjunction.
  • Dreadnought™ may experience minor flickering in game menus or gameplay while using AMD FreeSync technology.
Package Contents
The Radeon Software Crimson Edition 16.9.2 installation package contains the following:

  • Radeon Software Crimson Edition 16.9.2 Driver Version 16.40.2311
The Radeon Software Crimson Edition 16.9.2 installation package can be downloaded from the following links:


Installing Radeon Software Crimson Edition 16.9.2

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

 
you know... When you actually look at the known issues they are quite specific and not really game breaking. I mean for me and my 290 not one impacts me.
 
A big known issue that they haven't resolved yet =
> AMD CCC restores Mem/Core overclocks on boot but doesn't restore voltage resulting in a black screen if you are doing a memory overclock which requries overvoltage to boot up.

I can't run my card pas 1300 because of this and there is no workaround.
 
A big known issue that they haven't resolved yet =
> AMD CCC restores Mem/Core overclocks on boot but doesn't restore voltage resulting in a black screen if you are doing a memory overclock which requries overvoltage to boot up.

I can't run my card pas 1300 because of this and there is no workaround.
I just run my boot clocks at stock volts and load in my higher voltage profile as needed using MSI afterburner.
 
I just run my boot clocks at stock volts and load in my higher voltage profile as needed using MSI afterburner.
if i restart with those higher clocks applied, it automatically applies them at boot, even if i have afterburner uninstalled
 
  • Intermittent crash may be experienced in Mozilla Firefox while doing video playback on some Radeon RX 400 Series graphics products.
So glad that they fixed this one. I posted it on Reddit and they released the drivers about a week or so later. :)
 
My crossfire 290x setup crashes everytimeI launch a DX11 game with any 16.9.x series driver. Sometimes a stupid message appears that "WattMan restored my default power settings." WTF?! Just stock clocks here - no overclock or voltage adjustments. I thought WattMan was only supposed to come up on the 400 series anyway?
 
My crossfire 290x setup crashes everytimeI launch a DX11 game with any 16.9.x series driver. Sometimes a stupid message appears that "WattMan restored my default power settings." WTF?! Just stock clocks here - no overclock or voltage adjustments. I thought WattMan was only supposed to come up on the 400 series anyway?


Sounds like you need to run DDU.
 
A big known issue that they haven't resolved yet =
> AMD CCC restores Mem/Core overclocks on boot but doesn't restore voltage resulting in a black screen if you are doing a memory overclock which requries overvoltage to boot up.

I can't run my card pas 1300 because of this and there is no workaround.

There is a workaround.
Either install the latest version of MSI afterburner which deletes the regkey which loads the last applied clocks, or delete the key manually after applying clocks.

REG DELETE HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000 /v PP_CNEscapeInput /f

The key which holds the "stored" RAM and GPU clocks is PP_CNEscapeInput
 
There is a workaround.
Either install the latest version of MSI afterburner which deletes the regkey which loads the last applied clocks, or delete the key manually after applying clocks.

REG DELETE HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000 /v PP_CNEscapeInput /f

The key which holds the "stored" RAM and GPU clocks is PP_CNEscapeInput

I will try this when i get home, thanks
 
There is a workaround.
Either install the latest version of MSI afterburner which deletes the regkey which loads the last applied clocks, or delete the key manually after applying clocks.

REG DELETE HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000 /v PP_CNEscapeInput /f

The key which holds the "stored" RAM and GPU clocks is PP_CNEscapeInput

Is there any option that i need to enable in afterburner or does it do it by default?
 
there's a new tick-box at the very bottom of the settings panel in beta 14.
 
there's a new tick-box at the very bottom of the settings panel in beta 14.
There is a workaround.
Either install the latest version of MSI afterburner which deletes the regkey which loads the last applied clocks, or delete the key manually after applying clocks.

REG DELETE HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000 /v PP_CNEscapeInput /f

The key which holds the "stored" RAM and GPU clocks is PP_CNEscapeInput

Thanks,
The beta 14 works well. Finally solved this problem.
FUCK AMD for shitty software tho.
 
Sounds like you need to run DDU.

I always do a clean install. Tried you way anyway and it didn't work. Still getting a message saying general wattman settings restored after system failure. Going back to 16.8.3.
 
The Windows 10 Anniversary update hosed my PC. What I ended up doing was looking on Microsoft's website and grabbing the latest ISO that already has the Anniversary Edition patched in. Reinstalled Windows 10 and now everything works. It hosed Digital Foundry's Win 10 install also, and you can hear them talk about it in this video at the 3:50 section.

 
Back
Top