Download AMD Radeon Software Crimson 16.8.1 driver

Published by

Click here to post a comment for Download AMD Radeon Software Crimson 16.8.1 driver on our message forum
https://forums.guru3d.com/data/avatars/m/238/238369.jpg
247 MB? what happened there... Anyway im gonna install later. Thanks!
https://forums.guru3d.com/data/avatars/m/263/263072.jpg
It's 246 MB here. 😀 Anyway, tnx for posting.
https://forums.guru3d.com/data/avatars/m/252/252615.jpg
Release Notes:
Radeon Software Crimson Edition 16.8.1 Highlights Support for: Radeon RX 470 Graphics Radeon RX 460 Graphics New AMD Crossfire profile available for: F1 2016 Fixed Issues Max memory overclock available on Radeon RX 480 being too low in Radeon WattMan has been resolved. Overwatch™ may experience an application crash on some Radeon™ RX 480 configurations when using AMD Crossfire technology mode. The Division poor Crossfire scaling may be experienced in some low resolution configurations when using AMD Crossfire technology mode. DOTA2™ may experience lower than expected performance when in AMD Crossfire mode. Radeon Settings may not report the correct Vulkan™ driver or API version information. Firefox™ may experience an application crash when hardware acceleration is enabled for content playback. Low frame rate or stutter may be experienced Wolfenstein®: The Old Blood™ on Radeon™ RX 480. Updating drivers through Radeon Settings may sometimes fail with an error message. Known Issues A few game titles may fail to launch or crash if the AMD Gaming Evolved overlay is enabled. A temporary workaround is to disable the AMD Gaming Evolved "In Game Overlay". Ark Survival Evolved™ may experience an error message when trying to launch the game in some configurations. DOTA2™ may experience an application hang when using the Vulkan™ API and changing resolution or game/quality settings. Corruption may be experienced in Rise of the Tomb Raider using the DirectX®12 API on some Hybrid Graphics configurations when performing a task switch. Shader Cache may remain be enabled when set to "off" in Radeon Settings on some Hybrid Graphics configurations. Radeon RX 480 graphics may experience intermittent stuttering in The Division™ when high game settings are used and vsync is enabled. Battlefield™ 4 may experience intermittent crashes when using Mantle. As a work around users are suggested to switch to DirectX®11. Radeon Pro Duo may experience a black screen in Total War™: Warhammer with the games API set to DirectX®12 and V-Sync enabled. World of Tanks™ may experience stuttering after performing a task switch in AMD Crossfire mode. Rocket League™ may experience flickering when in AMD Crossfire mode. Ashes of the Singularity™ may experience an application crash with "crazy" in game settings and Multi-GPU enabled. Package Contents The Radeon Software Crimson Edition 16.8.1 installation package contains the following: Radeon Software Crimson Edition 16.8.1 Driver Version 16.30.2511.
Source (at the bottom you can find all the download links):
https://forums.guru3d.com/data/avatars/m/259/259654.jpg
They compressed the installer more than usual. As for the driver DLL themselves, there is certainly a reduction, but nothing really big. Most of the total compressed packages are 50-150KB smaller. Seems like a lot of code cleanup to me.
https://forums.guru3d.com/data/avatars/m/258/258688.jpg
The Win10 14393.10 build (Anniversary build released to the public) is once again choking on the AMD 16.8.1 certificates and refusing to install/run them unless secure boot is turned off. It's kind of bizarre, because AMD had fixed the problem in the 16.7.3's, so I thought we were good to go from that point on--so I have dropped back to the 16,7.3's because I'd rather run secure boot than the latest hotfix drivers. Hopefully they'll get it ironed out permanently, eventually.
data/avatar/default/avatar11.webp
They compressed the installer more than usual. As for the driver DLL themselves, there is certainly a reduction, but nothing really big. Most of the total compressed packages are 50-150KB smaller. Seems like a lot of code cleanup to me.
I added some extra compression to the driver packager process, glad someone noticed at least 🙂
data/avatar/default/avatar29.webp
The Win10 14393.10 build (Anniversary build released to the public) is once again choking on the AMD 16.8.1 certificates and refusing to install/run them unless secure boot is turned off. It's kind of bizarre, because AMD had fixed the problem in the 16.7.3's, so I thought we were good to go from that point on--so I have dropped back to the 16,7.3's because I'd rather run secure boot than the latest hotfix drivers. Hopefully they'll get it ironed out permanently, eventually.
The 16.7.3 drivers were WHQL signed, these are not. Yes it will be sorted out later on since it requires extra certification by Microsoft even for none WHQL builds.
data/avatar/default/avatar18.webp
anybody know if AMD will be releasing the special Crimson "Omega" drivers this year? I thought they were going to be releasing these once a year...
https://forums.guru3d.com/data/avatars/m/250/250809.jpg
anybody know if AMD will be releasing the special Crimson "Omega" drivers this year? I thought they were going to be releasing these once a year...
Omega and Crimson were just certain points in the driver code that had huge changes / end of life for some products. AMD will be working hard on getting this new Crimson line rock steady before making any major moves.
https://forums.guru3d.com/data/avatars/m/209/209146.jpg
Nothing much between these and 16.7.3 for the Atiapfxx.blob dump, changes to Hitman and The Division crossfire profiles and Minecraft has the HighPerfGPU flag added.
https://forums.guru3d.com/data/avatars/m/238/238369.jpg
anybody know if AMD will be releasing the special Crimson "Omega" drivers this year? I thought they were going to be releasing these once a year...
End of the year.
https://forums.guru3d.com/data/avatars/m/226/226864.jpg
Drats, just like 16.7.3, these 16.8.1 drivers hang my 2x Radeon 7970M Windows 10 1607 (also 1511) system every time I try to restart/shutdown Windows (the circle just stops and the system is unresponsive). 🙁 16.7.2 still works fine.
https://forums.guru3d.com/data/avatars/m/252/252615.jpg
The Win10 14393.10 build (Anniversary build released to the public) is once again choking on the AMD 16.8.1 certificates and refusing to install/run them unless secure boot is turned off. It's kind of bizarre, because AMD had fixed the problem in the 16.7.3's, so I thought we were good to go from that point on--so I have dropped back to the 16,7.3's because I'd rather run secure boot than the latest hotfix drivers. Hopefully they'll get it ironed out permanently, eventually.
I've just bumped into this issue. Is there any workaround besides disabling secure boot? How about disabling driver signature enforcement? Would that be enough to bypass this thing? Thanks! EDIT: OK, so I gave disabling driver signature enforcement a go and, even though it appeared to have worked at first, I start getting the same error messages at the end of installation and after restarting Windows, I could see that the HDMI audio drivers weren't properly installed. I've rolled back to 16.7.3. I'll report this to AMD and Microsoft. Cheers!
https://forums.guru3d.com/data/avatars/m/265/265776.jpg
16.8.1 installed just fine for me w/o any signing issues, did an upgrade install. Not sure what's going on with others. If there was a bad cert, it would be affecting anyone with AU installed.
https://forums.guru3d.com/data/avatars/m/251/251189.jpg
Nope, Microsoft introduced W10 Redstone changes for the driver signing really only for fresh installations, upgrade installations are excluded. Also other drivers like the one of cFosSpeed are affected. Current workaround is to disable SecureBoot until the programs come with drivers which meet the new signing requirements.
https://forums.guru3d.com/data/avatars/m/220/220734.jpg
Nope, Microsoft introduced W10 Redstone changes for the driver signing really only for fresh installations, upgrade installations are excluded. Also other drivers like the one of cFosSpeed are affected. Current workaround is to disable SecureBoot until the programs come with drivers which meet the new signing requirements.
Upgrade build here and still the same issues. It's with all versions, what seems to be happening is if you have not restarted your PC since the install of the latest build, it will install without any issues, but as soon as you reboot, it will give you trouble. Not sure why it doesn't happen all the time.
https://forums.guru3d.com/data/avatars/m/259/259654.jpg
I added some extra compression to the driver packager process, glad someone noticed at least 🙂
Haha, nice. It confuses me too, since I usually connect size changes to code changes 😀
data/avatar/default/avatar26.webp
As an update the Redstone issue is being fixed at the moment. If anyone has any issues with Freesync the workaround would be to enable GPU scaling that is also being looked at too along with some other issues.
https://forums.guru3d.com/data/avatars/m/218/218722.jpg
WattMan still crashes randomly with this.