Contribute
Register

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

Hey guys, new to the forum here. I'm currently trying to get Mojave to work with my Z390 Designare with OpenCore. I downloaded the 0.7.6 EFI folder and made sure to set SecureBootModel to Disabled. When I try and boot it goes to the Apple logo with no loading bar and stays there. I had tried removing SSDTs/Drivers/Kexts that weren't applicable to Mojave (10.14.6) but keep getting stuck at the Apple logo. I tired older EFI files for OpenCore 0.7.1 & 0.6.6 & 0.6.1 with all the same issues. I also made sure to set the Device Info/ settings to iMac19,1

I wanted to stay on Mojave due to music software/hardware that I currently use. Any guidance would greatly be appreciated !
 
Hello
I made a colleague update to Big Sur and there is a problem with hanging your computer all the time.
I tried nvmefix.kext various versions. And also without nvmefix.kext. Each time the Crash system after a few minutes.



Code:
panic(cpu 0 caller 0xffffff80134ce860): nvme: "Fatal error occurred. CSTS=0x1 US[1]=0x0 US[0]=0x195 VID=0x1cc1 DID=0x8201
. FW Revision=32B3T8EA\n"@/System/Volumes/Data/SWE/macOS/BuildRoots/e90674e518/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.120.1/Common/IONVMeController.cpp:5499
Backtrace (CPU 0), Frame : Return Address
0xffffffa197593960 : 0xffffff8010c8e0dd
0xffffffa1975939b0 : 0xffffff8010dd4f33
0xffffffa1975939f0 : 0xffffff8010dc552a
0xffffffa197593a40 : 0xffffff8010c32a2f
0xffffffa197593a60 : 0xffffff8010c8d8fd
0xffffffa197593b80 : 0xffffff8010c8dbf3
0xffffffa197593bf0 : 0xffffff801149d81a
0xffffffa197593c60 : 0xffffff80134ce860
0xffffffa197593c80 : 0xffffff80134b345b
0xffffffa197593de0 : 0xffffff80113f4465
0xffffffa197593e50 : 0xffffff80113f4366
0xffffffa197593e80 : 0xffffff8010cd46c5
0xffffffa197593ef0 : 0xffffff8010cd5634
0xffffffa197593fa0 : 0xffffff8010c3213e
      Kernel Extensions in backtrace:
         com.apple.iokit.IONVMeFamily(2.1)[38BC0D0C-B305-30F6-8A8D-6804830F891A]@0xffffff80134ac000->0xffffff80134d5fff
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[423BF733-A622-3BC9-8F0F-920A2927CD35]@0xffffff80120fe000->0xffffff8012107fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[366C7BD4-9502-3D1C-ABBE-DE9749913D0C]@0xffffff80122c0000->0xffffff80122d5fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[99A70889-A31C-3B25-8E88-ADD3F317E4E4]@0xffffff801376a000->0xffffff8013792fff
            dependency: com.apple.iokit.IOReportFamily(47)[367CCAE7-DAB4-3424-B191-44044619D5CB]@0xffffff80137a1000->0xffffff80137a3fff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[A0D72FE9-649B-316A-8B5C-934E295FF0B5]@0xffffff801386d000->0xffffff801387efff

Process name corresponding to current thread: kernel_task
Boot args: alcid=1 chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20F71

Kernel version:
Darwin Kernel Version 20.5.0: Sat May  8 05:10:33 PDT 2021; root:xnu-7195.121.3~9/RELEASE_X86_64
Kernel UUID: 52A1E876-863E-38E3-AC80-09BBAB13B752
KernelCache slide: 0x0000000010a00000
KernelCache base:  0xffffff8010c00000
Kernel slide:      0x0000000010a10000
Kernel text base:  0xffffff8010c10000
__HIB  text base: 0xffffff8010b00000
System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 220545919183
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x00000033598faae4
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x00000018602a491a 0x0000000000000000


The system behaves the same on different SSD M.2. Clean or programs. The same all the time.
Mainboard Z390M Gaming BIOS F9.
 
Last edited:
Since upgrading to Big Sur, FCPX won't utilize iGPU when exporting in H264. Has anyone else experience the same? By the way I am using iMac19,1 on macOS Monterey.
 
Hello
I made a colleague update to Big Sur and there is a problem with hanging your computer all the time.
I tried nvmefix.kext various versions. And also without nvmefix.kext. Each time the Crash system after a few minutes.



Code:
panic(cpu 0 caller 0xffffff80134ce860): nvme: "Fatal error occurred. CSTS=0x1 US[1]=0x0 US[0]=0x195 VID=0x1cc1 DID=0x8201
. FW Revision=32B3T8EA\n"@/System/Volumes/Data/SWE/macOS/BuildRoots/e90674e518/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.120.1/Common/IONVMeController.cpp:5499
Backtrace (CPU 0), Frame : Return Address
0xffffffa197593960 : 0xffffff8010c8e0dd
0xffffffa1975939b0 : 0xffffff8010dd4f33
0xffffffa1975939f0 : 0xffffff8010dc552a
0xffffffa197593a40 : 0xffffff8010c32a2f
0xffffffa197593a60 : 0xffffff8010c8d8fd
0xffffffa197593b80 : 0xffffff8010c8dbf3
0xffffffa197593bf0 : 0xffffff801149d81a
0xffffffa197593c60 : 0xffffff80134ce860
0xffffffa197593c80 : 0xffffff80134b345b
0xffffffa197593de0 : 0xffffff80113f4465
0xffffffa197593e50 : 0xffffff80113f4366
0xffffffa197593e80 : 0xffffff8010cd46c5
0xffffffa197593ef0 : 0xffffff8010cd5634
0xffffffa197593fa0 : 0xffffff8010c3213e
      Kernel Extensions in backtrace:
         com.apple.iokit.IONVMeFamily(2.1)[38BC0D0C-B305-30F6-8A8D-6804830F891A]@0xffffff80134ac000->0xffffff80134d5fff
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[423BF733-A622-3BC9-8F0F-920A2927CD35]@0xffffff80120fe000->0xffffff8012107fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[366C7BD4-9502-3D1C-ABBE-DE9749913D0C]@0xffffff80122c0000->0xffffff80122d5fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[99A70889-A31C-3B25-8E88-ADD3F317E4E4]@0xffffff801376a000->0xffffff8013792fff
            dependency: com.apple.iokit.IOReportFamily(47)[367CCAE7-DAB4-3424-B191-44044619D5CB]@0xffffff80137a1000->0xffffff80137a3fff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[A0D72FE9-649B-316A-8B5C-934E295FF0B5]@0xffffff801386d000->0xffffff801387efff

Process name corresponding to current thread: kernel_task
Boot args: alcid=1 chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20F71

Kernel version:
Darwin Kernel Version 20.5.0: Sat May  8 05:10:33 PDT 2021; root:xnu-7195.121.3~9/RELEASE_X86_64
Kernel UUID: 52A1E876-863E-38E3-AC80-09BBAB13B752
KernelCache slide: 0x0000000010a00000
KernelCache base:  0xffffff8010c00000
Kernel slide:      0x0000000010a10000
Kernel text base:  0xffffff8010c10000
__HIB  text base: 0xffffff8010b00000
System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 220545919183
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x00000033598faae4
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x00000018602a491a 0x0000000000000000


The system behaves the same on different SSD M.2. Clean or programs. The same all the time.
Mainboard Z390M Gaming BIOS F9.
This might be due to a third party kernel extension. Two suggestions:
  • Post screenshot of /Library/Extensions
  • Boot in Safe Mode and see if system is stable. If it’s stable, it most likely means that a third party kext or app is causing the problem
 
This might be due to a third party kernel extension. Two suggestions:
  • Post screenshot of /Library/Extensions
  • Boot in Safe Mode and see if system is stable. If it’s stable, it most likely means that a third party kext or app is causing the problem

It is not it. All 3 SSD operate correctly on Z590 and Z690.
But this topic has signed me that the problem is somewhere else.


SSD NVME was on the processor line, hence the "CPU Fatal Error".

1000.png


I gave SSD to the second slot and the problem solved.
Probably Big Sur has a problem with such a configuration. On Catalina it works almost a year.


Changed the BIOS from 7 to 9 and lifted the system from Catalina to Big Sur.
There was Clover on Catalina. At Big Sur Opencore. But he was hanging at Opencore on Catalina too.
Now it works, but when I put in a second M.2 SSD, it's also a panic kernel after a few minutes.
 
Last edited:
Hi @CaseySJ, happy new year and happy (past) 3rd anniversary of your incredible guide!

I'm on OC076 & Monterey 12.0.1 for some time, had some bluetooth issues so it wasn't really working properly, especially after wake up from sleep it would disconnect and connect after login to desktop -> disable bluetooth -> enable bluetooth.

Some days ago I upgraded to Monterey 12.1 and now I have another problem: whenever wake from sleep happens "bluetoothd" process is working like crazy and fans are spinning so fast as if I'm rendering something. After I disable and enable back the bluetooth from the menubar that the craze is over. I don't know if this is happening because of BrcmPatchRAM, OC or macOS Monterey 12.1.

I had my VtD disabled and "DisableIOMapper" was also checked off since November. Today I enabled DisableIOMapper and i think bluetooth problem with connecting (especially after waking) is solved, I'll let you know if I'll have that problem anymore. But my problem with the intense bluetoothd process continues.

Do you have any ideas what should I try? Today OC077 will be released I think, so I will migrate to that but I don't think that will solve anything really.
 
Hi @CaseySJ, happy new year and happy (past) 3rd anniversary of your incredible guide!

I'm on OC076 & Monterey 12.0.1 for some time, had some bluetooth issues so it wasn't really working properly, especially after wake up from sleep it would disconnect and connect after login to desktop -> disable bluetooth -> enable bluetooth.

Some days ago I upgraded to Monterey 12.1 and now I have another problem: whenever wake from sleep happens "bluetoothd" process is working like crazy and fans are spinning so fast as if I'm rendering something. After I disable and enable back the bluetooth from the menubar that the craze is over. I don't know if this is happening because of BrcmPatchRAM, OC or macOS Monterey 12.1.

I had my VtD disabled and "DisableIOMapper" was also checked off since November. Today I enabled DisableIOMapper and i think bluetooth problem with connecting (especially after waking) is solved, I'll let you know if I'll have that problem anymore. But my problem with the intense bluetoothd process continues.

Do you have any ideas what should I try? Today OC077 will be released I think, so I will migrate to that but I don't think that will solve anything really.
Hello @echosat1,

Happy new year to you as well!

Some (obvious) things to try first:
  • Cold start. This means shutting down the system and flipping power switch on PSU to OFF for 10 seconds, then powering up.
  • If problem persists, try Reset NVRAM by pressing space bar at the OpenCore boot picker.
  • If problem still persists, try disabling BrcmPatchRAM3.kext.
 
It is not it. All 3 SSD operate correctly on Z590 and Z690.
But this topic has signed me that the problem is somewhere else.


SSD NVME was on the processor line, hence the "CPU Fatal Error".

View attachment 538549

I gave SSD to the second slot and the problem solved.
Probably Big Sur has a problem with such a configuration. On Catalina it works almost a year.


Changed the BIOS from 7 to 9 and lifted the system from Catalina to Big Sur.
There was Clover on Catalina. At Big Sur Opencore. But he was hanging at Opencore on Catalina too.
Now it works, but when I put in a second M.2 SSD, it's also a panic kernel after a few minutes.
  • What is the make/model of each NVMe SSD?
  • Have you tried CMOS Reset?
  • Is there a hardware problem with the NVMe SSD? If you have another computer, does this NVMe SSD work correctly on that system? (If you have external enclosure for NVMe SSD, you can connect it to the same computer or another computer via USB.)
 
Back
Top