mXDriver 16.6.1 (based on AMD Radeon Software Crimson Edition 16.6.1)

40 comments on “mXDriver 16.6.1 (based on AMD Radeon Software Crimson Edition 16.6.1)”

1. I just installed this and it works perfectly. Thanks so much for posting this!!

   • Glad to hear that! What GPU do you have?

     • Mac Pro Tower with D300s. The basic model. Although this morning The driver is acting weird. It won’t launch Radeon Settings for some reason.

       • I am consistently getting an error message now when I try to launch Radeon Settings. I thought a reboot might fix it, but alas no.

         “Radeon Settings are currently not available. Please try again after connecting AMD graphics.”

         I just checked the device manager and it shows the display adapters are looking for drivers. Do I need to leave “bcdedit.exe -set nointegritychecks on” in the command prompt? I turned it off after the initial install.

         • I also re-enabled “bcdedit.exe -set testsigning on”, re-booted and this resolved my issue. Is my system vulnerable if I leave these settings on? Thx.

         • If Testsigning is on you can install drivers which are not signed, meaning you can install drivers from ANY source. This isn’t a problem as long as you don’t install a driver which includes malware, which you normally don’t know prior installing it. :-/
           So, yes Testsigning disabled makes your computer a bit more secure, but only a bit, as also the bad guys can sign theirs drivers.

           It’s up to you what to do. For mXDriver there is no extra software included and of course no malware! I download the original driver at AMDs website and adjust it to run on the newer Macs.

2. the crossfire still doesnt work well for The Division, the ftps keep drop and lag after playing over 30mins

3. Corssfire never worked that great for me, also on Non-Mac-Machines. I think AMD needs more adjusting the driver for The Division.

4. This didn’t work for me. I have a late 2015 iMac with the AMD R9 M395X GPU. I have the final installer screen shot and Report log file. Email me and I can send these files to you. I’d like to assist in getting this working on my iMac if possible.

   • Hi Ron, please send the files to [email protected]. Thank you mate!

     • I sent you the files – let me know if you didn’t get them.

       • Hi Ron, thanks for the files, I received them and took a look at them. Unfortunetaly the XML file does not have any information which could be helpful to hunt down the issue. :-/
         I think I really need to get my hands on a M395X.

         • Oh well, it was worth a try. Maybe Apple can get their act together and release a updated display driver. But that may be hoping for too much. 🙁

   • Same for me on M395. Installs fine. Actually works fine until reboot. Event log typically shows about a device failure with AMD’s kernel driver.

     • The M395 is a tricky one, as long as I don’t have any hardware or at least logfiles I could not do much, sorry.

       • I will get you any log files that you need. Just tell me what to send you.

         • Hi Josh,

           if you like you can send me this logfile: C:\Windows\INF\setupapi.dev.log

           That could help, if I need anything more I will respond to you. Please send them to [email protected].

           Thanks.
           Joe

   • Same issue with same card and imac 395x. Amd says it’s apples fault apple support says it’s Amd fault. Go figure. I would gladly pay for a solution

     • It really sucks because there are so many games that play like garbage due to optimization. The Division, Quantum Break, etc… I actually got like a 100% increase in fps when I got mxdriver working before rebooting.

     • My next step is to get a code-signing certificate which should solve the need for enabling testsigning mode, maybe this could help a bit.

5. I just installed on the 2013 MacPro with the D500s and the firepro drivers installed with driver signing disabled and clearing out old AMD with DD but they both have exclamation points. Any suggestions?

6. I got it to work! My only issue now is severe flickering in Overwatch in Crossfire mode. Does anyone have settings?

   • I also have problems with Crossfire mode enabled, best is to disable it.

7. I am working with a macpro and D700. The last driver (16.6.1) works fine with cross fire option in off position. Testsigning mode on. I am using 3 monitors.

   I hopefully good hint. Check this out: http://www.iobit.com/en/driver-booster.php

   It´s free and you will find out that most of the 6.0 bootcamp drivers for win10 are out of date. There is a roll back possibility inside the software.

8. Can’t find the right INF file that contains the R9 M370x driver

   • You don’t need to look for INF files you can go with the Setup program.

9. Thanks and the driver works fine. But there is one problem, I cannot find crossfire setting in the FirePro advanced setting. I have tested the performance is crossfired. Is there any possible to bring this option back? My system is MacPro with d500. Thanks.

10. Works great on nMP with d700. Thank you!

11. Tried your driver, didn’t let me install it. During the install, after I got a slightly different driver install override window than usual it said it can’t install because no supported product was found. Installation finished but no driver.
    So I download the 16.6.1 driver myself and mod it myself and it installs just fine.

    I have a question though: I’m on the dual FirePro D700. After install it is detected as D700 and R9 200 series (Linked). My question is this:
    Could the mismatch itself cause performance issues (as opposed to if both cards were detected as D700)? Does that mean that each card is being interpreted differently and thus used differently by the driver?

    Thanks

    • What device ids got your dual D700? Mine installs just fine as dual D700 with mXDriver.

12. Hi, the drivers seem to have installed fine, but the control pannel doesnt appear when right click on the desktop… any idea?… I have a Mac Pro with dual D700.

13. Any updates on the M395x? I have a late iMac 5k that cannot accept the new Bootcamp driver. My current driver is from Feb 2016. Its really annoying to of spent all this money on a machine that has such bad bootcamp driver support.

    • Hi Dave,

      I looked once more into the M395X issues and compared parts of Apple’s official driver with Radeon Crimson 16.6.2. I found one difference and adjusted mXDriver 16.6.2 accordingly.
      I hope that helps but I am unsure. I cannot test if mXDriver is working for M395X as I don’t have any access to M395X machines.

      • Would a teamviewer session help? I wouldn’t mind offering you my machine for a bit (supervised of course) and you could take a look around?

        • David – Have you tried the newly updated driver installer yet, and did it work on your M395X?

        • Hi David,

          if you like you can send me this logfile: C:\Windows\INF\setupapi.dev.log

          That could help, if I need anything more I will respond to you. Please send them to [email protected].

          Thanks.
          Joe

          • I’ve emailed the log file, I also tried installing the driver just released (16.7.1) it installed first time without issue and when I rebooted I got the black screen again :-/ I’ll send over the updated log

          • Thanks for the log files, David. I checked them but didn’t find any helpful information. I am currently not sure if there are logs with better information about the Radeon driver installation. Does anybody have an idea?

      • Hi Joe – I’ll give your mXDriver another shot now that you made a change. But just to confirm, you modified the 16.6.2 package, and not the 16.5.3 package?

        • Hi Ron, yes I meant 16.6.2 but as it seems now the adjustments don’t make any difference. :-/

Comments are closed.