Kernel panic report, how to solve this？

panic(cpu 0 caller 0xffffff8014d876a2): nvme: "3rd party NVMe controller. Loss of MMIO space. Write. fBuiltIn=1 MODEL=Samsung SSD 970 EVO Plus 500GB FW=2B2QEXM7 CSTS=0xffffffff US[1]=0x0 US[0]=0x2e VID=0x144d DID=0xa808 CRITICAL_WARNING=0x0.\n" @IONVMeController.cpp:6090

Panicked task 0xffffffa78d888670: 200 threads: pid 0: kernel_task

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

I put an EVO 970 SSD a few years ago to my Mac Book Pro mid 2015 and it has been walking very well. But since the update Monterey, which the current one of my Mac, it is running out of a blow and Lorqué 'He turns back on, what does this problem send me how to settle it?

Posted on Nov 20, 2023 8:00 AM

Similar questions

2 replies

MrHoffman

Level 10

158,335 points

Nov 20, 2023 8:35 AM in response to Byu613

The firmware in that NVMe SSD-970 EVO Plus is 2B2QEXM7, which does not appear to be the 4B2QEXM7 current.

https://semiconductor.samsung.com/consumer-storage/support/tools/

https://www.samsung.com/ca/support/memory-storage/update-the-firmware-of-your-samsung-ssd/

Might have to re-replace the NVMe M.2 here though, if the vendor and if that firmware update don’t resolve this.

Nov 20, 2023 8:16 AM in response to Byu613

that panic report points DIRECTLY at third-party drives malfunctioning.

The Samsung EVO drives have a very bad track record when used in Macs.

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 report, how to solve this？