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

itsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
 
Posted by: @aj_scarcella

@itsage Awesome!

Quick question for you as well, now that you mention XConnect: when your Mac Pro had a working eGPU, did you ever get XConnect going? For a time, while my eGPU wasn’t working in Windows, I did have the XConnect icon in my taskbar. It doesn’t seem to be there anymore though, and I can’t figure out if there’s a way to get it back, or if it’s even worth it.

XConnect icon appearing is inconsistent. I have seen no icon but eGPU working and vice versa. In an iGPU-only computer, if the XConnect icon doesn’t appear internal display loopback doesn’t work automatically. You can manually assign it to accelerate any app/game through Windows graphics settings similar to a dGPU host. XConnect showing but non-functional eGPU is usually a scenario when the AMD eGPU is detected and drivers loaded during boot but Windows yellow-bangs it somehow.

@roedi78 This particular error 12 issue effects many systems other than Macs running Windows in Boot Camp. I have recently tested a 2019 MSI Prestige 15 which suffers the same error 12 when paired to an AMD eGPU. 

@tailslide The 2016 15″ MacBook Pro is actually a rare exception to this issue. I have the same machine and it has survive all the current OS Builds with the latest being Win10 1909 18363.449. I use automate-eGPU EFI boot loader with the modified DSDT.aml. You can find an example build of 2016 15″ MacBook Pro + Radeon RX 5700 XT.

This post was modified 4 weeks ago

Best ultrabooks for eGPU use | eGPU enclosure buying guide


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

I am still on the 295 for my mini with no harm no foul. I am holding off on Catalina unless someone else is confident that a direct update to the system won't force me to do a full recovery.

Also, are we allowed to host ISO or is that too much of a risk as egpu.io can't support if people have issues?

2018 Mac mini running Radeon vii


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

@ttamnogard We don’t host files that don’t belong to our community. Members can reference or link to other file hosting services.

 

Best ultrabooks for eGPU use | eGPU enclosure buying guide


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

Pretty much the same problem that bootcamp's users reported, code 12 on device manager since update to .300. Version from winver is 19018.1.

But it doesn't work anymore after restarting the computer and using it without the eGPU. It actually started working after a BSoD, caused by plugging it during boot sequence iirc.

Razer Blade Stealth 2019 w/ MX150
Razer Core X + AMD Radeon VEGA 64


ReplyQuote
Roedi78
(@roedi78)
Trusted Member
Joined: 2 years ago
 

@tidesgoesegpu

Just tested the most recent Insider Preview build of 20H1 (19023.1) from today...

Same probs than before (error 12) on my system.

Had to roll back to my last stable build (18922.1000). 🙁

This post was modified 4 weeks ago

MacBook Pro 15" Late-2016 w/TB 16GB with RP460 4GB
automate-eGPU EFI 1.0.5 USB w/DSDT override
 macOS Catalina 10.15.1 w/Win10 (1903) BootCamp
Sonnet Breakaway Box 650 TB3 /wAMD Sapphire Radeon VII 16GB
 Alphacool Eiswolf 240 GPX-Pro AiO Radeon VII M02 Water Cooling


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

@roedi78 I'm sorry to read that. I edited my first message to avoid this situation and I'll be more cautious next time I don't understand the whole chain of effect.

I contacted AMD's support to update my ticket. I tried to replicate working conditions with no success. I also updated to 19023.1 with no improvement. Would there be a way to check stop error codes after reboot ?

This post was modified 4 weeks ago

Razer Blade Stealth 2019 w/ MX150
Razer Core X + AMD Radeon VEGA 64


ReplyQuote
teltersat2
(@teltersat2)
Eminent Member
Joined: 4 months ago
 
Posted by: @ttamnogard

I am still on the 295 for my mini with no harm no foul. I am holding off on Catalina unless someone else is confident that a direct update to the system won't force me to do a full recovery.

Also, are we allowed to host ISO or is that too much of a risk as egpu.io can't support if people have issues?

I updated my MBP to Catalina with no issues to be honest. My Boot Camp is my main partition and still works with no issues (still on 1903-295)

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
MackieWack
(@mackiewack)
Active Member
Joined: 4 weeks ago
 

I currently run a Gaming Box GTX 1070 on my 2017 13" MacBook Pro with retina and touchbar.  I've order the PowerColor Red Devil RX 5700 XT and it comes tomorrow with a Razer Core X.  It's interesting to see what feels like a fair bit of non-uniformity regarding AMD and Windows Bootcamp.  I'm running 1909 (18363.476) which is the most current build.  I have no problems with my Gaming Box (Outside of having to do a timed plug-in on boot and restarting the audio driver, which all seems pretty much par right now for Nvidia and boot camp).  I would love the option of plug-and-play in Catalina that the rx 5700xt gives now but also need it to work in Windows cause I use Steam for games in windows only.  The fact that several have gotten things working is heartening.  I'll see what happens.  I've downloaded DDU in advance.  I assume I'll just want to remove all my Nvidia drivers prior to getting the rx5700xt to work in boot camp.

There are a couple other things I'm interested in.  I wonder about the performance of the Razer Core X vs the Gaming Box.  Catalina recognizes the Gaming Box just fine, hot plugging it.  Just doesn't see the Nvidia card.  If the performance is similar, I'm quite tempted to DIY my Gaming Box for the PowerColor card.  Yes, I know it's too big but nothing a little (or not so little) hole in the end of the Box won't fix!  I think the gaming box has a 400w PSU.  Any comments on the viability of the Gaming box running the rx5700xt given that I can figure a way to fit it?

2017 MacBook Pro 13" (iGPU - Intel Iris 650) with Retina and Touchbar. Windows boot Camp (1909 build 18363.476) + Gigabyte Gaming Box GTX 1070


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

@mackiewack Timed hot-plug should allow the RX 5700 XT eGPU to work with your 2017 13″ MacBook Pro in Boot Camp. I have a very similar setup that I use automate-eGPU EFI boot loader instead of timed hot-plug. DDU is always a good idea when switching cards even if they are the same brand. 

If you’re to modify the Gaming Box Thunderbolt 3 mainboard, you’d need 90-degree angle 24-pin power adapter. Gigabyte had this connector placed vertically so it blocks any cards longer than ITX form factor. The 400W PSU should be good to handle the RX 5700 XT. Considering 60W Power Delivery to the 13″ MBP and about 30W overhead, you still have around 300W for the graphics card.

Best ultrabooks for eGPU use | eGPU enclosure buying guide


ReplyQuote
MackieWack
(@mackiewack)
Active Member
Joined: 4 weeks ago
 

@itsage

Thanks so much for comment.  I'm just fine with boot-plugging so this is excellent news.  Also great to know the PSU on the Gaming box will work.  As for that right angle 24 pin ATX...I actually had one in the cart and removed it. Doh!  I had taken the Gaming Box apart the other day and noted that clearance issue.  As long as performance doesn't differ significantly between the two, I'm probably going to try and figure something out with the Gaming Box.

Ummm.  What does the "reset system" option in eGPU-EFI do?

I fixed it.  Being an inquisitive dummy, I clicked that option as my GTX 1070 was not recognized by eGPU-EFI.  Then it wasn't working at all.  I unplugged the gaming box for a few minutes and I'm back to stable boot-plugging.  whew!

This post was modified 4 weeks ago

2017 MacBook Pro 13" (iGPU - Intel Iris 650) with Retina and Touchbar. Windows boot Camp (1909 build 18363.476) + Gigabyte Gaming Box GTX 1070


ReplyQuote
(@denis_ja)
New Member
Joined: 4 weeks ago
 

Hi guys,

I read the whole thread and I can confirm that this is not a Apple or Bootcamp issue but a TB3 issue since Windows 1903. I use TB3 for Networking between two PCs connected over a TB3 cable. Since 1903 the TB3 Networking is not working properly anymore. Reading Speed has been reduced to 60% and writing Speed to 0.1%. So I can only write in KBytes/Sek, before it had been 600MB Sek. 

If you Google TB3 issues with 1903 you will find a lot of issues. 

I did a clean install with 1909 still the same issue. Going back to 1809, TB3 functionallity is broken I guess. 

What did I try: DCH Drivers and non DCH Drivers, almost everything I could find. Updated the Firmware. I spend over 50hours in solving this issue, no Chance at all..

What do you guys think?

Some Topics:

Networking:  https://social.technet.microsoft.com/Forums/en-US/9604447b-131c-41b4-9c72-18f229013a66/slow-upload-speed-to-qnap-nas-since-build-1809-and-1903?forum=win10itprogeneral

Docks: https://www.reddit.com/r/windows/comments/cs65j1/1903_update_disabled_usb_c_port_functionality/

NAS/Networking:  https://superuser.com/questions/1452466/windows-10-v1903-can-no-longer-write-to-thunderbolt-reading-is-ok

This post was modified 4 weeks ago

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


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

@denis_ja Thank you for your feedback regarding other features through Thunderbolt 3 are also having issues in Windows 10 1903 and newer. Microsoft clearly doesn’t want to get onboard with Thunderbolt 3 (Apple & Intel IP). They have no motivation to make sure TB3 functionalities aren’t breaking with their software updates.

 

Best ultrabooks for eGPU use | eGPU enclosure buying guide


ReplyQuote
MackieWack
(@mackiewack)
Active Member
Joined: 4 weeks ago
 

That is all very disheartening.   But I guess my puzzlement then is why does my Nvidia (GTX 1070 Mini ITX in my gaming box and a Razer Core X) card work fine in 1909 across TB3?  If this is truly just a TB3 issues then I would think it will affect whatever card you try to use across Thunderbolt. 

However, this theory is not true.  I have successfully used GTX 1070 across TB3 on 1909 (most current build) without any difficulty just this AM (In bootcamp with boot-plugging as before).  I then attempted to use my new PowerColor RX 5700XT.  It is "seen" in Windows but Windows states that there is no driver.  I current going through steps to cleanly install AMD drivers and then many disable some PCI ports that I saw someone else do to successfully get AMD cards working in Bootcamp windows.

2017 MacBook Pro 13" (iGPU - Intel Iris 650) with Retina and Touchbar. Windows boot Camp (1909 build 18363.476) + Gigabyte Gaming Box GTX 1070


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

Just a quick "thank you" to everybody here who is working on this issue. I was starting to get the itch to update my 2018 Mac mini  to Catalina, but it would break a number of (mostly older) games that I'd like to still have access to. Since those games are unlikely to ever get updated to 64-bit, I first tried running them in Mojave and Windows 10 VMs in Parallels 15, but with no luck - some worked OK, some seemed to work for a bit and then crashed, some didn't work at all.

So, I had a choice to make: either keep a Mojave boot drive around for when I wanted to play the games in question (boring, and still unable to play Windows-only games), or try to get Windows running, either via Boot Camp or some other means that would give it full access to hardware, including my eGPU. I first went the Boot Camp route - not easy, since I only have a 250GB SSD in the mini - but ran into the dreaded Error 12 because I used the latest Windows 10 ISO, with no way to uninstall any of the updates that break eGPU support. So, I nuked that option and started over.

Since @mydoomfr had uploaded a 1903 V1 ISO, I didn't go hunting around (the Swisstransfer link still works). I had tried various methods of getting Windows installed directly onto an external SSD via WinToUSB, both via Parallels and VirtualBox, but kept ending up with a failure partway through the install, or with a disk that wouldn't boot. I gave it one more try before giving up (via VirtualBox) and, to my surprise, it completed and was bootable.

However, since I didn't go through Boot Camp, @mydoomfr's comment about not worrying about his ISO being French since you could pick your language during install turned out not to be the case - WinToUSB blows right past that choice with no input possible. So, while I had a bootable copy of Windows, it was entirely in French, which meant spending a fair bit of time with Google Translate pointed at my screen so that I could figure out everything I needed to do to download and install the various language packs and pick the right settings to get Windows switched to English (mostly - there are still small vestiges of the French origins scattered around).

So, that got me to .30, and I was eventually able to get all the proper drivers for everything installed and working up to the point of plugging in the eGPU. Unfortunately, even after getting the latest Radeon drivers installed, I was still getting Error 12 in Device Manager. Even though I had read some of the posts in this thread, I hadn't seen @daniele_pugliese's original post that spelled out exactly which update was needed to take 1903 V1 to .295, and after a couple of reboots, everything is now working perfectly.

So, thanks to everyone who has worked so hard on the various issues here. The site was a tremendous help last year in making sure I got a good, reliable setup with an eGPU on my new Mac mini - my main concern - and has now also been a huge help in getting Windows up and running with the eGPU, as well. I have turned off Windows Update in Services, and have also created a few manual restore points as I installed software, so I should be well-protected until such time as Microsoft actually fixes the issue with more recent builds (assuming that they do, of course).

2018 i7 Mac mini - OWC Mercury Helios FX (Sonnet 550) - ASRock Vega 56 - BenQ SW271


itsage liked
ReplyQuote
(@dumitru_pascu)
New Member
Joined: 2 months ago
 

Guys, now that 1909 update is out, anyone tried to use both with AMD and NVIDIA cards? Does it work? I feel I did my worst buy ever when it comes to HW setup.

Mac Mini 2018, i7, 16 GB RAM, 512 GB SSD, Razer Core X Chroma, Asus AMD Vega 64 Strix.


ReplyQuote
lexine
(@lexine)
Trusted Member
Joined: 2 years ago
 

@dumitru_pascu I actually tried the Win10 1909 paired with Macbook 13" 2018 model along the AMD RX580 + Razer Core X.
Actually I had the no problem with setting up the egpu with this configuration (only the issue with the iGPU being deactivated which was solved by the automate-egpu-efi ) ...

Actually process for me was:
1. Installation of Windows 1909 via bootcamp
2. Installation of standard bootcamps drivers
3. plugging the egpu & installation of latest AMD officials drivers
4. Initially I have seen error 12, so therefore I disabled pcie express port #5 in system, however this was related only because I hot plug the egpu into already booted up Windows systems, with some of the later tests I realised that I can leave that controller enabled

The bootup process is fairly simple, just plug the egpu and turn on the mac, if I dont use the automate-egpu-efi (apple_set_os.efi / included in automate-egpu-efi, the iGPU will be deactiveted with just he windows logo on macbook display), when I use the mentioned solution everything works fine.

Capture
Capture

This post was modified 4 weeks ago

2017 13" MacBook Pro TouchBar + [email protected] (Aorus Gaming Box) + macOS10.13 & Win10


ReplyQuote
(@denis_ja)
New Member
Joined: 4 weeks ago
 

@lexine

Ok this is getting really interesting. You deactived the PCIe Port 5. This port is for me mapped for the TB3 Networking. I tried to find current Drivers for the chipset, 1909 installs Drivers from 2016. This could be for me a proper solution and Maybe for others too..

 

edit: I installed the 10.1.1.45 manually for port 5. Still TB3 issues for Networking 🙁

This post was modified 4 weeks ago

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


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

@lexine

Wait, I'm confused. So that means eGPU are working again in the newest version of Windows or is this just a lucky coincidence? However, I will follow your instructions and see if it's also working for me. (When I have the time to go down that rabbit hole again ^^)

MacBook Pro 13' 2018 & Mac mini 2018, Razer Core X, RX 5700XT


ReplyQuote
lexine
(@lexine)
Trusted Member
Joined: 2 years ago
 

@denis_ja sorry I cant really comment on the networking issue, as I don't have this setup … 

@maximilian_aussprung Well that's it the question, not sure if just lucky or they fixed something, maybe worth to mentioned that I updated my macos to Mojave as well (I think there was some apple firmware upgrade as well included), this the version of windows I am running :

Capture

but definitely more people would need to test have some final confirmation 

2017 13" MacBook Pro TouchBar + [email protected] (Aorus Gaming Box) + macOS10.13 & Win10


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

@lexine

Thanks, with my setup I got the error 12 after the upgrade to 1909. Before 1903 it was working flawlessly without any other workaround :(. I am considering reinstalling the whole bootcamp partition again.

Mac Mini 2018, i7, 16 GB RAM, 512 GB SSD, Razer Core X Chroma, Asus AMD Vega 64 Strix.


ReplyQuote
(@adam_kilian)
Active Member
Joined: 4 weeks ago
 

enybody have a link to Win10 18362.295 iso ?

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


ReplyQuote
Tailrotorblade
(@tailrotorblade)
New Member
Joined: 4 months ago
 

With 18363.476 build (1909) I have error 12 with my MacBook pro too.

Thierry 

Mac mini 2018 hex 32Go Ram - Razer Core X - AMD RX5700XT
MacBook Pro 13 2019 - 8Go - 2TB3


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

@adam_kilian

I don't think there is a direct link to 295 - you have to download V1 (.30) and install the update Daniele linked in the first post of this thread to get to 295.

I just did some searching, and found this link to get whatever version of Windows you want:

https://tb.rg-adguard.net/public.php

Just feed it the correct information, and it will download directly from Microsoft - you want 18362.30, the x64 version. This would have made my life so much easier a couple days ago 😜

2018 i7 Mac mini - OWC Mercury Helios FX (Sonnet 550) - ASRock Vega 56 - BenQ SW271


ReplyQuote
lexine
(@lexine)
Trusted Member
Joined: 2 years ago
 

@dumitru_pascu sorry to hear that, I was kind of hoping that they fixed something, but seems I was just lucky ? btw when do you connect the egpu ? I need to connect it before I select windows to boot-up, all the hot-plug attempts during windows boot gave me error 12 as well. Also I did perform the clean bootcamp installation with 1909 available to download from Microsoft website.

2017 13" MacBook Pro TouchBar + [email protected] (Aorus Gaming Box) + macOS10.13 & Win10


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

@rnb2 Excellent find! I updated the OP with the link.

 

Best ultrabooks for eGPU use | eGPU enclosure buying guide


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

@lexine

Polaris GPUs seem to be working fine on newer Windows builds (there were some earlier posts who had success as well IIRC). Problem seems to lie with Vega/Navi.

purge-wranglerpurge-nvdaset-eGPU
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


itsage liked
ReplyQuote
AJ Scarcella
(@aj_scarcella)
Trusted Member
Joined: 2 months ago
 

Currently running 1909 (18363.476) and eGPU is still working as per my previous post. Oddly enough though, in my most recent boot, I didn't go through automate-eGPU EFI to load Windows, but the eGPU still showed up in Device Manager and is working. This means that the DSDT override is currently not active, so I don't have a Large Memory device in Device Manager at all. 

Mac Pro 2013
OWC Mercury Helios FX
Radeon RX 580 8GB


ReplyQuote
(@adam_kilian)
Active Member
Joined: 4 weeks ago
 

@rnb2

thank you very much 😉

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


rnb2 liked
ReplyQuote
red_joe
(@red_joe)
New Member
Joined: 3 weeks ago
 

Hi guys, I have a Lenovo Yoga 920 laptop with Razer Core X and AMD Vega 64 which ran into the same Error 12 problem described here. Was working perfectly fine until last month when I updated my windows. Currently running Windows version 1909 (Build 18363.476).

Unfortunately, I can no longer go back to the previous build because the files has been deleted by Windows after 10 days from the update. I have a few questions about how to go back to the previous version of Windows.

  • If I choose the "Reset this PC" option in Windows Recovery settings, will it reinstall the Windows version that came when I bought the laptop, or will it simply reinstall the latest clean version of Windows?
  • If it is the latter, perhaps my only option is to install Windows 10 1903 V1 ISO (OS Build 18362.20) from external drive. It may be a stupid question, but how can I create a bootable drive? I have already downloaded the Windows ISO file from https://tb.rg-adguard.net/public.php and I already have a USB drive that I can use.
  • Can I simply install the Windows by using virtual DVD software (e.g. Daemon Tools)? Or is it just safer to create a bootable drive first and then install from there?

Sorry for the stupid questions.

Thanks in advance for your help.

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


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

For me upgrade to 1909 does not work (err 12) on Mac mini + Vega56.

Before upgrade to 1909 version, I was running 1901 V1 with VERY poor performances issues in games (Apex, Paladins), FPS drop from 140 to 10... while moving (fast) the mouse around the screen. (lower graphics settings)

I don't know if it's related to Windows, AMD drivers, or TB3 bandwidth. I've also tested several settings tweaks like enable/disable freesync, but it was unplayable.

At this point, I'm considering to buy another eGPU with an RTX ($$$$$$) card to avoid err12 code and having an enjoyable gaming experience..........

This post was modified 3 weeks ago

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
 
Posted by: @rnb2

@adam_kilian

I don't think there is a direct link to 295 - you have to download V1 (.30) and install the update Daniele linked in the first post of this thread to get to 295.

I just did some searching, and found this link to get whatever version of Windows you want:

https://tb.rg-adguard.net/public.php

Just feed it the correct information, and it will download directly from Microsoft - you want 18362.30, the x64 version. This would have made my life so much easier a couple days ago 😜

Downloaded and saved to Dropbox for safe keeping.

Cheers buddy.

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


rnb2 liked
ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined: 3 years ago
 
Posted by: @mydoomfr

For me upgrade to 1909 does not work (err 12) on Mac mini + Vega56.

Before upgrade to 1909 version, I was running 1901 V1 with VERY poor performances issues in games (Apex, Paladins), FPS drop from 140 to 10... while moving (fast) the mouse around the screen. (lower graphics settings)

I don't know if it's related to Windows, AMD drivers, or TB3 bandwidth. I've also tested several settings tweaks like enable/disable freesync, but it was unplayable.

At this point, I'm considering to buy another eGPU with an RTX ($$$$$$) card to avoid err12 code and having an enjoyable gaming experience..........

I had a huge issue when I installed the my Corsair keyboard driver (keyboard is connected thru a thunderbolt 3 dock on the other side of the macbook). The games became unplayable. But as soon as I uninstalled it it became normal again. Not sure if that's your problem.

mid-2017 15" Macbook Pro RP555 + [email protected] (Mantiz Venus) + macOS & Win10


ReplyQuote
confidantduck
(@confidantduck)
Active Member
Joined: 3 years ago
 

*update!*

HUZZAHHHH The fix worked y'all!

Here are my steps 

1a. I created a bootable usb drive via rufus(free and no bs) with the 1903 V1 link that has been posted in the original thread. I booted up from the bootable drive and installed it over my old drive where the os was installed(think this preserves windows license? no idea).

1b. It's now reset to 1903 V1, showed .30 when running 'winver' command, I turned off internet and windows update completely via the 'Services' function just in case I got undesirable updates.(Later I found out I was jumping the gun a little)

1c. Did the update to .295, installed .295, didn't show until restart(ironically couldn't install .295 with windows update disabled, needed to reenable it but with internet off
to let it continue)

1d. Since we did a full reset, drivers for almost everything was non-existent, this is where I connected the razer core and installed drivers for the 5700xt, the screens flash to life(WOO we're back baby!).

1e. Restart was done, winver shows .295, since all drivers weren't existent, which included the iGPU from intel, internal screen stopped working after this restart. Also, most of the razer core components couldn't because windows update was disabled (lol).

1f. Here I created a restore point in case anything went wrong, and let windows update do its thing, surprisingly it decided to update most things except the next
ver of 1903, which is awesome. I also had the 'metered connections' if that matters, was on ethernet too but hey, not complaining that it didn't install it.

1g. Finally, had to go out of my way to download the 620 drivers, windows update didn't pick up on it for some reason, glad the intel driver update utility seemed to be able to solve the rest of my issues.

DONE 

Those were the steps I took and my setup is working beautifully again! I ran unigine(max settings) just so we could see how well it does now, attached the picture below!

__________________________________
I just want to say thank you to the community for helping out so much and reporting all your builds. I initially was not able to fix my Razer Blade Stealth(early 2019) + Razer Core V2 Setup + Vega 56.

Backstory: I've been thinking that it's been a hardware issue this whole time since Aug. Been trying to debug if it was my laptop that was a lemon, or my egpu, or my gpu, and support staff have been righty scratching their heads too.

What's interesting for me is that I was able to make it work with a friend's GTX 1060 on Win Ver 1903(18362.472).

Also since then, I've bought a 5700xt thinking that perhaps it was my vega 56 that was the issue. Nope, the new gpu doesn't work either.

Finally chanced upon this thread and looking forward to reset it with 1903 V1(or further back if it doesn't work), will updated y'all on this!

 RBSearly2019 5700xt
This post was modified 3 weeks ago

Current setup: Late 2016 Razer Blade Stealth, Powercolour devil box + gtx 1060

Prev setup: 2016 13" MBP (no touchbar)
Powercolor Devil Box + GTX 1060/GTX 980(succeeded somewhat), RX480 Nitro+ 4GB(attempted but failed)


rnb2 liked
ReplyQuote
MackieWack
(@mackiewack)
Active Member
Joined: 4 weeks ago
 

Follow up on my attemps with RX 5700 Xt and Razer Core X.

TL;DR - It failed (on the windows side)

Even after cleaning up in Safe Mode with DDU and re-installing AMD drivers, I was unable to get the 5700 xt working.  It was recognized but the driver was not functional.  I got error 12 and then error 43.  Tried some of the PCI disabling stuff and only managed to mess up my drivers for windows bootcamp.  had to down load current boot camp drivers and re-install which has everything working right on the gaming box 1070.  I decided to RMA the rx 5700 xt and core X a day later. 

The decision to return everything was based on a couple of things.

  • struggle to get things going on Windows 1909 (current).  I really didn't want to have to go back to windows pre 1903 and then be actively trying to keep it from updating to prevent breaking everything.  (A number of years ago I was actively involved in the hackintosh community and had a function rig for over 5 years.  I know how this all goes down.  It can be a real headache and I'm no longer up for that.)
  • the second deal breaker was the performance I was getting with the 5700 xt in mac os catalina.  quite underwhelming with about 60 fps in Heaven on max settings with Open GL.  I had been hitting 72 fps in heaven in windows bootcamp with DirectX on my Gaming box 1070.  My OpenGl numbers in Windows were ~80fps with the 1070 gaming box.
  • the Razer Core X box is MASSIVE.  It is literally 6-8 times the size of the gaming box and built like a tank.  I would like some level of portability and the idea of toting the razer core around would like tucking you mid-ATX case under your arm.  Guess I should have realized this but seeing the two together really brought that reality home.

Given what felt like lackluster performance in Catalina, and the real possibility of needing to reinstall windows, I opted to go back to Nvidia.  I know that works (timed boot plug & disable/enable audio driver).  The size of the Core was a bit of a deal breaker as well.

My 2cents in all this is AMD and Windows boot camp does not appear to be a consistent or reliable setup currently.  If you like to tinker, by all means, go for it.  But you better do a lot of reading first.  Hopefully this will all get figured out in not too long but for now I'd recommend deciding on which OS you want your graphical accelerations and then purchase accordingly.  This is of course only intended for Macbook users like myself.  (see my signature for the details)

2017 MacBook Pro 13" (iGPU - Intel Iris 650) with Retina and Touchbar. Windows boot Camp (1909 build 18363.476) + Gigabyte Gaming Box GTX 1070


ReplyQuote
DeeKay
(@deekay)
New Member
Joined: 1 month ago
 
Posted by: @mackiewack
[...] My 2cents in all this is AMD and Windows boot camp does not appear to be a consistent or reliable setup currently.  If you like to tinker, by all means, go for it.  But you better do a lot of reading first.  Hopefully this will all get figured out in not too long but for now I'd recommend deciding on which OS you want your graphical accelerations and then purchase accordingly.  This is of course only intended for Macbook users like myself.  (see my signature for the details)

Sums up how I (and probably few others) feel on the matter.
I've spent about 15 hours in total on the issue (reinstalling Windows 3 times in the process) post a 5700 XT purchase, while the 970 GTX I upgraded from, still works fine.

An AMD card was the choice because of native macOS gaming, but consider the following:
1. Games that weren't specifically optimized and tested on macOS may run badly (frame skipping in League of Legends for one) or have visual artefacts (Diablo III for another).
2. Bad to non-existent peripheral support (Razer, probably most others).
3. A pathetically small games library, which just got smaller with the 32-bit kill (my Steam library got cut in half).

As for Boot Camp, you're entirely at the mercy of Apple, Microsoft and AMD, considering:
1. Apple may occasionally revise the hardware, causing one user report of a "successful" setup not apply to your seemingly-exact model.
2. Microsoft and AMD may not support all/recent varieties of components, particularly as they have little incentive to do so.
3. Said incompatibility may lead to software issues ricocheting outside of eGPU realm, such as peripheral issues mentioned earlier while the eGPU is plugged in (due to mismatched/buggy resource management, for instance).
4. You're forced to use an old, potentially vulnerable OS version.

Sure one may be able to fix some, most or all of the issue depending on technical knowledge, but at the end of said 15-or-so hours on the issue, the realisation is that the deeper you dive the more work there is to do (and at a certain point the closed source code won't allow further progress).

This post was modified 3 weeks ago

MacBook Pro 13" 2018
OWC Mercury Helios FX 650
AMD Radeon 5700 XT (via Boot Camp, Windows 10 18362.295)


ReplyQuote
Knot3D
(@knot3d)
Active Member
Joined: 8 months ago
 

Well, I finally got my laptop back from HP service center.

Initially, they thought the culprit might be my EGPU - which I doubted to be the case, since it was still lighting up and recognized by the TB3 software, just not in device manager.

Well, turns out it was actually a motherboard issue. Got a replacement under warranty plan. They also updated the BIOS to F34 and installed 

1903 OS build .18362.476  and hurray, my Aorus Gaming Box 2070 works again.

 

This post was modified 3 weeks ago

HP Spectre X360 13inch Diamand Cut 2019 i7 - 8565U with 8Gb RAM + Aorus Gaming Box RTX2070


ReplyQuote
 of  10