[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
@beardedbro, which version of Bridge OS are you on (you can check from System Report)? Have you ever installed any Big Sur betas? If so, which version?
I’m not sure the version I’ll have to check, I haven’t tested the 5700 on Mac side only windows atm. Never installed or used anything other than DDU and bootcamp drivers.
to be clear it’s a TOTALLY fresh install of bootcamp, wiped everything, ran first aid on the drives then did the above.
Edit: I’m running Bridge 17.16.16610.0.0,0
After 10 minutes more testing I’ve found the following:
Windows does not like the eGPU, it will error 12 if you plug it in after booting up. HOWEVER, if you plug it in after booting up and then tell it to restart, it will accept the card without a problem and won’t disable the internal GPU (from what I can tell).
With that being said, I’m not sure if it overwrites the drivers on boot up by fetching new ones or not, I haven’t tested it. It doesn’t appear too though as the 5700xt is perfectly accepted by windows if you boot with it plugged in.
To Do List
Test if the Drivers get overwritten
Run New Haven Benchmark and see if numbers are comparable to old ones I have
Possibly Reinstall Drivers?
Test mac side of card
Test Hot plugging and Cold plugging and see if any crashes occur (they used too).
I've been thinking about purchasing an eGPU with an AMD Radeon 5700 XT GPU so I could play games in Bootcamp. But I've been reading around about how eGPU's don't run properly in Bootcamp. I was curious if BigSur is going to change that or not. I also read how certain windows ISO versions are better, but I am also not sure how to download specific versions of them.
The other day tried to update adrenalin drivers and everything got unstuck. Tried to update to latest windows but with no success. Windows even replaced the pci.sys file back to news version.
Fortunately when I restored back to last restore point everything is working ok again.
From past experience the best way to succeed is to find a build guide with exactly the same config as your system and follow it religiously. This is what it did with Andys guide for setup and minii5 for the pci.sys swap. Add a good portion of patience .......
I hope this helps .
A) 2020 MacBook Pro, i7-1068NG7, 32GB RAM, 1TB, EGPU Razer Core X, Nitro+ RX5700 xt 8Gb, Samsung 49 1440p UltraWide C49RG
Mac OS Catalina 10.15.7, Internal Bootcamp Windows 10 2004 pci.sys swap.
B) 2.7 GHz I7 4 Cores, 16Gb, 1TB MBP 13 2018 TB3 , EGPU Razer Core X, Nitro+ RX5700 xt 8Gb, LG 32UK550
Mac OS Catalina 10.15.2, Ext SSD Windows 10 1903 V1 .295
I got the downgrade working. No wi-fi but that's OK. First I had not signal then I hotplugged and restarted like someone recommended - and after that everything's been easy. Took me a while to figure this out, whew!
I've been successfully running Win 10 build 19041.264 version 2004 and using the PCI.sys trick. Windows updates were set on long term pause. However, it seems Windows notifies me/tries to nudge me this week, for a supposed (BIG) update?
What to do? I don't really want to risk having to go through EGPU problems again.
TLDR: Windows Builds 20236 and onwards (available through the Windows Insider program) have had fairly stable eGPU support for my dual GPU Macbook Pro. After updating to the dev channel and doing some basic troubleshooting, it's been working WITHOUT fancy bootloaders, pci.sys replacements, or finicky hot plugging.
Here's my setup:
2017 Macbook Pro 15" with Radeon Pro 560 4GB
Sapphire Radeon Pulse Vega 56
LG 27QN600-B 27” QHD Display connected to the eGPU with DisplayPort 1.4
MacOS Catalina, Bootcamp w/ Windows 10 Insider Edge Dev Channel
I had both Error Code 12 and 43 in Windows. I signed up for the Windows Insider Dev Channel builds, and was shocked when my eGPU was recognized on boot after the update.
I went through a few BSODs, and then the system stabilized (it's dev channel after all). I had to uninstall all graphics drivers with DDU, then installed the latest Adrenalin (Red) drivers from BootCampDrivers.com. A few reboots later, port swaps, and fiddling later, everything seemed to work quite well and right from boot-no fancy bootloaders, hot plugging, etc needed.
One of the Windows updates brought back Error Code 43, then after a hot port swap, Error Code 12. I disabled the internal dGPU in device manager, rebooted, and then reenabled the internal dGPU, and it worked.
For my system, I do have to use the front left TB3 port-I get Error Code 12 on the rear port. Also, on my machine the left hand ports have the higher graphics bandwidth PCIE lanes.
I've been running the Windows Insider Dev Channel releases for about 1.5 months now. After some minor instability at the beginning, I've been getting rock solid stability and eGPU performance. I'm currently on OS Build 20262.1010, but have had fairly rock-solid stability with this setup since 20236.
MacOS Catalina has worked flawlessly right since the start. But I'll admit I've been most excited about the fact that my otherwise mediocre MBP can now put up decent framerates in Windows games. Older games can mostly run at 1440p and Ultra settings with 60+ fps. 🙂
for the past 12 hours I've trying to get my 570 to work on my Imac with no success. i get this in task manager: This device cannot find enough free resources that it can use. (Code 12)
does anyone know how to fix this or am i out of luck?. I've also updated windows and restarted multiple times and download Amd Drivers.