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  8
  RSS

(@daniele_pugliese)
Active Member
Joined: 7 months ago
 

Hi all,

I have a Mac mini 2018 i7 with a thunderbolt eGPU amd vega 64. After my windows update, the egpu is showed in Device Manager with the  yellow exclamation point (error 12). I installed the latest amd drivers but when I restart the Mac mini i need to connect the HDMI cable directly to Mac mini to see something and the egpu stay with exclamation point. I tried to install the May windows version from zero and the issue wasn't resolved. Now I installed again the windows version october 2018 and it work fine again. However I cant use xbox game pass with this version because a latest windows update is needed. any idea to solve this issue ?

thank you.


Uninstall Windows 10 Updates:

The May 2019 update is OS Build 18382.30, ISO file is called Windows 10 1903 V1. The OS Build versions that work well with eGPU are .30 to .295. If your Windows 10 are newer than these versions, uninstall any (or all) of the following:

  • October 8, 2019—KB4517389 (OS Build 18362.418)
  • October 3, 2019—KB4524147 (OS Build 18362.388)
  • September 26, 2019—KB4517211 (OS Build 18362.387)
  • September 23, 2019—KB4522016 (OS Build 18362.357)
  • September 10, 2019—KB4515384 (OS Build 18362.356)
  • August 30, 2019—KB4512941 (OS Build 18362.329)

If you need to do a clean install of Windows 10 1903 V1, a manual update to .295 can be done by downloading:

  • August 13, 2019—KB4512508 (OS Build 18362.295) which can be found Microsoft Update Catalog
    • "2019-08 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4512508)"
    • Be careful one is for SERVER, that is not the one that will work with Bootcamp...

If you need to download Windows 10 1903 V1 ISO (OS Build 18362.30) use this link - https://tb.rg-adguard.net/public.php

This topic was modified 2 days ago

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


rawwd liked
ReplyQuote
teltersat2
(@teltersat2)
Eminent Member
Joined: 3 months ago
 

maybe try removing the windows drivers with DDU, update Windows to 1903 and then give it a go again? Also, are you sure 1903 is detecting the thunderbolt drivers properly? I upgraded to 1903, and then switched to the DCH drivers with no problems. Lastly, would you be able to give us a breakdown of the steps you use to set up your bootcamp partition on your Mac Mini? (including the boot camp drivers I'm assuming)

And just a caveat, I never do any upgrades to the OS and drivers with the eGPU installed, I always boot up Windows by itself just to avoid any issues.

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
(@daniele_pugliese)
Active Member
Joined: 7 months ago
 

Hi,thank you for your reply.
I used this drive : https://www.amd.com/en/support/graphics/radeon-rx-vega-series/radeon-rx-vega-series/radeon-rx-vega-64
I also installed windows 19.03  with a clear installation but this not solved my problem.
I follow this steps:
1- Start mac with with the EGPU off, then when windows is started I turn on the egpu and restart the machine.
2- at startup I see the monitor blinking so I put off the mac with power button unplug the hdmi cable and turn on the mac again with the display port cable only and the egpu plugged in. 

With this steps the windows previusly version the egpu is correctly detected with the 19.03 not :(.

what mean dhc driver ?

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
 

Which macOS version are you using? If you install Catalina Beta, there’s Boot Screen support through the eGPU so that you don’t have to switch back and forth between HDMI port from Mac mini to DisplayPort from eGPU. That way your boot up procedure is also simpler, always have the eGPU connected and powered ON prior to boot. I’m using my 2018 Mac mini + Radeon VII exactly this way and there’s no error 12 issue with the latest Windows 10 1903.

Best ultrabooks for eGPU use | eGPU enclosure buying guide


ReplyQuote
(@daniele_pugliese)
Active Member
Joined: 7 months ago
 

@itsage

Hi,
in this case I will wait for the official update on the next week for Catalina. Thank you

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


ReplyQuote
ttamnogard
(@ttamnogard)
Trusted Member
Joined: 3 months ago
 

I can confirm that if you install the latest "Optional" update from Microsoft for windows that it disables eGPU... without update, no problem... as soona s you run the update it kills it. I will be testing it again tonight but there is something fishy going on with a recent optional update. My recent build with my 2019 MBP worked great... ran the optional install and now error 12... no amount of DDU repairs it... 

2018 Mac mini running Radeon vii


atlr liked
ReplyQuote
Visvism
(@visvism)
Active Member
Joined: 2 years ago
 

I too ran into an issue with the latest update. Had everything working on my 2018 Mac mini + Akitio Node Vega 64 eGPU and then update... stopped working. Frustrating to say the least.

Current: 2018 Mac Mini i5 / 64GB RAM / 256GB SSD + Sapphire Radeon RX Vega 64 in Akitio Node


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

@daniele_pugliese, @ttamnogard, and @visvism Can you run winver in the Taskbar search box to get the OS Build number? I’m collecting information to see whether this new Windows 10 build is causing more headache. I updated my 2016 15″ MacBook Pro to 18362.329 tonight and setting up eGPU becomes harder.

Best ultrabooks for eGPU use | eGPU enclosure buying guide


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

@itsage

Hey there, just dropped in here to add my voice. I too updated Windows 1903 and have 18362.329, and completely unsure why my eGPU stopped working.

MBP 2018 w/ Radeon Pro 560X + Razer Core X + Vega 64.

MacBook Pro 2018 / Radeon Pro 560X / Razer Core X / Radeon RX Vega 64 / Windows 10 (1903 - 18362.295)


atlr liked
ReplyQuote
Jam0r
(@jam0r)
New Member
Joined: 2 months ago
 
Posted by: @adam_chester

@itsage

Hey there, just dropped in here to add my voice. I too updated Windows 1903 and have 18362.329, and completely unsure why my eGPU stopped working.

MBP 2018 w/ Radeon Pro 560X + Razer Core X + Vega 64.

 

Exact same system as above and eGPU now shows Code 12 error when it was working perfectly fine before.

I'm on latest Mojave 10.14.6

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


atlr and Adam Chester liked
ReplyQuote
Visvism
(@visvism)
Active Member
Joined: 2 years ago
 
Posted by: @itsage

@daniele_pugliese, @ttamnogard, and @visvism Can you run winver in the Taskbar search box to get the OS Build number? I'm collecting information to see whether this new Windows 10 build is causing more headache. I updated my 2016 15" MacBook Pro to 18362.329 tonight and setting up eGPU becomes harder.

Unfortunately I already wiped and went back to a clean install of Windows 10 Pro with automatic updates disabled. I'm back on version 1903 (build 18362.30). I have my Mac Mini working again with Intel PCI Express Root Port #2 - A339 and Intel PCIe Controller (x16) -1901 disabled. The only downside I see to this is that my ethernet port on the Mac Mini stops working and I have to use WiFi only. But I have successfully gamed with the Vega 64 in The Division 2 without any crashes or stutter issues.

Thanks for everything @itsage.

Current: 2018 Mac Mini i5 / 64GB RAM / 256GB SSD + Sapphire Radeon RX Vega 64 in Akitio Node


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

@itsage I presume this is the update in question: https://support.microsoft.com/en-us/help/4512941/windows-10-update-kb4512941

There don't seem to be any red flags in the changelog after a quick look. Odd. I might try updating after creating a restore point for testing.

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


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

@itsage Confirming that build 329 does cause Error 12 for my setup as well. Somehow it also deleted my restore point, but uninstalling the update manually did the trick.

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


integrii, atlr, ttamnogard and 1 people liked
ReplyQuote
itsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
 

@mac_editor Thank you for the confirmation. At least uninstalling the update let you roll back to a working version of 1903. I’m seeing the same issue on the 2018 Mac mini. Hot-plug is no longer a possibility with OS Build 18362.329. I disabled most PCIe root controllers and ports to see if error 12 can be resolved. Unfortunately it did not make a difference. Booting into Windows with the eGPU connected didn’t work either.

Last night I updated my 2016 15″ MacBook Pro to this OS build and it’s not as easy to run an eGPU like the previous build. I’m no longer able to hot-plug an AMD eGPU in Windows to run alongside the Radeon Pro dGPU. The AMD eGPU would encounter error 12 even when Large Memory is allocated through DSDT override + automate-eGPU EFI. I’m relying on an older procedure that attaches the internal display to the Intel iGPU and disabling the x16 PCIe Controller to Radeon Pro dGPU.

The most concerning observation was the reported bandwidth in AIDA64 (down to 1,6XX MB/s from 2,6XX MB/s). This of course effects internal display mode performance. I used a .5m Thunderbolt 3 cable so there’s no questionable components that might have caused this drop in throughput. If you’re able to get eGPU going with this build of Windows 10 on your Mac, please check AIDA64 GPGPU benchmark.

Update #1: I tested different Radeon graphics cards with different enclosures this morning. They were not capped at 1,6XX MB/s like the Vega Frontier Edition but the H2D could not reach more than 2,2XX MB/s. Definitely something has changed in this build of Windows 10.

Best ultrabooks for eGPU use | eGPU enclosure buying guide


atlr liked
ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 
Posted by: @itsage

If you’re able to get eGPU going with this build of Windows 10 on your Mac, please check AIDA64 GPGPU benchmark.

@itsage I didn't immediately see a way to get it going, since last we checked, apple_set_os.efi + iGPU muxing caused issues on 2018+ 15" MBPs. This might have changed, given that on build 295 (what I'm currently on), I can boot with the eGPU plugged in with all displays active, support for clamshell mode in Windows (need to wake system using external mouse/keyboard after closing lid), and hot-plugging also works sometimes. This is the best it has been for me so far. Looks like a combination of Catalina firmware updates and 1903 have improved eGPU significantly, but this update is disappointing (and hopefully there's better to come).

This post was modified 2 months ago

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


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

It is disappointing each system update in both macOS and Windows can cause such headache. At least we can isolate the culprit to build .329 and rollback to .295 works well. I tested an Nvidia eGPU just now. Of course it remains working even with hot-plug support, like always.

Best ultrabooks for eGPU use | eGPU enclosure buying guide


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

@itsage

Can confirm build 329 causes same problems on my setup.  I tried disabling left side TB3 ports and the pcie root connected to the wifi card but could not get egpu working at all.  Even with all of that disabled *and* booting with egpu plugged in to disable igpu could not make radeon vii work.  Uninstalled the update for now and everything is back to working again.

2018 13 Macbook Pro + Core v2 + Radeon VII MacOS 10.14.6
Core X Chroma + RTX 2080 Windows 10 1903


itsage liked
ReplyQuote
(@daniele_pugliese)
Active Member
Joined: 7 months ago
 

@itsage

At least we can isolate the culprit to build .329 and rollback to .295 works well. Do you mean that I can install the version .295 ? Can you please link me a guide to do that. Usually windows asks for automatically update to the last version.

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


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

@daniele_pugliese

Go to Windows Update settings -> View Update History -> Uninstall Updates.

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


ReplyQuote
Jam0r
(@jam0r)
New Member
Joined: 2 months ago
 
Posted by: @mac_editor

@daniele_pugliese

Go to Windows Update settings -> View Update History -> Uninstall Updates.

Won't allow me to uninstall it 😐

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


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

ReplyQuote
(@daniele_pugliese)
Active Member
Joined: 7 months ago
 

@mac_editor

but if I will update from my working version directly to the latest version I can't return back to an intermediate version. 

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


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

@daniele_pugliese

I just uninstalled the update as described above and returned from 329 to 295. I did not use a restore point (since it got deleted for some reason).

@itsage

Good to hear at least NVIDIA side is a-ok on the update. Hopefully we see a newer Windows build soon which does not have this problem.

This post was modified 2 months ago

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


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

@mac_editor I did the rollback to .295 and AMD eGPU is now hot-pluggable again with no issues.

This post was modified 2 months ago

Best ultrabooks for eGPU use | eGPU enclosure buying guide


ReplyQuote
(@keith_walls)
Eminent Member
Joined: 2 years ago
 

I can confirm that rolling Windows back to 1903 (18362.295) solved this issue on my iMac Pro with a Radeon VII (using bootcampdrivers.com August drivers.) I wish Microsoft would stop breaking stuff!

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


rawwd, atlr and mac_editor liked
ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 3 years ago
 

Is it worth saving a standalone iso or whatever of the “good” windows anywhere as a resource for folks?

2017 13" MacBook Pro Touch Bar
GTX1060 + AKiTiO Thunder3 + Win10
GTX1070 + Sonnet Breakaway Box + Win10
GTX1070 + Razer Core V1 + Win10
Vega 56 + Razer Core V1 + macOS + Win10
Vega 56 + Mantiz Venus + macOS + W10

---

LG 5K Ultrafine flickering issue fix


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

Also confirmed working again here, after uninstalling KB4512941 and thereby putting windows back to 1903 (18362.295), and reinstalling the bootcamp august drivers.

This post was modified 2 months ago

MacBook Pro 2018 / Radeon Pro 560X / Razer Core X / Radeon RX Vega 64 / Windows 10 (1903 - 18362.295)


rawwd and atlr liked
ReplyQuote
(@sanut_chongthanavanit)
New Member
Joined: 2 months ago
 

Confirmed here too. 
KB4512941 causes error 12.

2018 13-Inch MacBook Pro with Razer Core X Choma + Radeon VII


atlr liked
ReplyQuote
itsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
 
Posted by: @eightarmedpet

Is it worth saving a standalone iso or whatever of the “good” windows anywhere as a resource for folks?

I believe the Windows 10 1903 ISO from Microsoft website is still V1 from April 1st. We can all download them and save a copy just in case. Hopefully Win10 1909 gets better rather than the setback in this OS Build 18362.329.

Best ultrabooks for eGPU use | eGPU enclosure buying guide


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 3 years ago

rawwd liked
ReplyQuote
teltersat2
(@teltersat2)
Eminent Member
Joined: 3 months ago
 

oh! good to know! I'll stay on 1903 until there is better support for eGPUs!

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
Ningauble77
(@ningauble77)
Estimable Member
Joined: 2 years ago
 

Added this to the other (wrong) thread, but putting it here too:

Build 1903.356 being pushed out tonight has the exact same issues as the prior optional update. This one comes in as KB4515384. This one also unfortunately has security fixes also.

Rolling it back resumes normal operations of the egpu.

A Microsoft Employee I know suggested I submit this as an issue to Microsoft.  I couldn't see anyway to create a ticket without paying for a service contract, so I submitted it via the feedback hub instead.  Not super hopeful anything comes of it but it couldn't hurt.

This post was modified 2 months ago

2018 13 Macbook Pro + Core v2 + Radeon VII MacOS 10.14.6
Core X Chroma + RTX 2080 Windows 10 1903


ReplyQuote
JMGmr2
(@jmgmr2)
Active Member
Joined: 2 months ago
 

I had the same problem. Windows 10/Mojave Mac Mini 2018. 16GB/Razer Core X - Radeon 7 with 19.82 drivers.  Windows update absolutely nuked me. 1903.356.  Update keeps me from booting with the egpu connected.  Screen is black.  The computer boots if HDMI directly to monitor.  If I install the driver and try to open it, I get a gpu undetected AMD error even if the egpu is connected. My device manager shows an ominous  "Base System" addition with a driver warning exclamation mark.  I can't update the driver.  I can uninstall it but it leads to nothing. 

I had four downloaded updates. Cumulative Update for 1903 KB4512508, KB4515384 plus a flash update KB3516115 and Security KB4514359.   Currently, I removed all but Security KB4514359 (which has no removal options and I think I'm going to have to use wusa/dism via Admin in Safe Mode to nuke it...maybe) and KB4515384 which gives a error when I try to remove it now.

The updates obliterated my save points.  System Restore isn't working.  I'm getting all kinds of little errors but they ameliorated dramatically the second I tore out 2/4 updates.  I'm hoping I can remove the other two and save my install.

Does anyone know what to do about KB4515384's error upon attempted installation?  Will Powershell deal with it? Do I need to go into the registry?  Is there something I can do in the filesystem? I can't uninstall it because it gives an error but it clearly shows it there under the update uninstall screen.  It won't let me reinstall it to "fix" the update either.

Really trying to avoid a full bootcamp reinstall.  Took a ton of tweaks and configery to get Adobe CS3, Office 2k14 and similar software to work.  
I also need to get that egpu back online.

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


atlr liked
ReplyQuote
cpow681
(@cpow681)
New Member
Joined: 1 year ago
 

Just ran into this very same issue and this thread saved my life! Shut down my Mac Mini working just fine with the Core X to run updates, and then booted back up a few days later to nothing! Rolled back to .295 and reinstalled drivers from AMD website after running the cleanup tool. Back up and running. Thank you all so much.

2018 Mac Mini i7 32GB + Razer Core X Chroma (ooh lights!) + AMD Radeon 5700 XT
2015 Macbook Pro + Working Keyboard + New, Non Exploding Battery


ReplyQuote
JMGmr2
(@jmgmr2)
Active Member
Joined: 2 months ago
 

Mac_editor was helpful but apparently rolling back with the damaged update was impossible.  I had to reinstall.  Took me 8 hours.  

I have the new install...it’s working again.  Stopped at .30.  Windows is already trying to install again.  Once you guys uninstall the updates, what are you doing to keep them away?  

Thanks.

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


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 3 years ago
 

@jmgmr2

IIRC the way I prevented Windows updates is to set it to block them on a metered connection (such as tethering to a phone) then set your home network up as a metered connection (think its just a tick box).

2017 13" MacBook Pro Touch Bar
GTX1060 + AKiTiO Thunder3 + Win10
GTX1070 + Sonnet Breakaway Box + Win10
GTX1070 + Razer Core V1 + Win10
Vega 56 + Razer Core V1 + macOS + Win10
Vega 56 + Mantiz Venus + macOS + W10

---

LG 5K Ultrafine flickering issue fix


User99999 and itsage liked
ReplyQuote
 of  8