[Solved] eGPU error 12 fail after update to Windows 10 1903 or newer (OS Build 18362.329 or newer) inc downgrade pci.sys version solution  

@aj_scarcella

I'll look it up and let you know. Have a ton of college work lined up so haven't had a chance to mess around in Windows recently.

Posted by: @ravynarcadia

Just an FYI about the November update:

If you have a Vega 20 in your MacBook Pro, it will stop the driver from working properly. I had to go back to the September update to fix it.

Mat just posted an update on bootcampdrivers.com saying he's planning to release a V2 of the Adrenalin November edition driver for the Vega 16 / Vega 20 chipsets on Tuesday.

Hopefully that one will work then and maybe we'll get some positive results concerning the error12 issue on newer versions of Windows 10 1903 or even 1909. 🤞

@aj_scarcella

Here it is - it's AMD (18362.295 with November drivers). I was booted with eGPU connected/functional.

@mac_editor

That's very odd. The November drivers didn't reinstall that driver for me after I DDU'd everything - on the September drivers, I had that same AMD driver. I also thought it was odd that AMD were even supplying a driver for that in the first place. It also looks like it hasn't been updated since March anyway. Perhaps once the V2 Adrenalin drivers are out, you might get a different result.

Hi everyone,

During weekend I tried to install bootcamp on my new setup MacMini 2018 i3 + Sapphire Gearbox + Sapphire RX Vega56. The Windows ISO was downloaded automatically when I tried installing trial version of Parallels 15 under MacOS. Windows 10 1903 V1. After install, I ran all windows auto updates up to Build 18362.418. Than I tried to start eGPU. No success! Even the box was wrong identified (intel thunderbolt software didn't find it) and Vega56 driver was with error 12. I deleted the bootcamp and start it again. After second install, the first thing was to stop automatic updates. I plugged the eGPU in while I watch processes in device manager. Box was found and identified  with all peripherals (USB+Ether) and Vega was signed as MS Basic Adapter, as it should be.  Immediately I installed newest adrenalin from web. During installation I lost all bluetooth, wifi, ethernet and USB ports from MacMini. So I plugged Ethernet cable to the eGPU Ethernet port and after a while Windows was back online. But still I wasn't able to use any keyboard or mouse (tried cable / wireless) because all ports on MacMini were suspended. I was able to connect to Windows via RDP (remote desktop connection which I allowed right after windows startup). Via RDP from iPhone I was able to restart mini in proper way. No hard restart. After start up, all was working perfect with all devices enabled. I didn't have to disable any ports in device manager. Restarts between macOS 10.14.6 / Windows withou any problems (no boot screen). Unigine Superposition 1080p medium score 11207.

Hi Folks,
I’ve had a MacBook Air 2018 (8GB model, 10.15.1) + Mantiz Venus + Radeon RX 580 setup working acceptably well for the past year. I do use it for occasional work at home, but the primary purpose for the eGPU purchase was gaming, and the only game I seem to be able to make time for is DOTA 2. I’ve been fairly disappointed with the graphics performance of DOTA in macOS with this setup, especially on the internal display, as it is comparable if not worse to the performance I had with the same eGPU paired with my old and wheezing 2011 MacBook Pro. Certainly my own fault for having inflated expectations about what the bottom tier of the 2018 lineup’s silicon could deliver, graphics-wise. 😉

I’ve decided to go the Bootcamp route to try to squeeze out whatever Windows optimization gains there might be to be squeezed out, but I’ve so far not been able to get past the dreaded yellow-bang of code 12 death. I’ve disabled many devices in Device Manager, I can hot-plug no problem at the Windows logo, but no dice. I’ve downloaded the May 2019 ISO from https://www.microsoft.com/en-ca/software-download/windows10ISO, but by the time the Bootcamp installation is finished, the version showing is later than the magic release number 18362.295—perhaps it’s running updates during the Bootcamp process itself? Could this be an issue?

These forums are a wealth of information and I’ve really appreciated the help in getting previous builds running—in this case I feel like I’m drowning under all the information and am not sure where to go next!

Anyone out there actually have this or a very comparable setup working?

Many thanks in advance

same problem here code 12. Win10_1903_V2 (download at 12.11.19). wondering when will this be fixed

@fire1ce

@errantpixel

Did you try downloading the Win_10_1903_V1 iso file?

Then as mentioned in the very first post apply the KB to update manually to version .295 afterwards and disable automatic updates. This should help. 

My contact at AMD XConnect confirmed they are aware of this issue and actively working with Microsoft to get it resolved.

@itsage

Sounds good, thanks for the info!