mXDriver 17.6.1 is based on AMD’s Radeon Software Crimson ReLive Edition 17.6.1 and brings the usual optimizations from AMD (newly supported games and bugfixes) as well as improved support for Prey® and DiRT 4™. Vulkan support is also included and gives Doom a big fps boost. Please note: Newer versions of the Vulkan API (1.0.26+) don’t work with the Vulkan Stardust Demo although other applications like Doom work great in Vulkan mode.
If you have trouble running a Vulkan application, which ran with mXDriver 16.9.1 Reloaded (Vulkan API 1.0.21) or other older drivers please see the FAQ for help.
For a more detailed look into the changes of 17.6.1 please see the changelog.
KEEP IN MIND INSTALLING AND USING THE DRIVER IS AT YOUR OWN RISK! I AM NOT RESPONSIBLE FOR ANY DAMAGES! PLEASE BACKUP YOUR STUFF PRIOR INSTALLING THE DRIVER!
For prerequisities and installation details please see the mXDriver Howto.
SHA1 Checksum: 968b769a480270a5bc8692c0dd2324dcc90d6758
I don’t know why, but with these drivers I can’t change screen brightness anymore on my iMac 5K with M295X 🙁
Same Mac, same card, same drivers.
I didn’t experience the issue before, but now it’s stuck on maximum brightness.
The troubleshoot in the FAQ doesn’t work either: the KMD you’re told to search for is not there…
I can attest to this. 15 rMBP 2015 with M370X
Same here. iMac 5k M395X, lost brightness control. The registry key wasnt there, but I created it, rebooted and re-enabled video device, all to no avail.
MacBook pro with M370X, can not change screen brightness anymore
Does this driver bring support for legacy driver issues?
i have a laptop running windows 10 with an HD 7970m + 7660g and since amd dropped support for the 7660g my life has been a nightmare with flash application (can stream stuffs in fullscreen) performance drop in games etc…
17.6.1 works fine on COD IW–thanks Joe!
Mac Pro (2013)
Bootcamp: Win 10 v1703
Hey. I have downloaded and installed the driver, but now the Direct3D version is only Direct3D® Version
9.14.10.01261, meaning games like UNKNOWNPLAYER’S BATTLEGROUNDS will not open as requires Direct 11, which opened before I install this driver.
Is there an easy fix, or is this driver not compatible?
Did you end up find a fix? Have the same issue.
From what I can work out, Battleye is blocking aticfx64.dll from loading which intern gives you the DirectX Version 10 error. If I restart the Battleye service about 5 seconds after I launch PUBG then I can get the game to launch. Problem then is as soon as I try and connect to a server it get kicked out with a Battleye error. Don’t know if that helps you at all.
My problem is with the same file. It’s my belief that the file aticfx64.dll is a customized driver file (although under the same name as the standard driver files), which is why Battleye chooses to see it as a problem and block it outright. This problem exists outside of the control of our nice driver producer here and exists solely in the hands of the people at Battleye. People have found “temporary” fixes, that have very low (but varying) degrees of success, however, most do not work. In fact, many solutions that are suggested on forums and Battleye’s website can put your computer at MAJOR security risks, with very little chance of success.
In short, our only hope of getting the Battleye service to start functioning without blocking files is if Battleye specifically marks this file as safe. Seeing as Apple can’t even support their own drivers, my hopes are very low. So, you have 3 options: A) Wait for Battleye to support the file, B) Try one of the very risky solutions and pray for the best, or C) buy something not produced by Apple.
I’m currently looking into option C myself.
Or just use version 17.5.2 of the drivers.
If version 17.5.2 works and doesn’t get blocked, then it should more than suffice.
“The file aticfx64.dll,aticfx64.dll,aticfx64.dll,amdxc64.dll is not digitally signed, which means that it has not been tested by Microsoft’s Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo’d driver from the hardware manufacturer.”
Coming from dxdiag utilizing the run.exe. Despite having the Certificate signing the Driver files, that is more than likely why Battleye blocks the files. It does say on their website:
“Ensure that you don’t use any tweaked/custom versions of system files (including DirectX).”
and aticfx32.dll is a custom file of DirectX. This is the root cause of the problem, so any game that utilizes Battleye will be unplayable.
Hi there, after I have installed them 17.6.1 on Mac Pro d300 I have lost access to win 10 start button + search task bar, back to the previous version(17.5.2). The rest of the system worked fine. I have played Division from Ubisoft, I have checked integrity sys file no problems etc. But many thanks for all efforts and all you do for us.Best!
Any chance we will see support for the iMac with Radeon Pro 580? The driver that came with Bootcamp for the 580 Pro is 17.1.1!