panic(cpu 1 caller 0xffffff801be2581e)

panic(cpu 1 caller 0xffffff801be2581e): nvme: "AppleS3XController. PCI link down. Write. ID=0xffffffff ARG1=0xffffffff ARG2=0xffffffff ARG3=0xffffffff EDD0=0xffffffff EDD1=0xffffffff EDD2=0xffffffff EDD3=0xffffffff EDD4=0xffffffff EDD5=0xffffffff EDD6=0xffffffff EDD7=0xffffffff NANDV=0x2, DRAMV=0x1, SSDC=256G.\n" @IONVMeController.cpp:6147

Panicked task 0xffffff9bb39eae18: 162 threads: pid 0: kernel_task

Backtrace (CPU 1), panicked thread: 0xffffffa07fd1ab30, Frame : Return Address

0xfffffffef875fab0 : 0xffffff8019670c7d

0xfffffffef875fb00 : 0xffffff80197c5294

0xfffffffef875fb40 : 0xffffff80197b4da7

0xfffffffef875fb90 : 0xffffff8019611971

0xfffffffef875fbb0 : 0xffffff8019670f5d

0xfffffffef875fca0 : 0xffffff8019670607

0xfffffffef875fd00 : 0xffffff8019ddb8eb

0xfffffffef875fdf0 : 0xffffff801be2581e

0xfffffffef875fe20 : 0xffffff8019d19196

0xfffffffef875fe70 : 0xffffff8019d190a6

0xfffffffef875fea0 : 0xffffff80196c6e28

0xfffffffef875fee0 : 0xffffff80196c7eb8

0xfffffffef875ffa0 : 0xffffff801961119e

Kernel Extensions in backtrace:

com.apple.iokit.IONVMeFamily(2.1)[E85F403D-E6C2-3039-BF07-C7B0416E9CC9]@0xffffff801be1d000->0xffffff801be49fff

dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[2C4E071D-42C7-3601-AD40-07F2C05EA45C]@0xffffff801ac05000->0xffffff801ac38fff

dependency: com.apple.iokit.IOPCIFamily(2.9)[05751018-D5D6-39CE-9F45-B2652D5B9E94]@0xffffff801c0b5000->0xffffff801c0e6fff

dependency: com.apple.iokit.IOReportFamily(47)[491DDA55-D371-3A28-9A77-C28DB013D8AE]@0xffffff801c0f7000->0xffffff801c0f9fff

dependency: com.apple.iokit.IOStorageFamily(2.1)[70B6B0B8-8059-3529-A544-D33C65534409]@0xffffff801c1ea000->0xffffff801c201fff


Process name corresponding to current thread (0xffffffa07fd1ab30): kernel_task


Mac OS version:

22G720



MacBook Pro 13″, macOS 13.6

Posted on Jul 18, 2024 4:44 PM

Reply
Question marked as Top-ranking reply

Posted on Jul 18, 2024 8:13 PM

Most likely the SSD is failing....all things being equal the SSD is the weakest link assuming there is no liquid damage. This also happens most often on the MacBook Pro 13" 2016 & 2017 models with just two USB-C ports as that SSD has a very high rate of failure (Apple even had a free repair program that has expired).


I hope you have a good backup since the SSD could fail completely at any time.....this Kernel Panic has been your warning.


FYI, this SSD failure typically occurs when powering on the laptop or when waking from sleep. The SSD has trouble going ready. You may be able to boot the laptop by holding the Option key immediately after hearing the startup chime (Intel Macs only) which may give the SSD a bit more time to go ready so you can boot from it.


People should always have frequent and regular backups. This is even more important than ever before since there are a lot more new ways to permanently lose access to the data on the internal SSD due to all the hardware, software, and security changes.

Similar questions

2 replies
Question marked as Top-ranking reply

Jul 18, 2024 8:13 PM in response to Mahdi3355

Most likely the SSD is failing....all things being equal the SSD is the weakest link assuming there is no liquid damage. This also happens most often on the MacBook Pro 13" 2016 & 2017 models with just two USB-C ports as that SSD has a very high rate of failure (Apple even had a free repair program that has expired).


I hope you have a good backup since the SSD could fail completely at any time.....this Kernel Panic has been your warning.


FYI, this SSD failure typically occurs when powering on the laptop or when waking from sleep. The SSD has trouble going ready. You may be able to boot the laptop by holding the Option key immediately after hearing the startup chime (Intel Macs only) which may give the SSD a bit more time to go ready so you can boot from it.


People should always have frequent and regular backups. This is even more important than ever before since there are a lot more new ways to permanently lose access to the data on the internal SSD due to all the hardware, software, and security changes.

Jul 18, 2024 5:08 PM in response to Mahdi3355

Hi,

It seems your MacBook SSD controller related hardware issue. If the kernel Panic occurs frequently, you'd better take your MacBook Pro to your local retail AppleStore, Genius Bar or Apple Authorized Service Provider to be examined your MacBook Pro there, though try to run Apple Diagnostics if it reports SSD related error before go to AppleStore.

Use Apple Diagnostics to test your Mac - Apple Support

Genius Bar Reservation and Apple Support Options - Apple

Find Locations


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.

panic(cpu 1 caller 0xffffff801be2581e)

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