[Solved] eGPU error 12 fail after update to Windows 10 1903 (OS Build 18362.329 or newer)
Last night I did a clean reinstall of windows (external ssd), installed bootcamp drivers (obtained from macOS 10.15.3 beta 2), joined the windows insiders program and installed the latest insider build. Then I ran DDU (safe mode), followed by an install of Adrenalin 2020 drivers from bootcampdrivers.com.
I reboot, plug the eGPU, and get error 12.
Any suggestions welcome!
see my previous posts tried various configuration but with no luck so far.
Next I will try to disable wifi before connecting the egpu.
To be honest, I am a little bit confused by all the possibilities how, in theory, eGPU support under Windows 10 might work again. Also it seems to differ for every Mac...
Maybe someone can give me a short answer:
Is there a solution for my setup that's currently working? Setup is in the signature.
Macbook Pro 13" i5/16/512 - Sonnet Breakaway Box 550 with Sapphire Pulse Vega 56 - Xbox One X - PS4 Pro - Nintendo Switch - Sony KD55X8505 - Denon AVR-X1300W - Klipsch - Klipsch R-115SW
iPhone 11 Pro Max 256GB Midnight Green / iPhone X 64GB Silver - iPad Pro 128GB LTE - Apple Watch Series 2 - Synology DS218+ - Xbox Live ID: Iron Breed PSN - ID: IronBreed
My windows 1903 version 18362.295 was updated to 18362.592 yesterday.
This is what I did to enable egpu.
- Disable PCIE Root port#3 -9DBA
- Shut down windows
- Power cycles egpu (turn off at least 30 secs)
- Turn on egpu, connect TB3 cable to laptop, (Turn on laptop)
- Use Refind to enable internal graphics
MacOs Mojave 10.14.6
AMD ver 19.12.3
So far it seems that you are the only one who manage to get an AMD eGPU to work with the latest 1903 version (excluding the insider build). Or at least I haven't seen anyone else in this thread?
Is it still working? I noticed you posted a build about an hour ago (at the time I'm writing this post). But that build seems to be on the .295 version.
I managed to get it done.
On W10 .295
I disabled pci port 9
Run the setup of amd downloaded drivers 20.1.1
The card was identified and asked for restart. Restarted and boom it works with ext display
Main Display shows the windows sign.
Can I enable port 9 now?
What limitations do i have if I keep port 9 disabled ?
@tsakal Once the eGPU is working in Windows, you can re-enabled the PCIe Root Port. You have to disable it again prior to shut down/restart so that the next boot would allow the eGPU to work.
In windows version 1903-18362.592, it only works with RX580 only. I tested using the Aorus Gaming Box and Mantiz Venus. It doesn’t with the new Navy cards. I apologize for not making myself clear. To get it working with 5700 XT, you would need to use the pci.sys method
i will do
I’m running Catalina 10.15.2 and Windows 1909 (Build 18262.535) with secure boot turned off, the pci.sys file replaced in windows and no other modifications (and no pci devices/controllers disabled in windows). I leave my eGPU connected at all times, but when booting into Windows I turn my monitor off at the mains (I use a smart switch to make it easier) and then turn on my monitor once the backlights on my keyboard stop flashing and it works every time. Booting into Mac I don’t need to turn anything off, it just works.
Going straight to the problem: whatever is the way I install the video drivers (Gigabyte Vega 56 in Akitio Node @ 600W - latest Win10 updates) I can get only the RX570 or 580 working. The Vega 56 flashes for a second at first startup then I get the yellow triangle with the "!". Are the VEGAs particularly problematic (as I read somewhere)?
For Windows 10 1903, here is a temporary fix for getting your eGPU working. Only tested on the 2015 MBP. Change driver IDs in the .bat file to match your device.
Hello, I read 13 pages at a time. Thank you very much for your efforts. As for the method of modifying pci.sys file, my English is not very good, so I hope it can help me. I recovered to the version (1903) that can run egpu normally according to the method, found the pci.sys file, and extracted it. Then what I want to do is Upgrade 1909, and then overwrite the upgraded pci.sys file? I hope you can reply me, thank you
If you can track down the PCIE controller connecting your eGPU, right click it, go to Properties, Details, Hardware Ids, then copy and replace the driver name in eGPU-toggler.bat with everything up until the 2nd "&" symbol. To test out which one is connecting your eGPU, you can try toggling off the PCIE controller #4 or #7 in Device Manager to see if your eGPU disappears, then toggle it back on. The one that makes your eGPU disappear from the Device Manager is the one you'll want to replace the driver name with. You can also try to view "Devices by connection" on Device Manager, un-collapse Microsoft ACPI-Compliant System, Pci Bus, then your PCI Express Controllers to find where the eGPU is located, then go with the PCI Express Controller containing it.
On the actual eGPU (not the PCIE controller), copy the Hardware Ids that looks similar to this and replace it in eGPU-toggler.bat :
"PCI\VEN_1002&DEV_66AF&SUBSYS_081E1002" ( this was mine for the 2015 MBP )
This will allow eGPU-toggler to detect changes to the status of error 12.
Hope that this helps! Once you get it working, you may want to follow the steps on my GitHub page to install to startup. If the program doesn't resolve error 12 within the first few minutes, try restarting the computer and running it again off of a fresh reboot. Again, I personally have only been able to confirm that this work around works on Windows 10 build 1903.
I think I am gonna try using the 1803 pci.sys file. The method I made works, but it is not as consistent as I would like. Had trouble triggering a successful connection after updating my GPU drivers. Hopefully this is a solid solution.
edit: It looks like a Windows 10 update was swept under the rug after I did my fresh install and disabled the auto updates. I uninstalled the updates and updated to .295, hopefully this is enough to allow for hot-plugging the eGPU.
Question: Can I use the pci.sys file that is currently installed with .295 to update windows to 1909 and retain hotplug functionality?
cant find the pci.sys file mentioned on the first page, can’t seem to find the .1 version of Windows 10. Tried using an older version of Windows 10 and it kind of broke bootcamp, but I did install it from the macOS side of my computer. Maybe that’s the wrong way to install it? Do I install it with a windows 10 usb and change the permissions of pci.sys? The only way I’ve gotten this to work so far has been with my toggler script. Was just looking for a more elegant solution
I think it's finally working in the latest preview.
PC: Lenovo X1 Extreme Gen 2
Windows: 10 Pro Insider Preview OS 19551.1005
EGPU: Core X Chroma
GPU: Asus Strix RX Vega 56
Gonna test it myself. My windows side got f’d and I was forced to do a reset. Think I finally fixed it, but the fan is blasting in the first few minutes after startup. Didn’t notice that happening before. Might have to reinstall windows 10 fresh, but I’ll try out the update first
Got my 5700XT working in Akitio Node/Bootcamp with pci.sys substitution with the following variations to the instructions:
- needed to disable virus security because pci.sys was immediately replaced with the actual/present version
- had to reboot after giving max control to the User before replacing pci.sys
Crossing fingers for the next Win update.
Thanks to all,
Can you provide more detailed instructions for replacing pci.sys? Which windows did you rip it from? The way I did it destroyed my windows 10 build, had to start scratch.
I’m currently attempting to use the Insider Preview OS 19551.1005 as recommended by @jason_nguyen
I think I might attempt that replacement of pci.sys sometime.. The new Preview did not work for me, downgraded back to 1903. My eGPU-toggler script still seems to do the trick, but it can take sometime before a stable connection is made. For now, I will probably stick with using eGPU-toggler. Doesn't require any special bootup, just takes some patience with each reboot.
I just took over ownership of that file and Windows allowed me to replace this one with the old copy - without entering Safe Mode or using any USB Emergency system.
I am glad you made it work. I hope Microsoft will fix it soon. I heard rumors that the next build will address this issue officially.
Issue fixed for me automatically with windows update, on version 2004, installed today. Build 19559.1000
FYI: I'm on Thinkpad X1 Extreme 1st gen, RX5700 and Sonnet Breakaway Box.
Edit: forgot to mention I'm on the Windows Insider Program so I get to preview new builds quickly. Hopefully this will get released to everyone soon 🙂
Thank you all for reposting success with Insider versions. Last I heard from AMD, they said they’re working with Microsoft to remedy this issue. This is very hopefully we’ll see a fix in the Spring Update 2004 release.
Thank you all for reposting success with Insider versions. Last I heard from AMD, they said they're working with Microsoft to remedy this issue. This is very hopefully we'll see a fix in the Spring Update 2004 release.
@itsage can you confirm if latest insider fixes this on a MacBook as well?
I've discovered a new way in EFI for enabling the iGPU and allocating resources for the Thunderbolt root bridge, solving the error code 12 on 2015 15" MBP (M370X) with Radeon VII. This method may be applicable for many systems. My Win10 version is 1909 (18363.592).
My implementation post should be ready to be published this weekend.
@goalque That’s excellent news! I have a 2015 15-in MacBook Pro (iGPU-only) to test. I needed dsdt.aml through automate-eGPU EFI boot loader in order to resolve error 12 in Boot Camp. Looking forward to your implementation and findings this weekend!
Take a closer look at rows 4-6 in my EFI Shell script.
MacBook Pro 2017 13” with touchbar
egpu = razer core x + sapphire nitro 5700xt
mac works great plug and play no issues.
boot camp loads but under device manager there’s a warning sign over the graphics card showing code 12
attempted to do a thumb drive efi boot no luck. Tried DDU in safe mode and reinstall no luck.
have uninstalled windows 3 times and tried different approaches.
any help appreciated. Tried to follow similar builds on here but couldn’t replicate their success.