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

Med Badr Chemmaoui
(@med_badr_chemmaoui)
New Member
Joined: 2 months ago
 

Thanks to this thread, I was able to pinpoint why my Vega 64 with MBP 13in 2019 wasn't working. I confirm that the latest build has issues (aka code12) -- after going back to .295, it's now working fine, Microsoft store is not working though, can't download anything. any fix to that? 

MBP 13in 2019 + RazerCoreX w/ Vega 64


ReplyQuote
realistic
(@realistic)
Active Member
Joined: 1 year ago
 

Hi.

My 2018 15'' MBP + Razer Corex X with RX480 in bootcamp is working ooookay at 18362.356.

Only issue is to keep internal screen running with dGPU ready to rock at any moment. I am able to keep dGPU online in device management without yellow exclamation mark, but internal screen keeps disappearing from display options and screen is going black in bootup. I am able to get dual screen situation up and running by booting twice: First time boot to Windows without eGPU to make internal screen available again. Then boot to Windows with eGPU plugged in from the getgo. Until next shutdown internal screen keeps running with dGPU acceleration. Next time same issue occurs again.

OS and eGPU acceleration work just fine tho, so I seem to be lucky out of this bunch.

Huomautus 2019 09 29 101526
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


rawwd liked
ReplyQuote
User99999
(@user99999)
Eminent Member
Joined: 11 months ago
 

@eightarmedpet

Thanks! this is the only way that worked as the featured update is now pushed out automatically without choice.  Looks like MS is serious in getting these featured updates rolled out there must be something important in them. 

This post was modified 2 months ago

Pending: Macbook Pro Retina Mid 2015 m370x eGPU Radeon Rx 5700 W10


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

I put a 7870XT/LE GPU in a TB3 eGPU enclosure and that works with Windows 10 build 18362.356 and Radeon driver 19.9.2 but a 5700XT gets a Device Manager Code 12 error.

One thing @user99999 and I have in common is the 7870 XT/LE is GCN 1.0 like the M370X.

I uninstalled KB4515384 as suggested in this thread.  The Win10 build is now 18362.239 and the 5700XT is now running fine.

This post was modified 2 months ago

User of eGPUs at my job.


ReplyQuote
horizondawn20
(@horizondawn20)
Active Member
Joined: 10 months ago
 

Hi everyone,

I have a 2018 Mac Mini i7 with Gigabyte Aorus GTX 1070. The eGPU won't work if I boot it on Windows after the update. I only get a black screen even though the HDMI cable is attached at the back of the eGPU. I tried to hot-plug the eGPU when Windows is starting but still the black screen appears. The lights of the eGPU is turned off but I heard its running. I tried to boot the Mac again with the eGPU turned off and the HDMI attached to the Mac Mini and it booted fine because the internal gpu took over. I then switched ON my eGPU and the screen froze for about less than a minute. After that, the eGPU was detected and it worked well. I tried to run the Heaven benchmark and it has detected the eGPU as well. When I switched the HDMI cable back to the eGPU, I can't click but I can see the windows desktop. I don't know if I'm the only one to have this kind of problem or I did something wrong. The 1070 drivers are up to date as I recently played the Modern Warfare beta.

Mac Mini 2018: i7 16GB RAM 256GB SSD
eGPU: Gigabyte Aorus Gaming Box GTX 1070


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

FYI: Radeon driver 19.9.3 that was released September 30 did not solve the Code 12 error with Windows .3xx  builds and Radeon 5700 for a Dell Precision 7730 laptop. This laptop has the most recent BIOS, TB3 firmware and drivers.

Runs fine after uninstalling KB4515384.

This post was modified 2 months ago

User of eGPUs at my job.


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

With three separate updates breaking egpus, not just via bootcamp but altogether, we have to assume that it's a mistake and not an intent.  Does anyone know where to notify them of the issue? Can we hit them with a few notices to underscore that they broke egpus?

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


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

I've used the Windows Feedback hub app to report this issue to Microsoft, the following URL should link you to it (I think you may need to be running Windows for this to work):

https://aka.ms/AA65meb

There are 2 other feedbacks complaining about the same issue, if you like you could upvote them too.

https://aka.ms/AA66had

https://aka.ms/AA669l4

I also think that anyone suffering this issue on a laptop with "official" egpu support from their vendor (i.e. Razer, Dell, HP, Lenovo, etc) would be extremely helpful to all of us if they reported this to their corresponding support, since Apple/Microsoft/Nvidia/AMD do not support egpu in boot camp, but the other vendors may be able to report this to Microsoft with more weight than these feedback hub reports.

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


atlr liked
ReplyQuote
User99999
(@user99999)
Eminent Member
Joined: 11 months ago
 

Rumour has it that it could possibly be intentional change by MS... this must have got detected during routine testing

Pending: Macbook Pro Retina Mid 2015 m370x eGPU Radeon Rx 5700 W10


ReplyQuote
sunny
(@sunny)
Eminent Member
Joined: 9 months ago
 
Posted by: @user99999

Rumour has it that it could possibly be intentional change by MS... this must have got detected during routine testing

Doubt they would intentionally break a feature. What’s in it for them?

Mac Mini 2018 / Aorus Gaming Box RTX 2070


ReplyQuote
User99999
(@user99999)
Eminent Member
Joined: 11 months ago
 

moolah, royalty fee or eGPU user group too small to warrant support...who knows maybe MS hates Apple

This post was modified 2 months ago

Pending: Macbook Pro Retina Mid 2015 m370x eGPU Radeon Rx 5700 W10


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

Rumour has it that it could possibly be intentional change by MS... this must have got detected during routine testing

What rumor? Highly doubt eGPUs are involved in routine testing in any way, given MS hardware has no Thunderbolt to begin with. By and large, eGPUs are niche in the ginormous PC market. Regardless, if we don’t see a resolution from MS (sooner or later), either we’ll stick to an old Windows build, or yet again, the community will have to attempt to take up the challenge head on and come up with workarounds.

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


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

Hey everyone. So I recently installed windows 10, have the latest build.. Was running my GTX 680 just fine in OSX and Windows. Now that I switched over to a Nitro+ Vega 64 I'm unable to use the AMD Card in windows due to error 12. OSX works fine.

What should I do in my case? I don't think I have the option to roll back as I installed the latest build just a few days ago.

I’m using a Early 2015 13” MPB. I’ve read around and found many with error 12 problems and some with none. Nothing thats currently available as a work around for error 12 has worked for me. So I definitely suspect my windows build to be the culprit.

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
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 
Posted by: @macbackpro

So I definitely suspect my windows build to be the culprit.

@macbackpro maybe confirm that by launching the command prompt and typing winver. If you just installed Windows using an ISO, you didn’t get the latest build (it must have been updated). Follow the recommendations in this thread. 

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


ReplyQuote
macbackpro
(@macbackpro)
Active Member
Joined: 2 months ago
 
Posted by: @mac_editor
Posted by: @macbackpro

So I definitely suspect my windows build to be the culprit.

@macbackpro maybe confirm that by launching the command prompt and typing winver. If you just installed Windows using an ISO, you didn’t get the latest build (it must have been updated). Follow the recommendations in this thread. 

I just confirmed it was the build. I uninstalled the last few windows updates for 1903, and installed kb4512508. Reinstalled DSDT and the AMD drivers. GPU is working fine now.

I was pulling my hair out for a little while. Reverting back isn't as hard as it might seem. You essentially need to install .295 after you clear out the other build updates.

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 am running the .3 build... last night the .387 update (optional) hit when I was trying my new 5700XT... I don't normally swear, but when I do it's at windows update.

This post was modified 2 months ago

2018 Mac mini running Radeon vii


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

So today I was testing my Razer Blade Stealth 2016 / different laptops with my Mantiz Venus to test a cable problem (different thread) and I managed to get the Blade working with the .356 build! Thing is that I just installed the Sept 30 drivers from AMD. Can't do this on my Lenovo (Corporate build) and my MBP (I need the BootCampDrivers to support both the dGPU and the eGPU)

Edit: As far as I am aware, staying in a previous feature build should not disrupt any security fixes, as they also get rolled out to the previous feature builds - but still it's a pain to not be able to install them.

Snippet
This post was modified 2 months ago

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: 2 months ago
 
Posted by: @teltersat2

So today I was testing my Razer Blade Stealth 2016 / different laptops with my Mantiz Venus to test a cable problem (different thread) and I managed to get the Blade working with the .356 build! Thing is that I just installed the Sept 30 drivers from AMD. Can't do this on my Lenovo (Corporate build) and my MBP (I need the BootCampDrivers to support both the dGPU and the eGPU)

Edit: As far as I am aware, staying in a previous feature build should not disrupt any security fixes, as they also get rolled out to the previous feature builds - but still it's a pain to not be able to install them.

Snippet

I tried a newer windows build with the bootcamp drivers, and the sep 30th AMD drivers. Neither worked. I wonder if dgpu laptops work still.

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


ReplyQuote
Delta_Bravo
(@delta_bravo)
New Member
Joined: 1 year ago
 

Prety much everyone who have problems with this newest update are with AMD eGPU, but I can confirm that my nvidia setup (Mac mini 2018 + razer core  v2 + nvidia 1080Ti) also encountered the same problem. The only exception is that I dont't have error code 12, but every other (10, 1, 43). Neither hot or cold plug worked for me after update. I was able to make things work again after uninstalling two last updates (KB4517211,  KB4515384) reverting back to build 18362.30.

This is sad 😥

update:

I cheked my MacBook Pro 15 late 2018 and looks like KB4515384 is installed there and everything is working fine, thats strange, I will try to reinstall this update on Mac mini

update 2:

I reinstalled KB4515384 back on mac mini (build 18362.356) and everything becomes even more complicated, because this build works very well on my MacBook Pro 15 but on Mac mini it's not: cold plug won't work anymore, hot plug is working but with significant delay, delayed plug (one with spinning dots timing) is also working. 

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


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

I think this would get escalated as razer runs win 10 and sells this egpu.... (and they are the best in the game).

Also, did we identify that 18362.387 also has the error?

I'm running .30, is there a way to get to .295 (August 13 build)

This post was modified 2 months ago

2018 Mac mini running Radeon vii


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

@ttamnogard OS Build .387 has similar error 12 issues. Either staying at .30 or run a manual update to .295 would keep your AMD eGPU working. 

The Microsoft Surface event just wrapped up and there’s a clear message. Microsoft does not want to participate in the Thunderbolt ecosystem. Intel and Apple run this show and Microsoft wants none of it. They start offering ARM and AMD products as well. Again we’re seeing big players flexing their muscle at the expense of end users.

This post was modified 2 months ago

Best ultrabooks for eGPU use | eGPU enclosure buying guide


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

@itsage

And Razer is a niche compared to Dell, Lenovo, etc (I agree with your feelings on this). I am wondering why whatever they are doing is breaking the eGPU... I would think that Intel would have enough weight to make sure that Microsoft wouldn't break thunderbolt3? With tbolt4 coming up and usb C growing to adopt the thunderbolt standard as the universal one.... I don't understand the rationale... wouldn't increased use of eGPU increase the market segment?

2018 Mac mini running Radeon vii


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

I highly doubt that Microsoft did this on purpose.  I also am not sure any improved functionality we have seen in boot camp was on purpose either.  At any rate Razer is advertising full compatibility with their enclosures and laptops, including cards not officially sanctioned by AMD like the Radeon VII.  Razer laptop customers should be letting them know about this so Razer can accelerate a resolution.

I think the main issue atm is that egpu adoption is niche to begin with, *most* windows laptop egpu users seem to have gravitated towards nvidia cards, and many mac users have gone AMD to maintain functionality under MacOS, but have no official support from anyone in windows, so the total number of people affected by these issues with hardware officially sanctioned to be doing so is pretty small.

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


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

I also am not sure any improved functionality we have seen in boot camp was on purpose either.

Definitely agree. The improvements are likely side effects of the intended changes.

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


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

For some reason, an Intel NUC 6iKYK works with an eGPU 5700XT and OS Build 18362.356. 

I do not know why.

Intel NUC 6i7KYK
BIOS 59
Intel HM170 (Skylake PCH-H)
Thunderbolt Alpine Ridge (1575) host FW 27
Thunderbolt software package 17.4.78.500
Windows 10 Version 1903 (OS Build 18362.356)
AMD Radeon Driver package 19.9.3

This post was modified 2 months ago

User of eGPUs at my job.


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

October 2, Build .388 (KB4524147) has a Code 12 device manager display driver error with a Dell Precision 7730 laptop connected to a 5700XT in a Thunderbolt chassis.

 

Dell Precision 7730 laptop
BIOS 1.11.0
Intel CM246 (Cannon Lake-H) chipset
Thunderbolt Titan Ridge (15EB) FW 41.00
Thunderbolt software package 17.4.78.500
Windows 10 Version 1903 (OS Build 18362.388)

AMD Radeon Driver package 19.9.3

 

This post was modified 2 months ago

User of eGPUs at my job.


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

Similar situation here, desktop pc with TB3 addin card works fine with 356, with both a rtx 2080 dgpu and radeon vii egpu, but MacBook Pro 13 gets error 12 with just the RVII.   According to thunderbolt control panel, desktop is not "egpu capable" either.

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


atlr liked
ReplyQuote
User99999
(@user99999)
Eminent Member
Joined: 11 months ago
 

Runs ok on latest update. 

DevieManager2
Wattman
UnigineRx580 2
This post was modified 2 months ago

Pending: Macbook Pro Retina Mid 2015 m370x eGPU Radeon Rx 5700 W10


itsage liked
ReplyQuote
atlr
 atlr
(@atlr)
Active Member
Joined: 8 months ago
 
Posted by: @eightarmedpet

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

Shazbat.   Window Media Tool now creates a USB installer that incorporates the .356 build which does not allow uninstalling the cumulative update KB4515384  that is causing problems. 

This post was modified 2 months ago

User of eGPUs at my job.


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

Can anyone confirm build .388 fixed the problem?

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


ReplyQuote
User99999
(@user99999)
Eminent Member
Joined: 11 months ago
 

@sanut_chongthanavanit

Every system is different.  My system didn’t even need the dsdt  large memory mod. 

This post was modified 2 months ago

Pending: Macbook Pro Retina Mid 2015 m370x eGPU Radeon Rx 5700 W10


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

It would be great for all of us to check OS Build .388 and report whether error 12 is no longer an issue. It’s easily reversible if you currently run .30 or .295.

Best ultrabooks for eGPU use | eGPU enclosure buying guide


ReplyQuote
TheMarkness
(@themarkness)
New Member
Joined: 2 years ago
 
Posted by: @itsage

It would be great for all of us to check OS Build .388 and report whether error 12 is no longer an issue. It’s easily reversible if you currently run .30 or .295.

388 no go here same as 329/356 for me. Akito Node w/ Radeon VII on a 2018 MacBook Pro 15 Vega 20. Reverted back to 295 again to get rid of error 12.

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


atlr liked
ReplyQuote
mesocyclone
(@mesocyclone)
Active Member
Joined: 4 months ago
 

I don't know how relevant this question is, but for someone like me who has yet to purchase a Windows license, is it still possible to roll back to a working configuration? Would I need to purchase Win 10 Pro or is Home the same in terms of build options? I'm keen on using it in bootcamp on a 2018 Mac Mini with a Razer Core X + Vega 56 eGPU setup. 

2018 Mac Mini/i7/16GB
Razer Core X/Sapphire Pulse Radeon Vega RX 56
Old 1080p Dell monitor


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

@mesocyclone As long as you have a restore point you can go back. It makes no difference between the Pro or Home version.

I tried .388 and error 12 remains an issue. Rollback to .295 and everything worked great, including AMD eGPU hot-plug on the 2019 13″ MacBook Pro.

Best ultrabooks for eGPU use | eGPU enclosure buying guide


atlr liked
ReplyQuote
Maiiikell
(@maiiikell)
Active Member
Joined: 2 months ago
 

I can also confirm that with Macbook pro 2018 15" 560x with a RX 5700 in the latest windows build error 12 is still there. Rolled back to 18362.239 and everything is working again.

Macbook Pro 15" 2018


atlr liked
ReplyQuote
 of  8