eGPU error 12 fail after update to Windows 10 1903 or newer (OS Build 18362.329 ...
 
Notifications
Clear all

[Solved] eGPU error 12 fail after update to Windows 10 1903 or newer (OS Build 18362.329 or newer) inc downgrade pci.sys version solution  

 of  69
  RSS

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.

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

atlr liked
ReplyQuote
Test1
(@test1)
Eminent Member
Joined: 1 year 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?

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

itsage and atlr liked
ReplyQuote
atlr
 atlr
(@atlr)
Active Member
Joined: 1 year 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
(@pete_martson)
New Member
Joined: 9 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: 4 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

 
2020 13" MacBook Pro [10th,4C,G] + RTX 2080 Ti @ 32Gbps-TB3 (AORUS Gaming Box) + Win10 2004 [build link]  


ReplyQuote
teltersat2
(@teltersat2)
Trusted Member
Joined: 11 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) + Noctua NF-A14 + Gigabyte GeForce GTX 1070 G1 Gaming 8G (rev. 1.0)
Replaced parts: Sapphire Radeon RX 580 Nitro+; Sapphire Radeon RX Vega 64 (Reference model)


ReplyQuote
Dumitru Pascu
(@dumitru_pascu)
New Member
Joined: 10 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)
Eminent Member
Joined: 1 year 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 350W (Noctua NF-A12x25 ULN) + PowerColor RX 5700 XT 8GB, TEKQ Rapide TB3 1TB SSD, macOS Catalina, Win10 Pro
Mac Pro 2010, X5690 3.46GHz 6c, 64GB RAM, Samsung SM951 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: 3 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 9 months ago

2019 16 Macbook Pro + Core v2 + Radeon VII MacOS 10.15.1
Core X Chroma + RTX 2080 Windows 10 1909
Asrock X570 Phantom Gaming ITX/TB3, Ryzen 5 3400G + Core v2 + Radeon VII Win10 1909

 
2019 ASRock X570 Phantom Gaming-ITX/TB3 [R3K,4C,G] + Radeon VII @ 32Gbps-TB3 (Razer Core V2) + Win10 1909 [build link]  


rawwd and atlr liked
ReplyQuote
Suwit Suriyasriwan
(@suwit_suriyasriwan)
Active Member
Joined: 9 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

 
2018 15" MacBook Pro (RP560X) [8th,6C,H] + RTX 2070 Super @ 32Gbps-TB3 (ASUS XG Station 2) + Win10 [build link]  


ReplyQuote
 of  69