Home › Graphics › Radeon Crimson 16.5.2.1 released – mXDriver updated to version 16.5.2.1

Radeon Crimson 16.5.2.1 released – mXDriver updated to version 16.5.2.1

Posted on by — 13 Comments ↓

AMD released Radeon Crimson 16.5.2.1 yesterday with improved support for Doom running on R9 M390 systems! For details please see AMDs website.

mXDriver supports AMD Graphics powered Mac Pros (2013+), Retina iMacs and MacBook Pros (2015+). To see all supported GPUs please see listing below.

mXDriver also supports all the GPUs which the original Radeon Crimson 16.5.2.1 supports out of the box. So beside your Apple specific AMD GPUs the driver is also suitable for newer AMD PC GPUs.

Currently supported GPUs by mXDriver:


Mac Pro

D300, D500, D700

iMac

M290X, M295X, M380, M390, M395, M395X

MacBook Pro

M370X

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.5.2.1-64Bit-Win10-Win8.1-Win7

SHA1 Checksum: 8273efbcca6964c5d42502e05b04922423cbd137

13 comments on “Radeon Crimson 16.5.2.1 released – mXDriver updated to version 16.5.2.1”

  1. During installation the Imac crashes with a colourful display. (M390)
    any suggestions? tried everything like described

    • As AMD made some adjustments to R9 M390 in 16.5.2.1 you could try 16.5.2 and see if it does a better job at installation.

      Which OS do you have? Did you properly uninstall old graphics driver via DDU?

  2. windows 8.1, and I did uninstall via DDU before. 16.5.2 doesn´t work either 🙁
    already tried so many things, but it keeps crashing in wild coloures.
    thanks for your work, if someone has an Idea how to solve the problem, it would be great

    • I am sorry the driver isn’t working for you. 🙁

      There is at least one more person which has problems with R9 M390. I will look into this issue tomorrow once more. Currently I don’t know if it’s a problem of the modification or if the driver isn’t able to support R9 M390 Mac graphics.

    • The R9 M390 seems to have two different Device IDs (DEV_6819&SUBSYS_0139106B and DEV_6819&SUBSYS_014E106B), but until mXDriver 15.2.1 there was only one Device ID (DEV_6819&SUBSYS_014E106B) handled. If you have a R9 M390 with SUBSYS_0139106B you could try out mXDriver 16.5.3 if you like. Hope that eliminates your problems.

  3. Is there a way to turn on crossfire, I have just installed the 16.5.2.1 driver and have been looking for an option to enable crossfire. Using Firepro D700 on Mac Pro 2013. Thank you for the drive, otherwise working flawlessly and absolutely wonderful. Thank you

    • Glad you like it! 🙂
      I also miss the Crossfire enable/disable section in 16.5.2.1, it seems to be missing. This change was not made by me so it might be a bug on AMD’s side.
      As far as I analyzed it it seems like Crossfire is enabled right from the start as GPU-Z shows it is enabled. But I need to disable it for some applications/games (e.g. World of Warships).
      Maybe someone knows how to disable it without AMD’s menu?

  4. Dear Sir,

    I’m using Macpro late 2013 with D500, with windows 10, I tried to clean install windows 10, straight away to install the provided 16.5.2.1, and also tried to use Guru3D’s display uninstaller to uninstall bootcamp provided amd display driver, and turn on Testmode before install the driver.
    Unfortunately, the 16.5.2.1 seems not ‘installed’, means there is no radeon setting control panel, would anyone using D500 also having this similar problem?
    Thanks.

    • Same problem with D700. Tried many times, will not take. Once I got the actual driver to show in properties but nothing else worked and there were no AMD control panels etc.

      • Hi Patrick, hi G.C.,

        I had similar problems once they happened because I didn’t disable the integritychecks and activated Test Signing Mode.

        Activate Testsigning via command line: bcdedit.exe -set testsigning on
        Disable Driver Signature Enforcement via command line: bcdedit.exe -set nointegritychecks on

        If you already did that a fallback would be to go with the slightly older official Boot Camp drivers from AMD: https://www.mxdriver.com/amd-releases-new-boot-camp-driver-version-15-301/

        • Thanks for the attempted help. I did both testsigning and Signature disable several times and once frustrated just did a DDU cleanup and re-installed the Apple provided drivers that I keep around for this. It isn’t the first time I failed to install one of these drivers. Glad you make them available though.

  5. Yea, agreeing with Joe if there is any definitive way to disable crossfire, I know you could go into the profile for the game and do it there. With all the other options, but if there was any switch or just way to turn on and off that would be awesome.

    • I read somewhere that the current Hotfix drivers from AMD have some issues with Crossfire I just can’t find the website any more where I read that. 🙁

Comments are closed.