Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

Joined
May 27, 2011
Messages
27
Motherboard
Gigabyte Z390 Designare
CPU
i9-9900K
Graphics
Vega 64
Mac
  1. MacBook
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. iOS
Hey all, I hope you can help me with this (imho) minor issue.

Setup is: two NVMEs with each it's own OS (Windows 10/MacOS BigSur)

Since I updated to OC 0.7.3 from 0.6.9, I cannot boot windows 10 from the OC picker. MacOS boots and works flewlessley, but when I try windows, it just shows the windows splash logo (in full resolution) and doesn't continue (no further errors, just stuck).

However, when I boot windows directly from it's own NVME by choosing it over F12 boot menu, Windows boots up without a problem. Interrestingly the windows splash screen is now low resolution, but that's just a side note.

I know there was a change in the way OC handles NVRAM somewhere after 0.6.9, so I obviously tried to clear NVRAM, I tried to erase all boot entries in BIOS and set only the UEFI where OC is installed, tried different scenarios within BIOS boot order, but no luck.

Where should I look next?

thank you so much!
 

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
16,384
Motherboard
Gigabyte Z490 Vision D
CPU
i5-10400
Graphics
RX 580
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
Hey all, I hope you can help me with this (imho) minor issue.

Setup is: two NVMEs with each it's own OS (Windows 10/MacOS BigSur)

Since I updated to OC 0.7.3 from 0.6.9, I cannot boot windows 10 from the OC picker. MacOS boots and works flewlessley, but when I try windows, it just shows the windows splash logo (in full resolution) and doesn't continue (no further errors, just stuck).

However, when I boot windows directly from it's own NVME by choosing it over F12 boot menu, Windows boots up without a problem. Interrestingly the windows splash screen is now low resolution, but that's just a side note.

I know there was a change in the way OC handles NVRAM somewhere after 0.6.9, so I obviously tried to clear NVRAM, I tried to erase all boot entries in BIOS and set only the UEFI where OC is installed, tried different scenarios within BIOS boot order, but no luck.

Where should I look next?

thank you so much!
Please try enabling VT-d in BIOS. If that does not help, then it’s necessary to disable AppleVTD by following a short procedure described in the link that appears in the Mini-Guide for OpenCore 0.7.3.
 

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
16,384
Motherboard
Gigabyte Z490 Vision D
CPU
i5-10400
Graphics
RX 580
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
Sorry, I can't speak English. I want to ask if there is a complete EFI configuration file or GitHub publishing address!

Gigabyte Designare Z390​

Please see Quick Reference spoiler at the top of Post 1.
 

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
16,384
Motherboard
Gigabyte Z490 Vision D
CPU
i5-10400
Graphics
RX 580
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
Secure Boot Violation
"Invalid signature detected. Check Secure Boot Policy in Setup"

My Z390 is dual boot, Windows 10 & macOS, and with OC 0.7.2.

I couldn't resist (after making full backups first) and upgraded to Windows 11, (shockingly, everything works perfectly in Windows 11... so far). This however required me to Enable Secure Boot and TPM.

However... upon boot I no longer am getting OC, it goes directly to Windows 11, but before that, I get two instances of:

Secure Boot Violation
"Invalid signature detected. Check Secure Boot Policy in Setup"

I click on each of the two OK buttons, and then it goes into Windows 11.

Has anyone encountered this yet? Looking for how to resolve.

Side note: Unlike prior "new versions" of Windows, (such as Windows H8), Windows 11 is really nice! I'm really liking it a lot, and as previously stated, NO issues. I was able to do an upgrade on my Z390 and no issues, everything works, and Windows 11 is fully Activated. It's crazy. I also was able to use the same Windows 11 USB flash drive I created to do a clean install on a different machine. I bought a new Windows 10 key from UR CD KEY DOT COM and was able to use that new key for the clean install of Windows 11, and fully Activated. Very pleased... Just need to resolve the annoying Secure Boot Violations so I can get back to OC and macOS now.


Thanks all!
I believe it’s only necessary to enable Intel Platform Trust Technology (PTT). Secure Boot can remain disabled in BIOS.
 
Joined
May 27, 2011
Messages
27
Motherboard
Gigabyte Z390 Designare
CPU
i9-9900K
Graphics
Vega 64
Mac
  1. MacBook
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. iOS
Please try enabling VT-d in BIOS. If that does not help, then it’s necessary to disable AppleVTD by following a short procedure described in the link that appears in the Mini-Guide for OpenCore 0.7.3.
It worked by enableing VT-d in BIOS. But with following notes:
-it only worked after I reset NVRAM again
-Windows only boots up on the second try after the machine was booted in MacOS (if that makes sense :) )

I didn't disable AppleVTD, for now I just live with having to do two boot ups to start windows.

thank you again.
 
Joined
Apr 20, 2021
Messages
138
Motherboard
Gigabyte Z390 Designare
CPU
i9-9900k
Graphics
RX 580
Mac
  1. Mac mini
Mobile Phone
  1. Android
I didn't find the complete EFI
Maybe I'm too stupid!
Have you been able to get your EFI / working?

I don't think (I could be wrong) just using someone else's EFI is a good idea. There are specific bits of information you need for your particular board, cards, and configuration. There is a lot of info here about that on CaseySJ's thread. It will just take patience, reading, and research to figure out how to do it. Once you get kind of close, there are many people here willing to help you out.
 
Last edited:
Joined
Apr 20, 2021
Messages
138
Motherboard
Gigabyte Z390 Designare
CPU
i9-9900k
Graphics
RX 580
Mac
  1. Mac mini
Mobile Phone
  1. Android
I believe it’s only necessary to enable Intel Platform Trust Technology (PTT). Secure Boot can remain disabled in BIOS.
Once again thank you very much @CaseySJ (and all who replied), for the excellent help and support!

Once I Disabled Secure Boot, Open Core appeared again.

However, when going into Windows 11, it went through a "Configuring devices" process, but afterwards did go into Windows 11, which I'm working in now.

I got my Windows 11 from the Microsoft Dev Channel, currently on:
Version 21H2
OS build 22000.194
Experience Windows Feature Experience Pack 1000.22000.194.0

So at this time I am not certain if Secure Boot being Disabled is being allowed, but with the to be released next month version may demand Secure Boot be Enabled. I guess we shall soon see.
 
Joined
Jun 18, 2010
Messages
129
Motherboard
z390 Designaire
CPU
i9-9900K
Graphics
AMD Radeon VII
Mac
  1. iMac
  2. MacBook Pro
  3. Mac mini
  4. Mac Pro
Classic Mac
  1. 128K
  2. 512K
  3. Classic
  4. Lisa
  5. Plus
  6. Portable
  7. Power Mac
  8. PowerBook
  9. Quadra
Mobile Phone
  1. iOS
Just updated to OC 0.7.3

With CpuTscSync 1.0.4 enable, my build can't wake up from sleep
I also experienced inability to wake with puTscSync. I get a hang on wake with kernel stack corruption. Disabling the kext seems to get everything working again.
panic(cpu 0 caller 0xffffff8018ac0e72): "Kernel stack memory corruption detected"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.141.40/libkern/stack_protector.c:37 Backtrace (CPU 0), Frame : Return Address 0xffffff8754e73a40 : 0xffffff801831c5dd mach_kernel : _handle_debugger_trap + 0x49d 0xffffff8754e73a90 : 0xffffff8018456d45 mach_kernel : _kdp_i386_trap + 0x155 0xffffff8754e73ad0 : 0xffffff80184488ce mach_kernel : _kernel_trap + 0x4ee 0xffffff8754e73b20 : 0xffffff80182c2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff8754e73b40 : 0xffffff801831bca7 mach_kernel : _DebuggerTrapWithState + 0x17 0xffffff8754e73c40 : 0xffffff801831c097 mach_kernel : _panic_trap_to_debugger + 0x227 0xffffff8754e73c90 : 0xffffff8018ac0f1c mach_kernel : _panic + 0x54 0xffffff8754e73d00 : 0xffffff8018ac0e72 mach_kernel : _mac_exc_action_check_exception_send + 0x3a2 0xffffff8754e73d10 : 0xffffff80182df8b9 mach_kernel : ___stack_chk_fail + 0x9 0xffffff8754e73d20 : 0xffffff80189ece33 mach_kernel : _IOHibernateSystemHasSlept + 0x4c3 0xffffff8754e73d40 : 0xffffff8018a845ba mach_kernel : __ZN14IOPMrootDomain15powerChangeDoneEm + 0xafa 0xffffff8754e73de0 : 0xffffff8018a15757 mach_kernel : __ZN9IOService8all_doneEv + 0x767 0xffffff8754e73e50 : 0xffffff8018a124ec mach_kernel : __ZN9IOService23actionPMWorkQueueInvokeEP11IOPMRequestP13IOPMWorkQueue + 0x86c 0xffffff8754e73ea0 : 0xffffff8018a0fb80 mach_kernel : __ZN13IOPMWorkQueue17checkRequestQueueEP11queue_entryPb + 0xa0 0xffffff8754e73ef0 : 0xffffff8018a0fa19 mach_kernel : __ZN13IOPMWorkQueue12checkForWorkEv + 0xc9 0xffffff8754e73f30 : 0xffffff8018a2b27e mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x11e 0xffffff8754e73f70 : 0xffffff8018a2a876 mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x36 0xffffff8754e73fa0 : 0xffffff80182c213e mach_kernel : _call_continuation + 0x2e BSD process name corresponding to current thread: kernel_task Boot args: keepsyms=1 debug=0x100 alcid=11 shikigva=80 igfxfw=2 Mac OS version: 19H1417 Kernel version: Darwin Kernel Version 19.6.0: Tue Aug 24 20:28:00 PDT 2021; root:xnu-6153.141.40~1/RELEASE_X86_64
 
Joined
May 28, 2017
Messages
86
Motherboard
Asus ROG G750JW
CPU
i7 4700HQ
Graphics
GTX 765M - 1920x1080
Mac
  1. iMac
Mobile Phone
  1. Android
I was finally able to dump this ROM properly. I don't think anyone has uploaded it yet. This was taken today from a brand new, Gigabtye GC-Titan Ridge Rev 2.0. It should be firmware 50, but the 50 version in the repository is different. I believe it may be from a Rev 1.0, I'm not sure.
 

Attachments

  • originalTitanRev2-BlueChip-2021-09-16.bin.zip
    276.1 KB · Views: 9
Joined
May 28, 2017
Messages
86
Motherboard
Asus ROG G750JW
CPU
i7 4700HQ
Graphics
GTX 765M - 1920x1080
Mac
  1. iMac
Mobile Phone
  1. Android
I just analyzed the two, they might be the same. Please double-check, if it is then it's mislabeled as Rev 1.0.
 
Top