Tweaked Ati Drivers For Mac

1. Tweaked Ati Drivers For Mac Download

I’m using Windows 10 with on my ). Overall I’m pretty happy with the hardware but Apple seems to limit functionality when running under Windows. A good example is the trackpad which simply doesn’t operate as smoothly as under Mac OSX. This isn’t because Windows is a less good Operating System, it’s simply Apple supplying drivers and support software this is less good. For the trackpad I found a good solution with which enables 2, 3- and 4-finger gestures and improves scrolling. The AMD Display Drivers as supplied with BootCamp are instable leading to “Display driver stopped responding” messages.

Some of the Advanced features in the supplies AMD Catalyst Control center such as Power Management are simply unavailable. An annoyance is that AMD Catalyst Control Center reports that updates are available but when trying to install it errors with this message: At this point and are likely tweeting that I should stop using Windows on a Mac but I will ignore that. So let’s go ahead and update those AMD drivers, shall we? In my case the Catalyst Control Center stored the drivers in C: AMD AMD-Catalyst-15.7.1-Win10-64bit so I will use this path and this particular version and bitness (64 bit). Note that modified files for the installation can be download from the bottom of the page.

But please read/understand the steps below before downloading. Step 1 – Edit InstallManager.cfg Add the line EnableFalcon=true to Config InstallManager.cfg: Step 2 – Find your hardware id Open Device Manager, expand Display Adapter, right-click your Display Adapter and select Properties. Go to the Details Tab, select Hardware Ids and Copy the VENdor and DEVice id string: Step 3 – Edit driver inf file Open Packages Drivers Display WT6AINF C0187674.inf with Notepad and search for PCI VEN1002&DEV6821 (take the closes match, in my case REV83): Change this line to match the Hardware Id in Device Manager: Now take the section name of the same line, in my case ati2mtagR577 and search for that section: Remove the line ExcludeID= and save the file. Step 4 – Recreate the driver CAT file Because the AMD driver is digitally signed we needed to recreate the driver’s.cat file after changing the.inf file.

Ati drivers free download - ATI Universal Installer for Mac OS, Apple HP Printer Drivers, HP DesignJet 1050C and 1055CM Drivers, and many more programs.

To do this we need the tool, I used the version from the (DDK). Use the following command to create a new cat file (note that you should not specify the path to the inf file but to the directory where the inf file resides). Exe sign / ac 'DigiCert High Assurance EV Root CA.crt' / f 'YourCodeSigningCertificate.pfx' / p YourPassword / tr 'c0187674.cat' Step 6 – Install away! Now we can finally install by launch the Setup.exe, I recommend choosing for Custom installation and uncheck the Gaming Evolved App: Much Better: Also notice that PowerPlay options are now available: But most importantly – I have had no more crashes of the Display Driver! Heeroyuyj 10 @Remko Weijnen i used ur moded file, and i installed the crimson driver successfull! Anthony 17 Hey, it’s a great job you’re doing but it doesn’t work for me 🙁 I’ve got a 5K iMac with R9 295X 4gb with W10 Pro 64bits.

I’ve downloaded crismson driver radeon-crimson-15.11-win10-64bit.exe, installed, then I’ve got an error that says No hardware support. OK, I’m headed to C:/AMD and replace the files with your AMD Crimsom 15.11 package. It install everything except graphic driver, the most important part I checked my graphic card hardware ID and it’s already in your package. PCI VEN1002&DEV6938&REV00 Have you got a solution please? Vadim 30 Hello, have been trying for a couple of days now to install Crimson 15.11.1 using your method and provided files, though no luck, meaning it starts to install, but fails and states that display driver was not installed. Wanted to ask wether I am doing something wrong.

My rig is nMP d500 with PCI VEN1002&DEV679E&SUBSYS0126106B&REV00 HWID, win 10 64-bit I did all your steps, but edited all three provided.inf files matching ur algorithm, then copied your.cat files from provided ones. Installing app is now running fine, but as I stated above – display driver fails to install.

What am I doing wrong? Give me a tip plz. And a huge thanks for all your work, will be donating for sure, if this works for me. Edward Harby 40 I’ve run into a bit of a pickle. I think I had the drivers working at some point and saw huge improvements.

I had to uninstall them because I was getting some texture glitching that was present in the previous driver. Now when I try to install Crimson and the Crimson beta, I get a failed installation during the driver installation. I included the hardware ID in the ini file, and took out the exclude portion in the INI file too. Maybe I’m going something wrong? My hardware id is PCI VEN1002&DEV6938&SUBSYS013A106B&REV00 Any suggestions?. Sasha 55 Thanks for your effor, but it doesn’t work. If I go to official AMD web page, and manually select my card and search for drivers, I have both options, Catalyst Software Suite and Crimson Beta.

But if I check their info about Crimson, my card isn’t supported (as well as all other 5xxx desktop cards). So, it looks that the only chance I might have with Win 7 Catalyst 5.7.1 drivers. Unfortunately, you have only Win 10 version here.

🙁 Any chance that you ca make it for Win 7? If not, I’ll fully understand, you are not here free service for everyone. Thank you anyway, all the best, cheers!.

64 Hey @Alex: trying to figure out why it doesn’t install for you as the original driver uses the following:%AMD6920.1%” = ati2mtagTonga, PCI VEN1002&DEV6920&SUBSYS014C106B&REV01 “%AMD6920.2%” = ati2mtagTonga, PCI VEN1002&DEV6920&SUBSYS014D106B&REV00 AMD6920.1 = “AMD RADEON R9 M395” AMD6920.2 = “AMD RADEON R9 M395X” this means that your card maps to ati2mtagTonga which is what I’ve mapped your card to in the modified drivers as well. So as far as I can see here all is correct. (ignore the fact that it shows as different card, it’s just an id). What error message do you get exactly?.

Sasha 67 Yes, I tried with Crimson driver (that also works on Win 7), but I can’t get to login screen. So I went to Safe Mode, and put back old Bootcamp drivers.

From what I found on the web, AMD dosne’t care about 5000 and 6000 cards anymore, they even officially announced they will not support it anymore. However, in theory, Crimson version 15.11 should work (and should be the last version for 5000 and 6000 cards), but probably they didn’t make any serious tests for all cards, so it’s possible that some models will not work at all.

Just bad luck with my card, I guess. Maybe I should try to install it more than once, what do you think?. Pat 83 @Rolf I just had the same happen. The 15.11 driver installed properly – but I deployed a fubar tactic which worked for whatever reason I forced the miss ID’d card “windows Generic” to be an “intel generic” but it glitches and now you have 3 video cards.

Have the new AMD install software ready at the install prompt – then uninstall the “windows generic” and immediately clicked the install button for the new AMD software. While windows is busy glitching the AMD software installed the second card. You are left with 3 cards – uninstall the “intel generic”. It worked out for me – no idea wtf the issue really was. Pat 85 @Remko Weijnen After much confusion I can get the package to install unsigned code but after a reboot there is an error – something about amd.secure. Unsigned code etc.

I was using the 15.11.1 beta driver for this attempt. This is for the nMP Firepro D500 cards I can not figure out inf2cat – after installing the development pack I still seem to need a certificate to do anything. I was lost after that. Getting a certificate looks expensive is there a cheap option for one?

I added these lines to C0297019.inf: “%AMD679E.1%” = ati2mtagR575, PCI VEN1002&DEV679E&SUBSYS0126106B&REV00 “%AMD679E.2%” = ati2mtagR575, PCI VEN1002&DEV679E&SUBSYS0125106B&REV00%AMD679E.2% was added by me. So I also updated this part: AMD679E.1 = “AMD Radeon HD 7800 Series” AMD679E.2 = “AMD Radeon HD 7800 Series” Perhaps adding the 679E.2 is a bad idea? Is it better alter an existing line? As I am only interested in Windows 10 the only file I updated was C0297019. Is there any need to modify the other two inf files?

I appreciate any help – Thanks!. Pat 86 some more questions if anyone has answers to share. Part of the inf file defines a Max Memory configuration for the type assigned to the nMP D500 cards ati2mtagR575.GeneralConfigData MaximumDeviceMemoryConfiguration=256 MaximumNumberOfDevices=4 The D500 has a 384-bit-wide memory bus.

Is this line related to the memory bus? I was tempted to change the 256 to 384. Would such a change work in a meaningful way and change how the hardware it operated by the system? Could I also remove all other hardware then redefine the following to build a custom driver specific to the nMP D500? AMD679E.1 = “AMD Firepro D500” AMD679E.2 = “AMD Firepro D500” Is any of the above likely to work?

Or would this just fail to make any difference in the performance of the cards? I may figure out the code signing tools if there is hope of doing this. Pat 88 I think my problems are solved. After performing the install using the unsigned drivers procedure (from Amir above) you must reboot manually back into the unsigned driver mode for the install to finish properly. The difference is amazing compared to how it was before. I had to install Mac fan speed control and max out the fan on the nMP – it overheated and shutdown as auto fan control does not seem to work on windows?

But no harm done. Before I found these instructions Black ops 3 was almost unplayable on the lowest graphics settings. Now it plays 60+fps with all options set to max quality. NMP owners are being left out for no good reason by AMD which is sad. Thanks for making these instructions available!

I am still interested in setting the 384 bit memory bus option for the D500 cards if anyone knows more about how they works. Stozer 103 Hi Remko, I can confirm that Imac 5K 2014 R295x works flawlessly with latest Radeon-Crimson-15.12-Win10-64Bit Hardware ID: PCI/VEN1002&DEV6938&SUBSYS013A106B&REV00 I followed the instructions but couldn’t get it installed “card is not supported error” so I downloaded your package and swapped the files and Voila installed first time. Have just ran Project cars and can now crank all the settings to ultra(1080p) and i’m still getting more FPS than I had on Med-high settings. Remko you are a star. Yakk 104 @remko On the m395x I ran the catalyst installer and that appeared to be successful. Then I checked device manager and the card was listed using the same old apple driver. So I manually updated the driver by pointing to the 15.12 folder.

Once that was installed the card was now identified as 200 series and was listing the correct driver. I also experienced the display brightness bug. Problem is, once I restarted the iMac Windows wouldn’t boot. So I had to start in safe mode and roll back the driver to the apple one. Thanks for all your work btw.

Kristoffer 108 First of all thanks for all your work! Much appreciated.

I’ve installed the 15.12 version on my Mac pro with d700s. It seems that a lot of the new Crimson features works as intended, but a few things doesn’t work as good as before. In 3dmark I get half the score that I used to and one card shows as “AMD Radeon R9 200 / HD 7900 Series” – the other just as “”AMD Radeon R9 200.” Not sure if that makes the crossfire work less than optimal?

Do any other d700 owners experience something similar? And any idea on how to fix it?.

Woody 111 Hi Remko – Using the latest signed files you have kindly created on my Mac Pro 2013 model only installs the correct driver for one of the two AMD D500 cards present. The other card is seen as a HD7800 for some reason which prevents cross fire from running all? The hardware ID’s are actually slightly different for the two cards PCI VEN1002&DEV679E&SUBSYS0126106B&REV00 (already present in your files). PCI VEN1002&DEV679E&SUBSYS0125106B&REV00 (not present in your files) They are supposed to be the same card D500 so not sure what Apple/AMD are doing here, but it does stop the driver loading for the second card correctly, and thus crossfire does not work?

Hope you can help revised files. With revised hardware ID’s? Will Make a bunch of us Mac Pro users happy to have latest drivers and crossfire working!: Cheers Woody. 117 Hi Remko, Thanks for your post. It really did gave me hope that there would be a solution.

I’ve been digging around the source files a lot (and also used the non-sign method mentioned here). But whatever I do, I just don’t get the M395X to work. After 2 restore point recoveries I think I’ll leave it at this.

I’m also having many crashes during games for the same reason that you had. I tried with the latest beta and latest production driver, but no luck. It seems that the M395X code name is Amethyst, which I found in the config file as well, so I tried adapting one of those lines and removed the hardware device from the exclusion list, but even then it never shows in the list.

For the record, I’m trying to update the driver via device manager and force it to that particular conf directiory. But somehow the M395X is just never in the device list.

So maybe I should use a different catalyst driver all together. I’m going to keep looking at this thread in case someone finds a solution. For the moment I guess I need to wait for bootcamp to update, or AMD to update. If anyone can point to a right driver that can list the R9 M395X, that would be great 🙂. Chris 121 Hi Remko Firstly, thank you for all you excellent work trying to solve this problem. I have a new iMac 17,1 with the M395X AMD chip. Like others, I have not been able to get the drivers updated using your method.

I have just tried the new WHQL 16.1 setup.exe an it is again failing. But in a different way! Now it reporting that it can’t find the.inf files – which is strange as I just placed them there from your download files. Any ideas on what be going on would be greatly appreciated.

Kind regards, Chris. TomAguy 123 Just reporting back. Used the latest you put up to try and solve some intermittent stability issues I had playing Fallout 4. I’m running a late 2015 5K imac with the M395X in it.

Your files worked great and brought up the install display. I noticed though that while the installer would update the HDMI audio driver and install the new APC feature it was not going to update the display driver as it said I had the newest driver available. So I cancelled the install and decided to try it as Florin did “Manually went to device manager, video card, properties,driver,update driver,manually install a driver and selected the new driver from the list.” I had the sudden and dramatic increase in brightness which led me to believe that it had worked so without further checking I booted back into OS X to adjust the brightness. On booting back into Windows 10 the brightness was back under control but when I checked the driver via device manager, it showed the same version number as the old apple boot camp driver.

So I decided to just try installing it, once again as Florin had but this time pointing it at the C: AMD WHQL-Radeon-Software-Crimson-Edition-16.1-64Bit-Win10-Win8.1-Win7-Jan7 Packages Drivers Display WT6AINF folder rather than picking from a list. This seemed to take. Now however Device Manager identifies my card as one of the R9 200 series. The hardware ID is the same as the M395X though. It identifies the driver as 15.301.1201.0, dated. GPU-Z shows it as 15.301.1201.0 Beta (Catalyst 15.8) and the card as a R9 200 series. Not really sure what the deal is with that.

I haven’t tried ti yet to see if it corrects the issues I had with Fallout 4 but I have noticed that my fan is now cycling regularly even as I type this. Not sure this is a positive development but we’ll see. Thanks for your help!. TomAguy 128 A follow-up to my follow-up. Did not work.

I left my system booted into windows over the night and at some point it crashed and rebooted into OS X. Could not get it into windows 10 at all.

Finally got a safe boot and restored to per-installation point. I used the files you provided in your download as I could see you’d already commented out the relevant lines for this card. One thing I note: Under driver info in C0297917.inf, the Hardware ID for the M395X, PCI VEN1002&DEV6920&SUBSYS014D106B&REV00, shows up with ati2mtagTonga. Under the general install section it shows up under both ati2mtagTonga and ati2mtagAmethyst. I mention this because the localizable strings give “AMD Radeon (TM) R9 M390X” for the Amethyst identifier. The techpowerup GPU database lists the M390X and the M395X as both being Amethyst, as with the M295X in the previous model 5K imac. However, unlike the previous M295X, the GPU and memory speeds are different (according to the techpowerup GPU database).

It also notes that where as the mac and non-mac versions of the M295X had both run on the MXM-B (3.0) bus, the M390X is running PCIe 3.0 x16 while the M395X is still running on MXM-B (3.0). Perhaps there is some apple installed firmware particular to this card on the 5K imac, which would make sense I guess given that they are still(?) running a custom timing controller for the display. In any event, I am forced to conclude that I must stick with the boot camp drivers apple supplies lame as they are. Thanks for your help and pardon my tortured thought process. TomAguy 130 Also, I should note that examining what product specs are available on AMD’s site for the M395X, and there is precious little and much of it both vague and contradictory, seems to bear out the differences between the M295X and the M390X/M395X. But as I say there seems precious little solid information available.

I would note though that there is specific mention of support for the M395X in the Crimison 15.12 mobile driver package (here ). I was wondering if anyone here with the iMac had tried installing that driver and what their experience was?. Glen 132 I was unable to use the Oculus DK2 in Boot Camp under Windows 10 with the latest Oculus runtime (0.8.0.0) on a Mac Pro D500, because it requires more recent AMD drivers than the Apple-provided ones.

Thanks to your tweaks, the Crimson 16.1 drivers install and seem to work. The Oculus Configuration Utility now detects the headset, shows the demo scene, and the camera activates for positional tracking. It would be nice if Apple/AMD provided proper support without resorting to such hacks.

In the meantime, many thanks; I thought I’d have to give up on my Mac Pro for VR development (even under Boot Camp). Chris 143 @Remko Thanks for the reply! I just had a chance to try the updated files but they still don’t seem to work =( When I use the installer for 16.1 with the updated files it says driver is up to date, but if I go to device manager and select update driver and navigate to the folder it does show a newer driver. However it comes up as a R9 m200x series, if I try to install this I get the error “The system cannot find the file specified.” The newest drivers I have been able to install were the Crimson Edition 15.11.1 beta 64Bit drivers. Cinetagonist 148 Remko Weijnen, I have the same ID as you.

I’ve tried to install Crimson 16/1 update and it installed everything except the driver. Then I opened Device Manager and tried to update the driver manually by selecting C: AMD folder where was the Crimson update with your files. And the driver did update but now I have AMD Radeon R9 M200X Series instead of my AMD Radeon R9 M370X before the update. I’ve check inf files.

Indeed PCI VEN1002&DEV6821&SUBSYS0149106B&REV83 id is set to label AMD Radeon R9 M200X. And now I’m wondering why did you decide to rename the graphics card? Ben 149 Hi, I have a MacBook Pro (Retina, 15-inch, Mid 2015) with R9 M370X, and the hardware ids are: PCI VEN1002&DEV6821&SUBSYS0149106B&REV83 PCI VEN1002&DEV6821&SUBSYS0149106B PCI VEN1002&DEV6821&CC030000 PCI VEN1002&DEV6821&CC0300 With radeon-crimson-15.12-win10-64bit and the modified files above, the setup program have the option to install display driver and amd setting. Although the driver failed to install, i can install it through device manager and idenfity correctly as R9 M370X. With WHQL-Radeon-Software-Crimson-Edition-16.1-64Bit-Win10-Win8.1-Win7-Jan7 and the modified files above, the setup program do not have the option to install display driver and amd setting. When i try to install the driver through device manager, it misidentify as AMD Redeon R9 M200X Series. Stefan 154 First, I want to thank the author of this article, Remko Weijnen, for his effort in improving the dire AMD driver situation for the recent Macs.

However, since this is more or less a hack and does not work for all GPUs, this can only be a temporary solution. I would therefore ask everyone who reads this to submit feedback to apple to improve their driver support for Bootcamp. As there is not really a direct way to get in touch with Apple, please use one of these feedback forms: Hopefully, if several hundred people complain about this, Apple will once in a while actually release a driver update. J Craig 159 Thanks so much for sharing these instructions and resources Remko! For those who might be a bit confused about the process for applying the patched files provided here, you must first download the installer from the AMD site for each new driver version. The installation files by default will be placed in C: AMD version directory.

Inside will be the Setup.exe file referenced in this guide. Simply make the changes to the.conf and.inf files as Remko has instructed, then copy the Config and Packages folders to C: AMD version directory, replacing the existing files.

Run the Setup.exe and you should be good. I had originally downloaded AMD Crimson 15.11 from an earlier failed attempt to upgrade and had copied the patched files for a newer driver version (16.1) into the original install directory, but was getting errors until realizing my mistake. Brian 166 @Remko thanks for your reply. Yea, I found that to be confusing after looking into the INF files and not finding a good match to replace, given that these release notes specifically say that the 6000M series is supported: Although, it does say ‘limted support’ I would still expect to find a suitable 6750m entry in the INF. Do you think it’s possible to add? I will try some experimentation but not completely sure where I could add a new entry or if that’s even possible. Thank you for your work.

Jesse 167 Hi Remko, I’ve been following this thread for a couple days now. I just got Windows 10 for my late 2014 5K iMac, specifically to play games, so it’s been pretty upsetting that they’ve been crashing. I used your files on the 16.1.1 release and it worked great at first (thank you for your hard work by the way), but now when it does crash it doesn’t even get to the desktop to say the driver stopped working and recovered anymore. It just stops working and I have to restart. I added “TdrDelay” and “TdrLevel” strings to the registry editor as per another solution I found online. Could that be interfering with your fix? I honestly have no idea what I’m doing.

Mirekmal 168 Remko, first of all – big, big thanks to you for taking effort and making this guide and associated installation files available to community! As I struggled with Cross-FireX configuration with new Raise of the Tomb Raider with stock bootcamp drivers (flickering, colors fading, random flashes) I was so excited when I’v e seen new AMD optimized drivers (16.1.1) and then found this blog! So yesterday I took the bullet and installed new modded drivers on my nMP, basic config with 2xD300. Installation went like a charm, with absolutely no glitches. I was able to configure RoTR to use crossfire and tweaked up all settings. Everything works great, performance up and all visual glitches are gone!

There is, however, one small glitch in driver set itself After installation Radeon control panel (and Device Manager as well) reports that I have 1xD300 and 1xR9 200:-0 So seems there is some mismatch in HW IDs in the latest set of config files you provided. Would it be possible to get this corrected, please? Here are some details of what I gathered from my system, that might help diagnose issue: Primary card (not properly recognized): HW ID: PCI VEN 1002&DEV6810&SUBSYS012A106B&REV00 Recognized as: AMD Radeon R9 200 Series Secondary card (properly recognized): PCI VEN 1002&DEV6810&SUBSYS012B106B&REV00 Recognized as: AMD FirePro D300 (FireGL V) Best regards! Andres Ramirez 171 @Remko I’m not sure benchmarks tell the whole story at it depends on that benchmarks optimization as well, but here it goes.

Stock apple on 3DMark FireStrike: 8651 With 16.1.1: 9547 On TombRaider, although I haven’t benchmarked it, I went from hovering in the low 30s ( with the settings I like ) to hovering between 50-60fps with the new drivers. I have the exact same laptop as you, so I’m sure the brightness fix works there, and I didn’t have issues with the nmp before. @ mirekmal – don’t worry about the names. If it works ( which it does ) it’s all good. Mirekmal 176 UPDATE: OK, so I took some more in depth view on my situation trying to eventually update R9 200 to D300 manually via Update Driver To my surprise situation is following: – Radeon control panel shows version 16.1.1, but – Driver version of D300 is 15.201 (so bootcamp one!) – Driver version of R9 200 is 15.301 (something strange not bootcamp, but not 16.1.1 either) So now I’m really confused. At least I have working CrossFire (probably thanks to good game profile in Radeon Software), but drivers are not up to date.

I tried manually to changes these (e.g. To make both R9 200 or D300), but no go D300 driver is now not visible (from AMD installation package) and R9 200 does not want to install over D300 (not compatible error message). So, any way to get both cards on the same version driver (even with wrong description and eventually to make it really 16.1.1, which I assume would give some extra performance too?. 180 Hey Mirekmal: if you look at original drivers from Apple they map your card like this: “%AMD6810.2%” = BR186303ati2mtagR575, PCI VEN1002&DEV6810&SUBSYS012A106B&REV00 “%AMD6810.3%” = BR186303ati2mtagR575, PCI VEN1002&DEV6810&SUBSYS012B106B&REV00 The card appears with the following friendly name: AMD6810.2 = “AMD FirePro D300 (FireGL V)” AMD6810.3 = “AMD FirePro D300 (FireGL V)” Note that AMD FirePro D300 is just a name that was invented for Apple and therefore is not even present in non Apple AMD drivers. In my driver it is mapped to AMD6810.10 and AMD6810.11 with the following labels: AMD6810.10 = “AMD Radeon R9 200 Series” AMD6810.11 = “AMD Radeon (TM) R9 370 Series” I have just uploaded the 16.1.1 from 3rd of Feb (why do vendors not update version numbers properly!) in which I’ve added your card like this: “%AMD6810.10%” = ati2mtagR575, PCI VEN1002&DEV6810&SUBSYS012A106B&REV00 “%AMD6810.11%” = ati2mtagR575, PCI VEN1002&DEV6810&SUBSYS012B106B&REV00 and the following labels: AMD6810.10 = “AMD FirePro D300 (FireGL V)” AMD6810.11 = “AMD FirePro D300 (FireGL V)”. Mjaestewart 185 Thanks a lot for all of your efforts!

I have the mid2015 15″ rMBP with 2GB AMD Radeon M370X DDR5 GPU, 16GB RAM, and 1TB of PCIe SSD. Apple never releases Driver updates for this GPU running on Windows 10 Pro with Bootcamp.

Drivers are the most important updates a system can receive. I’m guessing Apple’s logic is to NOT run updates if version is stable. Not so good thinking. I’m a Windows Engineer, so I won’t be using OS X. If Apple won’t provide its customer’s with driver updates for Windows 10 running on Bootcamp, then we need to rely on a community of Windows Engineer’s that uses Apple’s hardware to provide fixes and workarounds.

Thanks for your dedication in knowing how important it is for people to have updated drivers. Also, thanks for taking the time to document and post the instructions on this site. Finally, thanks for having the correct files and binaries already modified for instant download without going through Malware and Spyware hell to get them. ISSUE:. I’ve attempted the instructions that you documented on this page. However, I did not have availability to a Cert that I can use for digital signing.SOLUTION:. To get around this issue you can disable “Signed Driver Enforcement” in Windows 10.

Then, all you have to do is modify the.inf and.cfg files.INSTRUCTIONS. 1.

Open Command Prompt as Admin 2. Run the following command to disable Signed Driver Enforcement PERMANENTLY: bcdedit /set testsigning on 3. Reboot the computer 4.

Follow the initial Steps 1 – 4 in Remko’s Instructions. (NOT Step 5). 5. Run the Setup.exe and Install the drivers, etc.

This will work since we bypass the digital driver signing checks from disabling Driver Signing Enforcement. Be sure to re-enable Driver Signing Enforcement after Installing all of the updates to reduce your machine from being vulnerable to rogue install attacks.POST INSTALL. Run the following CMD to re-enable Signed Driver Enforcement: bcdedit /set testsigning off Hope this helps those of you that can’t digitally sign the package OR download Remko’s packages because you are on a different machine with different hardware. Thanks a bunch Remko for posting this great article! All of my drivers are up-to-date and stable. Mick 193 Thanks for all the work you put in to this.

A lot of people wouldn’t know what to do without you. I seem to be having the same problem as mirekmal. The driver 16.1.1 seems to be installing perfect, but actually only installed for 1 of 2 of my FirePro D500. I did everything you sugested mirekmal to do, but it doesn’t work for me. When I try to install drivers manually for the not-updated card it tells me there is no better driver found or that the driver I selected doesn’t support my version of Windows Vista. I have Windows 10 64 bits Do you know what is going wrong?

Hardware ID’s: PCI VEN1002&DEV679E&SUBSYS0126106B&REV00 PCI VEN1002&DEV679E&SUBSYS0125106B&REV00. Chris 214 @Remko Weijen Radeon 6750M support is included in the legacy crimson drivers v16.2.1 www2.ati.com/drivers/beta/non-whql-64bit-nieg-radeon-crimson-16.2.1-win10-win8.1-win7-feb27.exe Can you replace 6740.1 with PCI VEN1002&DEV6740&SUBSYS00F8106B&REV00 Also for ehola, his 6750M is 6741. Not sure why, but you can replace 6741 in the inf with PCI VEN1002&DEV6741&SUBSYS00E3106B&REV00 Also another tidbit, when searching for 6740/6741 at the very bottom with the Series name, can you rename 6700 series to AMD Radeon HD 6750M Thanks. Tom 216 hi guy´s! Thx for this amazing work! I install crimson 16.2 & 15.12! With your upload!!

There is just one Thing; now wenn i connect my sony tv with hdmi,l Windows dispalys me the icon´s much biger, i tryed to Change to normal 100%, but is no possible! Wenn i have both dispalys duplikatet on 1 & 2, is possible to Change the Icon size of Windows! On the lcd from the macbook, is also possible to Change, but not if just the sony is on! This is strange, is there any fix for this! Please write me, thx a lot!. Jake 226 Hi Remko, I’m running a late 2013 Mac Pro with dual AMD FirePro D700 cards and Windows 10 via Bootcamp.

I’m trying to get Oculus DK2 to work in Windows 10 via the steps in this thread. After scouring over this post and comments and getting to the WT6AINF folder from your provided 16.2.1 file, I see 3 inf files named the same “C0299897” Each file seems slightly different which has me confused as to if i modify all of them or a specific one and do I do it across both graphics cards as the number changes slightly between them on the hardware ID. I know someone else got this working through your steps here (although with D500 cards) (via Oculus forums. Search for post by “glenf”) I went ahead and made a screenrecording of where I get stuck so you can better help me troubleshoot. Make sure to download the 30MB.MP4 locally as Dropbox compresses video horribly in the browser window. Very happy to donate $25 if you can help me towards a speedy resolve on this as I need Oculus DK2 to work in Windows 10 for my client project. 243 Hi Remko, sorry to bother you again.

16.3.1 behaves the same way as 16.3 did, even with the files you distributed. (2015 riMac with M395X, Windows 10 Home 64-bit, Boot Camp 6) Installation went well, I was being asked if I trust the drivers signed by you (of course), and then the AMD software asks for a reboot. Then things get flaky.

The machine reboots, fails to boot, reboots again and again until the automatic repair feature kicks in. “Windows could not be loaded correctly.” The diagnosis tool tries to revert things to how they were before the installation of the new driver. I guess it uses the last recovery point before the installation, and after a final reboot I’m on the 15.201.2001 Version. The Non-WHQL folder I created while installing the driver then gets completely botched – I guess that’s part of the “repair process”. Cosimo 253 Hi Remko!

IMac 5k with R9 M395X user here! Just downloaded your new driver 16.3.2. But doesn’t seems to work. I did select the display adapter from device manager, hit update, went to the folder (by the way, compressed in RAR? C’mon Really?;)) selected the driver, but I can’t install it as it says: Windows encounter a problem installing the driver software for your pc.

(W10 64bit) If I run the installer, I can open the installer window but then it ends without installing the diver and saying that installation failed. 🙁 I am still on official bootcamp driver, which are from, which are extremely buggy and slow. I would love to find a way to install newer drivers. Maccc 261 Remko, thanks a ton! Was able to get my oculus finally working! I’ve got macbook pro with a r9 m370x and windows 8.1.

By simply downloading your files and copying them into the driver folder allowed me to install the drivers, too easy. For anyone wondering, this GPU is definitely not optimal for usage with the oculus rift – while it didn’t cause me motion sickness, because theres so much lag, you don’t experience a sense of presence. That being the experience is not terrible, and I think I’ll likely develop for the rift with my mac for the time being. Eric 269 Hi, I installed the 6.3.2 drivers on a Macpro with dual D700:s. Bit odd tho; still have two different graphics cards listed in the device manager, AMD FirePro D700 and AMD Radeon HD 7900, but the Crossfire seems to be working. If any savvy person could point me in the right direction to wether this dual gfxcards affects my system or not? I changed according to Remko’s instructions above: I’ve updated the.inf file corresponding “%AMD6798.1%” = ati2mtagR575, PCI VEN1002&DEV6798&SUBSYS0127106B&REV00 “%AMD6798.2%” = ati2mtagR575, PCI VEN1002&DEV6798&SUBSYS0128106B&REV00 then removed all the excludes under ati2mtagR575 and finally added AMD6798.1 = “AMD FirePro D700” AMD6798.2 = “AMD FirePro D700” under Strings.

272 Just another update: I know now why I don’t get the 15.301 anymore. My Apple Software Update program already files the graphics driver update 6.0 under “Installed” and that’s why I don’t get it anymore. Even when I de-installed everything that’s related to Boot Camp, iTunes and AMD, this one doesn’t work anymore. Can you say anything about it, @Dave? The drivers via Apple Software Update crashed my machine for me while installing, that’s why I wanted to try a clean install in the first place. Geoff Taylor 281 I got the Apple Bootcamp update notice a week ago too, but I have a 5K iMac from late 2014 with m295x.

After installing the new update my resolution options are limited to 3200×1800, 3840×2160, and 5120×2880. Also, Apple Software Update then pushed an “update” to fix 5K issues in Windows 10, which are the drivers from last November. I only noticed that after letting my system “update”. Whichever of those two updates I install, I am then notified of the other update again. Is the new Bootcamp update with 15.301 not intended for m295x iMacs? I’m frustrated being stuck with the 15.201, but the other doesn’t seem to work correctly on my system and I’ve no idea how to get 15.301 or even newer to run with all options and stable on my system. Andres Ramirez 282 I’m going to try the official drivers now.

I’m sure they won’t be as good for games, but will probably be better for 3D work, since I was having errors rendering with the GPU on some 3D software with the “hacked” drivers. Note that it took me a few tries to clean the machine up to take the update. I had to run AMD cleaning utility twice before I got a good install that actually shows the cards as FirePro’s and with the proper control panel. I have a feeling that running the apple updater while on the drivers on this site was the problem. Once I had a machine with no AMD drivers, I got them directly from the AMD bootcamp site.

Remember that while its great that thanks to Remko we can trick the drivers, in theory, the D700 should get the firepro treatment and not the r9 treatment. Here are my results today. On the latest drivers here my fire strike score was: 9547. Fire strike with the official bootcamp drivers: 11461 Wow!

I was not expecting that. It seems for once, the bootcamp drivers are working great. ( sadly, it could also be a better version of fire strike than a few months ago ) I’m going to go check if my GPU rendering problems are gone, but benchmark wise, these new Bootcamp drivers are killing it. Geoff 291 Hi, I have a late 2014 iMac 5K 27″ with the Radeon R9 M295X graphics card. I have installed the latest Apple drivers for Bootcamp and I am now trying to update these drivers with the latest Crimson drivers. I have downloaded the official Crimson drivers and replaced the files from the “Config” and “Packages folders with the onesfrom Remko. I have tried every version you offer from 16.1 to 16.4.1 but I keep getting the same error: “An Exception occured!

Type:RuntimeException, Message: The primary document entity could not be opened. Id=” Am I forgetting something? Could anyone please help me? Nmihalevich 307 Apologies in advance for being completely new to this type of stuff. I’m excited to find a legit thread on the matter.

Here’s my situation and again apologies if it doesn’t apply to this workflow. I have a Mac Pro (2013 w/D500s). I’m looking to get Oculus working in Boot Camp.

I know they don’t support it but I also know that the hardware is robust enough to run it after doing some comparing of recommended specs on Oculus’ site. I can get through the first two steps above, but am getting stuck on Step 3. I should mention I’m confused about being able to work in the AMB Catalyst Control Center in Boot Camp Windows on the Mac Pro.

The Control Center that is on my Boot Camp is AMB FirePro because I have the D500s. Am I missing something here? I guess I’ll stop at that since thats where I’m stuck.

I downloaded the mods above and see how they pertain to the next steps but don’t really know how to implement them into my systems directories. Thanks in advance for anyone willing to help out.

I’d love to get this figured out and to not have to drop another 3k on a “Oculus ready PC”. So lame they won’t support OSX anymore. Gotta love it. SuperUser 333 Thanks a lot! In furtur compiles, maybe you would like to add these two lines to the areas of inf file for support of smaller iMac Retina R9 M290 (without X(!!), so other SUBSYS ID).

Another User with same problem —– #213 post Kyle March 3rd, 2016 at 20:53 Code to add to section: ATI.Mfg.NTamd64.10.0 “%AMD6819.22%” = ati2mtagR575B, PCI VEN1002&DEV6819&SUBSYS0139106B&REV00 Strings AMD6819.22 = “AMD Radeon R9 M290” At the moment i’m runnig it successful with code-signing off. But not an option with a new realse of Windows 10 clean install, as no longer supported.

Tweaked Ati Drivers For Mac Download

Thanks in advance!. Wim Vanbelle 334 I decided to buy another PC. I’ll be putting my imac on ebay soon. This is just not acceptable that Apple forbids us to install native AMD drivers on one hand and doesn’t release proper driver updates on the other hand.

That just isn’t right and I regret wanting to use apple for gaming as well. I won’t be buying any AMD anymore either, after all this misery either. I can post my pcpartpicker config, if anyone wants to know what I put against my latest imac 5K.:). In any case, thanks Remko and Mandi for trying to help out earlier. Good luck to you both. Maksym Pavlov 353 Hi Remko.

I’ve uploaded the archive of the WT6AINF folder from the latest WHQL-Win10-64Bit-Radeon-Software-Crimson-16.9.1-Sep13 update to your favourite sharing site: The.inf file was cleaned off of Exclude line for your (and mine and probably almost everyone else’s here) video card. So all you need to do is to unzip my archive and do steps 4 and 5 – recreate cat and digitally sign it. This would allow everyone to benefit from the latest update and takes off some of the hassle from you. Thanks in advance for signing this for us.

379 Hello and like everyone else I wanted to thank you so much for posting this. My question is this: I have a Mac Pro Late 2013 dual 12-core and I wanted to know the most up-to-date AMD software I can use. I’ve tried some and had some massive crashes where I had to completely re-install so I don’t want to make that mistake again (I think I tried to install Crimson ReLive 17.1 but I’m not sure) Anyhow could you let me know how I can find out which driver and software is the best/most current I can use? Hardware Ids PCI VEN1002&DEV6798&SUBSYS0127106B&REV00 PCI VEN1002&DEV6798&SUBSYS0128106B&REV00. Dick Starmans 390 Dear Remko, I’m truly scared as hell to modify my bootcamp drivers, yet I know the speed boost is whopping (FPS +300% in Fallout4). You may wonder, if I succeeded once in installing these drivers, why am I writing this?

Long story short: I used a source that required root access to my system. Also I failed to untick the auto-update feature, that wasn’t supported, tried to restore from an earlier restore point and messed up my bootability into windows 10. So I come from a fresh Win 10 install on a nMP, with similar vendor signature as Emil, found here on the Blog (yes, I read it through. 🙂 My first endeavours with DDU left me with a standard driver supporting only one of my monitors.

I could use a bit of guidance, please. Best regards Dick.

Sutucol 407 Hallo Remko, (1) Download-Link “here” from “EDIT ” is identical to the Download-Link “here” from “EDIT ”. (2) Download-Link from the Button “Download” is the one that should be the Download-Link “here” from “EDIT ”. Download-Link from the Button “Download” previously led to all files you provided on your share. Now it only leads to “Non-WHQL-Win10-64Bit-Radeon-Software-Crimson-ReLive-17.7.1-July10” (3) The brightness control gui is visible when installing one of the last three Downloads (, ).

But it is only functional in “Non-WHQL-Win10-64Bit-Radeon-Software-Crimson-ReLive-17.6.1-June6” from. Why not in and? I use the same hardware as you (MacBook Pro, Retina, 15-inch, Mid 2015) and I used the “AMD Clean Uninstall Utility” before installing the a new driver. Thanks a lot for your work!. Laurent Daudelin 413 Hmmm I proceeded to use the “Download” button as recommended by @sutucol, proceeded to install. Not sure why but the installer started checking the drivers available and decided to install 17.7.1? Restarted and when I now try to open the Radeon settings from the system tray, I get an error message that says: “No AMD graphics driver is installed, or the AMD driver is not functioning properly.

Please install the AMD driver appropriate to your AMD hardware.” I think I will try 17.6.1.