Modded AMD Radeon Crimson 16.2.1 for Mac Pro available

I finished my work on the Radeon Crimson 16.2.1 Hotfix. The driver should install on all new Mac Pros under 64-bit Windows beginning with Windows 7. Your Windows needs to be in Testsigning Mode as the driver isn’t fully signed yet because a code signing certificate costs around 100 $.

If you have a new Mac Pro (Late 2013) with an AMD FirePro D300, D500 or D700 you can install that driver on your system.

Please feel free to download and install the modded driver and leave me a comment if you like it or have problems.

Please KEEP IN MIND INSTALLING AND USING THE DRIVER IS AT YOUR OWN RISK!

Download: Non-WHQL-64Bit-Radeon-Software-Crimson-16.2.1-Win10-Win8.1-Win7-Feb27_MODDED_BY_MX

SHA1 Cecksum: 6b0e130b9a4d6262e76e7552070bc64235e993ff

13 comments on “Modded AMD Radeon Crimson 16.2.1 for Mac Pro available

  1. Hello,
    Thanks for making this available! However, I just tried to install it on my MacPro 2013 which has dual D700’s and the installer failed to install the ‘AMD Device Driver’. The other things (AMD Install Manager, Audio, FirePro Settings, etc) all had “Success”. Any hints as to what might be wrong?

    • Ahh, I think I see the problem — I hadn’t rebooted after using BCDedit to turn on testsigning.

      I just did that and retried the install — it says it succeeded now, but still problems…
      The AMD Installer finishes with “AMD FirePro software and drives have successfully been installed” and the details page seem to agree, with the display driver there showing as 15.301.1901.000. However, I then restart and check the driver from the device manager and it is still 15.201.1301.0…

      • Hi Brent,

        I had similar problems once. I would suggest completely uninstalling the driver and the accompanying driver software with the Display Driver Uninstaller (DDU) which you can find here: http://www.wagnardmobile.com/

        As you already know testsigning mode is a must, my MacPro runs in this mode for 2 months now without any problems. If I get a cheap code signing certificate I will start signing the modded driver so that testsigning mode isn’t needed any more.

        • Hmm, tried that — still problems. After running DDU and rebooting, I verified that the AMD driver was gone — display was using Generic PnP Monitor. I then reran the installataion of “Non-WHQL-64Bit-Radeo-Software-Crimson-16.2.1-Win10-Win8.1-Win7-Feb27_MODDED_BY_MX” and it completed successfully. However, after rebooting, there was no AMD driver — still the Generic PnP Monitor.

  2. Hi again — I think the issue may be the hardware ID’s in the .inf file. Checking my hardware ID, I have:
    PCIVEN_1002&DEV_6798&SUBSYS_0127106B&REV_00

    In your modded inf file you have SUBSYS_0127106B, but not with REV_00. You do have REV_00 with SUBSYS_012A106B and SUBSYS_012B106B.

    I guess I could edit that myself, but I’m not clear on how to sign the driver, etc…

    • Thanks for your hint regarding the different revisions, that could be indeed the problem. I’ll check and keep you updated.

    • And also there is an exclude line in CU300321.inf:

      ExcludeID-PCIVEN_1002&DEV_6798&SUBSYS_0127106B

      • It should be the Exclude-lines which cause problems. I updated the Crimson 16.3 driver package. If you like give it a try and let me know the result.

  3. Hello,

    Is this still available to download the link does not seem to work.

    thanks

    • You’re right, I’ve tested this and the link isn’t working anymore. I need to re-upload. In the meantime feel free to use the current mXDriver 16.4.2.
      Just to let you know, mXDriver 16.5.1 is in the pipeline. 😉

Comments are closed.