Setup & Software Discussions
Boot Camp eGPU Setup Guide - Windows Gaming with Macs
 

Boot Camp eGPU Setup Guide - Windows Gaming with Macs  

 of  7
  RSS

(@stanley_yung)
New Member
Joined: 2 weeks ago
 

I have a MacBook Pro 15 late 2016 with a AMD Radeon pro 460. I am trying to install the Aorus gaming box RTX2070 eGPU.

In Step 3 Point 1. “ Connect the eGPU to a right TB3 port then boot into Windows - Boot Selector” when do I plug in the TB3? When the computer is off? Or when it is in the rEFInd boot screen?

Here are the 3 scenarios that I encountered.
1. If I plug the TB3 when the system is completely off, the screen just don’t turn on. But I can see the eGPU fan spinning so I guess there is power but the screen just not on.
2. If I plug it in the rEFInd boot screen, the selector freeze and I can not select anything. Or in the case that the selector is working, but it stay in the spin of ring and windows never launch.
3. If I plug the TB3 in Windows that was booted from EFI and restart, my display turn black and my keyboard light stays on. I needed to unplug the TB3 and force shut down the system then restart.
4. In this scenario, I let windows turns on without plugging the TB3. In device manager I can see two display adopters, Intel(R) HD Graphic 530 and Microsoft Basic Display Adapter. When I plug in the eGPU, another Microsoft Basic Display Adapter with a yellow exclamation mark on it popped up(code 12). And the system detected the RTX2070 display card and ask for restart. I unplugged the TB3 and restarted the system (so I don’t get black screen) and I was able to install the RTX 2070 driver. But after a while, the RTX 2070 in display adapters encounter the Code12 again..... I disabled PCIe Controller (x8) - 1905 like Step 3 Point 3 says, unplugged the TB3 and restated but the Code 12 is still there. So I disabled PCIe Controller (x16) - 1901 as well, unplugged TB3 and restarted. But this time, something new happened, in the spin of ring, the ring just keep spinning but never able to enter windows. I need to force restart and launch windows by not hitting ENTER on “boot apple_set__os.efi from EFI” and enable PCIe Controller (x16) - 1901 back on and boot again with “boot apple_set__os.efi from EFI”. But still this doesn’t solve the code 12 problem.

In summary, I have the following 3 problems or questions

1. When should I plug in the TB3 and install the eGPU? Is plugging it when windows is up then installing it correct?
2. How come the spin of ring keep spinning but windows doesn’t launch by disabling PCIe Controller (x16) - 1901 which is the dGPU?
3. I already disabled both PCIe Controller (x8) - 1905 and PCIe Controller (x16) - 1901 but code 12 still appear on the RTX 2070 display adaptor..... there should be enough resources for the eGPU by disabling 1905 and 1901 right?

I am a beginner on messing around with computer, it took me almost 24 hours to get here because I encountered the same thing at the beginning and I thought re-install boot camp and have a clean start can solve the problem but it didn’t. Please help me. I have been wanting to game in a eGPU for two years and i final got it but I m stuck now....

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
itsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
 

@stanley_yung I feel for your frustration with setting up an eGPU on this particular MacBook Pro. I had one when we started this website and I learned a lot of things on it. I sold it then actually bought another one because I missed the challenge.

I have not used an Nvidia RTX eGPU with the 2016 15″ MacBook Pro recently to give you the exact step-by-step. What I recall is a firmware compatibility between the RTX series cards and the Mac. This causes the boot hang when you have the RTX eGPU connected prior to boot. My recommendation is to follow this build guide then hot-plug the RTX eGPU once your MacBook Pro fully loads Windows.

Best ultrabooks for eGPU use

eGPU enclosure buying guide


ReplyQuote
(@agustin_karque)
New Member
Joined: 2 weeks ago
 

I have installed all of that, but the system doesn’t use the eGPU, it still uses the 650M on my MacBook Pro Mid 2012.
How do I fix this? Any ideas?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
joevt
(@joevt)
Honorable Member
Joined: 2 years ago
 

My Mac Mini 2018 has Windows 10 1803. How do I safely update to Windows 10 1903 OS Build 18362.295? I have a 1903 installer from July if that helps. The Windows ISO download page has an installer from May. I think either of those should be fine since .295 is August?

 

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
itsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
 

@joevt Either one of those ISOs should be safe. The OS Build is 18362.20 on Win10 1903 V1 ISO. Once your 2018 Mac mini runs the good version, disable Windows Update service completely to prevent automatic updates. Also manually create restore points to revert back should you need to.

 

Best ultrabooks for eGPU use

eGPU enclosure buying guide


ReplyQuote
joevt
(@joevt)
Honorable Member
Joined: 2 years ago
 

@itsage As an experiment (and because I didn't want to create a USB stick for update or reinstall Windows), I tried just using Windows Update. It installed the latest 1903 18362.418 (there were times when the screen remained black, I just left it alone until it booted back into Catalina, then I restarted into Windows to continue the install, repeated a couple times until I could log into Windows). My apps and settings remained from before the update which is nice.

There was an uninstall option for KB4517389 which is the KB for that version 418. Uninstalling that gives version 18362.1. Then I downloaded KB4512508 to install that. Now I am at build 18362.295.

I connected my eGPU to see what would happen (still using iGPU). Some freezing for a few seconds, then some automatic driver updates or something (where do I see progress for those? stuff is happening while I'm not doing anything), then after about 5 or 10 minutes the display connected to the Radeon RX580 turned on. All this without automate-eGPU EFI  though I think I'll not to install that later?

Windows says I should restart for some hardware changes. Before restarting I see that "AMD XConnect" and "Dolby Atmos" was installed (shows in Notifications) and AMD Settings (shows in "Uninstall or change a program"). I launch AMD Settings (RADEON SETTINGS) then a notification from CNEventWindowClass appears "The system has detected a problem with the connection between your computer and the DisplayPort display that will prevent you from using the highest resolutions and/or refres" the rest of the message appears in RADEON SETTINGS "h rates. For more information". I think this was caused by the display being connected to a DisplayPort 1.4 MST hub (HP Thunderbolt Dock G2 connected by GC-TITAN RIDGE). A DisplayPort 1.4 MST hub reduced total bandwidth by a few MHz (for example, the DisplayPort 1.4 display that I'm using has a 4K 120Hz timing but I need to reduce it to 117Hz in mac OS. In Windows, 120Hz timing exists, but it is 6 bpc color).

Radeon Software is Version 17.1.1 (Is there an update drivers button or will it tell me if there's a newer version later?) I click on "Display" tab in RADEON SETTINGS and get another notification from CNEventWindowClass "Radeon Settings has detected that one or more high-DPI panels are connected to your system. Enabling Virtual Super Resolution will increase your resolution and allow you to customize DPI settingings (the iGPU and eGPU have 4K displays). Clicking around some more and I get a new notification from Settings "Restart required Your PC needs to be restarted to finish setting up this device: PCIe Bus" and "Device is ready 'Audio Device on High Definition Audio Bus' is set up and ready to go."

Changing the connection of the display from the dock to the RX 580 caused a hang. Disconnected eGPU. Restarted. Anyway, hot plug of eGPU works and I didn't need to disable any devices in Device Manager.

Driver Genius 19 found some new drivers: AMD High Definition Audio Device Drivers and AMD Radeon Adrenalin Edition Graphics Drivers as well as Intel HD/UHD Graphics Drivers and Intel Chipset Drivers so I installed those too.

Of course, restarting with the eGPU connected causes the iGPU to be disabled, so I created a FAT partition on an external USB for automate-eGPU EFI . gave it a disk label, and a disk icon too. When I boot into it, it says "egpu not detected". I click q to go to boot menu, select Windows, press return, and it seems to hang in the boot menu. There's no boot log like with Clover so I don't know what's going on.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
itsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
 

@joevt Win10 1903 18362.30 to .295 are very eGPU friendly. I found out about AMD eGPU hot-plug possibility in Boot Camp back in June. This is not unique with the 2018 but almost all Macs since 2017 model year. Even the 2016 15″ MacBook Pro worked similarly once DSDT.aml was applied for Large Memory allocation. By default Windows would search and install new device drivers automatically. Radeon drivers 17.1.1 sounds about the same version I got when I let Windows handle the AMD eGPU. I always use DDU to remove older graphics drivers then manually download and install the latest version.

Regarding automate-eGPU EFI boot manager, it’s a bit more cloudly without knowing how you have everything hooked up prior to boot. On my 2018 Mac mini setup for example, I have the ASUS USB-C monitor connected to Thunderbolt 3 port #1 and AMD eGPU (w/ Samsung CHG90 monitor) connected to port #2. Holding OPTION would bring up the boot screen on the ASUS USB-C monitor. Catalina firmware would show the boot screen on the monitor connected to a supported AMD eGPU when no monitor was running off iGPU. At the boot screen I have three volumes to choose (all are on the internal drive).

Select macOS volume works kinda funny during boot. There are horizontal color lines on the eGPU-connected monitor. The Apple logo and progress bar would switch back on forth between iGPU-connected and eGPU-connected monitor. Select Windows volume works as you would expect with the Windows logo and spinning circles on the iGPU-connected monitor until Radeon drivers kick in. Login screen on Windows Desktop would then appear on eGPU-connected screen only. Select EFI volume brings up automate-eGPU EFI screen. The bottom line “eGPU detected/not detected” doesn’t always work correctly. The line with all present graphics card PCI IDs is what I look at. Hit [q] to proceed and arrow down to Windows to finally boot. Windows logo and spinning circles show on iGPU-connected monitor and eGPU-connected monitor would come on during login screen.

I’d recommend creating the automate-eGPU EFI volume on the internal drive as shown above. I have been using this boot volume configuration on all Thunderbolt Macs without issues. You can set automate-eGPU EFI to come on by default at every boot too. This is useful for people that boot into Windows more often than macOS. Once in a while the 2018 Mac mini would act up when you want the Boot Screen. I’m not exactly sure why this happens. It could be due to my USB-C monitor needing bus power. Usually connecting through the HDMI port to a different monitor would sort it out for me.

This post was modified 7 days ago

Best ultrabooks for eGPU use

eGPU enclosure buying guide


ReplyQuote
joevt
(@joevt)
Honorable Member
Joined: 2 years ago
 
Posted by: @itsage

The bottom line “eGPU detected/not detected” doesn’t always work correctly. The line with all present graphics card PCI IDs is what I look at. Hit [q] to proceed and arrow down to Windows to finally boot. Windows logo and spinning circles show on iGPU-connected monitor and eGPU-connected monitor would come on during login screen.

I’d recommend creating the automate-eGPU EFI volume on the internal drive as shown above. I have been using this boot volume configuration on all Thunderbolt Macs without issues. You can set automate-eGPU EFI to come on by default at every boot too. This is useful for people that boot into Windows more often than macOS. Once in a while the 2018 Mac mini would act up when you want the Boot Screen. I’m not exactly sure why this happens. It could be due to my USB-C monitor needing bus power. Usually connecting through the HDMI port to a different monitor would sort it out for me.

Ok, I do see the iGPU and eGPU in the GPU(s) line even though it says eGPU not detected. Clicking Load Windows causes a hang. The bottom line says "Saving...". Is it trying to write to NVRAM? This usually causes a hang in Ubuntu which is why you have to install it without installing grub. Maybe the same problem occurs here but you've used automate-eGPU v1.0.5 before on a 2018 Mac mini? Have you ever tried installing Ubuntu?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
itsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
 

@joevt I’ve used automate-eGPU EFI 1.0.5 on my 2018 Mac mini regularly. I have not tried installing Linux though. The “Saving…” hang is something I’ve experienced before too on different Macs. I don’t know what it’s trying to do when that happens. What I recall I did to fix it is to bless macOS volume as default boot then reformat my EFI volume and copy automate-eGPU EFI back onto it. 

 

Best ultrabooks for eGPU use

eGPU enclosure buying guide


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 3 years ago
 

@itsage

I am guessing the “Saving..” state could also potentially refer to some settings the app persists (such as remembering last booted disk), or writes to NVRAM. Checking with debug flag enabled might provide insight. 

This post was modified 7 days ago

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


itsage liked
ReplyQuote
Aegus
(@aegus)
Active Member
Joined: 1 year ago
 

@stanley_yung

I had the same issue when I was setting up my new 5700XT for bootcamp.

after 12 hours of troubleshooting this is what I found to fix it. From what I have seen the reason why it continues to load is because it's trying to activate your dEGPU however since you are receiving error 12, it cannot activate and there will never turn on.  You should use automate egpu efi with Refind as I find it easier, and it will be vital in the next part.

 

This is how I resolved it.

1. Boot into MacOS and setup the USB EFI https://egpu.io/forums/mac-setup/automate-egpu-efi-egpu-boot-manager-for-macos-and-windows/paged/7/#post-46528

2. Boot into bootcamp normally, DDU your drivers for your dGPU and eGPU. Restart, and boot back in normally.

2. Disable 1901, then hotplug your eGPU. You should receive the Microsoft display adapter. Install your drivers, reboot into Mac OS

3. Follow steps 1-3 here: https://egpu.io/forums/pc-setup/fix-dsdt-override-to-correct-error-12/#post-1598

4. Take your DSDT.aml file and put it on the EGPU EFI usb. Location should be D:\EFI\CLOVER\ACPI\WINDOWS

5. Boot into bootcamp using the EFI bootloader. In Refind youll have to select "Legacy" for the usb drive. Hit Q then hit windows

 

2016 MacBook Pro 15in Touch Bar + Breakaway Box 350 + RX 5700 XT


itsage liked
ReplyQuote
joevt
(@joevt)
Honorable Member
Joined: 2 years ago
 
Posted by: @mac_editor

@itsage

I am guessing the “Saving..” state could also potentially refer to some settings the app persists (such as remembering last booted disk), or writes to NVRAM. Checking with debug flag enabled might provide insight. 

I have Boot -> Debug set to true in my config.plist but it does nothing. Is it supposed to do something? Is there a different debug flag?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 3 years ago

ReplyQuote
joevt
(@joevt)
Honorable Member
Joined: 2 years ago
 

@mac_editor I'm a noob. Partition was formatted ExFAT. EFI apps can only write to MS-DOS (FAT) partitions. The automate-eGPU EFI app wants to create a "settings" binary file in the root directory of the FAT partition and the debug.log file in the misc folder. Or did something else create that file? If automate-eGPU EFI created it, then maybe it should have been created in an automate-eGPU EFI folder or have an automate eGPU name?

None of this explains why it failed when I tried it from the automate eGPU partition of the external USB disk which was correctly formatted as MS-DOS (FAT). I just noticed a "settings" binary file created yesterday on a different MS-DOS (FAT) partition on the USB disk (not the automate eGPU partition on the USB disk or the EFI partitions on any disks).

Anyway, it seems to have worked - the iGPU was not disabled when booting into Windows with the eGPU connected. The eGPU display remained disabled. Thunderbolt port connections: 1) iGPU display, 2) USB drive, 3) eGPU - disabled until I swap #2 and #3. Rebooting with this setup, the eGPU is not enabled again. What's the purpose of automate eGPU if I still need to hot plug the eGPU? I tried a third reboot, this time the eGPU display was active and the iGPU was disabled. Fourth boot, both eGPU and iGPU disabled. Weird...

I tried eGPU only for the first time. Apple boot icon appeared for a couple seconds on the eGPU display then the screen turned white.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
itsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
 

@joevt I’m using the 2018 Mac mini everyday with at least one eGPU attached. Boot Camp mode is used whenever I need to do tests. In the beginning, Secure Boot screwed with the booting process a lot and often left me confused. Since you’re booting off an external USB drive to use Windows, I guess you have disabled Secure Boot as well. Personally I have never used Boot Camp with an external SSD because it’s another component to manage.

Currently Mac mini‘s internal drive is partitioned three ways (24MB for automate-eGPU EFI, 55GB for Windows, and 200GB for macOS). Windows games and applications are installed on an external SSD which I connect when needed. Have you tried DDU to remove all Radeon graphics drivers and display device associations? Also check the box that says [Prevent downloads of drivers…] in DDU Options. Once this is done you can manually download and install the latest Radeon drivers from AMD website.

This post was modified 6 days ago

Best ultrabooks for eGPU use

eGPU enclosure buying guide


ReplyQuote
joevt
(@joevt)
Honorable Member
Joined: 2 years ago
 

@itsage I think I wanted to try to put Windows on an external disk but it didn't work. What I have is a small Windows boot loader on the external disk but it doesn't seem to work to boot the Boot Camp partition on the internal disk so I continue to use the Windows Boot loader that is on the internal disk's EFI partition. I haven't tried DDU yet. I wanted to experience the normal install procedure firstly. The external disk has a rEFInd boot loader partition.

For some reason my Mac Mini 2018 has started to boot into macOS with white screen on the eGPU display when eGPU + display is connected at startup (port 3) even with iGPU display also connected at startup (port 1). Disconnecting the eGPU allows the boot process to continue, and I can reconnect the eGPU after the Finder appears.

I moved the eGPU to port 2 and the eGPU did not turn white. Boot succeeded on the iGPU display (still connected to port 1) (looking at the ports, counting from left to right). This change did not fix the need to hot plug the eGPU in Windows though (but automate-eGPU does keep the iGPU enabled at least).

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
itsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
 

@joevt The current drivers for Polaris in Catalina is the cause of white screen on eGPU-connected monitor when it’s attached at boot. This behavior doesn’t occur with RX Vega and Radeon VII in my testings. It’s interesting the white screen issue only happens on your Mac mini when connected to Thunderbolt 3 Controller #1. Can you test whether you have Boot Selector through the eGPU-connected monitor through both TB3 Controllers? On my 2018 Mac mini I can only get the Boot Selector when the eGPU connects to TB3 Controller #1 [Port #3 & 4]. Maybe this white screen issue on Polaris cards is a side-effect of Boot Selector support in the Mac mini firmware. 

In Win10 1903 18362.295 or older, I can have the eGPU connected at boot and Thunderbolt device detection and XConnect work properly. Using automate-eGPU EFI would allows the Intel iGPU stay working alongside eGPU. Windows auto detection and drivers installation is nice for a fully supported system but it’s not the best approach on a Mac running Boot Camp. It may work at initial setup but the consistency of subsequent boots with eGPU is far from ideal. DDU gives you a clean start and full control of which drivers to use and with which TB3 Port/PCIe connection the eGPU associates.

Best ultrabooks for eGPU use

eGPU enclosure buying guide


ReplyQuote
joevt
(@joevt)
Honorable Member
Joined: 2 years ago
 

@itsage

I did some tests. iGPU display connected. Only one eGPU display connected. USB drive with LED connected to USB type A port. Ethernet connected. Display USB connected. Nothing else.
Thunderbolt port 1 (next to Ethernet): Startup Manger appears, select Catalina, white screen appears.
Thunderbolt port 2, 3, 4: Same (boot progress bar momentarily appeared on port 3, boot progress and Apple icon momentarily appeared on port 4)

Adding iGPU display (connected via built-in HDMI 2.0 port):
Thunderbolt port 1: First boot: input timing was not 4K 60Hz so it didn't work (my iGPU display only supports certain HDMI 2.0 timings). Set the correct timing by booting with eGPU into Catalina. Rebooted. Now boot up on iGPU Display works. Shutdown Retrying with eGPU.
Thunderbolt port 1: Second boot: Nothing appears on either display. HDMI is probably still broken in Catalina. I blindly press return (probably while in Startup Manager) then white screen appears. I guess I should stick with DisplayPort for iGPU display. Connect via Thunderbolt port 4.
Thunderbolt port 1 Third boot: Apple icon appears, Startup Manager appears on iGPU display, select Catalina, progress bar and Apple icon appear, progress bar progresses for a few seconds, green screen appears on iGPU display, white screen appears on eGPU display, disconnect eGPU, progress bar and Apple icon reappear, boot progresses to Finder.
Thunderbolt port 2: same
Thunderbolt port 3: same
Thunderbolt port 4: same (iGPU display moved to port 1)

All fail. Try to recreate my previous success with eGPU connected to port 2 and iGPU connected to port 1. Fail. Try again without going into Startup Manager. Success: Apple icon and progress bar appears on iGPU display, progress bar progresses, iGPU displays turns green as before for a couple seconds, but eGPU display does not turn white, Apple icon and progress bar reappears, boot progresses to Finder, both iGPU and eGPU displays work. I guess this means Startup Manger does some extra stuff that drawing Apple icon does not which then causes white screen later? I guess I should retest all ports without going into Startup Manager:
Thunderbolt port 1: Apple icon appears on iGPU display (connected to port 4), Progress bar appears, progresses, iGPU display turns green, progress continues, Finder, both displays working.
Thunderbolt port 2: same
Thunderbolt port 3: same
Thunderbolt port 4: same (iGPU display moved to port 1)

Repeating tests with eGPU display only, no Startup Manager:
Thunderbolt port 1: Apple icon appears, white screen
Thunderbolt port 2: same
Thunderbolt port 3: same
Thunderbolt port 4: same (progress bar appeared for a second)

 

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
viciousmoth
(@viciousmoth)
New Member
Joined: 4 days ago
 
Posted by: @itsage

 

I'd recommend creating the automate-eGPU EFI volume on the internal drive as shown above. I have been using this boot volume configuration on all Thunderbolt Macs without issues. You can set automate-eGPU EFI to come on by default at every boot too. This is useful for people that boot into Windows more often than macOS. Once in a while the 2018 Mac mini would act up when you want the Boot Screen. I'm not exactly sure why this happens. It could be due to my USB-C monitor needing bus power. Usually connecting through the HDMI port to a different monitor would sort it out for me.

Hi, does automate-eGPU function with MacOS Catalina? I am setting up a build of a Mac Mini 2018 to use with an eGPU for the first time and am unsure how necessary this EFI volume is for dual boot.  I have MacOS (for every day computing) and Windows (for gaming) both on the internal SSD.

 

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
joevt
(@joevt)
Honorable Member
Joined: 2 years ago
 
Posted by: @viciousmoth

I am setting up a build of a Mac Mini 2018 to use with an eGPU for the first time and am unsure how necessary this EFI volume is for dual boot.

You should be able to dual boot without automate-eGPU - just disconnect the eGPU before booting Windows. Then connect it when Windows has done booting.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
(@ruby_diansyah)
New Member
Joined: 2 days ago
 

Hi all, I need help here. I am on imac 21" 4k 2017 with radeon 555 inside. and connected with Mantiz egpu with Vega 58. I follow bootcampdrivers.com for all setup (Sep version ). now, the win10 recognize the egpu, but system said not enough port and need to fee it. 

can anyone please help me with this? i need to run my bootcamp win with multi monitors for trading apps. i really appreciate for any help ... thank you.. I am not willing to change my imac with pc because I need osx too and i already upgrade the ssd and memory up to 16gb.  

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
 of  7