I just updated to Windows 10 which has installed Radeon Crimson driver v15.11. However, the Radeon Settings Utility finds WHQL driver 16.3.2. There is also the non-WHQL Crimson v6.6.1 Hotfix driver on AMD's web site which I had problems with in Windows 8.1.
Have people found WHQL driver v16.3.2 to be reliable or am I better off sticking with the older v15.11 driver Windows 10 has decided to install?
I have v16.5.3 with hot fix on my R7 260 and is working perfectly.
Thanks. v16.5.3 shows up as non-WHQL from AMD's web site. I think I'll use WHQL v 16.3.2 first and see how that goes.
16.5.3 was released as "Hot fix" only for some games that had troubles with earlier versions, not much in it for others.Thanks. v16.5.3 shows up as non-WHQL from AMD's web site. I think I'll use WHQL v 16.3.2 first and see how that goes.
What does Hot Fix mean when they release the drivers? I see the regular driver download and under that I see another download but says Hot Fix. Not sure what that means. Thanks16.5.3 was released as "Hot fix" only for some games that had troubles with earlier versions, not much in it for others.
Hotfix drivers will contain either or both game or bug fixes without having gone through the WHQL process.
As far as WHQL goes to many get hung up on whether the driver is or not. There are also quite a few that believe that Microsoft does extensive testing on drivers in order for them to be WHQL. That couldn't be further from the truth. In order for a driver to be called WHQL it is up to the hardware manufacture to use this,
Windows HLK downloads - Windows Hardware Dev Center
and do the testing themselves, and the submit the log(s) to Microsoft for verification.
Some also confuse WHQL with a driver being digitally signed. A driver can be both non-WHQL and digitally signed,
What is a signed driver?
Thanks, I usually just download the main driver and have had no problems at all. Just wondered what Hot Fix meant.Hotfix drivers will contain either or both game or bug fixes without having gone through the WHQL process.
As far as WHQL goes to many get hung up on whether the driver is or not. There are also quite a few that believe that Microsoft does extensive testing on drivers in order for them to be WHQL. That couldn't be further from the truth. In order for a driver to be called WHQL it is up to the hardware manufacture to use this,
Windows HLK downloads - Windows Hardware Dev Center
and do the testing themselves, and the submit the log(s) to Microsoft for verification.
Some also confuse WHQL with a driver being digitally signed. A driver can be both non-WHQL and digitally signed,
What is a signed driver?
