Error 12 on 16" MacBook Pro [i9, 5500M] + Razer Core X + RX580
I've commented on a few threads but thought it would be best to start a new thread.
My last attempt went as follows:
- Install Windows 10 Pro 1903 V1 (18362.30) + Activated
- Install Boot Camp drivers
- Install .295 update
- Reboot into Safe Mode and run DDU to remove AMD drivers
- Shutdown, Plug-in Core X (front-left port), Turn on
- Install BCD drivers (Adrenalin November 2019 edition)
- Reboot (keeping Core X plugged in)
I only had power and the eGPU connected, no external devices (maybe some BT devices, unsure).
Previously I have also attempted to disable tb3 controllers, disable the 5500M, use automate efi boot usb, all to no avail.
Any help/insight/ideas would be appreciated!
death to self
@haoshiro I have tried several Radeon eGPUs with the 2019 16-in MBP in Boot Camp and error 12 was not an issue. I have not used any of our workarounds yet. If you have not tried hot-plug in Windows Desktop, give it a try. Usually the the Network and Sound icons on the Taskbar would show as disabled while the system is initiating the PCIe connection for the eGPU. After about two minutes you would get notification of the PCIe device. You can also try connecting the eGPU on the right sided Thunderbolt 3 ports and see if that makes a difference.
I’ve tried cold and hot plug of every port with no success. Hot plugging doesn’t seem to disable anything and pop up in device manager in seconds with Error 12
I went ahead and order a 1070 in hopes nVidia works out simpler.
death to self
Yeah I’m really disappointed as I have a Freesync 4K monitor and the 8GB XFX Radeon RX 580 GTS Black Edition OC+ which has been great.
I tried with and without the workarounds and I’m using the same windows version as you (Win10 18362.295). I’ve even disabled the dGPU entirely after DDU and had only the eGPU connected.
It strikes me as very strange to be getting Error 12 on this new machine as I expected to work much easier than my Mid-2015
Even disabling controllers and booting with an automate efi usb boot doesn’t help (although the monitor will come on pre-windows using the boot loader).
death to self
Any chance you have an 8GB 5500M? I have ran into the same issue with code 12 using what should be a working Windows 10 build + AMD driver. The only difference I can tell between other working configurations is the extra vram could be causing the issue.
Nope. I have the stock 2.3Ghz i9, 16GB RAM, 4GB 5500M + Intel UHD 630
death to self
I did a bunch more testing trying to get this to work through different drivers (BCD and Official) while using an automate-efi USB boot drive.
It showed some promise as I did get some different behavior a few times.
The first few times booting with automate-efi the Intel UHD 630 would appear and I was able to install drivers for it but it would disappear again and never reappear after reboot.
Once I received Error 43 on the RX580 instead of Error 12 but was unable to reproduce it under the same circumstances.
Several times it booted with the external monitor black but still actually powered on, when that happened the RX580 didn't show up in Device Manager at all.
In a few scenarios with automate-efi everything looked promising but it was stuck at the windows loading animation (I waited 15min+ and it stayed hung up).
I tried disabling every thunderbolt controller, usb hub, etc except that used by the SSD and the eGPU and still received Error 12 on cold or hot plug and I tried this using all four ports individually.
In summary the non-Error 12 states I experienced were:
- Error 43 once, could not reproduce
- Active external monitor (only connected to the eGPU) but eGPU missing from Device Manager
- Windows infinite loading animation on boot (reproducible using automate-efi)
I did also try not removing the Pro 5500M drivers and can confirm it causes a black internal screen on boot that I could not get around without booting a recovery disk, starting safe mode, and using DDU.
death to self
@haoshiro Keeping the stock Apple Radeon drivers and hot-plug an Radeon eGPU would result in black internal display as you found. This is due to Windows auto driver installation for the eGPU which then corrupts the dGPU drivers. The scenario when you got a stuck Windows logo while booting with automate-eGPU EFI is due to the connected eGPU. It’s a recent compatibility issue of Mac firmware and apple_set_os.efi. I believe it effects Apple T2 Chip Macs only.
Have you tried booting into Windows using automate-eGPU EFI but no eGPU connected? If your Win10 is still on 18362.295, you can attempt hot-plug the eGPU. Don’t disable any PCIe components because it may mess with Thunderbolt 3 device detection. Make sure to use the modified Radeon drivers from BCD. I tried original Radeon drivers from AMD but encountered error 173 “AMD graphics hardware was not found”.
@itsage Thank you for the information on what causes those scenarios. I also received that Error 173 error initially trying to install the official drivers but if you reboot with the eGPU connected and try again it then installed correctly (but still Error 12)
I did try hot plugging the eGPU after booting with automate-efi and the BCD drivers leaving all the devices enabled and was still stuck with Error 12. Trying to disable devices was the last thing I did as a last ditch effort and the last thing I could think of left to do.
When I created the automate-efi boot disk I did use the install script and chose "NVIDIA" as the instructions said to due to out of date AMD patches.
Edit: And yes I am still on .295
death to self
@haoshiro I tried automate-eGPU EFI boot loader to see whether the Intel UHD Graphics 630 iGPU in the 2019 16-in MacBook Pro is usable. Unfortunately it’s the same situation as 2018 & 2019 15-in MacBook Pro. While it’s possible to enable the Intel iGPU and force attach it to the internal display, you’d get white dots and eventual black display. We have to wait for @mat_hd‘s December release of the BCD drivers to use both RP eGPU and Radeon eGPU at the same time.
@Haoshiro I'm also looking for a solution to this. I also experience the *exact* same issues like you. Error 12 no matter what. I think I tried all the things you tried. Anyway, my MacBook is slightly different. 2,4 GHz, 64 GB, 5500M 8 GB. And I am using the Razer Core X with a Radeon Vega64. So I assume it does not affect only RX graphic cards.
Will try a few different windows versions now. Starting with 1809 and then the newest 1909. Will let you know if I figure something out. 🙂
Tested both the 1809 and 1909... still no luck... - I'm really wondering what causes the issue. Especially as itsage doesn't have any issues getting this setup running at all.
Anyone else made any progress here?
The one thing I kept missing was the tiny check box at the bottom of the DDU settings that says keep Windows from reinstalling drivers after uninstall. This was key and the only thing I had forgotten before.
Interesting. I also has checked the checkbox and still experiencing error 12. I gave up on that. I sold my Vega64 and will get a 2080 soon. Don't need the eGPU under macOS anyway.
This is the post I followed verbatim (from itsage). Make sure to have the Win 10 xxxx.30 installer.