Setup & Software Discussions
Boot Camp eGPU error 12 fail after update to Windows 10 1903 (OS Build 18362.329...
 

[Solved] Boot Camp eGPU error 12 fail after update to Windows 10 1903 (OS Build 18362.329 or newer)  

 of  10
  RSS

(@pete_martson)
New Member
Joined: 2 months ago
 

I HAVE SOLVED THIS ISSUE FOR NOW.

My setup is as follows: MacBook Pro Mid 2017 - Razer Core X - Vega 64

I am using the rEFInd Boot Manager to turn on the Intel GPU when booting into Windows 1903. This causes the built in Radeon 560 to quit working (yellow triangle in devices) and allows the eGpu to work. I can do dual monitor with the internal display and external display or use the Windows display setting to turn off the internal display and run in clam shell mode. Another advantage is that you can use the Intel GPU for hardware accelerated encoding in Adobe Premiere or Davinci Resolve (and other software). It seems like a hack but it works well until this gets resolved.

You MUST plug the eGpu into the right side Thunderbolt port toward the back for this to work. It has to do with port mapping.

Let me know if this works for you.

This post was modified 2 months ago

MacBook Pro Mid 2017 - Razer Core X - Vega 64 - Samsung Odyssey Mixed Reality HMD


atlr liked
ReplyQuote
(@mauro_diez)
New Member
Joined: 2 months ago
 

I can confirm that the latest September cumulative update for Windows 10 Oct. 3 (KB 4524147) breaks my egpu setup (2018 Mac mini, razor core x, Vega 56, boot camp). The previous three cumulative updates on Sept. 10 (KB 4515384), Sept. 23 (KB 4522016) and Sept. 26 (KB 4517211) caused no issues. I was getting an error 12 code (not enough resources to run this device) in device manager for my gpu. I uninstalled the Oct. 3rd update (KB 4524147) to eliminate the error and get my system back up and running for now at least. I also disabled automatic updates temporarily. I’ll be contacting razor about all of this as well. 

2018 Mac Mini Core i7 32GB ram Razer Core X Sapphire Pulse Vega 56 Catalina with Windows 10 in bootcamp


atlr liked
ReplyQuote
Knot3D
(@knot3d)
Active Member
Joined: 8 months ago
 

Ok, I can confirm that this week's build .418 (KB 4517389) works for my EGPU. 

HP Spectre X360 13inch diamond cut 2019 version, WIN 10 Home 64bit + Aorus Gaming Box RTX2070

 

 

HP Spectre X360 13inch Diamand Cut 2019 i7 - 8565U with 8Gb RAM + Aorus Gaming Box RTX2070


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

@knot3d My NUCi5 automatically updated to 18362.418 last night. Nvidia eGPU remained working through hot-plug. We may not be in the clear just yet as most error 12 issues occur with AMD eGPU.

external graphics card builds
best laptops for external GPU
eGPU enclosure buyer's guide


ReplyQuote
Knot3D
(@knot3d)
Active Member
Joined: 8 months ago
 

@itsage

Yeah, that might still be the case for AMD EGPUs.

Builds .329 and .356 were the culprit for my RTX2070, so I basically went from .295 to .418, to retain EGPU functionality.

HP Spectre X360 13inch Diamand Cut 2019 i7 - 8565U with 8Gb RAM + Aorus Gaming Box RTX2070


itsage liked
ReplyQuote
sunny
(@sunny)
Eminent Member
Joined: 10 months ago
 
Posted by: @knot3d

@itsage

Yeah, that might still be the case for AMD EGPUs.

Builds .329 and .356 were the culprit for my RTX2070, so I basically went from .295 to .418, to retain EGPU functionality.

I can confirm, hot plug egpu working fine on .418 with aorus gaming box rtx2070

Mac Mini 2018 / Aorus Gaming Box RTX 2070


itsage liked
ReplyQuote
Ningauble77
(@ningauble77)
Estimable Member
Joined: 2 years ago
 

Tested 418 here and could not get things working hotplug at desktop, hotplug at boot or connected at boot.  Still Error Code 12.  Rolled back to 295, getting kinda nervous about missing security patches now though.  May have to swap the Radeon VII out for the 2080 and see if that works.

2019 16 Macbook Pro + Core v2 + Radeon VII MacOS 10.15.1
Core X Chroma + RTX 2080 Windows 10 1909


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

@ningauble77 If you can try the Nvidia eGPU on the same system and Windows 10 build that would be great. When I tested my 2019 13″ MacBook Pro running .356, AMD eGPU encountered error 12 regardless which connection method I tried. Nvidia eGPU on the other hand worked great through hot-plug.

 

external graphics card builds
best laptops for external GPU
eGPU enclosure buyer's guide


ReplyQuote
PandamanNG
(@pandamanng)
New Member
Joined: 9 months ago
 

Just tried build 418 on MBP 15" 2016 + Aorus Gaming Box RTX2070 + DSDT override & hot plug at boot, still having issue where booting takes way too long (it eventually boots after few minutes) and headphone jack not detected (could be fixed by disabling and re-enabling the sound card). This occurs on my setup with every build after 295.

Weirdly, on build 418, the headphone jack works fine when egpu is unplugged and DSDT not applied.

May be the issue is related to new security patches interfering with memory addressing or how we apply DSDT?

2016 15" MacBook Pro + Aorus Gaming Box RTX2070


itsage liked
ReplyQuote
JMGmr2
(@jmgmr2)
Active Member
Joined: 3 months ago
 

I can confirm that the .418 update broke my system as well. Reverting back to 295, restored everything.

Mac Mini 2018, Windows 10, & a Core X/Radeon VII.

 

I'm at a loss here.  I don't understand why Microsoft is doing this.  Worst part was that the updates were forced on me.  I had it to a disabled/manual installation setup and it STILL pushed them and broke my system.

 

 

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


ReplyQuote
sunny
(@sunny)
Eminent Member
Joined: 10 months ago
 

What an interesting situation, MS screwing up AMD users, Apple screwing up Nvidia users...

 

Mac Mini 2018 / Aorus Gaming Box RTX 2070


itsage liked
ReplyQuote
ttamnogard
(@ttamnogard)
Trusted Member
Joined: 4 months ago
 

I was just about to try .418... so that is another hard pass.... 

2018 Mac mini running Radeon vii


ReplyQuote
Mgear1981
(@mgear1981)
Eminent Member
Joined: 3 years ago
 

There is something strange going on, on my macbook pro 2019 vega 20 i get the same error 12 as you guys have. But, i have 1 intel nuc, the nuc8i7hvk with the same thunderbolt 3 controllers buildin as my macbook. On my nuc i run 2 vega 7 videocards and all the updates from windows got installed automaticly, suprisingly the vega 7 cards keept on working on every build. I have the feeling it has to do with memory adressing somehow or intentional distortion of bootcamp/apple. Perhaps we should compare memory adressing in the systems to find out where the difference lies. What could also make a difference is the fact that my intel 8 has also 2 videocards build in just like my macbook. It has an intel buildin card and a RX vega M GH card. On my nuc i did disable the internal vega card.

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


atlr liked
ReplyQuote
Test1
(@test1)
Active Member
Joined: 9 months ago
 

I discovered this topic way too late..  I didn't notice the "Note:" banner since it blends quite well with the rest of the background. Would be really cool if important alerts like these could use a warmer color or a little yellow triangle with "!" in the beginning  (since most setup guides tend to say to always use the latest version).

.418 broke my setup with Vega 56 on my late 2016 15" mbp. I was trying to reconfigure my setup multiple times and figure out what I was doing wrong, not knowing that the update .418 was the culprit. I rolled back to .295 and it all works like a charm. The update blocker @mac_editor linked was really helpful

I use the guide from @itsage . The furthest I had come trying to get .418 working was to NOT delete apple_set_os.efi . Get the iGPU working and bypass the dGPU (Since the dGPU will get yellowbanged error 43). Disable x16 and x8 and try to go from there. But it was already so late yesterday and I need to study..

Anybody know what's causing .418 + to do this?

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


itsage and atlr liked
ReplyQuote
atlr
 atlr
(@atlr)
Active Member
Joined: 9 months ago
 
Posted by: @mgear1981

... But, i have 1 intel nuc, the nuc8i7hvk with the same thunderbolt 3 controllers buildin as my macbook. On my nuc i run 2 vega 7 videocards and all the updates from windows got installed automaticly, suprisingly the vega 7 cards keept on working on every build ...

What is the firmware version of your thunderbolt enclosure? And the NUC8?

For me, a NUC6 with fw 27 and Thunderbolt driver package .500 and a fw 25.1 enclosure with the vega 7 will cause a loop of reboots if I reboot the NUC with it connected.   But, if I plug in the Vega 7 enclosure while the NUC6 is running, all is fine.

This issue does not occur when I use a 5700 instead of the vega 7 with the NUC6.

User of eGPUs at my job.


ReplyQuote
(@pete_martson)
New Member
Joined: 2 months ago
 
Posted by: @pete_martson

I HAVE SOLVED THIS ISSUE FOR NOW.

My setup is as follows: MacBook Pro Mid 2017 - Razer Core X - Vega 64

I am using the rEFInd Boot Manager to turn on the Intel GPU when booting into Windows 1903. This causes the built in Radeon 560 to quit working (yellow triangle in devices) and allows the eGpu to work. I can do dual monitor with the internal display and external display or use the Windows display setting to turn off the internal display and run in clam shell mode. Another advantage is that you can use the Intel GPU for hardware accelerated encoding in Adobe Premiere or Davinci Resolve (and other software). It seems like a hack but it works well until this gets resolved.

You MUST plug the eGpu into the right side Thunderbolt port toward the back for this to work. It has to do with port mapping.

Let me know if this works for you.

FYI... my system is still working with the above work around on .418.

MacBook Pro Mid 2017 - Razer Core X - Vega 64 - Samsung Odyssey Mixed Reality HMD


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

The 2016 & 2017 15″ MacBook Pro can be configured to solve error 12 once you enable Intel iGPU and disable Radeon dGPU (either rEFInd or automate-eGPU EFI works). I tested my 2016 15″ MBP through all these bad Win10 1903 versions and it remains working with this configuration.

external graphics card builds
best laptops for external GPU
eGPU enclosure buyer's guide


ReplyQuote
teltersat2
(@teltersat2)
Eminent Member
Joined: 4 months ago
 

Still waiting for things to go back to normal 🙁

Current build: 2017 15" MacBook Pro + Mantiz Venus MZ-02 + Silverstone SX700-LPT (750W Peak) + Sapphire Radeon RX Vega 64 (Reference model)
Replaced parts: Sapphire Radeon RX 580 Nitro+


ReplyQuote
(@dumitru_pascu)
New Member
Joined: 2 months ago
 

Using a Mac Mini 2018, Core X and a Vega 64 GPU - .418 broke it. Reverted back to .295 and everything is back to normal. Still waiting for the PATCH...

Mac Mini 2018, i7, 16 GB RAM, 512 GB SSD, Razer Core X Chroma, Asus AMD Vega 64 Strix.


ReplyQuote
Squuiid
(@squuiid)
Active Member
Joined: 6 months ago
 

@dumitru_pascu


Same here. I’m on a GTX 1080 and Sonnet eGPU.

Frustrating that Microsoft haven’t fixed this yet.

Mac mini 2018, i7 3.2GHz 6c, 32GB RAM, 1TB SSD, 10GbE, Sonnet eGFX + PowerColor RX 5700 XT 8GB, TEKQ Rapide TB3 512GB SSD, macOS Catalina, Win10 Pro
Mac Pro 2010, X5690 3.46GHz 6c, 64GB RAM, Amfeltec 3x XP941 512GB, Sapphire Pulse RX 580 8GB, Intel X540-T1 10GbE, Allegro Pro USB 3.0, AC/BT 4.2, macOS Mojave


ReplyQuote
Ningauble77
(@ningauble77)
Estimable Member
Joined: 2 years ago
 

@itsage

I can confirm RTX 2080 works fine with full hotplug functionality with Win 10 Build 18362.418

nvidia 418

Update:  RTX card works fine when hotplugged, but cannot be present at boot time or the system hangs on the apple logo and chassis gets warm.  The Radeon VII had a similar issue when restarting from boot camp, but restarting from macos and cold boots were fine.

This post was modified 2 months ago

2019 16 Macbook Pro + Core v2 + Radeon VII MacOS 10.15.1
Core X Chroma + RTX 2080 Windows 10 1909


rawwd and atlr liked
ReplyQuote
(@suwit_suriyasriwan)
Active Member
Joined: 2 months ago
 

Confirmed that RX 580 can work well in Windows 10 18362.418

2018 15″ MacBook Pro i7-8850H/Radeon Pro 560X dGPU/16GB RAM/512GB SSD; RTX 2070 Super & ROG XG STATION 2


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

@suwit_suriyasriwan Which Mac computer are you using?

Windows 10 1909 is around the corner so I decided to enroll my 2019 13″ MacBook Pro to Insider Program. The OS Build is 18363.418. Unfortunately error 12 issue persists. I tried booting with automate-eGPU EFI as well as disablement of a few PCIe device. Nothing helped.

I created a manual restore point right before updating so that I could rolled back to 18362.295 quickly. As soon as my 2019 13″ MacBook Pro was back to this Win10 version, AMD eGPU was hot-pluggable and XConnect worked right away.

This post was modified 2 months ago

external graphics card builds
best laptops for external GPU
eGPU enclosure buyer's guide


ReplyQuote
(@suwit_suriyasriwan)
Active Member
Joined: 2 months ago
 

@itsage My mac is MBP-15 2018 (RP560X) which build 18362.418

However, did you try hot-plug and uninstall Vega driver then reboot?

2018 15″ MacBook Pro i7-8850H/Radeon Pro 560X dGPU/16GB RAM/512GB SSD; RTX 2070 Super & ROG XG STATION 2


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

@suwit_suriyasriwan The TB3 15″ MacBook Pro is one of the few that can handle these newer builds with PCI Express Controller 1901 disabled. My 2016 15″ MBP can use AMD eGPU in Win10 1909 18363.418. However it’s a real issue with many Macs and some Windows systems.

This post was modified 2 months ago

external graphics card builds
best laptops for external GPU
eGPU enclosure buyer's guide


ReplyQuote
Swang Ho
(@swang_ho)
New Member
Joined: 11 months ago
 

ia this problem solved?

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


ReplyQuote
(@yun_zhu)
New Member
Joined: 2 months ago
 

Bro, I got this problem too, after Windows's auto-update to .418. Just uninstalled the latest update, then the windows rolled back to 18362.30 and everything works as normal now. My configuration is iMac 2019 + Razer Core X + Vega64.

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


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

I’ve done more bad Win10-1903-version testings on Thunderbolt 3 Macs. The victim today is the 2017 13″ MacBook Pro. Microsoft Windows 10 ISO download website has now changed to provide Window 10 1903 V2 file which comes with 18362.356 build. On previous attempts, the 2017 13″ MacBook Pro would always encountered an endless boot loop once Radeon drivers were installed (w/ Windows 10 1903). I believe @eightarmedpet experienced the same issue. Funny enough OS Build 18362.356 resolves this endless boot loop issue but presents error 12 issue for AMD eGPU. After disabling PCI Express Root Port #9 [right-sided TB3 controller] and Port #12 [Wireless card] as well as two switch ports under Port #5, error 12 was resolved. I used automate-eGPU EFI boot loader in order to keep the Intel iGPU activated.

The right-sided Thunderbolt 3 controller on 2016/2017 13″ MacBook Pro attaches to a x2 PCIe connection so it wasn’t ideal for connecting an eGPU. I’m using the VisionTek mini eGFX enclosure which has an Ethernet expansion port for network connection. WiFi adapter inside the MacBook Pro was not going to be the primary connection even if it was active. These PCIe Root Ports can be re-enabled in Device Manager once the AMD eGPU shows up as working without errors. I will update this MacBook Pro to the latest 18362.418 as well as Windows 10 1909 [OS Build 18363.418] and see how it goes.

This post was modified 2 months ago

external graphics card builds
best laptops for external GPU
eGPU enclosure buyer's guide


ReplyQuote
PandamanNG
(@pandamanng)
New Member
Joined: 9 months ago
 
Posted by: @pandamanng

Just tried build 418 on MBP 15" 2016 + Aorus Gaming Box RTX2070 + DSDT override & hot plug at boot, still having issue where booting takes way too long (it eventually boots after few minutes) and headphone jack not detected (could be fixed by disabling and re-enabling the sound card). This occurs on my setup with every build after 295.

Weirdly, on build 418, the headphone jack works fine when egpu is unplugged and DSDT not applied.

May be the issue is related to new security patches interfering with memory addressing or how we apply DSDT?

Update: Using iGPU and disabling dGPU PCI-E controller solved the long boot time issue as others suggested, minor catches:
- Windows is stuck at loading if Apple USB-C to HDMI dongle is used, boot must be done on internal screen
- eGPU is not detected consistently unless DSDT large memory patch is applied
- Microphone detection still doesn't work, reset via hardware manager required after each boot

From CUDA-Z readings, it seems that there is no reduction on H2D or D2H performance compared to my previous records.

Posted by: @itsage

I've done more bad Win10-1903-version testings on Thunderbolt 3 Macs. The victim today is the 2017 13" MacBook Pro. Microsoft Windows 10 ISO download website has now changed to provide Window 10 1903 V2 file which comes with 18362.356 build. On previous attempts, the 2017 13" MacBook Pro would always encountered an endless boot loop once Radeon drivers were installed (w/ Windows 10 1903). I believe @eightarmedpet experienced the same issue. Funny enough OS Build 18362.356 resolves this endless boot loop issue but presents error 12 issue for AMD eGPU. After disabling PCI Express Root Port #9 [right-sided TB3 controller] and Port #12 [Wireless card] as well as two switch ports under Port #5, error 12 was resolved. I used automate-eGPU EFI boot loader in order to keep the Intel iGPU activated.

The right-sided Thunderbolt 3 controller on 2016/2017 13" MacBook Pro attaches to a x2 PCIe connection so it wasn't ideal for connecting an eGPU. I'm using the VisionTek mini eGFX enclosure which has an Ethernet expansion port for network connection. WiFi adapter inside the MacBook Pro was not going to be the primary connection even if it was active. These PCIe Root Ports can be re-enabled in Device Manager once the AMD eGPU shows up as working without errors. I will update this MacBook Pro to the latest 18362.418 as well as Windows 10 1909 [OS Build 18363.418] and see how it goes.

I'm not familiar with DSDT programming, but would it be possible for us to extend the QWordMemory range in our large memory patch? This might solve our issues as the it seems that Windows now requires more memory addressing space with newer builds?

This post was modified 2 months ago

2016 15" MacBook Pro + Aorus Gaming Box RTX2070


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

@pandamanng DSDT is only required for 2016 MacBook Pro. I recently paired a RTX 2070 Gaming Box with my 2016 15″ MacBook Pro. You can take a look at the build guide for step-by-step instructions. On another note, I completed updating to 18362.418 and AMD eGPU remains working on the 2017 13″ MacBook Pro with the workarounds detailed above.

This post was modified 2 months ago

external graphics card builds
best laptops for external GPU
eGPU enclosure buyer's guide


ReplyQuote
tidesgoesegpu
(@tidesgoesegpu)
Active Member
Joined: 8 months ago
 

Hey guys,

same issue here. Contacted Razer, told me to send back my enclosure for testing like they're not aware of the problem.
First and last time I buy a laptop from them, between the speaker crackling, the backlight bleeding, the coil-whinning and the loose TB3 port but that's not the subject here.

I enroled to Windows Insider since I'm coming from a clean install and don't have a working build saved somewhere. I'm running the latest build, 191004-1432, had some trouble rebooting after installing AMD Drivers, filled a report about it. Still doesn't work. I kindly suggest that everyone with my setup ("legit" Windows and AMD GPU) who can afford not having eGPU for some time or doesn't mind switching builds on a weekly basis does the same to hopefully increase the visibility of this issue. Also, I don't have Twitter but getting in touch with Microsoft and AMD there might lead us somewhere, if you guys don't bother doing it.

I'll keep this thread updated when new insider builds get released.

This post was modified 2 months ago

Razer Blade Stealth 2019 w/ MX150
Razer Core X + AMD Radeon VEGA 64


ReplyQuote
teltersat2
(@teltersat2)
Eminent Member
Joined: 4 months ago
 

Just got forced the new build after using the Windows Update "blocker" assistant script that was posted here.

Also, if you're having issues with your build (i.e. some functions don't work) try creating a new user instead of doing a clean install first - more often than not, this will remove all the noxious settings that you may have without having to clean up your system.

Current build: 2017 15" MacBook Pro + Mantiz Venus MZ-02 + Silverstone SX700-LPT (750W Peak) + Sapphire Radeon RX Vega 64 (Reference model)
Replaced parts: Sapphire Radeon RX 580 Nitro+


ReplyQuote
macbackpro
(@macbackpro)
Active Member
Joined: 3 months ago
 

2015 MBP 13" - Still experiencing the problem on .418 with DSDT injection at boot. Windows pushed out an update without my knowledge. *sigh*

 

Edit:

Confirmed that uninstalling the .418 update fixes the problem. A reboot did not help with .418 either. Tried to boot with egpu disconnected, then reconnected on reboot. Still didn't work. Going to hold out on windows updates until someone confirms that the issue is no longer present.

This post was modified 2 months ago

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


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

I tried Windows 10 1909 18363.418 on the 2018 Mac mini. I disabled as many PCIe components as possible but it was a no go. During the process, I learned that Thunderbolt 3 Port #3 and #4 [TB3 Controller #1] would always bring up the Boot Selector on the eGPU-connected monitor. Thunderbolt 3 Port #1 and #2 [TB3 Controller #0] would only bring up a black screen, there’s backlight on the monitor but nothing showed up.

The booting behavior into Windows is the reverse of a Mac laptop in that the Windows logo and spinning dots gets stuck on eGPU-connected monitor due to error 12 as soon as Radeon drivers load. I had the ASUS USB-C monitor attached to a different port so the Intel iGPU was able to power it.

This post was modified 2 months ago

external graphics card builds
best laptops for external GPU
eGPU enclosure buyer's guide


ReplyQuote
(@nelson_ten)
Active Member
Joined: 2 months ago
 

2014 Macbook Pro 15" Nvidia 750M

TB3>TB2 

Razer Chroma X

 

Greetings and salutations friends,

I've actually went through most of the guides here on egpu.io from start having nothing up to the point of many trial and errors to get to overriding DSDT but having still error 12 on my Radeon RX Vega.

<img> </img>

I began from https://egpu.io/forums/builds/2016-macbook-pro-154-tb3-gtx980tirazer-core-os-x-win10-clover-dsdt-in-memory-override/#cloverdsdt where I am using CLOVER and applying my DSDT.aml files in both patched and windows folder in the ACPI of EFI. The outcome of that was that I have now the large memory resource 

<img> </img>

However the error 12 still appears on my vega.

I've disabled the PCI Express of my Facetime Camera as well as my dGPU to try and free up some resources but to no avail.

<img> </img>

I've tried this hotplugging but I dont think it works with my macbook, as everytime I do it, the eGPU just doesnt get recognized at all. Or maybe I'm doing it wrong but I can't tell how many times I've plugged in my eGPU whilst the Windows Logo and spinning ring appears.

I downloaded drivers using bootcampdrivers.com which I am using, but I have tried Adrenalin, Crimson from AMD website which did not work either. What I did notice was sometimes halfway during the installations was the Vega 64 in device manager had the error 12 disappeared when reinstalling drivers after a DDU removal in safe mode. But after completing the installation it of course went back to Error 12.

Does anyone have any advice or recommendations to what I can do next? 

 

 

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


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

@nelson_ten What’s the OS Build number of your Windows 10? 

 

external graphics card builds
best laptops for external GPU
eGPU enclosure buyer's guide


ReplyQuote
 of  10