***Solved***Crash on Big Sur 11.3

[Bishan]

Hi everyone.
I have a PC with the following configuration:
MB: Gigabyte W480 Vision D
CPU: Intel 10900K
GPU: Asus ROG RX 5700XT 8GB
RAM: 2 x 32GB memory
NVMe: 2 x 1TB Samsung 970 Evo Plus and 1 x 1TB Samsung Evo
Wifi and BT: BCM94360CS2 mounted via a PCIe WiFi Card to PCI-Ex1

This system has been running stable with hardly any issue since Big Sur. Updates have been pretty smooth. OC and kexts are updated every month.

However, since the release of 11.3, things are very different. After an initial somewhat weird update, the system became almost unusable. I had to hard restart the PC because it got stuck midway through the installation. Afterwards, I kept getting crashes some 60s to 180s after every login. All the crashes produce the same kind of report.

** Panic Report ***
panic(cpu 0 caller 0xffffff8021cc2838): nvme: "Fatal error occurred. CSTS=0x3 US[1]=0x0 US[0]=0x102 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
0xffffffa1b965b960 : 0xffffff801f48e02d mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa1b965b9b0 : 0xffffff801f5d48e3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa1b965b9f0 : 0xffffff801f5c4eda mach_kernel : _kernel_trap + 0x55a
0xffffffa1b965ba40 : 0xffffff801f432a2f mach_kernel : _return_from_trap + 0xff
0xffffffa1b965ba60 : 0xffffff801f48d84d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa1b965bb80 : 0xffffff801f48db43 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa1b965bbf0 : 0xffffff801fc9d68a mach_kernel : _panic + 0x54
0xffffffa1b965bc60 : 0xffffff8021cc2838 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController14CommandTimeoutEP16AppleNVMeRequest.cold.1
0xffffffa1b965bc80 : 0xffffff8021ca7433 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController13FatalHandlingEv + 0x1af
0xffffffa1b965bde0 : 0xffffff801fbf54f5 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5
0xffffffa1b965be50 : 0xffffff801fbf53f6 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc6
0xffffffa1b965be80 : 0xffffff801f4d44b5 mach_kernel : _thread_call_delayed_timer + 0x4a5
0xffffffa1b965bef0 : 0xffffff801f4d5424 mach_kernel : _thread_call_delayed_timer + 0x1414
0xffffffa1b965bfa0 : 0xffffff801f43213e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[2A44DC48-B629-386C-985E-3BE03CCA48F2]@0xffffff8021ca0000->0xffffff8021cc9fff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[C6EE02AA-79D2-3EF8-83A6-9E52549E16D9]@0xffffff80208fe000->0xffffff8020907fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[2D13AEBE-3C77-3EE0-BC06-BDED7FE19FDE]@0xffffff8020ab8000->0xffffff8020acdfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[29933CED-5D05-36A4-BFA1-6F4B4F349283]@0xffffff8021f5f000->0xffffff8021f87fff
dependency: com.apple.iokit.IOReportFamily(47)[3F7604AB-EA65-3904-A1F4-AFEB25D288A7]@0xffffff8021f96000->0xffffff8021f98fff
dependency: com.apple.iokit.IOStorageFamily(2.1)[58EA4506-4E6B-3AC3-A70D-ED35EE2C381D]@0xffffff8022062000->0xffffff8022073fff

Process name corresponding to current thread: kernel_task
Boot args: debug=0x100 keepsyms=1 alcid=1 agdpmod=pikera shikigva=80 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20E232

Kernel version:
Darwin Kernel Version 20.4.0: Fri Mar 5 01:14:14 PST 2021; root:xnu-7195.101.1~3/RELEASE_X86_64
Kernel UUID: BB2FFEBA-7D53-301F-A238-9867CA51276F
KernelCache slide: 0x000000001f200000
KernelCache base: 0xffffff801f400000
Kernel slide: 0x000000001f210000
Kernel text base: 0xffffff801f410000
__HIB text base: 0xffffff801f300000
System model name: iMac20,2 (Mac-AF89B6D9451A490B)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 215435631094
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000003228f6e189
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000014c0240f84 0x0000000000000000

Correct me if I am wrong but looking at the report, it appears that something is not OK with the NVMe. However, the system was very stable with Big Sur 11.2.3. Has anyone had Big Sur 11.3 successfully installed and running properly on a hack with Samsung 970 Evo Plus? The NVMes have the latest firmware.

I thought that maybe something went wrong when I had to do the manual reset during the installation. So I tried a clean install. I also have the same crash 60s to 180s into the installation program!


I appreciate any and all advice.
Thank you very much!

 

[Bishan]

I cleared the CMOS of the motherboard by shorting the appropriate jumper, loaded the default BIOS settings and reconfigured BIOS for a Hackintosh. Upgraded to 11.3.1 from 11.2.3 with a full install image downloaded from the App Store and after some 45 minutes, the upgrade was completed.