Contribute
Register

Gigabyte Z390 M Gaming build with working NVRAM

I updated to 0.7.4 but then my Windows 10 boot would not launch. I would either get a blank screen or a message from Windows saying "Preparing Automatic Repair" but nothing would happen. I'd have to hard reboot. Booting directly from BIOS menu to Windows worked fine.

I downgraded back to 0.7.3 and Windows boot again worked fine.

Comparing the 0.7.3 config.plist to 0.7.4 and trial and error I found that if I removed SSDT-DMAR.aml and the corresponding delete then the boot to Windows worked fine BUT when launching into MacOS networking did not work. No ethernet, wifi or bluetooth. I put DMAR back in and network works again but Windows boot broken again.

Back to 0.7.3 for now but any ideas why this is happening?

Thanks in advance.

If you remove SSDT-DMAR and the delete DMAR, you should enable config.plist > Kernel > DisableIoMapper.
 
If you remove SSDT-DMAR and the delete DMAR, you should enable config.plist > Kernel > DisableIoMapper.

That worked! Networking fine in MacOS and Windows boots. Thanks!

What do I give up by not having SSDT-DMAR? Any idea why that would prevent Windows from booting?
 
That worked! Networking fine in MacOS and Windows boots. Thanks!

What do I give up by not having SSDT-DMAR? Any idea why that would prevent Windows from booting?
I haven’t looked into what in the 074 OC would cause this, but I, too, got the error on Windows boot, and I didn’t take the time to see what it would do. My solution was to reboot, hit F12 on startup and select the Windows boot loader (instead of booting with OC).
J
 
That worked! Networking fine in MacOS and Windows boots. Thanks!

What do I give up by not having SSDT-DMAR? Any idea why that would prevent Windows from booting?

I don't know either. To be honest, I haven't booted in to Windows on this system in months... When I do, I always use the BIOS boot menu anyway.
 
I don't know either. To be honest, I haven't booted in to Windows on this system in months... When I do, I always use the BIOS boot menu anyway.
So am I better off putting SSDT-DMAR back and booting Windows from BIOS too?
 
hi Pastrychef,

I have this odd boot problem since OC 0.72, and all the way to 0.74:

My 10.15.7 on Samsung M.2 970 EVO will disappear from boot menu. I have tried
  1. using your plist and only updating UUID - no go
  2. using my existing 0.71 plist - no go either
  3. saw SmackAttack's notes at #4479, I compared my existing 0.71 plist to 0.74 plist, they are both currently "0" value. Has this got anything to do with the OS drive disappearing?
Worked great on my end @pastrychef but I'd like to remind those (like me) still on Catalina, that you'll need to change the MinDate/MinVersion in UEFI/APFS to "ANY" in order to boot into OC.

Also, it's still best to reset NVRAM in the OC menu for the first boot, right?

* I updated Lilu, VirtualSMC, AppleALC, WEG kexts to current versions on my 0.71 and it works fine, so my guess is something to do with updates in OC.

How could I fix this problem?

Thank you.
 
hi Pastrychef,

I have this odd boot problem since OC 0.72, and all the way to 0.74:

My 10.15.7 on Samsung M.2 970 EVO will disappear from boot menu. I have tried
  1. using your plist and only updating UUID - no go
  2. using my existing 0.71 plist - no go either
  3. saw SmackAttack's notes at #4479, I compared my existing 0.71 plist to 0.74 plist, they are both currently "0" value. Has this got anything to do with the OS drive disappearing?


* I updated Lilu, VirtualSMC, AppleALC, WEG kexts to current versions on my 0.71 and it works fine, so my guess is something to do with updates in OC.

How could I fix this problem?

Thank you.

Is it a 970 EVO or 970 EVO Plus? If it's a Plus, you may need a firmware update.

I have a 970 EVO (non-Plus) and it has never disappeared from either the OpenCore Boot Picker or the Clover Boot Menu.

Does the 970 EVO appear consistently in BIOS? Is your EFI folder on the EFI partition of the 970 EVO? What version of macOS are you running?
 
Is it a 970 EVO or 970 EVO Plus? If it's a Plus, you may need a firmware update.

I have a 970 EVO (non-Plus) and it has never disappeared from either the OpenCore Boot Picker or the Clover Boot Menu.

Does the 970 EVO appear consistently in BIOS? Is your EFI folder on the EFI partition of the 970 EVO? What version of macOS are you running?

It is just 970 EVO, no plus.

I will check if there is a firmware update too, didn't think of that.

I have never had issue with the drive disappearing in BIOS. It seems since 0.72 OC no longer recognises my device (it is currently in the first M.2 slot, closest to the CPU).

There is also a second M.2 in the slot between the PCIE cards. A Silicon Power M.2 running just Windows 10.

Yes, the EFI is in EFI partition in the 970 EVO.
I am running Catalina 10.15.7.
 
Back
Top