Download AMD Radeon Software Crimson 16.8.1 driver
Click here to post a comment for Download AMD Radeon Software Crimson 16.8.1 driver on our message forum
LocoDiceGR
247 MB? what happened there...
Anyway im gonna install later.
Thanks!
srdjan1995
It's 246 MB here. đ Anyway, tnx for posting.
Jackalito
Release Notes:
Source (at the bottom you can find all the download links):
PrMinisterGR
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.
waltc3
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.
spyre
spyre
holler
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...
FunkyMike
JonasBeckman
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.
LocoDiceGR
Cave Waverider
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.
Jackalito
Chastity
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.
aufkrawall2
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.
KyleStilkey
aufkrawall2
Microsoft say it's related to fresh Redstone installations:
https://blogs.msdn.microsoft.com/windows_hardware_certification/2016/07/26/driver-signing-changes-in-windows-10-version-1607/
Which is exactly my experience with CfosSpeed.
PrMinisterGR
spyre
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.
asder00
WattMan still crashes randomly with this.