Contribute
Register

Gigabyte Z390 M Gaming build with working NVRAM

I've been getting an error when booting occasionally. I see the apple progress bar and it then stalls about 1/3rd way across. I then have to restart with the restart switch as its stuck. When it restarts it boots and I get the "Your machine restarted because of an error" message and below is the report. I see it mentions CPU but it's meaningless to me, can anyone decipher it and point me along the right path? I'm on OC 0.7.3 if that's relevant

panic(cpu 4 caller 0xffffff80003c4996): Kernel trap at 0xffffff8000344764, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x00007fa3aada1000, CR3: 0x00000004a9e35056, CR4: 0x00000000003626e0
RAX: 0xffdfff8687f07870, RBX: 0xffffff8687047940, RCX: 0x48e9067cf24d00db, RDX: 0xffffff868821b410
RSP: 0xffffffa0643c3910, RBP: 0xffffffa0643c3950, RSI: 0xffffff868821b320, RDI: 0xffffff8687047930
R8: 0xffffff868821b320, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000000180
R12: 0x0000000000002000, R13: 0x0000000000000000, R14: 0xffffff8687047930, R15: 0xffffff868821b410
RFL: 0x0000000000010202, RIP: 0xffffff8000344764, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0x00007fa3aada1000, Error code: 0x0000000000000000, Fault CPU: 0x4, PL: 0, VF: 0

Backtrace (CPU 4), Frame : Return Address
0xffffff80001581e0 : 0xffffff800028cfdd
0xffffff8000158230 : 0xffffff80003d3fd3
0xffffff8000158270 : 0xffffff80003c45ca
0xffffff80001582c0 : 0xffffff8000231a2f
0xffffff80001582e0 : 0xffffff800028c7fd
0xffffff8000158400 : 0xffffff800028caf3
0xffffff8000158470 : 0xffffff8000a9cdca
0xffffff80001584e0 : 0xffffff80003c4996
0xffffff8000158660 : 0xffffff80003c467d
0xffffff80001586b0 : 0xffffff8000231a2f
0xffffff80001586d0 : 0xffffff8000344764
0xffffffa0643c3950 : 0xffffff8000333f68
0xffffffa0643c39c0 : 0xffffff800032ed80
0xffffffa0643c3bc0 : 0xffffff800032ca47
0xffffffa0643c3d00 : 0xffffff80003790f5
0xffffffa0643c3d90 : 0xffffff80035e6ea4
0xffffffa0643c3e10 : 0xffffff80007cc187
0xffffffa0643c3e50 : 0xffffff80007cb834
0xffffffa0643c3eb0 : 0xffffff80007cd2a8
0xffffffa0643c3f30 : 0xffffff80007cc674
0xffffffa0643c3f70 : 0xffffff80007cc5d6
0xffffffa0643c3fa0 : 0xffffff800023113e
Kernel Extensions in backtrace:
com.apple.kec.pthread(1.0)[33C1DFBF-F57E-3D13-8D6A-650DC1D56CBD]@0xffffff80035e5000->0xffffff80035edfff

Process name corresponding to current thread: authd

Mac OS version:
20G165

Kernel version:
Darwin Kernel Version 20.6.0: Mon Aug 30 06:12:21 PDT 2021; root:xnu-7195.141.6~3/RELEASE_X86_64
Kernel UUID: C2591F4E-EE82-33CC-8C59-DB81D9AD80DD
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: 18531153838
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000004508afb4c
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x000000084328802d 0x0000000000000000
 
I've been getting an error when booting occasionally. I see the apple progress bar and it then stalls about 1/3rd way across. I then have to restart with the restart switch as its stuck. When it restarts it boots and I get the "Your machine restarted because of an error" message and below is the report. I see it mentions CPU but it's meaningless to me, can anyone decipher it and point me along the right path? I'm on OC 0.7.3 if that's relevant

panic(cpu 4 caller 0xffffff80003c4996): Kernel trap at 0xffffff8000344764, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x00007fa3aada1000, CR3: 0x00000004a9e35056, CR4: 0x00000000003626e0
RAX: 0xffdfff8687f07870, RBX: 0xffffff8687047940, RCX: 0x48e9067cf24d00db, RDX: 0xffffff868821b410
RSP: 0xffffffa0643c3910, RBP: 0xffffffa0643c3950, RSI: 0xffffff868821b320, RDI: 0xffffff8687047930
R8: 0xffffff868821b320, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000000180
R12: 0x0000000000002000, R13: 0x0000000000000000, R14: 0xffffff8687047930, R15: 0xffffff868821b410
RFL: 0x0000000000010202, RIP: 0xffffff8000344764, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0x00007fa3aada1000, Error code: 0x0000000000000000, Fault CPU: 0x4, PL: 0, VF: 0

Backtrace (CPU 4), Frame : Return Address
0xffffff80001581e0 : 0xffffff800028cfdd
0xffffff8000158230 : 0xffffff80003d3fd3
0xffffff8000158270 : 0xffffff80003c45ca
0xffffff80001582c0 : 0xffffff8000231a2f
0xffffff80001582e0 : 0xffffff800028c7fd
0xffffff8000158400 : 0xffffff800028caf3
0xffffff8000158470 : 0xffffff8000a9cdca
0xffffff80001584e0 : 0xffffff80003c4996
0xffffff8000158660 : 0xffffff80003c467d
0xffffff80001586b0 : 0xffffff8000231a2f
0xffffff80001586d0 : 0xffffff8000344764
0xffffffa0643c3950 : 0xffffff8000333f68
0xffffffa0643c39c0 : 0xffffff800032ed80
0xffffffa0643c3bc0 : 0xffffff800032ca47
0xffffffa0643c3d00 : 0xffffff80003790f5
0xffffffa0643c3d90 : 0xffffff80035e6ea4
0xffffffa0643c3e10 : 0xffffff80007cc187
0xffffffa0643c3e50 : 0xffffff80007cb834
0xffffffa0643c3eb0 : 0xffffff80007cd2a8
0xffffffa0643c3f30 : 0xffffff80007cc674
0xffffffa0643c3f70 : 0xffffff80007cc5d6
0xffffffa0643c3fa0 : 0xffffff800023113e
Kernel Extensions in backtrace:
com.apple.kec.pthread(1.0)[33C1DFBF-F57E-3D13-8D6A-650DC1D56CBD]@0xffffff80035e5000->0xffffff80035edfff

Process name corresponding to current thread: authd

Mac OS version:
20G165

Kernel version:
Darwin Kernel Version 20.6.0: Mon Aug 30 06:12:21 PDT 2021; root:xnu-7195.141.6~3/RELEASE_X86_64
Kernel UUID: C2591F4E-EE82-33CC-8C59-DB81D9AD80DD
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: 18531153838
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000004508afb4c
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x000000084328802d 0x0000000000000000

Since the kernel panic is sporadic, I'm inclined to think it's due to some failing hardware. If it were software related, it should consistently panic on every boot at the same point.

Please see the following link, the person posting there has pretty much identical panic.
 
Clover EFI updated to r5140.1.

This will likely be the minimum version of Clover we will need if we want to update to Monterey.

All kexts updated to latest release versions.

Remember to test with USB flash drive before deleing your existing/working EFI.
 
Hey all.

I've been following CaseySJ's thread on z390 Designare for a long time as I have several builds based on that thread, and recently something came to light that I wanted to share here as it appears to apply to this board as well (hopefully it's okay to do this and I have this Moderator's blessing!). I take no credit and fully disclose that I'm definitely not qualified to really know the ins-and-outs of all of this stuff -- nor do I fully understand how and why certain things like SSDTs function -- I'm just a very rudimentary practitioner! And of course, Pastrychef, please yell at me or correct any and all statements as you see fit, or if somehow I missed that this has been discussed previously.

I am a video editor, and one of my machines in particular had this strange problem that REQUIRED VT-d to be enabled in BIOS to circumnavigate (having to do with a BlackMagic PCIe card). In the past year, Casey and his skilled contributors developed the means to more properly enable VT-d in such a way that MacOS truly found it activated (Apple VTd), which can have the benefit of improved Thunderbolt device support, and better functioning wifi/ethernet.

Here goes;
Pastrychef acknowledges (sorry to speak of you in third person!) that he has never had a build that cared if VT-d is enabled in bios or not -- and I agree I've never seen ill-effects either way. However on my build, it seems Mac OS wasn't truly utilizing VT-d as if AppleVTD was available. Using Opencore (in my case 073) if one applies the same SSDT-DMAR.aml from the Designare thread (along with some OC config adjustments), AppleVTD will appear in IOReg like it would on a real Mac.

All info can be found here:
Enable AppleVTD with No Impact to WiFi and Ethernet

In a nutshell:
1) Enable VT-d in BIOS
2) Install the SSDT-DMAR.aml in OC/ACPI (attached)
3) Add the SSDT-DMAR.aml to the ACPI section in config
4) Uncheck DisableIoMapper in Kernel Quirks
5) Remove dart=0 from boot-args (if it exists)
6) Delete the standard DMAR table by adding an entry in ACPI/Delete
7) Reboot

I hope this a welcome contribution!

The following images were borrowed from Casey's thread:
screen-shot-2021-07-06-at-4-53-13-am-png.523868

screen-shot-2021-09-15-at-9-56-52-am-png.529007

screen-shot-2021-07-06-at-4-12-43-am-png.523867
 

Attachments

  • SSDT-DMAR.aml
    104 bytes · Views: 72
Got Beta
For Monterey Beta 7+ OpenCore 0.7.4 is needed with AdviseFeatures = True and sometimes SMBIOS iMac17,1 is needed.
Thanks. That did the trick. Running Beta 8 now with no issues after upgrading to the OpenCore 0.7.4 beta. Still using F9m firmware too.
 
Hey all.

I've been following CaseySJ's thread on z390 Designare for a long time as I have several builds based on that thread, and recently something came to light that I wanted to share here as it appears to apply to this board as well (hopefully it's okay to do this and I have this Moderator's blessing!). I take no credit and fully disclose that I'm definitely not qualified to really know the ins-and-outs of all of this stuff -- nor do I fully understand how and why certain things like SSDTs function -- I'm just a very rudimentary practitioner! And of course, Pastrychef, please yell at me or correct any and all statements as you see fit, or if somehow I missed that this has been discussed previously.

I am a video editor, and one of my machines in particular had this strange problem that REQUIRED VT-d to be enabled in BIOS to circumnavigate (having to do with a BlackMagic PCIe card). In the past year, Casey and his skilled contributors developed the means to more properly enable VT-d in such a way that MacOS truly found it activated (Apple VTd), which can have the benefit of improved Thunderbolt device support, and better functioning wifi/ethernet.

Here goes;
Pastrychef acknowledges (sorry to speak of you in third person!) that he has never had a build that cared if VT-d is enabled in bios or not -- and I agree I've never seen ill-effects either way. However on my build, it seems Mac OS wasn't truly utilizing VT-d as if AppleVTD was available. Using Opencore (in my case 073) if one applies the same SSDT-DMAR.aml from the Designare thread (along with some OC config adjustments), AppleVTD will appear in IOReg like it would on a real Mac.

All info can be found here:
Enable AppleVTD with No Impact to WiFi and Ethernet

In a nutshell:
1) Enable VT-d in BIOS
2) Install the SSDT-DMAR.aml in OC/ACPI (attached)
3) Add the SSDT-DMAR.aml to the ACPI section in config
4) Uncheck DisableIoMapper in Kernel Quirks
5) Remove dart=0 from boot-args (if it exists)
6) Delete the standard DMAR table by adding an entry in ACPI/Delete
7) Reboot

I hope this a welcome contribution!

The following images were borrowed from Casey's thread:
screen-shot-2021-07-06-at-4-53-13-am-png.523868

screen-shot-2021-09-15-at-9-56-52-am-png.529007

screen-shot-2021-07-06-at-4-12-43-am-png.523867

Thanks for the heads up. I'll give this a try in the next few days. :thumbup:
 
Thanks for the heads up. I'll give this a try in the next few days. :thumbup:
Cool, side note: I also have his SSDT-DMAC.aml applied, but Casey says their tests didn’t provide conclusive evidence this was needed.
Best,
J
 
Thanks for this pastrychef! Got my Z390 M Gaming up and running with the OpenCore 0.7.3 files. One issue - system will not sleep. Screen goes back, system "wakes up", but fans don't shut off and power light stays on.

Code:
pmset -g assertions
2021-10-03 18:30:11 -0700
Assertion status system-wide:
   BackgroundTask                 0
   ApplePushServiceTask           0
   UserIsActive                   1
   PreventUserIdleDisplaySleep    0
   PreventSystemSleep             0
   ExternalMedia                  0
   PreventUserIdleSystemSleep     0
   NetworkClientActive            0
Listed by owning process:
   pid 98(hidd): [0x00003547000987a1] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle.4294968371.3"
    Timeout will fire in 1200 secs Action=TimeoutActionRelease
Kernel Assertions: 0x4=USB
   id=500  level=255 0x4=USB mod=1969-12-31, 4:00 PM description=com.apple.usb.externaldevice.14300000 owner=Keyboard Hub
   id=507  level=255 0x4=USB mod=1969-12-31, 4:00 PM description=com.apple.usb.externaldevice.14330000 owner=USB Receiver
Idle sleep preventers: IODisplayWrangler

I tried adding darkwake=0 which didn't help. Only connected USB devices are mouse and keyboard. Specs are in my sig. Any thoughts from anyone?
 
Thanks for this pastrychef! Got my Z390 M Gaming up and running with the OpenCore 0.7.3 files. One issue - system will not sleep. Screen goes back, system "wakes up", but fans don't shut off and power light stays on.

Code:
pmset -g assertions
2021-10-03 18:30:11 -0700
Assertion status system-wide:
   BackgroundTask                 0
   ApplePushServiceTask           0
   UserIsActive                   1
   PreventUserIdleDisplaySleep    0
   PreventSystemSleep             0
   ExternalMedia                  0
   PreventUserIdleSystemSleep     0
   NetworkClientActive            0
Listed by owning process:
   pid 98(hidd): [0x00003547000987a1] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle.4294968371.3"
    Timeout will fire in 1200 secs Action=TimeoutActionRelease
Kernel Assertions: 0x4=USB
   id=500  level=255 0x4=USB mod=1969-12-31, 4:00 PM description=com.apple.usb.externaldevice.14300000 owner=Keyboard Hub
   id=507  level=255 0x4=USB mod=1969-12-31, 4:00 PM description=com.apple.usb.externaldevice.14330000 owner=USB Receiver
Idle sleep preventers: IODisplayWrangler

I tried adding darkwake=0 which didn't help. Only connected USB devices are mouse and keyboard. Specs are in my sig. Any thoughts from anyone?
Mine goes to sleep (and wakes) no problem, tertiumsquid. Perhaps you need to submit your EFI and a snapshot of your bios settings?
 
Thanks for this pastrychef! Got my Z390 M Gaming up and running with the OpenCore 0.7.3 files. One issue - system will not sleep. Screen goes back, system "wakes up", but fans don't shut off and power light stays on.

Code:
pmset -g assertions
2021-10-03 18:30:11 -0700
Assertion status system-wide:
   BackgroundTask                 0
   ApplePushServiceTask           0
   UserIsActive                   1
   PreventUserIdleDisplaySleep    0
   PreventSystemSleep             0
   ExternalMedia                  0
   PreventUserIdleSystemSleep     0
   NetworkClientActive            0
Listed by owning process:
   pid 98(hidd): [0x00003547000987a1] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle.4294968371.3"
    Timeout will fire in 1200 secs Action=TimeoutActionRelease
Kernel Assertions: 0x4=USB
   id=500  level=255 0x4=USB mod=1969-12-31, 4:00 PM description=com.apple.usb.externaldevice.14300000 owner=Keyboard Hub
   id=507  level=255 0x4=USB mod=1969-12-31, 4:00 PM description=com.apple.usb.externaldevice.14330000 owner=USB Receiver
Idle sleep preventers: IODisplayWrangler

I tried adding darkwake=0 which didn't help. Only connected USB devices are mouse and keyboard. Specs are in my sig. Any thoughts from anyone?

Please enter the following in Terminal and post the output:
PHP:
pmset -g assertions
 
Back
Top