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

atlr
 atlr
(@atlr)
Active Member
Joined: 2 years 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 1 year ago

User of eGPUs at my job.


ReplyQuote
Sanut Chongthanavanit
(@sanut_chongthanavanit)
New Member
Joined: 1 year ago
 

Can anyone confirm build .388 fixed the problem?

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


ReplyQuote
User99999
(@user99999)
Trusted Member
Joined: 2 years ago
 

@sanut_chongthanavanit

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

This post was modified 1 year ago

Macbook Pro Retina Mid 2015 m370x eGPU Radeon Rx 5700 W10


itsage liked
ReplyQuote
itsage
(@itsage)
Illustrious Member Admin
Joined: 4 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.

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

 
2020 15" HP Spectre X360 [11th,4C,G] + RTX 2080 Ti @ 32Gbps-TB4 (AORUS Gaming Box) + Win10 2004 [build link]  


ReplyQuote
TheMarkness
(@themarkness)
New Member
Joined: 3 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.

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
mesocyclone
(@mesocyclone)
Active Member
Joined: 1 year 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

 
2018 Mac Mini [8th,6C,B] + RX Vega 56 @ 32Gbps-TB3 (Razer Core X) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
itsage
(@itsage)
Illustrious Member Admin
Joined: 4 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.

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

 
2020 15" HP Spectre X360 [11th,4C,G] + RTX 2080 Ti @ 32Gbps-TB4 (AORUS Gaming Box) + Win10 2004 [build link]  


atlr liked
ReplyQuote
Maiiikell
(@maiiikell)
Eminent Member
Joined: 1 year 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 16" 2019 | 5500M 8Gb
- HP EliteDesk 800 G4 Mini with Thunderbolt 3 flex i/o
- AMD RX 570 4GB
- Case & PSU of a Mantiz Venus EGPU + PSU jumper
- JEYI LEIDIAN M.2 NVME Thunderbolt 3 Enclosure
- ADT-Link R43SL M.2 adapter


atlr liked
ReplyQuote
Pete Martson
(@pete_martson)
New Member
Joined: 1 year 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 1 year ago

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


atlr liked
ReplyQuote
Mauro Diez
(@mauro_diez)
New Member
Joined: 1 year ago
 

I can confirm that the latest September cumulative update for Windows 10 Oct. 3 (KB 4524147) breaks my egpu setup (2018 Mac mini, razer 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 razer 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
 of  79