Gigabyte Z390 M Gaming build with working NVRAM

[felixity]

Just upgrade to latest OpenCore EFI.

Ok I will go it a go later today, thank you.

*Update*
Upgrade to 0.71 folder, message is gone. Thank you very much for maintaining the updates~

 

[Biggs59]

Why don't you just boot in to Recovery, do a restore, then boot in to macOS and then update to the latest macOS?

I will try that next time

 

[astroboyvn88]

Hello @LiveSorcerer and @pastrychef,

Don't know if it can help you...

I got the same Samsung 970 Evo and use it with PastryChef EFI without pb, but since 11.3 update, I got the same kernel panic was you, randomly, after 30s to a minute...

I've been trying lot's of things to solve this included NVMEfix.kext, firmware update... but still no luck.
After lots of trying I finally find the problem, I am now sure it's related to Thunderbolt (I got a Titan Ridge 2 Add-In Card).
If I remove the Add-In card everything works like a charm, I can update to 11.4 without a pb.
View attachment 524556 View attachment 524557

as soon as I boot with thunderbolt card in, it freeze with NVMe panic.

I think weed need to hard flash the bios from the thunderbolt card to make it work again, but I'm not sure on how to do it and don't have the tool for the moment. (look at this post https://www.tonymacx86.com/threads/...bolt-3-i7-9700k-amd-rx-580.267551/post-208752)

Sorry for my English. Hope it will help you.

Hi @MRbrOwNfRoMLa, @LiveSorcerer, @pastrychef
I have the exact same problem. I put the RX 6900 XT on the PCIx16 slot. The card is a huge card. I also have an NVDIA card to do some 3D works but I couldn’t install it on the mobo because there is not enough room for the 2nd card plus the power supply wont be enough. I decided to put my Nvidia card in an eGPU shell and connect it using the Titan Ridge v2 on the PCIx4 slot in Windows. I was quite happy with the set up until my macOS freezes. As you know, pulling the Titan Ridge card out will solve the issue but my work needs both windows and mac so plug and unplug every time I switch the OS is not ideal. I don't need the Titan Rridge to work on macOS because it is mainly used to hook up the NVIDIA card in Windows. I tried many ways to disable the PCIx4 slot when in macOS but no luck until now. Do you know a way that works so I can disable this PCI slot when in macOS?

 

[LiveSorcerer]

Hi @MRbrOwNfRoMLa, @LiveSorcerer, @pastrychef
I have the exact same problem. I put the RX 6900 XT on the PCIx16 slot. The card is a huge card. I also have an NVDIA card to do some 3D works but I couldn’t install it on the mobo because there is not enough room for the 2nd card plus the power supply wont be enough. I decided to put my Nvidia card in an eGPU shell and connect it using the Titan Ridge v2 on the PCIx4 slot in Windows. I was quite happy with the set up until my macOS freezes. As you know, pulling the Titan Ridge card out will solve the issue but my work needs both windows and mac so plug and unplug every time I switch the OS is not ideal. I don't need the Titan Rridge to work on macOS because it is mainly used to hook up the NVIDIA card in Windows. I tried many ways to disable the PCIx4 slot when in macOS but no luck until now. Do you know a way that works so I can disable this PCI slot when in macOS?

About Titan Ridge V2, have you tried to update its firmware?
In my case it was freezing on macOS 11.3 onwards, I had to change the firmware, and it stopped giving the error, but TB3 doesn't work on Windows after that.

 

[pastrychef]

Hi @MRbrOwNfRoMLa, @LiveSorcerer, @pastrychef
I have the exact same problem. I put the RX 6900 XT on the PCIx16 slot. The card is a huge card. I also have an NVDIA card to do some 3D works but I couldn’t install it on the mobo because there is not enough room for the 2nd card plus the power supply wont be enough. I decided to put my Nvidia card in an eGPU shell and connect it using the Titan Ridge v2 on the PCIx4 slot in Windows. I was quite happy with the set up until my macOS freezes. As you know, pulling the Titan Ridge card out will solve the issue but my work needs both windows and mac so plug and unplug every time I switch the OS is not ideal. I don't need the Titan Rridge to work on macOS because it is mainly used to hook up the NVIDIA card in Windows. I tried many ways to disable the PCIx4 slot when in macOS but no luck until now. Do you know a way that works so I can disable this PCI slot when in macOS?

You can probably disable it with an SSDT but I've never tried this and don't know how to do it.

 

[MRbrOwNfRoMLa]

About Titan Ridge V2, have you tried to update its firmware?
In my case it was freezing on macOS 11.3 onwards, I had to change the firmware, and it stopped giving the error, but TB3 doesn't work on Windows after that.

Not at this time, I keep you inform when I'll be able to do it... I just plug/unplug my Titan Ridge when I need it and I made a second drive with 11.2.3 for now.

 

[astroboyvn88]

Thank you all for your reply.

@LiveSorcerer , unfortunately i do need the titan ridge card to work in windows so I don’t think I’ll update the firmware.

ill try the ssdt @pastrychef , I haven’t done any ssdt patch either but lets see, thanks

@MRbrOwNfRoMLa , thanks, please keep me posted! I cant go back to 11.2.3 though. Only 11.4 and onwards support 6000 series card have you tried Monterey? I hope the OS itself fixes the freezing issue

 

[astroboyvn88]

A bit of update from me,

I tried installing Monterey Beta (21A5284e), and it seems that this Build has fixed the TB3 issue. No more freezes like Big Sur. I will do more tests and will keep you posted!

 

[ibruno]

I too have recently started getting random crashes since I upgraded from OpenCore 0.6.6 to O.7.0 and from macOS 11.2.1 to 11.4. I also installed a Crucial P5 500GB NVME CT500P5SSD8 (disk1) at the same time as a backup to my OS SSD, a Samsung 860 EVO (disk0). I also have two other drives installed, both a 6TD WD mechanical drive; one named "Media" and the other "BackupMedia".

Anyway before this afternoon, my Hack had only crashed twice; the screen froze and by restarting it the problem went away. But just earlier today it crashed again, and now I can't get the computer to turn on for more than 2 minutes or so before it freezes again.

At first I thought it was because I had been uploading an 80,000 iPhoto Library to iCloud. The iPhoto library is on "Media" and according to HWMonitor, the temps on "Media" got up to 115 degrees Fahrenheit!

I let the computer cool off for an hour or so, and now the drive temps are at 84 degrees Fahrenheit. But I just realized that the NVME drive temp is at 122 degrees Fahrenheit!! I have only been using the NVME drive as a backup to the main OS SSD, the 860 EVO. Is that a normal temp for an NVME?

I've actually been able to successfully boot off of the backup NVME drive, and it's been up for 15 min or so with no restart. This was the error code that popped up when I booted into the NVME:


panic(cpu 1 caller 0xffffff80035f9a25): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (620 seconds ago): 63, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since load (590 seconds ago): 47, last successful checkin: 120 seconds ago

Backtrace (CPU 1), Frame : Return Address
0xffffffa0f593b670 : 0xffffff800028e0dd mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa0f593b6c0 : 0xffffff80003d4f33 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa0f593b700 : 0xffffff80003c552a mach_kernel : _kernel_trap + 0x55a
0xffffffa0f593b750 : 0xffffff8000232a2f mach_kernel : _return_from_trap + 0xff
0xffffffa0f593b770 : 0xffffff800028d8fd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa0f593b890 : 0xffffff800028dbf3 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa0f593b900 : 0xffffff8000a9d884 mach_kernel : _panic_with_thread_context
0xffffffa0f593b970 : 0xffffff80035f9a25 com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1 + 0x27
0xffffffa0f593b980 : 0xffffff80035f9660 com.apple.driver.watchdog : __ZN10IOWatchdog35userspaceDisableUserspaceMonitoringEP8OSObjectPvP25IOExternalMethodArguments
0xffffffa0f593b9a0 : 0xffffff8000a1e13e mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x1de
0xffffffa0f593b9f0 : 0xffffff80035f8a34 com.apple.driver.watchdog : __ZN20IOWatchdogUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x7c
0xffffffa0f593bb20 : 0xffffff8000a2837b mach_kernel : _is_io_connect_method + 0x35b
0xffffffa0f593bc80 : 0xffffff8000380961 mach_kernel : _iokit_server_routine + 0x4dd1
0xffffffa0f593bd90 : 0xffffff800029375d mach_kernel : _ipc_kobject_server + 0x2fd
0xffffffa0f593be00 : 0xffffff8000269cf5 mach_kernel : _ipc_kmsg_send + 0x115
0xffffffa0f593be60 : 0xffffff8000281312 mach_kernel : _mach_msg_overwrite_trap + 0x2d2
0xffffffa0f593bef0 : 0xffffff80003a982d mach_kernel : _mach_call_munger64 + 0x29d
0xffffffa0f593bfa0 : 0xffffff8000233216 mach_kernel : _hndl_mach_scall64 + 0x16
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[C29AFC04-7113-39AA-80DF-00F4DDAD0F46]@0xffffff80035f7000->0xffffff80035f9fff

Process name corresponding to current thread: watchdogd
Boot args: -alcbeta -lilubetaall debug=0x100 keepsyms=1 -wegbeta -vsmcbeta

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: 631422365993
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000009303b4b361
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x000000105e9a5826 0x0000000000000000

But I don't know if this is the correct error code; it may be from when I had last booted into the NVME drive, which was a couple of weeks ago. Where are the error logs stored when they are generated so that I can post it here in case anyone can help with what is happening.

Also can anyone recommend software that evaluate the health of my HD's? Here is a screenshot of the current temps from HWMonitor. Before the first crash earlier today "Media" was at 115 degrees Fahrenheit and in red. And the NVME has gone up to 138 degrees in the 30 min or so since I've been online.

Thanks,

Bruno

 

[ibruno]

So I decided to press my luck and rebooted back into my main HD, the EVO 860 SSD. It was up for a few minutes without crashing, so I further decided to launch Photos and see I couldn't get my iCloud Sync back on track.

Anyway, it crashed again, and gave me this error message:

panic(cpu 1 caller 0xffffff80035f9a25): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (1710 seconds ago): 172, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since load (1680 seconds ago): 156, last successful checkin: 120 seconds ago

Backtrace (CPU 1), Frame : Return Address
0xffffffa0f59a3670 : 0xffffff800028e0dd mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa0f59a36c0 : 0xffffff80003d4f33 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa0f59a3700 : 0xffffff80003c552a mach_kernel : _kernel_trap + 0x55a
0xffffffa0f59a3750 : 0xffffff8000232a2f mach_kernel : _return_from_trap + 0xff
0xffffffa0f59a3770 : 0xffffff800028d8fd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa0f59a3890 : 0xffffff800028dbf3 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa0f59a3900 : 0xffffff8000a9d884 mach_kernel : _panic_with_thread_context
0xffffffa0f59a3970 : 0xffffff80035f9a25 com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1 + 0x27
0xffffffa0f59a3980 : 0xffffff80035f9660 com.apple.driver.watchdog : __ZN10IOWatchdog35userspaceDisableUserspaceMonitoringEP8OSObjectPvP25IOExternalMethodArguments
0xffffffa0f59a39a0 : 0xffffff8000a1e13e mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x1de
0xffffffa0f59a39f0 : 0xffffff80035f8a34 com.apple.driver.watchdog : __ZN20IOWatchdogUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x7c
0xffffffa0f59a3b20 : 0xffffff8000a2837b mach_kernel : _is_io_connect_method + 0x35b
0xffffffa0f59a3c80 : 0xffffff8000380961 mach_kernel : _iokit_server_routine + 0x4dd1
0xffffffa0f59a3d90 : 0xffffff800029375d mach_kernel : _ipc_kobject_server + 0x2fd
0xffffffa0f59a3e00 : 0xffffff8000269cf5 mach_kernel : _ipc_kmsg_send + 0x115
0xffffffa0f59a3e60 : 0xffffff8000281312 mach_kernel : _mach_msg_overwrite_trap + 0x2d2
0xffffffa0f59a3ef0 : 0xffffff80003a982d mach_kernel : _mach_call_munger64 + 0x29d
0xffffffa0f59a3fa0 : 0xffffff8000233216 mach_kernel : _hndl_mach_scall64 + 0x16
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[C29AFC04-7113-39AA-80DF-00F4DDAD0F46]@0xffffff80035f7000->0xffffff80035f9fff

Process name corresponding to current thread: watchdogd
Boot args: -alcbeta -lilubetaall debug=0x100 keepsyms=1 -wegbeta -vsmcbeta

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: 1721434413784
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000190cd7ca149
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000001849c8103c 0x0000000000000000

And the next time I booted in the NVME Drive it also crashed after a few minutes, so now I'm afraid I won't be able to get into the Hack unless I first start from scratch with a new HD and then clone over the OS from one of my existing drives.

Any help would be appreciated.

Thanks,

Bruno