- May 29, 2013
- Gigabyte Z390 M Gaming
- i9-9900K OC'd @ 5.0GHz
- Vega 56 (Bios flashed to 64)
- Classic Mac
- Mobile Phone
I had the same issue with the 970 EVO 1TB on my z390 Gaming X. I went away when I switched my SSDs. I moved the 970 from the secondary slot (bottom one) to the primary (top one) and the 960 vice versa. It went away after that. No idea it is was a lucky shot but worth a try.Since a few day I am struggling with Big Sur 11.3.1. I get following kernel panic and the system freezes. How could I possibly fix it ?
panic(cpu 0 caller 0xffffff8002ac2838): nvme: "Fatal error occurred. CSTS=0x3 US=0x0 US=0x4a VID=0x144d DID=0xa808
. FW Revision=2B2QEXE7\n"@/System/Volumes/Data/SWE/macOS/BuildRoots/2288acc43c/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.100.13/Common/IONVMeController.cpp:5499
Backtrace (CPU 0), Frame : Return Address
0xffffffa109053960 : 0xffffff800028e02d mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa1090539b0 : 0xffffff80003d48e3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa1090539f0 : 0xffffff80003c4eda mach_kernel : _kernel_trap + 0x55a
0xffffffa109053a40 : 0xffffff8000232a2f mach_kernel : _return_from_trap + 0xff
0xffffffa109053a60 : 0xffffff800028d84d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa109053b80 : 0xffffff800028db43 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa109053bf0 : 0xffffff8000a9d68a mach_kernel : _panic + 0x54
0xffffffa109053c60 : 0xffffff8002ac2838 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController14CommandTimeoutEP16AppleNVMeRequest.cold.1
0xffffffa109053c80 : 0xffffff8002aa7433 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController13FatalHandlingEv + 0x1af
0xffffffa109053de0 : 0xffffff80009f54f5 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5
0xffffffa109053e50 : 0xffffff80009f53f6 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc6
0xffffffa109053e80 : 0xffffff80002d44b5 mach_kernel : _thread_call_delayed_timer + 0x4a5
0xffffffa109053ef0 : 0xffffff80002d5424 mach_kernel : _thread_call_delayed_timer + 0x1414
0xffffffa109053fa0 : 0xffffff800023213e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
Process name corresponding to current thread: kernel_task
Boot args: -alcid=18 -alcbeta -lilubetaall debug=0x100 keepsyms=1 -wegbeta -vsmcbeta brcmfx-country=DE darkwake=0
Mac OS version:
Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:47 PDT 2021; root:xnu-7195.101.2~1/RELEASE_X86_64
Kernel UUID: 068F99A3-1DB3-31C0-87D5-09942F122BB6
KernelCache slide: 0x0000000000000000
KernelCache base: 0xffffff8000200000
Kernel slide: 0x0000000000010000
Kernel text base: 0xffffff8000210000
__HIB text base: 0xffffff8000100000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0
System uptime in nanoseconds: 390329616930
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000005ae1754e87
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000001f0c97230c 0x0000000000000000
Ok. I've downloaded the efi-clover-5134-z390m-zip file. I assume that is the most current, having the highest build number?
Using the config.plist in your file, I mounted my EFI partition, navigated to EFI/Clover/ and opened the config.plist there. It is dated Oct 20, 2019, which seems like about when I originally tried to update MacOS.
In the SMBIOS section, I show iMac19,2 and an IM192.whatever Bios Version, and an SN under System.
Everything under 'board' is blank, and smUUID is also blank.
Am I looking in the wrong place?
Is the system serial number and hardware UUID I show in the Hardware Overview in System Report the SN/UUID that I want? Or do I need to generate new if I'm switching profiles to iMac Pro 1,1?
Got it. I don't mind switching.Use either iMac19,1 or iMacPro1,1.
If you want to keep using iMac19,2, you will have to redo the USB ports kext.
Got it. I don't mind switching.
Does that mean I just need to generate a new SN and SmUUID in your config.plist, generate config, and then copy/paste the contents of your EFI folder into my EFI folder, reboot, and continue the os install? Or is there something more I need to do?
I have been having issues with "Bluetooth Not Available" when my machine wakes from sleep. It wouldn't happen every time, but usually once a day. I would either need to restart or let the machine go back to sleep and usually that would resolve it. It seems like it started happening at some point and I couldn't pinpoint when. Anyways, long story short, I disabled the USBWakeFixup.kext and SSDT-USBW.dsl and it hasn't happened in 12 days. Now I have to click on the mouse a couple times to wakeup the screen, but that is much better than not having my bluetooth keyboard or mouse not available at random times. I have the Fenvi bluetooth/wifi card. Just throwing this out there in case anyone else is having this issue. I am not using pastry chef's EFI, but one I created myself from scratch following the dortania guide(I wanted to boost my mackintosh knowledge).
I am going to see if I can hit 14 days of uptime. If I do, I'll try reenabling the SSDT-USBW.aml and USBWakeFixup.kext and see if the problem reappears.
View attachment 519455
Ok - updated clover and 10.15.7 installed, I'm running, but I have a few issues:
1. Clover says there is a problem in config.plist: Warning Boolean value contained in a string, please use <true/> instead of <string>yes</string>.... I didn't catch all of it, but it ends in Parameters/InjectKexts:679 and says 'use cloverconfigplistvalidator or look in the log.'
I'm guessing perhaps that has something to do with the following:
2. I think it borked my USB 3.1 port on the back of the motherboard.
3. wi-fi is working, but bluetooth has gone offline - it says not available in the top bar, and no information found in system report. I have a FENVI FV-HB1200, that worked perfectly beforehand, including iMessage and so on.
Suggestions on where I should start to fix this?