ERROR 12 on BOOTCAMP HAS BEEN FIXED BY MICROSOFT! in WINDOWS INSIDER (FAST) !
 
Notifications
Clear all

ERROR 12 on BOOTCAMP HAS BEEN FIXED BY MICROSOFT! in WINDOWS INSIDER (FAST) !  

 of  18
  RSS

Christian Prinoth
(@christian_prinoth)
Active Member
Joined: 1 year ago
 

@arouris

well this is interesting. I come from a setup where I had an RX580 inside a Razer Core X. This worked fairly well, although (1) hotplug never works and (2) windows boots only with the EFI hack, otherwise very consistent and table behaviour, as long as I connect the eGPU when facing the EFI boot screen.

Now I had the stupid idea to replaced the RX 580 with an RX 5700 XT which is giving me no joy (always error 12 or error 43). The one consistent fact that I have is that windows will NOT boot without the EFI hack.

So I really wonder what difference between my mac mini and yours justifies the different boot behaviour.

To return on topic of this thread, I also tried updating windows to latest fast insider, but on one hand this does NOT fix error 12/43, but it does create the additional problem that on restart the EFI hack is ignored and I end up in the endless boot cycle. To get Windows to start up again I have to keep option key pressed, then select windows drive, then it goes through the EFI boot screen and boots correctly (and back to error 12/43...).

Tonight I will try to install 1903v1 and see if that changes anything.

2018 Mac Mini [8th,6C,B] + RX 580 @ 32Gbps-TB3 (Razer Core X) + macOS 10.15.4 & Win10 1903 // Oculus Quest [build link]  

ReplyQuote
arouris
(@arouris)
Eminent Member
Joined: 1 year ago
 
Posted by: @christian_prinoth

@arouris

So I really wonder what difference between my mac mini and yours justifies the different boot behaviour.

 

The behavior is not different. The way your combination behaves is exactly the same as mine when it does not work. I strongly believe that it's a matter of luck based on random pci express resource allocation that is being done by windows. Some combinations work, some others do not. I have just hit the sweet spot twice. The first time I did, I broke it irreversibly by moving the egpu cable slightly which caused it to disconnect and reconnect to the mini (while in Windows). This made Windows reallocate resources (or try to) which failed both at the time of the re-connection and at every subsequent reboot, port swap, whatever other combination I tried.

10 days after that and after a RAM upgrade that forced me to also do a PRAM reset, made Windows reallocate resources to the sweet spot that works.

Mac Mini 2018 (Core i5), Sonnet 550 enclosure, Sapphire 5700 XT Nitro


ReplyQuote
Christian Prinoth
(@christian_prinoth)
Active Member
Joined: 1 year ago
 

@arouris

again, just to make sure I understand correctly: after you moved the cables, were you not able to boot windows anymore (win logo + green gibberish endless cycle), or could you boot correctly but would just get error 12 which you were not getting previously?

I have yet to find a combination where boot works with egpu cold-plugged and "stock-default" EFI.

2018 Mac Mini [8th,6C,B] + RX 580 @ 32Gbps-TB3 (Razer Core X) + macOS 10.15.4 & Win10 1903 // Oculus Quest [build link]  

ReplyQuote
arouris
(@arouris)
Eminent Member
Joined: 1 year ago
 

@christian_prinoth, after moving the cables, I heard the device unplugged/replugged sound that Windows make and I could see Windows desktop on my monitor but said image was frozen. Which forced me to restart the Mini which resulted in no screen at all, or windows logo turning on and off or green gibberish. I could also see the GPU lights going on and off. I never managed to boot into windows with the egpu plugged in. Up until that ram update / pram reset a couple of days ago.

 

Mac Mini 2018 (Core i5), Sonnet 550 enclosure, Sapphire 5700 XT Nitro


ReplyQuote
Christian Prinoth
(@christian_prinoth)
Active Member
Joined: 1 year ago
 

@arouris, ok that makes sense and is consistent with my experience. Can you also please tell me what connections you are using? i.e. HDMI Mini-Monitor or HDMI egpu-Monitor or DP Mini-monitor or any combination thereof?

fwiw I think the Thunderbolt-USB-C implementation is quite flaky overall. At work I have a new 16" MBPro. I use an external USB-C hub which provides power and ethernet. Quite regularly, the mbpro will stop recognizing the ethernet adapter, until I switch to a different usb-c port. When all ports stop working, I have to reset PRAM to get it working again. This may be somehow related to your behaviour that may have been fixed by pram reset.

This weekend I will try the following:

1) reinstall 1903v1 from scratch, so to make sure I am using a win10 version where consensus is that it works

2) PRAM reset

3) installation of bootefi hack

 

let's see if that takes me somewhere.

 

2018 Mac Mini [8th,6C,B] + RX 580 @ 32Gbps-TB3 (Razer Core X) + macOS 10.15.4 & Win10 1903 // Oculus Quest [build link]  

ReplyQuote
arouris
(@arouris)
Eminent Member
Joined: 1 year ago
 

@christian_prinoth, I am using 3 of the 4 T3 ports. On 2 of them I have 2 external SSDs and on the 3rd I have the eGPU enclosure. LG 4K monitor is connected with DP on the eGPU. Nothing is connected on the Mini HDMI.

 

It is very interesting to read that the T3 ports (I assume that's what you mean by USB-C) stop working altogether until you do a PRAM reset to get them back.

 

Mac Mini 2018 (Core i5), Sonnet 550 enclosure, Sapphire 5700 XT Nitro


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

@arouris, after the PRAM reset are you able to upgrade to the latest Windows 10 without issue (either 2004 or do you require the Insider Fast Ring?)

Also keep in mind guys that the USB-C port that you physically plug into may affect your results...

At least on my iMac 5K 2017 I have read that it is recommended to plug into the one closest to the ethernet port (away from the usb 3.0 ports) - not sure if this makes any difference

Will be doing extensive testing tonight and will update with my findings

iMac 5K 2017 + Razer Core X Chroma + EVGA Hybrid 2080 Ti here

 

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

.

ReplyQuote
Christian Prinoth
(@christian_prinoth)
Active Member
Joined: 1 year ago
 

So tonight I recreated my bootcamp partition from scratch using Win10 1903v1.

Installation was uneventful, and at first nothing appeared to change in terms of getting my 5700xt to work: when cold-plugged, I would always get the endless winlogo+green gibberish cycle, and hotplug would invariably lead to error 12.

I tried to reset the mac mini's pram but to no avail.

Up to that point I had always the Mac Mini connected directly via HDMI to my monitor. After all, that is the setup that used to work flawlessly with my previous RX580. So I decided to try various combinations of mac-gpu-monitor connections. The breakthrough came when I had my Mac Mini connected to the monitor via HDMI, and at the same time the egpu connected via DP to the same monitor.

I rebooted the mac mini, and got the usual logo+gibberish cycle as above. But at that point I tried to switch my monitor to DP input, and to my surprise there was the Win10 desktop perfectly functional with the RX5700XT correctly recognized.

So I believe that what is happening is that the flashing boot logo is actually the iGPU failing somehow, since when I switch over to DP and look at the device manager, there is only the egpu, and the igpu does not show up at all. But the failing igpu clearly leaves free resources for the egpu.

I do not know if this works only with 1903v1, or if it would have worked the same with all other Win10 versions I tried before. Maybe one day I will find the courage to try updating 😉

But clearly my previous idea that I need to install the EFI hack in order to get the mac to boot with cold-plugged egpu was completely wrong. In fact, that setup leads exactly to a situation where both igpu and egpu are recognized, but the latter is resourceless.

2018 Mac Mini [8th,6C,B] + RX 580 @ 32Gbps-TB3 (Razer Core X) + macOS 10.15.4 & Win10 1903 // Oculus Quest [build link]  

ReplyQuote
Larry S
(@larry_s)
New Member
Joined: 1 year ago
 

I wonder if this topic had fulfilled? 

I try to upgrade to 2004, but unfortunately macOS just unable to find useful resources for me to install bootcamp. Or else anyone doing it at windows update? 

My built (Akitio Node Titan, Asrock RX 5700 XT Challenger D, Akitio Node titan original TB3 cable)...
Still not work in bootcamp, (Code 12) error even I disable the rest of the unused PCIe
On my MacBook Pro 2017, 4TB3, Touch Bar (TB3 port used were the one near the tab key)

For some reason or I'm just can't understand how to config the EFi, my boot keep booting back to macOS when I use EFi boot 
And if I cold plug the egpu case it will just loop on the windows logo. else hotplug it with error Code 12 

Am thinking to get a Nvidia GPU to use with bootcamp after I manage to rent one and test if it work. 

This post was modified 1 year ago

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

.

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

@arizor, clean 1903, then official bootcamp drivers, restart, then hotplug while online worked! It sees the 2080 Ti

will try with bootcampdrivers.com because i would like to use both imac display as well as external monitor

also will try jumping to 2004 and then insider fast ring if 2004 breaks it again

will update soon, thank you again!

 

 

 

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

.

ReplyQuote
 of  18