Boot Camp eGPU Setup Guide - Windows Gaming with Macs
Boot Camp eGPU setup on a Mac can be plug-and-play for some and a total nightmare for others. The easiest Thunderbolt 3 Mac to pair with an eGPU is one that has Intel integrated graphics only such as the 13″ MacBook Pro and 2018 Mac mini. Mac computers with a discrete graphics card often require more resources and Windows isn’t always very compliant. Error 12 (lack of resources) or flickering/stuck Windows logo at boot are primary issues when connecting an eGPU in Boot Camp. Now that Apple officially supports external graphics cards in macOS (since 10.13.4), we’ve devoted more effort to set up and maintain a functional external GPU in Windows 10 via Boot Camp. In the past three years, our community has provided many different solutions [External Graphics Card build guides]. This Boot Camp eGPU setup guide is a collection of those efforts.
- Graphics Switching & Your Mac
- AMD eGPU vs Nvidia eGPU
- Large Memory Allocation
- Step 1: Housekeep Windows 10
- Step 2: Force-activate iGPU
- Step 3: Solve eGPU Error 12
- Summarized Setup Procedure
- Windows Boot Up Procedure
Let’s discuss graphics switching in Windows briefly. Forum member Sky11 explained the three modes in Windows 10 (AMD XConnect, Nvidia Optimus, and Microsoft Hybrid Graphics) in this post. In order for automatic graphics switching to work, the crucial prerequisite is the Intel integrated graphics card. AMD XConnect/Nvidia Optimus provides internal display loopback acceleration through the Intel iGPU with a Radeon/GeForce eGPU. In a Mac that has an AMD discrete graphics card and no functional iGPU, you would need Windows 10 1803 or newer. Win10 1803+ provides manual graphics switching per app/game through Graphics Settings. Therefore the ideal Boot Camp eGPU environment is an Intel iGPU-only Mac running Windows 10 1903 OS Build 18362.295.
Prior to setting up an external GPU, it’s a good idea to identify the routing of the PCIe connection over Thunderbolt 3 for your host Mac computer to learn about its capabilities. For example we used HWiNFO64 to check the arrangement of PCIe controllers and lane allocation on a Late 2016 15″ MacBook Pro (same as 2017 to 2019 model). The x16 PCI Express Controller connects to the Radeon Pro dGPU (uses 8 PCIe lanes). The x8 PCI Express Controller connects to the left-side USB-C/Thunderbolt 3 ports (uses 4 PCIe lanes). The x4 PCI Express Controller connects to the right-side USB-C/Thunderbolt 3 ports (uses 4 PCIe lanes). They account for 16 total PCIe lanes directly off the CPU. Here’s the list of Thunderbolt 3 Macs that can work with eGPU in Boot Camp.
|Supported Macs||PCIe Speed|
|Thunderbolt 3 (USB-C)||32 Gbps|
|Mac Pro (T2 Chip, Late 2019) *
MacBook Pro (16-inch, T2 Chip, Late 2019) *
MacBook Air (13-inch, T2 Chip, Mid 2019)
MacBook Pro (15-inch, T2 Chip, Mid 2019) *
MacBook Pro (13-inch, T2 Chip, Mid 2019)
iMac (5K, 27-inch, Early 2019) *
iMac (4K, 21-inch, Mid 2019) *
MacBook Air (13-inch, T2 Chip, Late 2018)
Mac mini (T2 Chip, Late 2018)
MacBook Pro (15-inch, T2 Chip, Mid 2018) *
MacBook Pro (13-inch, T2 Chip, Mid 2018)
iMac Pro (5K, 27-inch, T2 Chip, Late 2017) *
iMac (Retina 5K, 27-inch, Mid 2017) *
iMac (Retina 4K, 21-inch, Mid 2017) *
iMac (21-inch, Mid 2017)
MacBook Pro (15-inch, Mid 2017) *
MacBook Pro (13-inch, Mid 2017)
MacBook Pro (15-inch, Late 2016) *
MacBook Pro (13-inch, Late 2016)
|* Indicates a Mac with discrete graphics card as standard equipment|
The 13″ MacBook Pros have no direct Thunderbolt 3 to CPU connection because of the U-processor. All PCIe lanes are routed through the platform controller hub (PCH). Apple Thunderbolt 3 support article states that the right-side Thunderbolt 3 ports on the 2016 & 2017 13″ Touch Bar MacBook Pro have lower bandwidth than the left-side ports. This is due to the x2 PCI Express Root Port #9 – 9D18 to which these ports attach. 2018 & 2019 13″ models use Intel 8th generation quad-core U-processors that provides more PCIe lanes. Therefore the right-side Thunderbolt 3 ports on these newer 13″ MacBook Pros have full x4 PCIe bandwidth. The left-side Thunderbolt 3 ports (all model years) attach to x4 PCI Express Root Port #5 – 9D14. We captured the PCIe arrangement of the Thunderbolt 3 15″ MacBook Pro (shown on the left) and Thunderbolt 3 Touch Bar 13″ MacBook Pro (shown on the right) in HWiNFO64 and labeled them for reference.
The 2018 Mac mini is one of the very few desktop Macs without a discrete graphics card. This is great news for eGPU users, especially in Boot Camp mode. Also more encouraging is the 65W processor and direct Thunderbolt 3 to CPU connection. In a way the 2018 Mac mini combines the most desirable elements of a powerful quad-core+ processor with iGPU-only graphics. On top of that is a pair of Thunderbolt 3 controllers to power four Thunderbolt 3 ports. Similar to the TB3 15″ MacBook Pro, the x16 PCI Express Controller is reserved for the optional 10Gb Ethernet card (uses 8 PCIe lanes), the x8 PCI Express Controller connects to the two USB-C/Thunderbolt 3 ports closest to Ethernet port (uses 4 PCIe lanes), and the x4 PCI Express Controller connects to the two USB-C/Thunderbolt 3 ports closest to the HDMI port (uses 4 PCIe lanes).
With the exception of a few base 21″ models, the iMac lineup is perhaps the most complicated for eGPU use in Windows Boot Camp. Due to desktop-only use, Apple deemed there’s no need for multiple GPU configuration like the 15″ MacBook Pro. Thus they disabled the Intel iGPU in the iMac firmware (Radeon dGPU models). AMD XConnect and Nvidia Optimus are not available for these iMacs so our options are limited to either running the eGPU with an external monitor or Windows 10 1803+ (manual graphics switching) for internal display loopback. One positive news is the full bandwidth four PCIe lanes directly attached to CPU for Thunderbolt 3 connection.
AMD eGPU vs Nvidia eGPU
What’s the best eGPU for Boot Camp is a question we’ve seen a lot. The answer is a sad joke that long-time Mac users understand all too well; get AMD graphics cards for macOS and Nvidia graphics cards for Windows. One AMD eGPU to rule it all in both operating systems is possible but you’d have to work for it. If you decide to go with the green team, stop reading any further and go hot-plug the eGPU to your Mac. More than likely it will work without much trouble. For the red team, get ready to go on an adventure called, error 12. These are the AMD Radeon cards with native macOS eGPU support and can function in Boot Camp.
|Radeon Pro||Radeon RX|
|Pro WX 9100||Radeon VII|
|Pro W5700||RX 5700 XT|
|RX Vega Frontier Edition||RX Vega 64|
|Pro WX 8200||RX Vega 56|
|Pro WX 7100||RX 480 / RX 580|
|Pro WX 5100||RX 470 / RX 570|
|Pro WX 4100||RX 460 / RX 560|
Large Memory Allocation
The name of the game is to allocate enough resources for the external graphics card to function in Windows 10 while not severely crippling other functionalities of the laptop. Other than the Late 2016 Thunderbolt 3 Macs, 2017 and newer models have “Large Memory” allocation in the firmware. Large Memory allocation helps Windows handle a PCIe component such as an external graphics card without error 12. Through many different user build guides, we have gathered not only setup procedures but also pre-compiled DSDT override files for those who need to patch the firmware of Late 2016 MacBook Pros.
Mac computers with only two Thunderbolt 3 ports would likely be able to negotiate enough resources for eGPU automagically. If error 12 arises, disabling the connection to the non-essential components such as iSight camera or Ethernet controller would usually resolve it. Macs with four Thunderbolt 3 ports are slightly harder for eGPU implementation due to an extra Thunderbolt 3 controller and two more Thunderbolt 3 ports. It’s best to confirm whether the Mac firmware has “Large Memory” in Device Manager > View > Devices by resources to determine the next steps.
Only a handful of Macs can work with an eGPU via hot-plug [connect at Windows Desktop] in Windows Boot Camp. The majority of reported successes are with Nvidia graphics cards. AMD graphics cards are likely to produce error 12. We have also learnt timed hot-plug [connect at Windows logo & spinning circles] can work with both Nvidia and AMD eGPUs. The most reliable method is cold-plug [connect when Mac is OFF]. Here are the recommended steps to set up an external GPU with a Thunderbolt 3 Mac and the reasons behind them. If you’re familiar with using an external graphics card in Windows 10 via Boot Camp, proceed to the summarized setup procedure.
Step 1: Install DDU & Restore Point
As of Fall 2019, the best version of Windows 10 to use with an eGPU is 1903, specifically OS Build 18362.295 (KB4512508). Microsoft has improved hot-plug detection and handling of Thunderbolt 3 devices in this version. Mac computers greatly benefit from these changes in Win10 1903. With the exception of a few models such as 2017 13″ MacBook Pro (boot loop when paired with Radeon eGPU), most Macs work well with this latest Windows version. If you experience issues, go with Win10 1809. Also keep in mind Security Updates may break eGPU compatibility. Windows 10 1903 [OS Build 18362.329 and 18362.359] for example causes most Macs to experience error 12 with an AMD eGPU. It’s best to disable automatic updates once you get a working configuration.
There are setup guides to install Windows on an external hard drive so that the internal PCIe flash storage can be preserved solely for macOS partition. We don’t recommend having the Windows volume on an external drive because it would complicate the eGPU setup process and may cause unforeseeable maintenance issues. If your MacBook Pro has a limited amount of storage, partition the Boot Camp volume with 50GB for Windows installation and save the rest for the macOS partition. You can then install all software and games on an external hard drive.
Windows 10 can detect new graphics cards and install the drivers automatically. However the drivers are not up-to-date and sometimes interfere with setting up an external GPU. We recommend using DDU to uninstall the Radeon Pro drivers that came with Apple Boot Camp drivers (part of Boot Camp Assistant in macOS). DDU can also disable Windows automated graphics drivers installation so that you have full control of which drivers version to use. If you have a Mac with Radeon dGPU and plan on using a Radeon eGPU, the modified drivers from bootcampdrivers.com is the best approach to use both dGPU and eGPU concurrently.
Keep in mind Apple itself has not provided support for external GPU in Boot Camp. Therefore the following steps to set up an external graphics card with your MacBook Pro can possibly cause bootup issues. We highly suggest the use of the Windows System Protection feature. You can create manual Restore Points that capture snapshots of Windows in order to revert changes should you run into trouble.
Step 2: Use EFI boot loader
When booting into an operating system that is not Mac OS, the Mac firmware tends to deactivate the internal GPU if there’s another GPU present. For example, the 15″ MacBook Pro boots into Boot Camp with only the Radeon Pro dGPU activated. Only having an Intel iGPU, the 13″ MacBook Pro sometimes hangs at the Windows bootup process if an eGPU is connected. Similarly the Radeon dGPU in MacBook Pro or iMac would be deactivated as well when there’s a connected eGPU at boot. Obvious symptoms is a stuck Windows logo during boot that flickers or worse a black screen on dGPU Macs. If you have an external monitor connected, you may be able to see Windows Desktop on it (given proper drivers for eGPU was installed). To remedy this hurdle we rely on apple_set_os.efi to trick the Mac into believing it’s booting into macOS. This boot loader file can be stored on either a USB drive or in the ESP partition of the Mac’s internal drive through the use of an EFI boot manager.
We strongly recommend using Goalque‘s automate-eGPU EFI, a boot loader that conveniently integrates apple_set_os.efi file. He provided clear instructions on creating a USB thumb drive so that the internal drive stays intact. It’s possible to create a small FAT partition on the internal drive as well if you prefer not to attached an external drive for the boot loader. rEFInd is another alternative for the need to use an external USB drive. Once the iGPU is active in Windows, we want to make sure it has the latest Intel graphics drivers. If the iGPU shows up in Device Manager as “Microsoft Basic Display Adapter,” you may need to install the Intel graphics drivers manually.
In the 2016 and 2017 15″ MacBook Pro, we want to attach the iGPU to the internal display so that we can use eGPU internal display acceleration and disable the dGPU if needed. This is where 0xbb’s integrated.bat comes in. The purpose of 0xbb’s GPU-switch script is to assign a particular GPU to the internal display at the next boot. We want to run integrated.bat in Command with Administrative privilege to execute iGPU attachment to the internal display. Upon the next and subsequent restarts, Windows will use the iGPU to power the Mac internal display. Microsoft Visual C++ 2013 may be required to run this script successfully. Users of 2018 & 2019 MacBook Pro with a Radeon Pro dGPU (both 15-in & 16-in) are encouraged to visit the build guides. This is due to Apple completely disabled the Intel iGPU in these Mac laptops. Force-activation and internal display attachment of the iGPU may cause black screen issue.
Warning: One important thing to keep in mind is that you have to re-enable PCIe Controller x16 – 1901 in Device Manager (if it’s disabled) then re-attach the dGPU to the internal display by running dedicated.bat prior to booting back into macOS. Otherwise the next Windows boot will hang due to macOS force-attaching the dGPU onto the internal display. This is another reason why we recommend creating manual restore points in Windows. In the event Windows fails to boot, you can go back to a safe point without redoing the entire setup process.
Step 3: Solve error 12
The last and most challenging step is to overcome error 12 (not enough resources for eGPU). This almost always happens on a Mac with dGPU paired to an AMD Radeon eGPU. There are several methods to resolve error 12. This is also called “yellow-banged,” as visually identifiable in Device Manager by the yellow triangle and black exclamation. A reasonable workaround is to disable PCIe controllers/bridges to free up enough resources so that Windows can handle hosting an external GPU. The PCIe arrangement is different for each Mac but the approach is similar. We start with the PCIe component with the least usage.
In the 13″ non-Touch Bar MacBook Pro, disabling the iSight camera PCIe bridge would likely resolve error 12. The 13″ Touch Bar is slightly different in that it has one more Thunderbolt 3 controller to handle the two additional Thunderbolt 3 ports on the right side. Some have success by disabling the PCI Express Root Port #9 – 9D18 that connects to the right Thunderbolt 3 ports and using the lower left Thunderbolt 3 port [closest to the TAB key] for eGPU.
The 15″ MacBook Pro is rather challenging to allocate resources for the external graphics card. By disabling the x16 PCIe controller – 1901 to the discrete Radeon Pro GPU, we found Windows likely has enough resources for an external GPU. From eGPU.io members’ experience, Windows has a harder time with AMD cards. When we tried AMD eGPU, we needed to also disable the PCI Express x8 Controller – 1905 that connects to the left Thunderbolt 3 ports. External GPU works reliably using the right-side ports that connect to the PCI Express x4 Controller – 1909. Again 2018-2019 15″ & 16″ MacBook Pro have a completely disabled iGPU and would need to use Windows Hybrid graphics instead of AMD XConnect/Nvidia Optimus through the Intel iGPU.
Boot Camp eGPU Setup Procedure
As the combination of of Host laptop + eGPU enclosure + Graphics Card grow exponentially larger, there’s no one setup guide for all. The best and easiest approach is to check our External Graphics Card Build Table which has hundreds of Boot Camp eGPU successes. Find the build with matching components and Windows version and follow the instructions in the build guide would be a good start. For example, here are all the steps from start to finish to get an external graphics card running on a 2017 13″ MacBook Pro. Do not connect the external GPU to the Mac laptop until instructed to do so. Download the linked resources at each step.
Windows Booting Procedure
We’ve tested different combinations of the R9 Fury/X, RX 480, RX 580, GTX 980 Ti, GTX 1070, and GTX 1080 with the AKiTiO Node, Gigabyte AORUS Gaming Box, Mantiz Venus, Razer Core, and Sonnet Breakaway Box on a Late 2016 15″ MacBook Pro, a Mid 2017 13″ non-Touch Bar MacBook Pro, and a Mid 2017 13″ Touch Bar MacBook Pro. External GPU works well and reliably once these steps are completed successfully. A normal boot procedure is as follows:
- Connect the external GPU to designated Thunderbolt 3 port and power MacBook Pro on
- Cold boot shows rEFInd boot menu (hold OPTION at boot if apple_set_os.efi is on USB drive)
- Press ENTER on apple_set_os.efi boot item – MacBook Pro‘s display flashes briefly to confirm selection
- Press ARROW key to Windows 10 volume then press ENTER to boot
- Windows loads to Desktop and AMD XConnect/Nvidia Optimus icon shows up to confirm eGPU activation
There are reports of hot-plug possibilities. However, we’ve found it’s not reliable and can crash Windows. Furthermore it may cause corruption in the bootup process. We’ve made a habit of always creating a manual restore point following a change. You never know when Windows will decide it can’t boot into the Desktop anymore. Having these restore points labeled for each step allows you to go back to a particular stage should something happen.
Apple can facilitate external GPU support in Boot Camp by optimizing its firmware. We’re uncertain how many engineers are working on external graphics support for High Sierra. Boot Camp eGPU is likely low on the list of priorities, if on the list at all. We’ve opened a thread to petition for support of eGPU in Boot Camp. Please voice your opinions so that Apple will hopefully focus more attention on Boot Camp Mac users.
We’re all learners as we venture into the territory of eGPU Boot Camp environment. If you know of a better procedure to setup and use external GPU in Boot Camp with a Mac, please share your experience with the community.
Apple has made some firmware improvements in 2017 and newer Macs. Windows 10 now shows “Large Memory” under Device Manager » View » Resources by connection. This means some 2017+ Macs may be able to use Nvidia eGPU without encountering error 12, no workaround needed. AMD eGPU typically requires more resources and error 12 is still an obstacle. Recent versions of Windows 10 (18362.365 and newer) produce error 12 on many Macs. The only remedy is to downgrade Windows 10 to an earlier version without this issue.
Great write up as always @theITSage - a very useful summary!
I appear to be one of the fortunate few who's MBP-2017 benefits from the later, enhanced F/Ware. I have had no issues with Code 12 and my Device Manager does indeed display the noted 'Large Memory' allocation to the PCI bus; which is a relief!
Apple has made some firmware improvements in the mid-2017 MacBook Pro. Windows 10 now shows "Large Memory" under Device Manager » View » Device by resource. This means some Mid 2017 MacBook Pros may be able to use eGPU without encountering error 12, no workaround needed.
Impressive guide, just created a back up/restore point of my current set up so I can roll back if/when I mess it up trying my 570 out again...
@Wunair, yes there is an alternative method of fixing error 12 on 2016 & 2017 15″ MBPs by having the eGPU allocated into ‘large memory’ instead of disabling PCI bridge. Here are the guides to do that:
- 2017 15″ MBP error 12 fix by reallocation to ‘large memory’ script by jzfgs
- 2016 15″ MBP error 12 fix using Clover DSDT memory override by Mikeal
@Wunair, also keep in mind AMD eGPUs seem to require more resources than Nvidia eGPU. If you’re currently using an Nvidia eGPU, disabling x16 PCI Express Controller – 1901 [connects to Radeon Pro dGPU] would free up enough resources to resolve error 12. This way you can use TB3 ports on both sides.
So I believe I am about there, but when i log into windows (without egpu connected) the desktop displays, then flashes black, and then back to the desktop again. It appears that it's attempting to switch from the igpu to the dgpu.
I installed rEFInd, copied apple_set_os.efi over to the boot partition. Select it, then go over to windows and tell it to boot. I disabled the x8 1905 pcie bit, installed the intel video drivers, and ran the integrated.bat file.
Ideally windows would be functional sans egpu if needed, and then with egpu for gaming if desired and for firmware updating. Ideas?
Oh yeah. If I start menu open, it stops flashing back and forth...
Late 2016 15" MacBook Pro
Late 2017 13" HP Spectre x360 + RX [email protected] (Mantiz Venus) + Win10 // 8th Gen i7 8550u, 16gb ram, 512gb ssd
Vega 56 (flashed with 64 bios)
I have already installed refind and copied the .efi file. However, when I boot into Windows, I can see two Microsoft basic adapter things. But when I tried to install the Intel graphics driver, it always said that my system is below the minimum requirement. How can I fix this?
I got a macbook pro retina which is MacBook Pro (Retina, 15-inch, Mid 2015), it only got the Intel Iris Pro 1536 MB and only comes with the thunderbolt 2. I was wondering if this guide can work on my computer since your mentioned "This explains the ease of eGPU implementation on iGPU-only hosts while dGPU + iGPU hosts such as the Thunderbolt 3 15″ MacBook Pro is harder to accomplish."
But since I know nothing about the "PCIe connection with thunderbolt" issue, which makes me really uncertain about purchasing a e-GPU set up ...
So, can you make the e-GPU working on the Macbook Pro retina with thunderbolt 2, and running it perfectly on its
Looking forward to your reply.
Frank from Australia.
I have an LG 5k Ultrafine display which needs to be connected via Thunderbolt 3. I wish to use this display as an external display, and don't want to use my internal 15" display on my Macbook pro. In order to have the eGPU drive the 5k display via thunderbolt 3 (connected to my macbook) would i disable the 1901 PCIe port? Or would I disable 1905? Or is it considered an external display even though it's connected via thunderbolt 3 and thus I don't have to do either?
Not sure if it was you who messaged me (it appears to have vanished - this forum's software is buggy as hell IMO) but I'm afraid my experience isn't transferable. I use the 13inch model and dont need to disable anything. The LG 5K gets treated like an internal screen by the eGPU and comes with the same sort of performance loss.
Not sure if it was you who messaged me (it appears to have vanished - this forum's software is buggy as hell IMO) but I'm afraid my experience isn't transferable. I use the 13inch model and dont need to disable anything. The LG 5K gets treated like an internal screen by the eGPU and comes with the same sort of performance loss.
Gotcha. So in terms of setting up the eGPU, I need to set it up as if I don't even have this 5k monitor because it's being recognized as an internal display, correct? Futhermore, have you had any updates on possibilities of connecting the 5k to the graphics card?
Got my 1080ti in today and went about installing the card. Everything went buttery smooth. Still working out how to get it correctly working with my LG 5k monitor, but I have no errors, and the system recognize the 1080ti just fine.
@itsage, I've just received my 1080 Ti, installed into a Mantiz Venus, connected via TB3 to 2016 15" MBP with R460, connected the card to an external monitor, followed the guide fully on macos H.S. & win 10, iGPU is working as expected, disabled both PCIe 16x 1901 and PCIe 8x 1905, and using the right side TB3.
still the 1080 Ti shows error 12 in device manager whatever I do, I restarted win many times, and in every time I'm activating the apple_set_os.efi and boot windows from rEFInd, then disable / enable both PCIe again, but with no luck!!!
do I miss anything here or it's macos H.S. prevents the setup from functioning? please advise...
Update: after being frustrated last night, today I updated macos on the same exact setup with the new supplemental update, and now with pessimistic trial, I decided to boot into windows (boot camp), I discovered that rEFInd is gone (may be due to a new firmware update in the supplemental update) so I decided to boot the usual way by holding the "option" key, without activating any apple_set.efi and without rEFInd at all.
And BOOOOOOOM... windows recognized my EVGA GTX 1080 Ti without code 12 (attached screenshot)
And even without disabling any of the PCIe controllers (attached screenshot)
Then I performed some benchmarks (attached screenshots) including CUDA-Z with the expected performance.
I restarted widows again to make sure everything will run smoothly as per the first boot, and yes... everything works just fine without any error.
Moreover, I'm connecting many peripherals to the Mantiz Venus, and to the left side TB3 using Belkin TB3 Express Dock Station, even windows 10 (bootcamp) is on an external TB3 raid SSD by Glyph
This is just amazing...
I do appreciate all support and help I found on this magnificent forum, and would like to thank all eGPU gurus for their priceless help to average users through this forum.
Mohammad Katayen (mklegend)
Great write-up - which I am trying to follow. I am on High Sierra 10.13.1 Beta - 2017 13-inch i7 MBP no touchbar.
No problem in Windows 10 anniversary with GTX 1080, Akitio Node,- but when I tried to use an RX 580 in Windows (worked great with High Sierra) -problems problems problems.
Easily detected the AMD card in the Node...but - Error 12. I tried to disable and re-enable the RX580, the the camera, the thunderbolt ports and used refind with apple_set_os.efi, then after updating the intel and Radeon drivers (still have error 12) - I now have a flickering windows logo in the center of my screen at all times including before the apple logo on startup even into High Sierra, it persists floating and flickering in the middle of my High Sierra desktop. I have reinstalled the last two sets of intel drivers. used DDU to clear both intel and Radeon drivers to no avail. Unfortunately I did not make a "DDU safe" manual start point before this happened.
Since this is a new laptop (purchased 18 days ago) and I have not made it my working one yet and I was online with apple support late into the night we did some pretty extreme things- wiped the SSD completely, reset the NVRAM and reset the SMC several times. We then went back and through the internet clean installed Sierra-no bootcamp and still the flickering windows logo remains in the center of the screen. It's been there since shutdown after the Windows 10 Intel GPU driver update. Does not effect external screens through thunderbolt hdmi adapters - only the laptop screen.
I've tried this twice now and, each time I disable the x16 PCIe controller – 1901 to the discrete Radeon Pro GPU, Windows locks up, cannot be restarted, and has to be wiped and reinstalled. I'm on a one day old 2017 MBP w/ Touch Bar and the bigger 560 dGPU. Any suggestions??? I would LOVE to be able to use the eGPU in Boot Camp
@Humanovation, Windows crashed because the dGPU was still powering the internal display. Make sure you run integrated.bat with Administrative privilege and restart into Windows so that the iGPU is powering the internal display.
Thanks so much itsage! I 'll give that a try. However, first, I'm going to buy Winclone and clone my bootcamp partition so that I don't have to reinstall Windows from scratch every time I screw something up ;-). Will let you know how the integrated.bat file works.
In Step 3, 2013 Visual C++ was linked in case you encounter an error. – https://egpu.io/bootcamp-setup-guide-tb3-macbook-pro/#summary
Yay!!!!!!! It's working ... finally! Running the Heaven benchmark (Boot Camp - Windows) util and getting 90-110 FPS at High quality 1080p. That is about 20% better than I was getting running it in OS X. Going to attach my HTC Vive and see if I can get SteamVR (Windows version) running 😉
Slight issue with Vive VR … headset needs to be run on the same graphics card as the SteamVR program (which right now is being run on the iGPU). Will try to fix by going from eGPU out to monitor via DisplayPort and to Vive Headset via HDMI, thus running them both on the same graphics card … had to order the right cable from Amazon so will report back in two days 😉
Update on persistent windows logo- solved.
After reinstallation of the bootcamp drivers in windows and a reboot it vanished. I imagine it was the intel driver software in bootcamp. It reappeared and was persistent again after I left the computer on overnight Friday night and it went to sleep. Was able to clear it with reinstallation of the bootcamp software and a reboot after NVRAM and SMC reset during which it "faded". Next time I will just reinstall bootcamp driver software. One odd feature of the persistent logo and flicker - it seems to slowly "fade". I have done a net search and this is reported happening without an egpu on 2016 MBPs as well unfortunately I did not find a solution in that search so I don't know if the driver reinstall would fix that on the 2016 MBP.
Long story short I was having 2 issues: first one, whenever I chain loaded apple_set_os.efi first, Windows 10 would crash and reboot. After consulting with Mantiz John and Nando4, I think the cause of this for me was that I was enrolled and using a windows insiders preview version. After going with 1703 version of windows and opting out of windows insider previews, I was able to enable the Intel iGPU on Windows.
My second setback was that my Mantiz Venus, was not properly detected or so I thought, as I would only get the 15D2 thunderbolt device appearing on the Device Manager console. The reason for this I discovered was that I was hot-plugging it and same as with Mac OSX, it needs to boot up with it plugged in. Again, all this applies to my setup, but as the guides have a broad audience, they mention to plug the eGPU on different parts of the bootup. For me, the best method is so far, to shutdown the mac, plug the eGPU, then turn the mac back on.
Boot with reFind selecting apple_set_os.efi(previously running the integrated.bat as mentioned on the guide), but I am diverting from the guide a bit by after apple_set_os.efi, chainloading Clover with the modified DSDT and then booting windows bootcamp with Clover.
Finally i see some results!!!
My configuration - Macbook pro 2016 with radeon pro 460 4gb, Akitio node tb3, nvidia gtx 1080Ti via bootcamp.
I did everything according to guide, but i have 1 issue and 1 question!
ISSUE - gtx1080ti is visible, but works only with external monitor.. any benchmarks do not want even start on internal monitor like on your video. And geforce menu says there is no monitor connected to graphics card.
I did everything in 5AM so there is a chance that I miss something, but what? ))
QUESTION - if I wannt just take my macbook without eGPU to trip or something, and work with it like before, with radeon pro 460, how can I do that and dont brake everything i do for eGPU? (on windows)
Thanks for your work!
@Humanovation : How did you end up getting past this issue with the Vive? "headset needs to be run on the same graphics card as the SteamVR program" What, if any additional hardware did you have to use? I have: 15" Mid-2017 MacBook Pro, Sonnet Breakaway Box, AMD RX 580, Windows 10 on removed link It seems that SteamVR content without laptop display mirroring works great, but SteamVR content that mirrors the HMD on the laptop display requires the USB and HDMI HMD to be connected to the same graphics removed link Is this the same problem you encountered and solved? If so, how? Thanks!
– I got a DP to HDMI cable and connected that from the RX 580 to my TV. – I set the TV up to extend my laptop’s display rather than mirror it, and then set the TV as the main display in Settings>Displays. – Plugged the Vive headset into the HDMI out on the RX 580 – Open SteamVR and/or any associated programs so that they open on the TV and not on my MBP display. That’s it … you are using the RX 580 to drive both your TV and the Vive headset while the iGPU continues to drive the laptop display.
I'll try to make this as clear as possible to understand because even I am slightly confused what is happening.
So firstly I got my Aorus Gaming Box and set everything up as above and it worked great! But then I became stuck in a boot-loop and the manual restore points I made wouldn't show so I just ended up clean installing windows on my 2017 15" MBP.
Here is where my problem lies when I open device manager on windows (not running on integrated) the integrated card doesn't show what so ever, not even as microsoft basic display driver. So when I run the intergrated.bat and then boot using the apple_set_os.efi in refind then boot to windows it just hangs. I have enabled show hidden devices in device manager with no results either, it is almost as if the internal graphics card is not there, which is obviously false as if i disable the radeon pro 555 the internal kicks in. Even then it does not display in Device manager. Any help would be great as i'm pretty stuck at the moment.
I managed to get this working by disabling the radeon 555 in device manager. Then running the integrated script,booting into windows and then everything worked out fine. Except I am stuck with a constant screen flicker when the display is idle, but if a youtube video is played then the flickering stops, any ideas?