External Graphics Card for MacBook Pro - Boot Camp eGPU Setup Guide  

Page 1 / 4 Next
 

theitsage
(@itsage)
Famed Member Admin
Joined:2 years  ago
Posts: 2522
September 10, 2017 6:10 pm  

Now that macOS High Sierra 10.13 officially supports external graphics cards, we've developed a reliable procedure to set up and maintain a functional external GPU in Windows 10 via Boot Camp. In the past month, we’ve tried many different solutions by reading through eGPU implementation guides. What we've found to work most reliably with a Late 2016 15″ MacBook Pro is a combination of apple_set_os.efi, rEFInd, integrated.bat, and the right-side Thunderbolt 3 ports. The 13" MacBook Pro is less involved to implement due to its lack of a discrete graphics card. Our goals were to have an integrated GPU active for eGPU internal display mode and a reliable Windows bootup without error 12.

External Graphics Card for 15" MacBook Pro - bootcamp setup guideExternal Graphics Card for 13" MacBook Pro - bootcamp setup guide

Why so serious?

Let's discuss graphics switching in Windows briefly. Forum member Sky11 explained the three modes in Windows 10 (Microsoft Hybrid graphics, AMD XConnect, and Nvidia Optimus) in this post. The crucial prerequisite is the Intel integrated graphics card for internal display acceleration with an external graphics card. Without a functional iGPU, eGPU would only work with an external display. 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. The worst-case scenario is when there's no iGPU present either due to the host firmware or its CPU configuration.

Prior to setting up an external GPU, it's a good idea to identify the routing of the PCIe connection over Thunderbolt 3 for each host. We used HWiNFO64 to check the arrangement of PCIe controllers and lanes on this Late 2016 15″ MacBook Pro (same as Mid 2017 model). The x16 PCI Express Controller connects to the Radeon Pro dGPU. The x8 PCI Express Controller connects to the left-side USB-C/Thunderbolt 3 ports. The x4 PCI Express Controller connects to the right-side USB-C/Thunderbolt 3 ports. It makes total sense to disable the entire line of communication to the dGPU so that we can free up resources for the USB-C/Thunderbolt 3 ports.

The 13" MacBook Pros have no direct Thunderbolt 3 to CPU connection. All PCIe lanes are routed through the platform controller hub (PCH). Apple's Thunderbolt 3 support article states that the right-side Thunderbolt 3 ports on the Late 2016 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. The left Thunderbolt 3 ports 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.

Overview of PCIe Lane Arrangement in Thunderbolt 3 MacBook Pro

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. Through trial and error, we found the right-side Thunderbolt 3 ports under PCI Express x4 Controller - 1909 is the best way to connect an eGPU to the 15" Thunderbolt 3 MacBook Pro. This is especially relevant when using an AMD Radeon eGPU in which both PCI Express Controller 1901 and 1905 need to be disabled to resolve error 12.

The 13" non-Touch Bar MacBook Pro would likely be able to negotiate enough resources for eGPU automagically. If error 12 arises, simply disabling the connection to the iSight camera would resolve it. The 13" Touch Bar iteration is slightly harder for eGPU implementation due to an extra Thunderbolt 3 controller and two more Thunderbolt 3 ports. It's best to use the lower left Thunderbolt 3 port [closest to the TAB key] for eGPU connection on this model and to disable the PCI Express Root Port #9 – 9D18 that connects to the right Thunderbolt 3 ports to resolve error 12.

Here are the recommended steps to set up an external GPU with Thunderbolt 3 MacBook Pros 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 Windows, DDU & Restore Point

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 200GB for the macOS partition. You can then install 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 6.1 (part of Boot Camp Assistant in macOS). DDU can also disable Windows automated graphics drivers installation.

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 encounter issues.

Step 2: Use apple_set_os.efi

When booting into an operating system that is not Mac OS, the Mac laptop's firmware tends to deactivate the integrated GPU if there's another GPU present. For example, the 15" MacBook Pro boots into Boot Camp with only the Radeon Pro discrete GPU activated. By only having an integrated GPU, the 13" MacBook Pro sometimes hangs at the Windows bootup process if an external GPU is connected. To remedy this first hurdle we rely on apple_set_os.efi to trick the Mac laptop into believing it's booting into Mac OS. 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 rEFInd boot manager.

Goalque’s guide on apple_set_os.efi is the resource for accomplishing this task. He provided instructions on creating a USB thumb drive with apple_set_os.efi. rEFInd is an alternative for the need to use an external USB drive and Option boot. 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 15" Thunderbolt 3 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.

Step 3: Run integrated.bat

This step is relevant to the Thunderbolt 3 15" MBP only. Skip to step 4 if you have a Thunderbolt 3 13" MBP. 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.

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 4: 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 both iGPU and dGPU. 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.

For late-2016 Macbook Pros, Nando's DSDT Override via registry works well, but the required Windows Test Mode prevents some some games and software working. The workaround Clover DSDT override method has some risks but can provide a simple final solution. Adventurous users may consider this. For mid-2017 15" Macbook Pros consider using a PCIe relocation script from here to solve error 12.

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 does the trick. 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. For us this method has worked with GTX 980 Ti, GTX 1070, and GTX 1080 eGPU. From eGPU.io members' experience, Windows has a harder time with AMD cards. When we tried the RX 580 and RX Vega 56 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.

Boot Camp eGPU Setup Procedure

If viewing this on the forum, please jump to the mirrored news post here to see steps 1-4 below correctly.

Here are all the steps from start to finish to get an external graphics card running on a Thunderbolt 3 15" MacBook Pro. Do not connect the external GPU to the Mac laptop until instructed to do so. Download the linked resources at each step.

Step 1: Windows 10 ISO and DDU

Download Windows 10 ISO then open Boot Camp Assistant to start installing Windows. If you intend to use an external SSD, partition the internal drive into 200GB for macOS and 50GB for Windows 10.

  Install Windows 10 ISO through Bootcamp Assistant - macOS

Right click on Display Driver Uninstaller to run as Administrator. Then proceed to uninstall both Nvidia and AMD drivers. This process disables Windows 10 automated GPU drivers installation as well.

Install DDU to remove default graphics drivers and disable Windows automated GPU driver installation - Windows

Type "system protection" into the Windows search box. Select Create a restore point under Best match. Make sure Protection is on for the Boot Camp partition and then create a restore point.

Create a manual Restore point just in case there’s boot up issues – name it DDU Safe - Windows

Step 2: rEFInd, apple_set_os.efi, Intel graphics drivers

Open Terminal then drag and drop refind-install to install rEFInd bootmager. Drag and drop mountesp to mount the ESP volume.

Create a new folder named custom inside EFI » EFI. Copy the apple_set_os.efi file into the folder. 

Hit ENTER on apple_set_os.efi volume at rEFInd screen. ARROW to the Windows volume to boot.

If you see two Microsoft Basic Display Adapter devices under Display adapters in Device Manager, proceed to install Intel graphics drivers.

Type "system protection" into the Windows search bar then select Create a restore point under Best match. Make sure Protection is on for the Boot Camp partition and then create another restore point.

Create a manual Restore point just in case there’s boot up issues – name it DDU Safe - Windows


Step 3:
0xbb's gpu-swich and 2013 Visual C++

Select View » Devices by connection in Device Manager then expand the PCI Express Root Complex to locate and disable Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core(TM) PCIe Controller (x8) - 1905.

Run gpu-switch integrated.bat as Administrator to attach the internal display to iGPU at next boot. If you encounter a System Error message due to missing MSVCR120.dll, install 2013 Visual C++ X86. Shut the computer down when Windows CMD screen disappears.


Step 4:
AMD Radeon drivers or Nvidia GeForce drivers

Connect the external GPU to one of the Thunderbolt 3 ports on the right side of the 15" MacBook Pro. ENTER on apple_set_os.efi at rEFInd boot screen. ARROW to select the Window volume to boot.

Open Device Manager to confirm there's a third graphics device. This new device is the external graphics card. Proceed to install the drivers accordingly to your external GPU device.

Nvidia eGPU can work without error 12 when the PCIe Controller x8 -1905 is disabled. AMD eGPU needs the PCIe Controller x16 – 1901 disabled as well to free up enough resources. Select View » Devices by connection in Device Manager and locate PCIe Controller x16 – 1901 to disable it.

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.

Closing Thoughts

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.

Update

Apple has made some firmware improvements in the mid-2017 MacBook Pro. Windows 10 now shows "Large Memory" under Device Manager » View » Resources by connection. This means some Mid 2017 MacBook Pros may be able to use Nvidia eGPU without encountering error 12, no workaround needed.

Best ultrabooks for eGPU use

eGPU enclosure buying guide

60 external GPU build guides


goalque, ppm, nando4 and 1 people liked
ReplyQuote
hypernurd
(@hypernurd)
Trusted Member
Joined:1 year  ago
Posts: 58
September 10, 2017 7:47 pm  

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!
Hypernurd

mid-2017 15" Macbook Pro RP560 + GTX1080Ti@32Gbps-TB3 (Mantiz Venus) + macOS & Win10


ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined:2 years  ago
Posts: 238
September 10, 2017 9:49 pm  
Posted by: theitsage

Update

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.

Man I was so happy I could use my eGPU on mid-2017 MBP without many issues. Now I'm just waiting for the High Sierra Nvidia drivers and we have a perfect setup.

mid-2017 15" Macbook Pro RP555 + GTX1080i@32Gbps-TB3 (Mantiz Venus) + macOS & Win10


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Honorable Member
Joined:1 year  ago
Posts: 755
September 13, 2017 2:10 pm  

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...

2017 13" MacBook Pro Touchbar + GTX1060@32Gbps-TB3 (AKiTiO Thunder3) + Win10
2017 13" MacBook Pro Touch Bar + GTX1070@32Gbps-TB3 (Sonnet Breakaway Box) + Win10
---
LG 5K Ultrafine flickering issue fix


ReplyQuote
Wunair
(@wunair)
Eminent Member
Joined:1 year  ago
Posts: 38
September 15, 2017 10:36 am  

Is there an alternate method to make Bootcamp work with an eGPU while using the LEFT TB3 ports?


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined:2 years  ago
Posts: 1722
September 15, 2017 10:45 am  

@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:

 

The 2017 15" MBP has provision for 'large memory' in the firmware. The 2016 15" MBP needs to have it added by way of a DSDT override.

2013 15" Dell Latitude E6540 HD8790M + RX580@4Gbps-EC2 (EXP GDC 8.x) + macOS 10.13.5 & Win10
--
eGPU Port Bandwidth Reference TableeGPU Setup 1.35


hypernurd and theitsage liked
ReplyQuote
theitsage
(@itsage)
Famed Member Admin
Joined:2 years  ago
Posts: 2522
September 15, 2017 12:44 pm  

@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.

Best ultrabooks for eGPU use

eGPU enclosure buying guide

60 external GPU build guides


hypernurd liked
ReplyQuote
dslater
(@dslater)
Eminent Member
Joined:1 year  ago
Posts: 23
September 15, 2017 6:33 pm  

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...

thanks!

dan

Late 2016 15" MacBook Pro
Late 2017 13" HP Spectre x360 + RX Vega56@32Gbps-TB3 (Mantiz Venus) + Win10 // 8th Gen i7 8550u, 16gb ram, 512gb ssd
Vega 56 (flashed with 64 bios)


ReplyQuote
(@xiaoyu9964)
New Member
Joined:10 months  ago
Posts: 1
September 20, 2017 5:50 am  

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?


ReplyQuote
theitsage
(@itsage)
Famed Member Admin
Joined:2 years  ago
Posts: 2522
September 20, 2017 3:43 pm  

Hi @沈念雨, which MacBook Pro are you using? The Intel graphics driver version you have maybe different than what's needed.

Best ultrabooks for eGPU use

eGPU enclosure buying guide

60 external GPU build guides


ReplyQuote
daqin9356
(@daqin9356)
New Member
Joined:10 months  ago
Posts: 2
September 24, 2017 10:58 am  

Hi there,

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

internal display?

I am thinking about buying a Akitio Node with a GTX1060 to run some steam games.

Looking forward to your reply.

Best regards,

Frank from Australia.


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined:2 years  ago
Posts: 1722

ReplyQuote
JonRoth
(@jonroth)
Active Member
Joined:10 months  ago
Posts: 14
September 28, 2017 7:32 am  

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?


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Honorable Member
Joined:1 year  ago
Posts: 755
September 28, 2017 10:01 am  

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.

2017 13" MacBook Pro Touchbar + GTX1060@32Gbps-TB3 (AKiTiO Thunder3) + Win10
2017 13" MacBook Pro Touch Bar + GTX1070@32Gbps-TB3 (Sonnet Breakaway Box) + Win10
---
LG 5K Ultrafine flickering issue fix


ReplyQuote
JonRoth
(@jonroth)
Active Member
Joined:10 months  ago
Posts: 14
September 28, 2017 4:22 pm  
Posted by: Eightarmedpet

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?


ReplyQuote
JonRoth
(@jonroth)
Active Member
Joined:10 months  ago
Posts: 14
September 30, 2017 1:32 am  

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.


ReplyQuote
mklegend
(@mklegend)
Eminent Member
Joined:1 year  ago
Posts: 22
October 5, 2017 8:04 pm  

@theitsage, 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.

Unigene Valley Benchmark (Default) 1080 Ti
Unigene Heaven Benchmark 4.0 (Default) 1080 Ti
Superpostition 1080 Extreme 1080 Ti
3DMark TimeSpy Default 1080 Ti
Cuda Z 1080 Ti
GPU Z 1080 Ti
PCIe Controllers   Device Manager
Display Adapters   Device Manager

 

Best Regards,

Mohammad Katayen (mklegend)


ReplyQuote
tbquixote
(@tbquixote)
New Member
Joined:9 months  ago
Posts: 3
October 8, 2017 2:05 am  

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.


ReplyQuote
tbquixote
(@tbquixote)
New Member
Joined:9 months  ago
Posts: 3
October 8, 2017 1:23 pm  

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.


ReplyQuote
Humanovation
(@humanovation)
Eminent Member
Joined:9 months  ago
Posts: 21
October 9, 2017 10:18 pm  

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

PS - Trying to use a Sonnet breakaway 350 with a Radeon RX 580 😉


ReplyQuote
theitsage
(@itsage)
Famed Member Admin
Joined:2 years  ago
Posts: 2522
October 9, 2017 10:21 pm  

@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.

Best ultrabooks for eGPU use

eGPU enclosure buying guide

60 external GPU build guides


ReplyQuote
Humanovation
(@humanovation)
Eminent Member
Joined:9 months  ago
Posts: 21
October 9, 2017 11:01 pm  

Thanks so much theitsage! 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.


ReplyQuote
Humanovation
(@humanovation)
Eminent Member
Joined:9 months  ago
Posts: 21
October 10, 2017 8:45 pm  

Integrated.bat will not run ... I keep getting error code 1300 - Not all privileges or groups are assigned to the caller ;-(


ReplyQuote
theitsage
(@itsage)
Famed Member Admin
Joined:2 years  ago
Posts: 2522
October 10, 2017 8:49 pm  

In Step 3, 2013 Visual C++ was linked in case you encounter an error. -  https://egpu.io/bootcamp-setup-guide-tb3-macbook-pro/#summary

Best ultrabooks for eGPU use

eGPU enclosure buying guide

60 external GPU build guides


ReplyQuote
Humanovation
(@humanovation)
Eminent Member
Joined:9 months  ago
Posts: 21
October 10, 2017 8:55 pm  

Yes, I installed it first according to the instructions, still no luck ...


ReplyQuote
theitsage
(@itsage)
Famed Member Admin
Joined:2 years  ago
Posts: 2522
October 10, 2017 11:27 pm  

@Humanovation, is the account you're using in Windows an admin?

Best ultrabooks for eGPU use

eGPU enclosure buying guide

60 external GPU build guides


ReplyQuote
Humanovation
(@humanovation)
Eminent Member
Joined:9 months  ago
Posts: 21
October 10, 2017 11:34 pm  

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 😉


ReplyQuote
Humanovation
(@humanovation)
Eminent Member
Joined:9 months  ago
Posts: 21
October 11, 2017 1:05 am  

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 😉


ReplyQuote
tbquixote
(@tbquixote)
New Member
Joined:9 months  ago
Posts: 3
October 16, 2017 12:51 pm  

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.


theitsage liked
ReplyQuote
csantiago78
(@csantiago78)
Active Member
Joined:10 months  ago
Posts: 8
October 16, 2017 6:36 pm  

Hey, I wanted to thank you for the guide. As I, like many used it to make my 15" MBP w/TB and Radeon 450 work with my GTX 1080 TI in the Mantiz Venus.

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.


ReplyQuote
Volodymyr Demtsiu
(@volodymyr_demtsiu)
New Member
Joined:9 months  ago
Posts: 1
October 17, 2017 7:50 pm  

Hi guys!
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!


ReplyQuote
DigiBldg1
(@digibldg1)
New Member
Joined:9 months  ago
Posts: 1
October 23, 2017 3:57 am  

@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!


ReplyQuote
Humanovation
(@humanovation)
Eminent Member
Joined:9 months  ago
Posts: 21
October 26, 2017 5:47 pm  

– 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.


ReplyQuote
MrDanne
(@mrdanne)
Active Member
Joined:9 months  ago
Posts: 12
October 27, 2017 1:18 am  

There is a new rEFInd available 0.11.2. Maybe it is good to update the link above.

MacBook Pro 15" Late 2016 Touch bar | Sapphire Radeon RX Vega 56 8GB HBM2 | Mantiz Venus MZ-02 Space Gray


ReplyQuote
deathtrapz
(@deathtrapz)
Eminent Member
Joined:9 months  ago
Posts: 20
October 27, 2017 6:47 am  

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. 

-----------

*Edit

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?

2017 MBP 15" - Aorus Gaming Box 1070 - 2012 iMac 21.5"


ReplyQuote
ICULikeMac
(@iculikemac)
Trusted Member
Joined:8 months  ago
Posts: 80
November 20, 2017 9:59 am  

Hi deathtrapz,

Did you ever work out the screen flickering solution? I have that problem as I'm typing? 

Thank you!!


ReplyQuote
Page 1 / 4 Next