ERROR 12 on BOOTCAMP HAS BEEN FIXED BY MICROSOFT! in WINDOWS INSIDER (FAST) !
Was hopeful that upgrading my PC to the fast ring (Insider) version would fix the issue and it hasn't.
I am using the latest drivers from bootcampdriver.com.
Going to clean install and go step by step, really hoping that it works
Any advice would be appreciated..
Ok I'd follow a clean install of 1903, let the default drivers install for your AMD, don't bother with BootCampDrivers.com just yet. After that's all done, reboot and once loaded into Windows, hot plug your 2080 and install the latest Nvidia. Hopefully you get some success!
I was on a 2004 insider build (without any tampering, efi, pci.sys or whatever) like a month ago and my Mac Mini was working splendidly with my 5700XT. Then at some point I adjusted the monitor height which made the T3 cables move and caused some disconnection, image froze and I never got the eGPU to work again.
Yesterday, I opened up the mini with a friend and swapped its RAM upgrading from 8GB to 32GB. At first the mac mini would not boot and apparently one of the memory dims was not seated properly. in the meantime however we did a PRAM reset.
Anyway Mini booted into Catalina with 32GB available so for some reason I tried to restart to boot camp just to show to my friend what I was talking about egpu not working and all of the sudden the damn thing started working fine again.
I don't know whether that's because after the pram reset or the ram upgrade windows decided to reallocate whatever resources properly to get the egpu working again or if the extra RAM help things out. I reckon is the first one and now I have to live with the agony of something unplugging or replugging to the mini that would mess egpu again in Windows.
@arouris, were you getting error code 12 when your egpu initially stopped functioning?
I am 99% that the PRAM reset did the trick in your case, but since you had it working to begin with, just curious if it showed up as "code 12" in device manager...?
Glad you got it working
- it only worked (both a month ago and now) if you boot with the eGPU connected (so the iGPU is disabled)
- when it doesn't work you don't get any signal on screen, it seems like the OS reboots a couple of times and then it arrives to the login screen but still no image. at some point I even saw the login screen for a split second before screen going black again.
- in every scenario if I boot using iGPU and hotplug eGPU after Windows has booted it always gets error 12.
- pci.sys fix never worked for me (using 3 different windows builds) as windows do not even boot and they attempt an automatic repair which fails. windows can boot again if I replace pci.sys with the correct version of the specific windows build.
- I believe that PRAM reset made windows reallocate resources to PCIe devices/lanes and it once again hit the combination where the eGPU works. even a device disconnection/re-connection can cause the whole thing to collapse again.
it seems that some Windows builds are better than some others but then again it comes downs to luck in order to get the 5700XT to work. 580 Polaris card that I used to have was working fine straight out of the box.
In my case, cold-plugging always leads to the infinte cycle of windows logo plus green gibberish. In order to get to the login screen, i MUST install the EFI patch...
However, this is circumstantial and random as it all depends on how Windows allocated whatever resources the eGPU needs. It is now at a state where it will work properly every time and with every reboot BUT any kind of HW modification/plug/unplug that will make Windows reallocate resources will most probably break it (as it did in the past) and there is no obvious way to make it work again. So if one makes it work, they either need to backup the whole Windows partition or maybe create a restore point and hope for the best in case it breaks again.