Contribute
Register

Gigabyte Z390 M Gaming build with working NVRAM

Joined
Jun 18, 2020
Messages
16
Motherboard
Gigabyte Z390 M GAMING
CPU
i9-9900K
Graphics
RX 580
Mac
  1. iMac
Classic Mac
  1. Power Mac
Mobile Phone
  1. iOS
Did you have previous versions of my EFI working?

Did you disable CFG lock in BIOS?
Yes, I had a previous version from when I reinstalled my system from scratch a few months ago. I was able to boot from the backup I made before trying the new EFI. CFG lock is disabled.

I also had an earlier version of your EFI on my Big Sur installation drive, I tried to boot from it but it got stuck at the beginning of the progress bar on the page with the Apple logo. Maybe this old EFI is not working because I made some OS updates since then ?

I am getting strange system crashes since last week, that is why I came back here to update my EFI to see if it would help. It often freezes immediately after trying to open some random FCPX projects. I also got a crash while streaming a Skype conversation on OBS. Here is the error report from this morning :
 

Attachments

  • Panic 2021-07-10.txt
    8.6 KB · Views: 23

pastrychef

Moderator
Joined
May 29, 2013
Messages
18,337
Motherboard
Asus Z370-G Gaming (Wi-Fi AC)
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
RX 6600 XT
Mac
  1. MacBook
  2. Mac Pro
Classic Mac
  1. iBook
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
Yes, I had a previous version from when I reinstalled my system from scratch a few months ago. I was able to boot from the backup I made before trying the new EFI. CFG lock is disabled.

I also had an earlier version of your EFI on my Big Sur installation drive, I tried to boot from it but it got stuck at the beginning of the progress bar on the page with the Apple logo. Maybe this old EFI is not working because I made some OS updates since then ?

I am getting strange system crashes since last week, that is why I came back here to update my EFI to see if it would help. It often freezes immediately after trying to open some random FCPX projects. I also got a crash while streaming a Skype conversation on OBS. Here is the error report from this morning :

I don't know why the EFI is not working for you. Just to re-confirm, I just downloaded the EFI from post #1 a few moments ago and booted from it without any issues.

The panic log doesn't say much. I just see that FCPX crashed on you.

I can tell it was an old version of Clover based the kext versions.
 

pastrychef

Moderator
Joined
May 29, 2013
Messages
18,337
Motherboard
Asus Z370-G Gaming (Wi-Fi AC)
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
RX 6600 XT
Mac
  1. MacBook
  2. Mac Pro
Classic Mac
  1. iBook
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
FYI:

Enabling TPM in BIOS does not affect Clover, OpenCore, or macOS on this motherboard.
 
Joined
Sep 10, 2017
Messages
343
Motherboard
Gigabyte Z590M GAMING X
CPU
i7-11700K
Graphics
RX6800 XT 16GB
Mac
  1. MacBook Pro
  2. Mac Pro
Classic Mac
  1. Power Mac
Mobile Phone
  1. Android
  2. iOS
Is anyone crashing on MacOS 11.4 with OpenCore 0.7.0 and 0.7.1?
panic(cpu 0 caller 0xffffff8002ace860): nvme: "Fatal error occurred. CSTS=0xffffffff US[1]=0x0 US[0]=0x307 VID=0x144d DID=0xa808
. FW Revision=2B2QEXE7\n"@/System/Volumes/Data/SWE/macOS/BuildRoots/e90674e518/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.120.1/Common/IONVMeController.cpp:5499

The system is crashing even with NVMefix active or not.
The System is installed on the Samsun 970 Evo Plus 500GB (firmware updated).
 

pastrychef

Moderator
Joined
May 29, 2013
Messages
18,337
Motherboard
Asus Z370-G Gaming (Wi-Fi AC)
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
RX 6600 XT
Mac
  1. MacBook
  2. Mac Pro
Classic Mac
  1. iBook
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
Is anyone crashing on MacOS 11.4 with OpenCore 0.7.0 and 0.7.1?
panic(cpu 0 caller 0xffffff8002ace860): nvme: "Fatal error occurred. CSTS=0xffffffff US[1]=0x0 US[0]=0x307 VID=0x144d DID=0xa808
. FW Revision=2B2QEXE7\n"@/System/Volumes/Data/SWE/macOS/BuildRoots/e90674e518/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.120.1/Common/IONVMeController.cpp:5499

The system is crashing even with NVMefix active or not.
The System is installed on the Samsun 970 Evo Plus 500GB (firmware updated).

Nope. I haven't had a Kernel Panic since NVRAM was fixed and that was well over 1.5 years ago.
 
Joined
Sep 10, 2017
Messages
343
Motherboard
Gigabyte Z590M GAMING X
CPU
i7-11700K
Graphics
RX6800 XT 16GB
Mac
  1. MacBook Pro
  2. Mac Pro
Classic Mac
  1. Power Mac
Mobile Phone
  1. Android
  2. iOS
This issue:
panic(cpu 6 caller 0xffffff8002ace860): nvme: "Fatal error occurred. CSTS=0xffffffff US[1]=0x0 US[0]=0x316 VID=0x144d DID=0xa808
. FW Revision=2B2QEXE7\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 6), Frame : Return Address
0xffffffa12b4c3960 : 0xffffff800028e0dd
0xffffffa12b4c39b0 : 0xffffff80003d4f33
0xffffffa12b4c39f0 : 0xffffff80003c552a
0xffffffa12b4c3a40 : 0xffffff8000232a2f
0xffffffa12b4c3a60 : 0xffffff800028d8fd
0xffffffa12b4c3b80 : 0xffffff800028dbf3
0xffffffa12b4c3bf0 : 0xffffff8000a9d81a
0xffffffa12b4c3c60 : 0xffffff8002ace860
0xffffffa12b4c3c80 : 0xffffff8002ab345b
0xffffffa12b4c3de0 : 0xffffff80009f4465
0xffffffa12b4c3e50 : 0xffffff80009f4366
0xffffffa12b4c3e80 : 0xffffff80002d46c5
0xffffffa12b4c3ef0 : 0xffffff80002d5634
0xffffffa12b4c3fa0 : 0xffffff800023213e
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[38BC0D0C-B305-30F6-8A8D-6804830F891A]@0xffffff8002aac000->0xffffff8002ad5fff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[423BF733-A622-3BC9-8F0F-920A2927CD35]@0xffffff80016fe000->0xffffff8001707fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[366C7BD4-9502-3D1C-ABBE-DE9749913D0C]@0xffffff80018c0000->0xffffff80018d5fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[99A70889-A31C-3B25-8E88-ADD3F317E4E4]@0xffffff8002d6a000->0xffffff8002d92fff
dependency: com.apple.iokit.IOReportFamily(47)[367CCAE7-DAB4-3424-B191-44044619D5CB]@0xffffff8002da1000->0xffffff8002da3fff
dependency: com.apple.iokit.IOStorageFamily(2.1)[A0D72FE9-649B-316A-8B5C-934E295FF0B5]@0xffffff8002e6d000->0xffffff8002e7efff

Process name corresponding to current thread: kernel_task
Boot args: agdpmod=pikera shikigva=80

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: 0x0000000000000000
KernelCache base: 0xffffff8000200000
Kernel slide: 0x0000000000010000
Kernel text base: 0xffffff8000210000
__HIB text base: 0xffffff8000100000
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: 1340582129184
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000013820ebf05e
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000001c269d92dc 0x0000000000000000
 

pastrychef

Moderator
Joined
May 29, 2013
Messages
18,337
Motherboard
Asus Z370-G Gaming (Wi-Fi AC)
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
RX 6600 XT
Mac
  1. MacBook
  2. Mac Pro
Classic Mac
  1. iBook
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
This issue:
panic(cpu 6 caller 0xffffff8002ace860): nvme: "Fatal error occurred. CSTS=0xffffffff US[1]=0x0 US[0]=0x316 VID=0x144d DID=0xa808
. FW Revision=2B2QEXE7\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 6), Frame : Return Address
0xffffffa12b4c3960 : 0xffffff800028e0dd
0xffffffa12b4c39b0 : 0xffffff80003d4f33
0xffffffa12b4c39f0 : 0xffffff80003c552a
0xffffffa12b4c3a40 : 0xffffff8000232a2f
0xffffffa12b4c3a60 : 0xffffff800028d8fd
0xffffffa12b4c3b80 : 0xffffff800028dbf3
0xffffffa12b4c3bf0 : 0xffffff8000a9d81a
0xffffffa12b4c3c60 : 0xffffff8002ace860
0xffffffa12b4c3c80 : 0xffffff8002ab345b
0xffffffa12b4c3de0 : 0xffffff80009f4465
0xffffffa12b4c3e50 : 0xffffff80009f4366
0xffffffa12b4c3e80 : 0xffffff80002d46c5
0xffffffa12b4c3ef0 : 0xffffff80002d5634
0xffffffa12b4c3fa0 : 0xffffff800023213e
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[38BC0D0C-B305-30F6-8A8D-6804830F891A]@0xffffff8002aac000->0xffffff8002ad5fff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[423BF733-A622-3BC9-8F0F-920A2927CD35]@0xffffff80016fe000->0xffffff8001707fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[366C7BD4-9502-3D1C-ABBE-DE9749913D0C]@0xffffff80018c0000->0xffffff80018d5fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[99A70889-A31C-3B25-8E88-ADD3F317E4E4]@0xffffff8002d6a000->0xffffff8002d92fff
dependency: com.apple.iokit.IOReportFamily(47)[367CCAE7-DAB4-3424-B191-44044619D5CB]@0xffffff8002da1000->0xffffff8002da3fff
dependency: com.apple.iokit.IOStorageFamily(2.1)[A0D72FE9-649B-316A-8B5C-934E295FF0B5]@0xffffff8002e6d000->0xffffff8002e7efff

Process name corresponding to current thread: kernel_task
Boot args: agdpmod=pikera shikigva=80

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: 0x0000000000000000
KernelCache base: 0xffffff8000200000
Kernel slide: 0x0000000000010000
Kernel text base: 0xffffff8000210000
__HIB text base: 0xffffff8000100000
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: 1340582129184
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000013820ebf05e
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000001c269d92dc 0x0000000000000000

Yeah. Looks like something is up with your NVMe SSD.
 
Joined
Sep 10, 2017
Messages
343
Motherboard
Gigabyte Z590M GAMING X
CPU
i7-11700K
Graphics
RX6800 XT 16GB
Mac
  1. MacBook Pro
  2. Mac Pro
Classic Mac
  1. Power Mac
Mobile Phone
  1. Android
  2. iOS
Yeah. Looks like something is up with your NVMe SSD.
I think so too, but I went to check its integrity through windows and it's good.
 
Top