Kernel Panic Nvme

How do I solve the below as I have just replaced the SSD using a third party SSD and it has caused kernel panic for several times whenever it goes to sleep state or inactive for a while.

Below is the Etrecheck report I got.


Diagnostics Information (past 7-30 days):

    2021-10-03 16:14:58 Kernel Panic (7 times)

        Details:

            panic(cpu 2 caller 0xffffff7f9ee3f231): nvme: "Fatal error occurred. C

            STS=0xffffffff US[1]=0x0 US[0]=0x3 VID=0xffff DID=0xffff


    2021-10-03 15:15:06 Cisco WebEx Start.app - Crash (2 times)

        Executable: /Users/***/Library/Application Support/WebEx Folder/*/Cisco WebEx Start.app

        Details: 

            Crashing on exception: Extension context of class NSExtensionContext h

            as not supplied an auxiliary connection host protocol.


    2021-10-02 18:53:07 cloudphotod - High CPU Use

        Executable: /System/Library/PrivateFrameworks/CloudPhotoLibrary.framework/Versions/A/Support/cloudphotod


    2021-10-02 18:09:15 Microsoft Outlook.app - Crash

        Executable: /Applications/Microsoft Outlook.app

        Details: 

            dyld: launch, loading dependent libraries


    2021-10-02 18:04:55 photolibraryd - High CPU Use

        Executable: /System/Library/PrivateFrameworks/PhotoLibraryServices.framework/Versions/A/Support/photolibraryd

MacBook Pro Retina

Posted on Oct 3, 2021 1:42 AM

Reply
Question marked as Top-ranking reply

Posted on Nov 1, 2021 4:36 AM

You are using a drive not officially supported by Apple along with an M.2 NVME Sintech adapter. You might need to change the internal drive to something else not so bleeding edge and / or downgrade to Big Sur until Apple fixes this problem, which may never actually happen as they don't officially support the drive.


Since Apple has been using soldered internal SSDs since 2016 on MacBook Pros with a Touch Bar and since they are changing from Intel to Apple Silicon SoC processors the chances of this being fixed are very low. When Intel based Mac's are 5-7 years old Apple will drop support for Intel entirely. The last MBP's to support upgrading the SSD is the 2015 13" / 15" and the 13" MBP non-Touch Bar (2016-2017). So at best you are looking at about 1-3 years in the best case scenario for a MacBook Pro with a replaceable internal SSD to still be supported by a recent macOS version.


There is a large discussion on MacRumors and several people report similar problems with kernel panics on Monterey with 2013-2015 MBPs. Sounds like a driver problem. Especially if you didn't have a problem before Monterey.


https://forums.macrumors.com/threads/upgrading-2013-2014-macbook-pro-ssd-to-m-2-nvme.2034976/page-386


Others are reporting issues with higher power draw resulting in large battery drains and seeing data errors via DriveDX disk diagnostics. Many with 3rd party SSD's are finding they had to re-install the Apple SSD so macOS Monterey would install a required firmware update that would not work with the 3rd party SSD installed. Then revert back to the 3rd party SSD and quite a few people have experienced kernel panics with the 3rd party SSDs. Apple may or may not decide to fix this problem. You should submit bug report feedback regardless using the Apple Feedback Assistant. https://feedbackassistant.apple.com/


Don't know if Sabrent offers drivers or not but they might not be compatible with Monterey. May require a kernel extension.


FYI, the M1 Pro / Max SSD speeds are incredibly fast, up to 7.5Gbps Read Max. They are also far more energy efficient drawing less power. Real world benchmarks are seeing 6.8Gbps or 6.9Gbs depending on 14" versus 16" as well as the size of the Apple SSD 512GB / 1TB / 2TB / 4TB. Even the M1 MBP/Air is twice the speed of the 2019 MBA.


Best of luck







Similar questions

9 replies
Question marked as Top-ranking reply

Nov 1, 2021 4:36 AM in response to Xaphier

You are using a drive not officially supported by Apple along with an M.2 NVME Sintech adapter. You might need to change the internal drive to something else not so bleeding edge and / or downgrade to Big Sur until Apple fixes this problem, which may never actually happen as they don't officially support the drive.


Since Apple has been using soldered internal SSDs since 2016 on MacBook Pros with a Touch Bar and since they are changing from Intel to Apple Silicon SoC processors the chances of this being fixed are very low. When Intel based Mac's are 5-7 years old Apple will drop support for Intel entirely. The last MBP's to support upgrading the SSD is the 2015 13" / 15" and the 13" MBP non-Touch Bar (2016-2017). So at best you are looking at about 1-3 years in the best case scenario for a MacBook Pro with a replaceable internal SSD to still be supported by a recent macOS version.


There is a large discussion on MacRumors and several people report similar problems with kernel panics on Monterey with 2013-2015 MBPs. Sounds like a driver problem. Especially if you didn't have a problem before Monterey.


https://forums.macrumors.com/threads/upgrading-2013-2014-macbook-pro-ssd-to-m-2-nvme.2034976/page-386


Others are reporting issues with higher power draw resulting in large battery drains and seeing data errors via DriveDX disk diagnostics. Many with 3rd party SSD's are finding they had to re-install the Apple SSD so macOS Monterey would install a required firmware update that would not work with the 3rd party SSD installed. Then revert back to the 3rd party SSD and quite a few people have experienced kernel panics with the 3rd party SSDs. Apple may or may not decide to fix this problem. You should submit bug report feedback regardless using the Apple Feedback Assistant. https://feedbackassistant.apple.com/


Don't know if Sabrent offers drivers or not but they might not be compatible with Monterey. May require a kernel extension.


FYI, the M1 Pro / Max SSD speeds are incredibly fast, up to 7.5Gbps Read Max. They are also far more energy efficient drawing less power. Real world benchmarks are seeing 6.8Gbps or 6.9Gbs depending on 14" versus 16" as well as the size of the Apple SSD 512GB / 1TB / 2TB / 4TB. Even the M1 MBP/Air is twice the speed of the 2019 MBA.


Best of luck







Oct 6, 2021 11:58 AM in response to ezrang

Most likely it is a compatibility issue with the SSD Adapter if you are using a standard M.2 SSD. It seems the most compatible adapter is from Sintech according to the forum posts I've seen here. If you are using a SSD made for an Apple laptop such as from one from OWC, then contact their tech support team for assistance.


There is also a chance you could have an issue with some installed third party software such as an anti-virus app, cleaning app, or third party security software that is interfering with the SSD's NVMe driver.

Nov 28, 2021 8:27 AM in response to rohitbatra14

This looks like an NVMe failure. You are using a 3rd party SSD, so it is possible it does not meet the specs that Apple needs for their Macs.


Maybe check with your SSD vendor.


You should also try an SMC reset and an NVRAM reset

Reset the System Management Controller (SMC) on your Mac - Apple Support

How to reset NVRAM on your Mac - Apple Support

I do not think they will help, but they will not hurt.

Oct 6, 2021 12:41 PM in response to ezrang

Please post one or more panic reports

Finder -> Go (menu) -> Go to folder -> /Library/Logs/DiagnosticReports


Command-Shift-Period will show invisible files. Look for files that end in the word .panic or .contents.panic and post them in an Additional Text box


Press Command-Shift-Period to hid the Finder invisible files again.



NOTE: without seeing the panic report, I am leaning towards HWTech's answer, that this is a hardware issue.

Oct 31, 2021 10:19 PM in response to ezrang

I have the exact same issue, am using Sabrent Rocket 1TB NVME with Sintech adapter, and getting many crashes after upgrading to Monterey. No issue with Big Sur or Catalina for the past 3 years.


panic(cpu 0
caller 0xffffff8016542836): nvme: "3rd party NVMe controller. Loss of MMIO
space. Write. fBuiltIn=1 MODEL=Sabrent FW=ECFM12.2 CSTS=0xffffffff US[1]=0x0
US[0]=0x5a VID=0x1987 DID=0x5012 CRITICAL_WARNING=0x0.\n"
@IONVMeController.cpp:6053



This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Kernel Panic Nvme

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.