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

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

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

Macbook Pro Retina Mid 2015 m370x eGPU Radeon Rx 5700 W10


ReplyQuote
sunny
(@sunny)
Eminent Member
Joined: 1 year 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)
Trusted Member
Joined: 2 years ago
 

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

This post was modified 11 months ago

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-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
macbackpro
(@macbackpro)
Active Member
Joined: 11 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 10 months ago

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

.

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-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
macbackpro
(@macbackpro)
Active Member
Joined: 11 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.

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

.

ReplyQuote
ttamnogard
(@ttamnogard)
Trusted Member
Joined: 12 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 10 months ago

2018 Mac mini + Razer Core X + Radeon vii

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


atlr liked
ReplyQuote
teltersat2
(@teltersat2)
Trusted Member
Joined: 12 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

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
macbackpro
(@macbackpro)
Active Member
Joined: 11 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.

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

.

ReplyQuote
 of  74