AMD 16.9.2 Catalyst Drivers 9/21/16

t0adp1p3

t0adp1p3

New member
http://support.amd.com/en-us/kb-art...are-Crimson-Edition-16.9.2-Release-Notes.aspx

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.

AMD Radeon Software Crimson Edition 16.9.2 Driver for Windows® 10 64-bit
AMD Radeon Software Crimson Edition 16.9.2 Driver for Windows® 8.1 64-bit
AMD Radeon Software Crimson Edition 16.9.2 Driver for Windows® 7 64-bit
 
Last edited:
And in case you were wondering about this:
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:

FLACalculator_2016-09-21_16-44-58.png
 
I had the "application has stopped" issue occasionally, good to see that fixed
 
:hmm:
You were linked to this download from a site outside of AMD.com
Since we do not allow downloads through sites outside of AMD.com, please download your file directly from our site. We want to make sure you have the right driver for your device and operating system. Choose your product and operating system on the AMD Driver Download page or use the AMD Driver Autodetect to obtain the correct driver for your device.
Click to expand...



that's new
 
With the latest Fast build of Win10, I got a blue screen error upon rebooting after this driver installation, and had to reinstall from a backup. Anyone else see that?
 
I still get crashes in wattman, no big deal because I can just restart it but a little annoying.

Looks like the also increased # of dx11 drawcalls again for this driver
 
rms said:
With the latest Fast build of Win10, I got a blue screen error upon rebooting after this driver installation, and had to reinstall from a backup. Anyone else see that?
Click to expand...

Yeah, this windows build 14931 has the same garbage going on as some earlier builds, with SFC & DSIM failing, and bizarre display scaling bugs, and I can't get 16.9.2 to stop giving CRITICAL_PROCESS_DIED bluescreen errors on reboot, either after installing them after a 14931 install, or in the opposite order.

I did install 14931 using the Update service; next I'll try converting the .esd file to an ISO and attempting a clean install from that. If that fixes the 16.9.2 problem I'll report back in this thread
 
Cartel said:
non-whql but did they fix the extra long reboot time yet or add the desktop colors back?
Click to expand...


What exactly do you mean by extra long reboot? Did it boot longer when reboot than boot up from cold boot? Is that what you mean? I never had like that. Either reboot or boot up from cold boot just fine...pretty fast for me.
 
rms said:
...I did install Windows10 14931 using the Update service; next I'll try converting the .esd file to an ISO and attempting a clean install from that. If that fixes the 16.9.2 problem I'll report back in this thread
Click to expand...

I installed 14931 via a USB ISO, and successfully installed 16.9.2 over that. I am seeing a display scaling issue, where MIRC will be blown up at some huge resolution larger than native, when the monitor is switched off then back on. Not sure where the fault lies there, but it's annoying.
 
Higgy10 said:
ya was gonna ask that too.

What is the problem lordhawkwind? Ill gladly test if i can
Click to expand...

The last few drivers have broke free sync especially on the desktop after finishing a game. The screen goes a bit funny and the free sync counter is all over the place. Restarting fixes it until you finish gaming again. Spyre is aware of it and it was even posted as a known issue. The 16.7's were fine the 16.8's had it. Look at the posts especially 16.8.1
 
Interestingly, with these drivers I have for the first time noticed an issue with FRTC. It seems to be randomly causing hitching/input lag in games. Biggest offender is League of Legends

I have it set at 143 (I have a 144hz monitor) and it has been completely fine at limiting frames with no input lag or other issues in the past. I had actually pretty much forgot I even had it on, but now I have to alt-tab out and turn it off when the above issues pop up.
 
LordHawkwind said:
The last few drivers have broke free sync especially on the desktop after finishing a game. The screen goes a bit funny and the free sync counter is all over the place. Restarting fixes it until you finish gaming again. Spyre is aware of it and it was even posted as a known issue. The 16.7's were fine the 16.8's had it. Look at the posts especially 16.8.1
Click to expand...

what free sync counter? I have no issues with free sync (maybe it's a monitor defect, or the counter you speak of causing it?)
 
NWR_Midnight said:
what free sync counter? I have no issues with free sync (maybe it's a monitor defect, or the counter you speak of causing it?)
Click to expand...

When you switch on freesync in the drivers and your monitor all top end freesync monitors can display a counter in the top right hand of the screen that shows you the frame rate when free sync is working. It's a good indicator of how free sync is working and works well with games and benchmarks like heaven and the valley. In the desktop the counter should remain at your monitors refresh rate as in my case 144. With this bug the counter is all over the place and the screen flickers when free sync shouldn't be on! As I've said AMD have acknowledged it as a bug in some drivers so it's obviously not a monitor defect but a driver issue. Even Spyre has acknowledged it as such.

They need to fix it and when they do stop breaking it again in future driver releases.
 
You must log in or register to reply here.
Back
Top