Last edited:
I have Catalina with OC on NVME and Windows 10 on another old PCIE card, all working great, fingers crossed.Is anyone running Windows 10 on a cMP 5,1 NVMe drive with an Sapphire Pulse RX 580 GPU? I want to know if you have any freezing problems, I'm constantly plagued by Windows Logo freezes or freezes during Windows normal use.
Try booting Windows through RefindPlus to eliminate issues with OC. RP also has Certificate protection.Is anyone running Windows 10 on a cMP 5,1 NVMe drive with an Sapphire Pulse RX 580 GPU? I want to know if you have any freezing problems, I'm constantly plagued by Windows Logo freezes or freezes during Windows normal use.
I just noticed you use the same Syba card, is your Windows disk on channel 0 or 1? Where is OpenCore installed, on one of the NVMes?Mine works fine.
The drive numbers 0 and 1 alternate, but always are either of the two (Windows 10 or Mojave). OpenCore is on the 240GB SATA SSD in the tray below the superdrive. That drive is strictly for that use and holds all my software installations in the main partition.I just noticed you use the same Syba card, is your Windows disk on channel 0 or 1? Where is OpenCore installed, on one of the NVMes?
My setup is:
- Mohave on SATA1 SSD
- OC + Big Sur on Syba NVMe CH0
- Windows 10 on Syba NVMe CH1
I see your OC is on a true internal SSD, not an NVMe like myself. Right now the only internal drive I have is Mojave. When I say channels, I mean the CH0 and CH1 design present into Syba SI-PEX40129, which uses ASM2824 PCIe switches.OpenCore is on the 240GB SATA SSD
If something goes wrong, it's useful to physically remove OC along with all unsupported versions of macOS and to boot natively into Mojave. You lose that ability if OC and Mojave are on the same disk. Note that when you reset the NVRAM, there is no blessing: the Mac will just choose whatever it sees first, which may or may not be your Mojave disk.@cdf, what would be the impact if I move OC into Mojave disk? If I reset the NVRAM will the blessing be removed from the Mojave disk?
I see, but that would be the same like leaving the SATA1 SSD where Mojave is in place and removing the Syba SI-PEX40129 where the Big Sur and Windows exist. My goal is to determine if running OC on a dual NVMe setup makes Windows go ballistic.Note that when you reset the NVRAM, there is no blessing: the Mac will just choose whatever it sees first, which may or may not be your Mojave disk.
That's what I usually do, after each Windows upgrade as is always broken. Looks like based on @cdf explanation and your input, I could order an SSD disk and use it only for OC. It sucks but based on your experience you do not have any issues with Windows and you have an identical setup as mines, except the OC SSD.@TECK, you may want to re-install Windows on top to fix any glitches
A separate drive for OpenCore is a failsafe. Look on eBay for a small 20GB drive. I'm about to get one for myself. I'm also considering one of those micro USB to plug in the rear of the chassis. The Windows problem could be drivers, also. Windows 10 requires the original bootcamp and an iMac bootcamp if using a trackpad 2 and updated bluetooth card.I see, but that would be the same like leaving the SATA1 SSD where Mojave is in place and removing the Syba SI-PEX40129 where the Big Sur and Windows exist. My goal is to determine if running OC on a dual NVMe setup makes Windows go ballistic.
That's what I usually do, after each Windows upgrade as is always broken. Looks like based on @cdf suggestion, I could order an SSD disk and use it only for OC. It sucks but based on your experience you do not have any issues with Windows and you have an identical setup as mines, except the OC SSD.
Not the same config as yours, since I have 4(SSD7101A-1 v1.01) + 1(Angelbird Wings) NVMe blades, and I don't have any problems with W10.My goal is to determine if running OC on a dual NVMe setup makes Windows go ballistic.
Sorry missed this till just now.@cdf I don't like the idea of replacing the OC BOOTx64.efi. I mean, there are many people who installed Windows and have no issues. Doesn't OC have cert protection also? This was discussed in your thread. Dayo can you please chime in?
@TECK already have a never booted image, so he can do any tests with pure UEFI Windows and then flash it back.Sorry missed this till just now.
OC has cert protection indeed and originates this. The one in RefindPlus is a copy of the OC implementation.
I believe all @startego was asking you to do is to try booting Windows without OC to see whether the issue is OC specific. To do this, you need a tool that will protect your NVRAM from UEFI Windows which RefindPlus can (needs to be explicitly switched on).
There is no big deal in temporarily renaming the OC boot loader, putting a different file in and rebooting. You don't even need to bless again. After the test is done, mount the ESP, delete the temp file and rename the OC one back.
Best way however is just to use MyBootMgr to implement a setup on a flash drive, this activates the NVRAM protection, use the "soft" bless feature to do the test and delete the flash drive once done.
If the issue is replicated after booting through RefindPlus, then you know it is Windows related ... maybe with the NVMe location. If not, then you know it is OC related. If I had to guess, I would say it is tied to the NVMe installtion.
Is your OC EFI on one of the NVMe disks?Not the same config as yours, since I have 4(SSD7101A-1 v1.01) + 1(Angelbird Wings) NVMe blades, and I don't have any problems with W10.
Yes, I keep it on the Samsung 970 Pro that is inside my Angelbird Wings.Is your OC EFI on one of the NVMe disks?
Both Samsung 970 EVO Plus drives have 2B2QEXM7 revision. I'm going to put the OC EFI on Windows drive, but it should not do make any change.Yes, I keep it on the Samsung 970 Pro that is inside my Angelbird Wings.
[floren@zeus ~]$ ls -lah /Volumes/EFI/EFI/
total 4
drwxrwxrwx 1 floren staff 512B 20 Sep 02:23 .
drwxrwxrwx@ 1 floren staff 512B 13 Feb 01:27 ..
drwxrwxrwx 1 floren staff 512B 20 Sep 07:25 Boot
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 Microsoft
[floren@zeus ~]$ ls -lah /Volumes/EFI/EFI/Boot/
total 3046
drwxrwxrwx 1 floren staff 512B 20 Sep 07:25 .
drwxrwxrwx 1 floren staff 512B 20 Sep 02:23 ..
-rwxrwxrwx 1 floren staff 1.5M 15 Jan 18:18 bootx64.efi
I guess that distinction is for OSX only.@startergo You asked me is the drives are internal in Device Properties, how do I check that?
View attachment 1730201
OpenCore automatically finds \EFI\Microsoft\Boot\bootmgfw.efi, so you should be able to remove that BOOTx64.efi file (after backing it up just in case). You might also want to use LauncherOption in case an update overwrites the OC@cdf or anyone else, what I need your help with is the /Boot/bootx64.efi clarification on Windows drive.
[floren@zeus ~]$ sudo diskutil mount /dev/disk1s1
Password:
Volume EFI on /dev/disk1s1 mounted
[floren@zeus ~]$ ls -lh /Volumes/EFI/EFI/
total 2
drwxrwxrwx 1 floren staff 512B 20 Sep 07:25 Boot
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 Microsoft
[floren@zeus ~]$ ls -lh /Volumes/EFI/EFI/Boot/
total 3044
-rwxrwxrwx 1 floren staff 1.5M 15 Jan 18:18 bootx64.efi
[floren@zeus ~]$ ls -lh /Volumes/EFI/EFI/Microsoft/
total 11
drwxrwxrwx 1 floren staff 5.0K 20 Sep 02:22 Boot
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 Recovery
[floren@zeus ~]$ ls -lh /Volumes/EFI/EFI/Microsoft/Boot/
total 11438
-rwxrwxrwx 1 floren staff 28K 14 Feb 18:07 BCD
-rwxrwxrwx 1 floren staff 32K 20 Sep 10:15 BCD.LOG
-rwxrwxrwx 1 floren staff 0B 20 Sep 10:15 BCD.LOG1
-rwxrwxrwx 1 floren staff 0B 20 Sep 10:15 BCD.LOG2
-rwxrwxrwx 1 floren staff 64K 14 Feb 20:14 BOOTSTAT.DAT
drwxrwxrwx 1 floren staff 1.5K 20 Sep 02:22 Fonts
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 Resources
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 bg-BG
-rwxrwxrwx 1 floren staff 4.9K 7 Dec 2019 boot.stl
-rwxrwxrwx 1 floren staff 1.5M 15 Jan 18:18 bootmgfw.efi
-rwxrwxrwx 1 floren staff 1.5M 15 Jan 18:18 bootmgr.efi
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 cs-CZ
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 da-DK
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 de-DE
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 el-GR
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 en-GB
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 en-US
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 es-ES
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 es-MX
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 et-EE
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 fi-FI
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 fr-CA
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 fr-FR
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 hr-HR
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 hu-HU
drwxrwxrwx 1 floren staff 1.0K 20 Sep 10:14 it-IT
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 ja-JP
-rwxrwxrwx 1 floren staff 31K 7 Dec 2019 kd_02_10df.dll
-rwxrwxrwx 1 floren staff 370K 7 Dec 2019 kd_02_10ec.dll
-rwxrwxrwx 1 floren staff 26K 7 Dec 2019 kd_02_1137.dll
-rwxrwxrwx 1 floren staff 234K 7 Dec 2019 kd_02_14e4.dll
-rwxrwxrwx 1 floren staff 43K 7 Dec 2019 kd_02_15b3.dll
-rwxrwxrwx 1 floren staff 43K 7 Dec 2019 kd_02_1969.dll
-rwxrwxrwx 1 floren staff 31K 7 Dec 2019 kd_02_19a2.dll
-rwxrwxrwx 1 floren staff 20K 7 Dec 2019 kd_02_1af4.dll
-rwxrwxrwx 1 floren staff 291K 7 Dec 2019 kd_02_8086.dll
-rwxrwxrwx 1 floren staff 19K 7 Dec 2019 kd_07_1415.dll
-rwxrwxrwx 1 floren staff 48K 7 Dec 2019 kd_0C_8086.dll
-rwxrwxrwx 1 floren staff 17K 7 Dec 2019 kdnet_uart16550.dll
-rwxrwxrwx 1 floren staff 27K 7 Dec 2019 kdstub.dll
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 ko-KR
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 lt-LT
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 lv-LV
-rwxrwxrwx 1 floren staff 1.3M 20 Sep 01:50 memtest.efi
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 nb-NO
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 nl-NL
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 pl-PL
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 pt-BR
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 pt-PT
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 qps-ploc
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 ro-RO
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 ru-RU
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 sk-SK
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 sl-SI
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 sr-Latn-RS
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 sv-SE
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 tr-TR
drwxrwxrwx 1 floren staff 512B 20 Sep 02:22 uk-UA
-rwxrwxrwx 1 floren staff 9.6K 7 Dec 2019 winsipolicy.p7b
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 zh-CN
drwxrwxrwx 1 floren staff 1.0K 20 Sep 02:22 zh-TW