Home › Graphics › mXDriver 16.6.2 (based on Radeon Crimson Edition 16.6.2)

mXDriver 16.6.2 (based on Radeon Crimson Edition 16.6.2)

Posted on by — 17 Comments ↓

AMD released Radeon Crimson 16.6.2 with minor fixes, for details please see AMD’s website.

mXDriver supports AMD Graphics powered Mac Pros (2013+). Retina iMac and MacBook Pro (2015+) support is currently experimental as I don’t have access to those machines. To see all supported GPUs please see listing below.

mXDriver 16.6.2 was made specifically for Mac users running Windows in a Boot Camp environment therefor mXDriver support for Non-Mac-Graphics is limited. Installing mXDriver on systems other than Apple systems is NOT RECOMMENDED.

As M395X users were still not able to install the previous drivers properly I made some minor adjustments to this driver release, hope that fixes these problems. If you have M395X Apple hardware and your keen enough you can test mXDriver 16.6.2, at you own risk of course. 😉

Currently supported GPUs by mXDriver:


Mac Pro

D300, D500, D700

iMac

M290X, M295X, M380, M390, M395, M395X (experimental)

MacBook Pro

M370X (experimental)

Please 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 installation your Windows needs to be in Testsigning Mode otherwise installation will fail!
For prerequisities and installation details please see the mXDriver Howto.

Download: mXDriver-16.6.2-64Bit-Win10

SHA1 Checksum: f9897b91e222bd5880fa187e0d0240ab611e0dab

17 comments on “mXDriver 16.6.2 (based on Radeon Crimson Edition 16.6.2)”

  1. Hello, I just wanted to report my findings with the R9 M370X. Driver installation completed, however the device manager shows: 7/15/2015 Microsoft Windows Hardware Compatibility Publisher.

    When trying to open Radeon Settings, I get the message to “Please try again after connecting AMD graphics.”

  2. Okay, it worked out. D700, installed without a hitch with Signature Driver Enforcement Disabled.
    AND it detects both cards as D700. It seems previously I had attached all my hardware IDs (meaning not rev specific ids as well) which created the mismatched card issue.
    Thanks!

    • Also, should say – I detected zero performance difference between both cards being ID’d as D700 and and one D700 and one 290x, so likely this is a purely cosmetic issue.

  3. Tried installing on iMac 5k with R9 M395X and it black screened and rebooted :-/ if there’s any way i can help with all this I’d be glad to!

    • I managed to get it to successfully install, and it ran amazingly, but as soon as I rebooted it have me black screen and I had to do a system restore :-/

      • Also I’d like to note that when it installs (rarely) it shows in device manager that it’s a FirePro 700, might be the problem?

      • Luckily a complete system restore is not necessary, you can boot Windows (10) in safe mode and do a driver rollback in the device manager. I also have an M395x and unfortunately the driver rollback is becoming a routine 🙁

      • Actually, I had the same problem. I solved it by unplugging/re-plugging the display thunderbolt cable. Done.

        • That’s quite a feat, considering that the iMac with M395X has builtin display and no display cable 🙂

    • And I cannot find any option to disable Crossfire on my D700s! Does anybody can disable it and where?

  5. Thanks so much for this!

    Followed the installation instructions and all works perfectly on my Mac Pro (D300s)

    Your work on this is much appreciated 🙂

    • Hi Joe, I really like to here when mXDriver helped somebody, have fun! 🙂

      • Turns out running in test signing mode is causing problems with multiplayer Arma 3. Battleye anti cheat will not launch which is required for online play.

        Could it be possible to run your modded driver without running test mode?

        Joe

Comments are closed.