Download Radeon Software Crimson 16.6.1 drivers

#5285293 Posted on: 06/07/2016 05:14 AM

---

Yeah I'm guessing its an Insider Preview issue. I've been using the build for so long I honestly forgot I was even running a beta, heh.

#5285310 Posted on: 06/07/2016 06:13 AM

---

I used to be on fast ring till MS pushed something what I could not get to work.
There were huge redraw issues on desktop with driver present.
After about minute or so on desktop, OS become unusable due to that.
So, I did reinstall and moved to slow ring.

#5285314 Posted on: 06/07/2016 06:35 AM

---

EDIT:

Fixed the issue in this post already by completely uninstalling 3DMark and Installing it again, then installing Firestrike & API Overhead Test again. I'll leave it here though in case anyone needs to know. I assume it happened after the major update to 3DMark in April and change of UI, maybe some files carried over that caused the result page to continuously crash after the API Test.

Okay guys I have to ask, for the last month or two I cannot get 3DMark API Test to show me the results.

So after every driver update, I run Firestrike, look at the results, then go and run the API Overhead test and get the result.

But with the last 3 or 4 drivers, I get the Firestrike result, then 3DMark just hangs (program does not respond) after the API Overhead tests are finished. So it goes to the result page, it hangs, and then just stays like that. I cannot exit 3DMark because it just stops responding.

Everything else works fine btw, I have no issues with any game or anything. Including with all OTHER 3Dmark tests and their results. Just the API Overhead test causes a hang in 3DMark after it's finished.

I verified the integrity of application cache (file check-up) using Steam and there's no files missing or anything. No issues. So I don't know what's causing the program to stop responding indefinitely after finishing the API Overhead test successfully.

#5285331 Posted on: 06/07/2016 07:38 AM

---

I do. Even after updating to a new Win10 Insider build, which fixed my issue when installing older drivers, it still won't install this one.

Edit: After updating to the new W10 build, something did change tho.
Before, if I tried to manually install the drivers with Device Manager, it would tell me that any driver I had before was better/more recent than 16.6.1.
After the new build, installing the drivers manually worked and Radeon Settings would show as 16.6.1.
BUT.
Once I rebooted, Windows act as if I have no AMD drivers present (Radeon Settings too). If I open Device Manager, I still see the drivers installed, but with a warning on them saying "blabla drivers unsigned blabla".
Disabling + Enabling the driver again brings it back as active, but a few options are then missing from Radeon Settings.
Overall, not worth the hassle unless this driver is AMAZING.

Same, I don't know what's changed but I'll keep everyone posted if a driver update fixes it or if it's a Windows Insider issue with the latest fast ring build.

I'm going with a driver issue as none of the other drivers have had any issues installing but these. I kept getting a Unable to detect Devices and it would close. Looking into this further they updated the atdcm64a.sys and replacing it (with a older driver set) under the Bin64 folder under the driver folder fixes the detection issue and allows for your to install everything like normal, but you still get the driver signature issue as mentioned.

Only reason I'll be going with these drivers is it fixes a major issue I was having which is when Video plays in a web browser it causes the screen to have major corruption problems.

#5285366 Posted on: 06/07/2016 09:33 AM

---

Rise of the Tomb Raider Crossfire profile was altered.

Same with Paragon

Same with Mirror's Edge Catalyst


A new Crossfire profile for Dark Souls 3


A new profile for 3D Mark Time Spy