eGPU error 12 fail after update to Windows 10 1903 (OS Build 18362.329 or newer)
 

[Solved] eGPU error 12 fail after update to Windows 10 1903 (OS Build 18362.329 or newer)  

 of  13
  RSS

Sace
 Sace
(@sace)
Eminent Member
Joined: 1 year ago
 
Posted by: @itsage

@sace Once you confirmed it's disabled, run DDU again to remove Radeon drivers and TB3/PCIe connection association. Manually reinstall the latest Radeon drivers and it should work.

 

Oh, I already did that. I ran DDU etc. after disabling the connection and reverting the OS. Might give it one more try but can't identify what I have done wrong.

Ok now I'm out of ideas. I have reinstalled first 1903 V1 as linked in this thread - No luck. Now I'm back on 1803 and still the same issue. I even followed my own guide from my original build thread but no, stuck with error 12. The only thing that's not the same is the AMD and bootcamp drivers. 

This post was modified 2 months ago

MacBook Pro 13” nTB (2016) - Razer Core X - MSI Radeon RX 580 Armor 8GB
Mac OS X 10.14.1 + Windows 10 1803 (Bootcamp)


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

Can anyone help me? My card does not appear on the video adapter, everything is connected right and nothing.

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


ReplyQuote
Lividity
(@lividity)
Eminent Member
Joined: 4 months ago
 

Hey all

Have any BootCamp users tried upgrading to this yet?

Any eGPU issues?

2017 15" MacBook Pro (Radeon Pro 555) + AORUS Gaming Box RTX 2070 + Win10 1903


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

@lividity

Working good mate https://prnt.sc/q7qegp

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


ReplyQuote
DayosS
(@dayoss)
New Member
Joined: 11 months ago
 

I found a solution, for those who have a 2017 macbook pro 13 'without touch bar + windows 10 1909, follow this:

1 - Install Windows 10 1909 (last version) without any devices connected to the tb3 ports.

2- After login, install apple's support drivers and shut-down.

3 - Plug-in only the egpu to the nearest port to the tab and boot (you can also try to connect the egpu after windows login, it should work too).

4 - Install AMD drivers, do not put any other device to the second tb3 port because in my situation, it can completly broke windows 10 if I try to install the driver at the same time.

5 - If you don't have errors in device manager, you can normaly shut-down, plug-in your egpu and your usb hub and you can now boot to windows 10. Don't need to use goalque automate efi or something else.

This post was modified 1 month ago

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


ReplyQuote
Squuiid
(@squuiid)
Eminent Member
Joined: 7 months ago
 

Downgrading to 1809 not only solved the code 12 issue with the RX 5700 XT but it also fixed the overheating Aquantia 10GbE NIC problem in the Mac mini.

It seems BootCamp is best suited to 1809 with the current Apple BootCamp drivers, at least on the Mac mini 2018. The problem is that Microsoft have now adopted an Ubuntu like release cycle where it drops support for older versions far sooner unless it's LTS. 1809 will only be supported with security updates until May 2020. Then, unless AMD/Microsoft have fixed error code 12 by that date, we're SOL.

https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet

UPDATE:

Ugh. Maybe not the Aquantia 10GbE issue...  Event ID 19: "Aquantia AQtion 10Gbit Network Adapter : Hardware overheat detected! Please power cycle the system."

This post was modified 1 month ago

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, Amfeltec 3x XP941 512GB, Sapphire Pulse RX 580 8GB, Intel X540-T1 10GbE, Allegro Pro USB 3.0, AC/BT 4.2, macOS Mojave


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

There’s this option though: Windows 10 Enterprise 2019 LTSC currently version 1809 that should have support till 2024.

 

edit: amended end of support as per https://support.microsoft.com/en-us/lifecycle/search/18165

This post was modified 1 month ago

16'' Macbook Pro - Razer Core X Chroma - PowerColor Red Devil 5700XT - LG 27UK850


ReplyQuote
zeamp
(@zeamp)
Active Member
Joined: 11 months ago
 

After upgrading to the latest Catalina beta and Windows 10 (1909?) I am suddenly getting Error 12 again, after having no issues for several months.

Disabling the usual stuff in Device Manager doesn't resolve the issue. Re-installed Windows 10 and that didn't solve it. I am now in the process of downloading the older Windows 10 Build 1809 with my fingers crossed...

Mac Mini 2018 (i5-8500B, 8GB RAM), Sonnet Breakaway Box 350W + AMD RX 580 8GB GFX


ReplyQuote
Sace
 Sace
(@sace)
Eminent Member
Joined: 1 year ago
 

I have now tried almost everything and I give up for now to get my 2016 nTB MacBook Pro to run with my Core X / RX580 setup again. I have been through a LOT of windows installs etc. and actually got it working a short while on 1803. But then I plugged in my external HDD and everything crashed leading to a never ending reboot loop.

It seems to be connected to what other mentions about plugging in other things in the ports. I can install everything as usual using timed hotplug etc. but that gives me error 12. Disabling the FaceTime camera does not fix that as it used to do. Then I tried the DSDT override method which actually solved the error 12 but then crashed or froze the system randomly. 

Often I would end in a situation where the screen turned blank right before the login screen. Removing either the TB3 cable OR the USB drive would get the loading screen back and then send me to a BSOD.

Another thing I have noticed is that sleep/wake is completely broken when I use bootcamp. I simply can't wake the computer if it goes to sleep. If the screen turns off it will only wake if I close the lid and open it again. This was on clean installs too. So I suspect that something has gotten a lot worse since I updated MacOS as I never had those problems a year ago when I first set up the system.

Well, an excuse for a new computer then 🙂

MacBook Pro 13” nTB (2016) - Razer Core X - MSI Radeon RX 580 Armor 8GB
Mac OS X 10.14.1 + Windows 10 1803 (Bootcamp)


ReplyQuote
Squuiid
(@squuiid)
Eminent Member
Joined: 7 months ago
 
Posted by: @zeamp

After upgrading to the latest Catalina beta and Windows 10 (1909?) I am suddenly getting Error 12 again, after having no issues for several months.

Disabling the usual stuff in Device Manager doesn't resolve the issue. Re-installed Windows 10 and that didn't solve it. I am now in the process of downloading the older Windows 10 Build 1809 with my fingers crossed...

See here, this may help 😉 

https://egpu.io/forums/pc-setup/windows-wont-boot-on-mac-mini-2018-with-only-egpu-attached-after-upgrading-catalina-10-15-2/#post-70664

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, Amfeltec 3x XP941 512GB, Sapphire Pulse RX 580 8GB, Intel X540-T1 10GbE, Allegro Pro USB 3.0, AC/BT 4.2, macOS Mojave


ReplyQuote
zeamp
(@zeamp)
Active Member
Joined: 11 months ago
 

@squuiid

Unfortunately, this doesn't help. Since it's stuck on Error 12, it never gets far enough in the process to actually install the AMD drivers (since I've done multiple re-installs now). It failed with both Windows 10 1809 and 1903.

Mac Mini 2018 (i5-8500B, 8GB RAM), Sonnet Breakaway Box 350W + AMD RX 580 8GB GFX


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

Using Macbook Pro 15'' 2019 with 555X and Core X + Vega 64, Installing Drivers on Windows 1903 cannot work with error 12, but switching to 1803 will solve the problem and everyting works fine.

But I wanna use new windows features in 1909, I wonder is there still a issue of error 12 for vega64 in 1909? Is there any successful build?

MacBook Pro 15'' 2019 i7/32G/555X + Razer Core X + Gigabyte Vega 64 in macOS and Bootcamp Windows


ReplyQuote
Squuiid
(@squuiid)
Eminent Member
Joined: 7 months ago
 
Posted by: @zeamp

@squuiid

Unfortunately, this doesn't help. Since it's stuck on Error 12, it never gets far enough in the process to actually install the AMD drivers (since I've done multiple re-installs now). It failed with both Windows 10 1809 and 1903.

You may need to RDP in from another computer in order to install the drivers but you will need to allow RDP in the first instance. This should be the first thing you do once Windows in first installed as it then prevents you from being ‘locked out’.

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, Amfeltec 3x XP941 512GB, Sapphire Pulse RX 580 8GB, Intel X540-T1 10GbE, Allegro Pro USB 3.0, AC/BT 4.2, macOS Mojave


ReplyQuote
zeamp
(@zeamp)
Active Member
Joined: 11 months ago
 

@squuiid

Remote in, instead of juggling my HDMI between the Mac and eGPU? I believe it's still going to Error 12 but I will re-install again and try setting up my AnyDesk headless for remote, that way I can reboot without anything plugged in and hopefully get all the allocation needed for my graphics card. I may also roll back even further to another 18XX build (other than 1809).

Mac Mini 2018 (i5-8500B, 8GB RAM), Sonnet Breakaway Box 350W + AMD RX 580 8GB GFX


ReplyQuote
Squuiid
(@squuiid)
Eminent Member
Joined: 7 months ago
 
Posted by: @zeamp

@squuiid

Remote in, instead of juggling my HDMI between the Mac and eGPU? I believe it's still going to Error 12 but I will re-install again and try setting up my AnyDesk headless for remote, that way I can reboot without anything plugged in and hopefully get all the allocation needed for my graphics card. I may also roll back even further to another 18XX build (other than 1809).

RDP gives you an easy way if you get a black screen, that’s all really.
1809 will be end of support in May 2020. I would not want to go back further than that.

1809 definitely works for myself and many others.

This post was modified 1 month ago

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, Amfeltec 3x XP941 512GB, Sapphire Pulse RX 580 8GB, Intel X540-T1 10GbE, Allegro Pro USB 3.0, AC/BT 4.2, macOS Mojave


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

hi all,

Just want to share my experience. I have a stable eGPU setup running for a while,  Razer Stealth 13 (early 2019) on Windows 10 1909 (18.363.535), Razer Core X Chroma and XFX RX580. I also use the eGPU with my Macbook Pro 13 2018 on Mojave 10.14.6 without any problem.

Recently I got Sapphire 5700 XT Nitro+, it doesn't' work (error 12), that's how I got to this thread. 

Seems like a Polaris based AMD card works fine, Navi based still have a problem. I am back to the RX580 for now until this thing settles down.
My old Nvidia 970 never had a problem as well.

 

 

Razer Stealth 13" (early 2019), Razer Core X Chroma, Sapphire Nitro+ RX 5700XT
Macbook Pro 13" (2018), Mantiz Venus, XFX RX 580


ReplyQuote
(@mauro_diez)
New Member
Joined: 4 months ago
 

I’m having trouble finding an older Windows 10 version to download. I’m looking specifically for 1809. Can anyone help point me in the right direction?

2018 Mac Mini Core i7 32GB ram Razer Core X Sapphire Pulse Vega 56 Catalina with Windows 10 in bootcamp


ReplyQuote
(@florin_samareanu)
Active Member
Joined: 2 months ago
 
Posted by: @mauro_diez

I’m having trouble finding an older Windows 10 version to download. I’m looking specifically for 1809. Can anyone help point me in the right direction?

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

 

16'' Macbook Pro - Razer Core X Chroma - PowerColor Red Devil 5700XT - LG 27UK850


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 3 years ago

ReplyQuote
(@mauro_diez)
New Member
Joined: 4 months ago
 

@eightarmedpet

Thank you, sir!

2018 Mac Mini Core i7 32GB ram Razer Core X Sapphire Pulse Vega 56 Catalina with Windows 10 in bootcamp


ReplyQuote
troubleboi
(@troubleboi)
Active Member
Joined: 2 years ago
 

Sorry i've probably not written this well, i just wanted to share my experience, i was about to give up mac mini 2018 working with eGPU, then i hit the combination finally got it working.

---

I've had the most frustrating 48+ hours, i brought a new mac mini 2018 with i7 & 32gb ram, it's probably been the hardest device i've had to setup with eGPU. The easiest device is my macbook 13-inch 2017, 4 thunderbolt 3 ports. 

I've managed to get the mac mini to use eGPU with both bootcamp and mac. It came with Catalina pre installed, i accidentally updated to 10.15.2 pretty much off the bat.

To load in macOS, i've found if you leave completely headless, no monitor connected, and then conned the eGPU after it booted it works fine. I get the white screen if it plugged in on boot up.

For windows, this is the real headache, i was plagued with error 12 and boot up issues. To fix error 12, i have had to disable PCIe controllers, i've found that pluging anything in can be enough to push this over the limit, so you pretty much have to keep it to bare min. 

Boot camp also has some boot up issues, the only method i can get to work is to turn on with eGPU unplugged, hold option key for boot menu, then plug in eGPU and boot up at same time. Windows will freeze on black screen if eGPU is plugged in on boot up. 

I have also managed to get windows 1909 to work in this setup, i started with 1809, and upgrade to 1903 first, then had the guts to try 1909 (i have 1909 working on my macbook 13-inch)

Quick sum up

1) install bootcamp

2) get drivers installed and to point of error 12

3) disable devices to clear error 12 (i did PCIe Controller)

4) reboot headless, press option for boot menu (blind), plug in eGPU, timing of plugging in eGPU is critical

I found using teamviewer really helpful to see/connect it when no screen attached., my feeling is there is a firmware issue with mac mini since latest update, that is effecting boot up of both windows & macOS. This may also be causing a hard error 12 to fix. 

From Dec 2019 - 2018 Mac Mini i7 / 32GB / 512GB / Intel UHD 630 - Mac OS 10.15.2 Catalina & Windows 10 - 1909 Build 18363.535
From Sept 2017 - 2017 Macbook Pro 13-Inch 4 port Thunderbolt / i5 / 8GB / 256GB / Intel Iris Plus 650 - Mac OS 10.15.1 Catalina & Windows 10 - 1909 Build 18363.535
Up to Oct 2019 - Late 2013 iMac i5 / 16GB / 256GB / Intel Iris Pro 520 - Mac OS 10.14 & Windows 10 - 1903

All working using same HP Omen Accelerator with RX580 / 4GB


ReplyQuote
Test1
(@test1)
Active Member
Joined: 11 months ago
 

I havent checked the forum since this problem occured back in september. I was hoping this was fixed. Appears that it's not, sadly. I'm still on .295, but it works like a charm on my 2017 15" macbook pro with Vega 56.

Despite it working very well, I am very uncomfortable not having a windows that's up to date. All the security risks around today, I have blocked all internet connections in windows to try UP the security and only surf on my iPad. I don't use any logins except my Steam account.

Does anyone have additional tips to improve security in a system like this? (with poor security updates). I'm using firefox, but have heard about a "indie" browser which is more security oriented.

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


ReplyQuote
Squuiid
(@squuiid)
Eminent Member
Joined: 7 months ago
 
Posted by: @test1

Does anyone have additional tips to improve security in a system like this? (with poor security updates). I'm using firefox, but have heard about a "indie" browser which is more security oriented.

Use Pi-Hole, a good firewall with content filtering/web blocking/AV and use Firefox or Brave with uBlock Origin installed.

Oh, and try and not browse the internet unless absolutely essential.

This post was modified 1 month ago

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, Amfeltec 3x XP941 512GB, Sapphire Pulse RX 580 8GB, Intel X540-T1 10GbE, Allegro Pro USB 3.0, AC/BT 4.2, macOS Mojave


itsage liked
ReplyQuote
Test1
(@test1)
Active Member
Joined: 11 months ago
 

@squuiid

Thanks for the tip! Will look into that 🙂

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


ReplyQuote
Agent
(@agent)
New Member
Joined: 1 month ago
 

I am getting error 12 with my setup, and I'd like some advice about what to try next to fix it.

I have got a Mac Mini 2018, a Mantiz Venus enclosure, and the AMD Radeon VII in the enclosure. The Radeon is connected to my monitor (Acer Nitro XV273K) via DisplayPort. I have got a Boot Camp partition with Windows 10 Home ver. 1909 build 18363.535 installed on it, and AMD's Adrenaline 2020 edition software ver. 19.12.3 installed in Windows.

When I do a blind boot with just the Thunderbolt/Radeon connection (without using the Mac Mini's built-in Intel UHD/HDMI connection), the monitor has no signal. When I boot with the HDMI connection and later connect the Thunderbolt/Radeon, I can see that Device Manager reports that the Radeon VII device is disabled because of error code 12 (cannot find resources). If I then disconnect the HDMI cable, the monitor has no signal.

I have tried rearranging which ports my peripherals are connected to, and I have tried disabling all the Device Manager devices I can (even including the Intel UHD iGPU), but I get the same behavior. It all works fine running under Mac OS Catalina.

I see three ways forward from here, and I'd like advice from y'all:

  • Maybe the problem is Windows. I could try installing the older Windows 10 ver. 1903 build 18362 (as described in another forum post).
  • Maybe the problem is all the devices and I/O included in the Mantiz Venus enclosure. I could instead buy a Razer Core X enclosure.
  • Maybe the problem is that the Radeon VII is just too much card. This doesn't seem likely, since other people have gotten it working, but I could instead get a Radeon RX Vega 64.

What say you?

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


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

@agent Reinstall Boot Camp with either Win10 1809 or 1903 V1 ISO [discussion link]. 

 

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


ReplyQuote
Agent
(@agent)
New Member
Joined: 1 month ago
 

Thanks! That seems to have done the trick. I disabled Windows Update as best I could and created a system restore point for when I inevitably have to run Windows Update.

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


ReplyQuote
tonyspizza
(@tonyspizza)
New Member
Joined: 1 month ago
 

I have a 2018 Mac mini with i5, 15GB RAM.  Windows 10 is at version 1909, build 18363.535.  I have a Sonnet eGFX 650 enclosure with a Radeon Vega 64 graphics card.  I cannot get it to work on the windows side.  I'm getting this error in Device Manager: "This device cannot find enough free resources that it can use. (Code 12)"

Please Help

Thank you!

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


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

Hi everyone, I have a   Razer Core X   with   Vega56   connected to a 2018   MBA  and purchased Win10 Pro (the latest 1909 version).

I have followed all eGPU bootcamp instructions, including the automate eGPU EFI boot (which showed 'no egpu detected' in the boot screen, not sure why, but eGPU is later detected anyway). When plugging the TB3 cable after Win10 loads the device becomes connected, I installed the Adrenaline 2020 drivers (which completed installation but showed an 'error 207', not sure what that is). Radeon RX Vega is now detected in Device Manager but with error 12, and nothing changes even after disabling iSight camera.

What else is there to do to fix this? As this is an installation file downloaded from Microsoft, there is no way for me to 'rollback' to an earlier version of Win10. 

Thanks a lot everyone,

Daniel

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


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

@tonyspizza @danielm Follow the instructions in the original post to download Win10 1903 V1 ISO. Perform a clean Boot Camp installation with that ISO and make sure you disable Windows Updates to stay at or below 18362.295.

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


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

Thanks for that, will try that now. Just a quick question though - after all is complete, every time I boot Windows on my Mac, do I need to keep on boot loading from EFI or simply from the Windows partition on bootcamp?

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


ReplyQuote
tonyspizza
(@tonyspizza)
New Member
Joined: 1 month ago
 

@itsage

Thank you for that.  I just did a fresh install.  What is the most reliable way to prevent Windows from updating automatically?

Thanks,

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


ReplyQuote
(@bas_timmer)
New Member
Joined: 1 month ago
 

A quick analysis shows that in `pci.sys`, a function called "PciOverrideBridgeRequirements" got changed between .1 and .329 to add 2 additional override cases from the initial build of pci.sys. There does not seem to be a registry change to bypass this, but perhaps this can be overridden from ACPI: that's a slightly later concern I might look into, it does seem to act on a resource requirement value.

For now, downgrading system32\drivers\pci.sys to the version shipped with the initial 18362.1/.10 ISO (take ownership, rename, replace) works fine, but it might be this'll need to be put back to allow future CUs editing this file to be installed. Perhaps as a workaround references to pci.sys in the registry could be renamed to, say, pci2.sys as well, but I'm not certain about this...

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


mac_editor, ahendarman, Gregor Pigula and 4 people liked
ReplyQuote
itsage
(@itsage)
Illustrious Member Admin
Joined: 3 years ago
 

@tonyspizza I have tried different methods to prevent automatic Windows updates. The most reliable approach is through Group Policy [gpedit.msc].

Expand Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Windows Updates. Double-click Configure Automatic Updates to make changes.

Click the radio button Enabled and choose 2-Notify for download and auto install in the drop-down under Options.

Once this is done, you’d see a notification message by the bottom right of taskbar periodically but no auto install will take place.

Simply ignore these messages and continue to create manual restore points when you install graphics drivers just in case.

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


ReplyQuote
Sace
 Sace
(@sace)
Eminent Member
Joined: 1 year ago
 

After having given up on getting my setup running a few weeks back I gave it another shot today. And I got it running!

Since this started I was never able to get past the Error 12 code by disabling the FaceTime camera as I could before. Maybe there has been some changes with the lastest version of Mac OS X. As mentioned I then started playing with the DSDT override procedure but that gave me a ton of problems and never really worked. 

Today I got the idea to reduce the memory range used to compile the modified .aml file. The result was another memory area seen in device manager but not labeled as “large memory” (Makes sense as the new entry was 4GB). But that seems to do the trick. The eGPU attaches get’s allocated in that memory area and I don’t have to disable anything.

Currently I have it running with the radeon drivers bundled with W10 1803 but I think I’ll play around with other versions of windows and the radeon drivers.

 

 

MacBook Pro 13” nTB (2016) - Razer Core X - MSI Radeon RX 580 Armor 8GB
Mac OS X 10.14.1 + Windows 10 1803 (Bootcamp)


ReplyQuote
(@gregor_pigula)
New Member
Joined: 1 month ago
 

@bas_timmer

Thank you, after update to 1903 newest build and replacing pci.sys, the 5700 XT is working.

Same after going up to 1909 newest build. I used an "Emergency" Windows Boot Stick for replacing the file.

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


ReplyQuote
 of  13