Boot Camp eGPU Setup Guide - Windows Gaming with Macs
@huy you need to include what work arounds /methods you’ve used and what OS for people to be able to help.
There are also plenty of build guides on here you could read...
So does all of these settings change anything in MacOS? Will it effect the iGPU, dGPU and eGPU in MacOS?
After set up everything (it worked on boot camp), can I turn SIP back on?
I think I have a solution for mb 13 2017 touchbar + core x + radeon card error12
try disable two thunderbolt root devices. the one that is mentioned in the manual, and the other that has wifi connected to it (#12). then shutdown.
Boot with option key, wait until you can see the moue pointer. then plug in core x and boot into windows,
As soon are you're in you should have no error 12. just go back to device manager and re enable back #12 root device back
Does not work, I tried Razer Core X with Air Boost Vega 56 on BootCamp for Internal display, it’s not possible as of now 2019. I used Purge-Wrangler and set-eGPU, installed correctly but AMD Settings could not find internal display so it’s all for nothing... just lagged the computer out and caused slower start up
@Andre Ponomarev You mean- you can’t get it to work, possibly because you are using the wrong solutions. I don’t have any experience with the 2019 MacBook Pro’s but I have a feeling you are trying the wrong solutions. Try looking through the builds section for someone with the same year and size MacBook as yourself and copying them...
I know you've previously said that you don't have any experience w/ 2019 MacBooks. However, I'm trying to use an Nvidia card w/ Bootcamp, does the year of the Mac have any effects on the process? I see guides w/ 2018 Macs, but not a 2019 🙁
I will be getting a Razer Core X, but it doesn't have a return policy so I just wanted to check up on that.
Hi, what size MacBook do you have? At a guess, based on other people’s experiences with new MacBooks I’d say you’ll be fine, Nvidia cards tend to be easier to set up. If you have any problems I’m sure folks can walk you through how to get up and running.
@eightarmedpet Actually, the guide you linked to doesn’t attempt to keep iGPU active haha. Trying to do so on the 2018 15” causes glitches and issues. Only thing needed is eGPU hotplug (or a little trick to allow boot with eGPU + functional internal monitor). 2019 MBP might show similar behavior.
@mac_editor whoops! My mistake... cheers for catching that! I'll edit that bit out since I was bloody wrong!
When you say hot plug, does that mean that I simply need to plug in the GPU while I'm loaded on Windows and then it'll use the GPU? I'm a bit confused about how to feed it back through to the screen, do I need to download some software to allow this to happen? Also, are there any guides out there on how to set up the eGPU on BootCamp for my 2019?
@Aaron , pls work through @OliverB's guide:
This description works perfect and is easy to follow. I got a macbook pro 16 with the AMD 460 gpu. The guide works fine and i was able to install my egpu. I use an AMD Vega RX 64. I would refresch the link under step 4. The AMD link connects to the official AMD Support and Driver Website. I downlaoded the software there and it didt'n work. So i changed to bootcampdrivers.com and dowloaded the software from this page and i worked with the Vega 64. I also didn't have to disconnect the PCle 16. The egpu was recognized and the yellow band Syndrom wasnt shown in the device manager.
I have the same configuration, can u activate your egpu in bootcamp?
Hello ,can u help me with gtx 1070 founders edition (6+2pin), Akitio Node , W10 boot camp 1903, MacBook Pro 13 2018 touch bar. When I hot-plug 1070 - nothing happens. No any new devices in manager. Card is good n working in desktop. But when I change 1070 to GT8600 (without additional power supply) then MBP is slows down for 2-3sec n after that I see a new video adapter in device manager, n I can install Nvidia drivers 4 it (when I plug 1070 again - nothing happens)
@just-be-freeman Download and run DDU to remove Nvidia graphics drivers. This process also disassociate detected eGPU from the Thunderbolt 3 PCIe connection too. You can then hot-plug GTX 1070 eGPU in Windows Desktop. The detection process can take several minutes. A clue when the system tries to initiate the Thunderbolt 3 component is Windows freeze up and WiFi and Audio icons become disabled. Once the trackpad and keyboard work again you can install latest Nvidia graphics drivers.
windows can't see 1070 at all. I tried to run DDU but after that I can see only one basic video adapter - intel graphics... hot plug, cold plug - same result - nothing happens...
@just-be-freeman You can try automate-eGPU EFI then. With certain Macs, Thunderbolt 3 device detection is better when it's connected prior to boot. A consequence with having an eGPU at boot is the deactivation of Intel iGPU which leads to stuck Windows logo on internal display. Using automate-eGPU EFI helps keeping the iGPU activated.
Great writeup and it is very useful!
One point, though about this comment: "In the 13″ non-Touch Bar MacBook Pro, disabling the iSight camera PCIe bridge does the trick."
This is NOT true for all nTB 13-inch MBP models. I have a 2016 nTB MBP and simply disabling the iSight camera PCIe bridge does NOT work to solve error 12. I spent countless hours trying to resolve error 12 on this machine in Windows, and eventually just gave up now as it wasn't worth my time anymore.
Perhaps the 2017 nTB MBP will work fine by doing this trick, but I can tell you for a fact that this does not always work in 2016 nTB MBP models. This should be mentioned so others don't waste their time.
So does this work with thunderbolt 2 ports when using with Bootcamp?
@acronychal There are many factors that may cause error 12 in Boot Camp when using an eGPU. Try the simplest approach first and if it doesn't work find a different solution. We recently learned Windows 10 OS Build 18362.329 & 18362.356 cause error 12 on most Macs with an AMD eGPU.
@itsage, Thanks for the reply. I understand there are many factors that can cause error 12. The thing is, in this article you state that simply disabling the iSight camera PCIe bridge will work to resolve error 12 for the 12" nTB MBP.
The simple fact is this is not true. Just like you said, there are many factors that can cause error 12. There are factors that could cause error 12 that no amount of disabling PCIe resources (iSight camera. etc.) will resolve for a 13" nTB MBP.
This sentence is misleading and can send a reader down a rabbit hole of disabling PCIe resources over and over when in fact this is not the case.
If you changed the sentence to simply read something like this, it would be more accurate: "In most cases, disabling the iSight camera PCIe bridge for the nTB 13"MBP does the trick. If this doesn't work, you will have to try some of the other solutions given."
Thanks and cheers!
@acronychal the problem is egpu implementation is an ever changing landscape... what's true one week may not be the next so without doing constant site audits (the mods here do this as a hobby not a job) it's impossible for every piece of information to be correct for every build out there. A good example recently is the last two Windows update that have both entirely changed the way AMD eGPU's can function.
I totally understand and I appreciate all of the hard work the mods do here. This site is an awesome resource for eGPU and I recommend it a lot to others.
I personally think that because of the changing landscape of eGPUs that you mentioned, certain statements should not be written as a catch-all fact. The sentence about the 13" nTB MBP is written this way.
I don't understand why it would be so hard to simply add something like "Most of the time" or "In most cases" or "With most Windows builds" to the sentence.
Right now that sentence about the 13" nTB MBP is not correct information. Adding some simple text to take into account the ever changing landscape of eGPUs like you mentioned and the myriad of reasons for error 12 like @itsage mentioned would make this sentence more accurate.