macOS 11+ restarts unpredictably #171
Comments
|
@samwzlim Try to unload |
Will try the next time I encounter a crash again, macOS is running smoothly at the moment. |
|
@profzei To unload the kext, I just remove it from the Kexts folder in the EFI right? |
|
No, you only need to put value |
|
@profzei believe this issue is related to #142. I tried unloading |
|
@samwzlim I've had the same issue recently for the last 3 months or so, to the point that I almost considered changing the ssd from my MBXPro to solve this issue. It happened all the time. In a desperate move I tried to clean the SSD, meaning opened the MBXPro and cleaned with alcohol the SSD contacts and It has solved the issue for about one week. I do not know if you had issues with both Windows and Mac, because in my case I had the issue with both. I hope this helps. |
|
@mmenendezg However @mmenendezg @samwzlim ...digging a little more this issue seems to be related to some incompatibility with some NVMe SSDs: @mmenendezg could you remember me what's your SSD? Please report here your feedback! |
|
I've had the same issue. my ssd is WDS500G3X0C-00SJG0 , SN750。 |
|
@profzei |
|
@myselfghost I found only one reference for this issue (not related to this config...) and I posted it above... I could only suggest to unload Btw, could you confirm, please, that your installation is on an internal SSD (i.e. no external enclosure was used)? |
|
I've had this problem with both Intel 660p (not 600, which is on the possibly problematic list) and in the last few days with a WD SN750 2TB NVMe also. I've done a new install on a SATA SSD and am running happy again, but I know I'll eventually miss NVMe. I don't know what model to buy to try again though honestly. |
I also use SN750. The strange thing is that there have been problems recently, and there have been no problems some time ago. |
Is internal SSD |
|
I dont have these problems. |
That's interesting. Do we think that might mean it's TRIM related? |
If it could be |
According to the note about that feature, it shouldn't be an issue, yeah? "Note: This option may be avoided on user preference. NVMe SSDs are compatible without the change. For AHCI SSDs on modern macOS version there is a dedicated built-in utility called trimforce. Starting from 10.15 this utility creates EnableTRIM variable in APPLE_BOOT_VARIABLE_GUID namespace with 01 00 00 00 value." The whole thing is so frustrating. I'd used that 660p for a long time before this cropped up at some point in the Big Sur releases. |
It's the reason I never enabled it before... since we have internal NVMe SSDs, but, in other project, I have turned this quirk on since I have 1 NVMe and 1 AHCI SSD and in the last months I didn't have any issues... (maybe I'm just lucky!) |
|
Well I am desperate and will try anything so why not right? |
|
Is there any chance that PowerTimeoutKernelPanic is related? That’s also there in Kernel > Quirks |
I don't know since the quirk you mentioned should be related to Catalina and not to Catalina+ |
|
Sounds good - thx My migration off the SATA SSD is complete and I'm up and running on the SN750 2TB NVMe with BigSur 11.4 with OC 0.7.1 and both the ThirdPartyDrives quirk enabled as well as the forceRenderStandby=0 boot flag. Fingers crossed. |
@blodt Ok! Btw, since you mentioned that you installed Big Sur 11.4, did you use latest EFI (i.e. |
You mean that latest OpenCore 0.7.1? If you mean the latest OC 0.7.1 in the EFI, yes I did I tested out the OC upgrade on my BigSur 11.4 Installation USB Stick first (usual OC update procedure) before copying it over to the EFI on the SATA SSD with my BigSur 11.4 installation on it... Then I unplugged everything but the NVMe and the USB stick to do a full fresh 11.4 install with OC 0.7.1 that just released. |
|
Anyone have any ideas on how to stress test this problem? Since I did a fresh install, I'm worried I'll think "everything is fine" and then a couple weeks from now...."it will be back..." It's in my head now. I just don't trust this NVMe situation anymore. |
Oh - No! I only am here due to the similarity of the NVMe kernel panic |
@blodt Ok! |
I face exactly the same issues, in my case it's is a Samsung 980 NVME ssd running on Z370N-Wifi Hackintosh. |
I have the exact same Motherboard as you. Interesting. Something is up for sure. What BIOS version are you running your MoBo on? I had always been on F10 forever. |
|
Maybe I found a way to circumvent the problem. do not mount windows Volume |
I am on F14a BIOS firmware. Actually my hack was working very well for a couple of months with WD SN550. Kernel panic happen after I updated from 11.2.3 to 11.4. First I thought something goes wrong with 11.4 so I decided to downgrade to 11.1, but the panic still there. And as you see, problems can not be solved even when I changed the SSD :( |
Please do explain! I do run dual boot on my Hack (each on its own drive). Do you think it's related or part of the issue? |
Hi, Have you checked "rc6 render standby" option in BIOS settings. I have it enabled, I read from https://dortania.github.io/OpenCore-Post-Install/universal/sleep.html#:~:text=IGP%20causes%20NVMe,opens%20new%20window) so I switch it to disabled state. the panic was gone for 2 days, its amazing! |
Hi I saw that also, yeah. It is currently enabled in my BIOS, but I believe the forceRenderStandby=0 boot flag is disabling that on macOS boot up (I am using that boot flag). Any idea how relevant (or not) rc6 is for the Windows side? |
|
@blodt I think the setting in bios is valid for both window and macos. |
|
I consider closed this issue... Official fix is the following: adding If this issue shouldn't be fixed then, please, refer to IGP causes NVMe Kernel Panic CSTS=0xffffffff for debugging purposes. |
EFI version: 2.3.0 (latest at the time of writing this)
macOS version: 11.5 beta
Occasionally, macOS will restart randomly during usage or idling. This is the error report when macOS restarts:
panic(cpu 0 caller 0xffffff8010cd0860): nvme: "Fatal error occurred. CSTS=0xffffffff US[1]=0x0 US[0]=0xd5 VID=0x1179 DID=0x116
. FW Revision=AAXA4103\n"@/System/Volumes/Data/SWE/macOS/BuildRoots/ad62260af4/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.120.1/Common/IONVMeController.cpp:5499
Backtrace (CPU 0), Frame : Return Address
0xffffffb094d8b960 : 0xffffff800e48d04d
0xffffffb094d8b9b0 : 0xffffff800e5d3f63
0xffffffb094d8b9f0 : 0xffffff800e5c455a
0xffffffb094d8ba40 : 0xffffff800e431a2f
0xffffffb094d8ba60 : 0xffffff800e48c86d
0xffffffb094d8bb80 : 0xffffff800e48cb63
0xffffffb094d8bbf0 : 0xffffff800ec9c8fa
0xffffffb094d8bc60 : 0xffffff8010cd0860
0xffffffb094d8bc80 : 0xffffff8010cb545b
0xffffffb094d8bde0 : 0xffffff800ebf34d5
0xffffffb094d8be50 : 0xffffff800ebf33d6
0xffffffb094d8be80 : 0xffffff800e4d3675
0xffffffb094d8bef0 : 0xffffff800e4d45e4
0xffffffb094d8bfa0 : 0xffffff800e43113e
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[8D47DA90-79B7-33A8-B5C9-DFD9B708CFA4]@0xffffff8010cae000->0xffffff8010cd7fff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[26D83939-D2C2-3B4E-A268-0DA7B01B187E]@0xffffff800f8fe000->0xffffff800f907fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[52E40A68-70FA-3782-9595-8D99527B837C]@0xffffff800fac0000->0xffffff800fad5fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[395E932C-57ED-368F-B673-DD261C7761A5]@0xffffff8010f6c000->0xffffff8010f94fff
dependency: com.apple.iokit.IOReportFamily(47)[A5283FFC-0B0C-3409-A86B-0CBFBF53D863]@0xffffff8010fa3000->0xffffff8010fa5fff
dependency: com.apple.iokit.IOStorageFamily(2.1)[3DE94082-367D-3255-9BE7-7F5A87838247]@0xffffff801106f000->0xffffff8011080fff
Process name corresponding to current thread: kernel_task
Boot args: igfxrpsc=1
Mac OS version:
20G5033c
Kernel version:
Darwin Kernel Version 20.6.0: Mon May 24 00:50:08 PDT 2021; root:xnu-7195.140.22~21/RELEASE_X86_64
Kernel UUID: 331AAB1E-6B00-3159-B97F-4AD6FE3D7A31
KernelCache slide: 0x000000000e200000
KernelCache base: 0xffffff800e400000
Kernel slide: 0x000000000e210000
Kernel text base: 0xffffff800e410000
__HIB text base: 0xffffff800e300000
System model name: MacBookPro16,3 (Mac-E7203C0F68AA0004)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0
System uptime in nanoseconds: 3435443454743
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000031fe0630929
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000000d9f0bbe24 0x0000000000000000
The text was updated successfully, but these errors were encountered: