Frequent Kernel Panic

Question

Level 1

47 points

Frequent Kernel Panic

I get frequent (once per week) kernel panic on my MacBook Pro (15-inch, 2017) running 10.14.2. Below is the excerpt from 2 recent crashes. Any pointers would be appreciated.

Panic #1

----

*** Panic Report ***

panic(cpu 0 caller 0xffffff7f868fa172): nvme: "Fatal error occurred. CSTS=0xffffffff US[1]=0x0 US[0]=0x149 VID/DID=0xa804144d

. FW Revision=CXS5EA0Q\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-387.230.1/IONVMeController.cpp:5327

Backtrace (CPU 0), Frame : Return Address

0xffffff922f15ba10 : 0xffffff8002daeafd

0xffffff922f15ba60 : 0xffffff8002ee85a3

0xffffff922f15baa0 : 0xffffff8002ed9fca

0xffffff922f15bb10 : 0xffffff8002d5bca0

0xffffff922f15bb30 : 0xffffff8002dae517

0xffffff922f15bc50 : 0xffffff8002dae363

0xffffff922f15bcc0 : 0xffffff7f868fa172

0xffffff922f15be20 : 0xffffff800345dd87

0xffffff922f15be90 : 0xffffff800345dca9

0xffffff922f15bec0 : 0xffffff8002deaf65

0xffffff922f15bf40 : 0xffffff8002deab15

0xffffff922f15bfa0 : 0xffffff8002d5b0ce

Kernel Extensions in backtrace:

com.apple.iokit.IONVMeFamily(2.1)[E3F646E0-5B0C-3ABC-88D1-728309F221C8]@0xffffff7f868e5000->0xffffff7f86924fff

dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A69BF990-ABB3-3731-A7A2-9C1FB76BCF6F]@0xffffff7f83d4c000

dependency: com.apple.iokit.IOPCIFamily(2.9)[7EA30FDD-A2FB-390F-99DD-42BC19691BB4]@0xffffff7f83695000

dependency: com.apple.driver.AppleEFINVRAM(2.1)[E68F9756-227E-3378-8E22-F37409594A7F]@0xffffff7f83f22000

dependency: com.apple.iokit.IOStorageFamily(2.1)[7D6A3E9B-D1CD-3F8B-9800-C4B943806679]@0xffffff7f83b47000

dependency: com.apple.iokit.IOReportFamily(47)[75A625B5-0DEB-343A-A723-9D72533F098C]@0xffffff7f846cc000

BSD process name corresponding to current thread: kernel_task

Mac OS version:

18C54

Kernel version:

Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:46 PST 2018; root:xnu-4903.231.4~2/RELEASE_X86_64

Kernel UUID: 56B30885-F9BA-30E8-AD1C-5D59EC243BA9

Kernel slide: 0x0000000002a00000

Kernel text base: 0xffffff8002c00000

__HIB text base: 0xffffff8002b00000

System model name: MacBookPro14,3 (Mac-551B86E5744E2388)

System uptime in nanoseconds: 253885703605585

last loaded kext at 245906530579001: com.apple.driver.AppleXsanScheme 3 (addr 0xffffff7f89df2000, size 32768)

last unloaded kext at 244523841202240: com.apple.driver.AppleUSBAudio 315.6 (addr 0xffffff7f89d72000, size 413696)

loaded kexts:

com.paragon-software.filesystems.ntfs 11.4.15

at.obdev.nke.LittleSnitch 5210

com.apple.filesystems.smbfs 3.3.1

....

-----------------------

Panic #2:

----

*** Panic Report ***

panic(cpu 0 caller 0xffffff7f85918172): nvme: "Fatal error occurred. CSTS=0xffffffff US[1]=0x0 US[0]=0x149 VID/DID=0xffffffff

. FW Revision=CXS5EA0Q\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-387.230.1/IONVMeController.cpp:5327

Backtrace (CPU 0), Frame : Return Address

0xffffff81f3413a10 : 0xffffff80039aeafd

0xffffff81f3413a60 : 0xffffff8003ae85a3

0xffffff81f3413aa0 : 0xffffff8003ad9fca

0xffffff81f3413b10 : 0xffffff800395bca0

0xffffff81f3413b30 : 0xffffff80039ae517

0xffffff81f3413c50 : 0xffffff80039ae363

0xffffff81f3413cc0 : 0xffffff7f85918172

0xffffff81f3413e20 : 0xffffff800405dd87

0xffffff81f3413e90 : 0xffffff800405dca9

0xffffff81f3413ec0 : 0xffffff80039eaf65

0xffffff81f3413f40 : 0xffffff80039eab15

0xffffff81f3413fa0 : 0xffffff800395b0ce

Kernel Extensions in backtrace:

com.apple.iokit.IONVMeFamily(2.1)[E3F646E0-5B0C-3ABC-88D1-728309F221C8]@0xffffff7f85903000->0xffffff7f85942fff

dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A69BF990-ABB3-3731-A7A2-9C1FB76BCF6F]@0xffffff7f8489e000

dependency: com.apple.iokit.IOPCIFamily(2.9)[7EA30FDD-A2FB-390F-99DD-42BC19691BB4]@0xffffff7f84295000

dependency: com.apple.driver.AppleEFINVRAM(2.1)[E68F9756-227E-3378-8E22-F37409594A7F]@0xffffff7f84a74000

dependency: com.apple.iokit.IOStorageFamily(2.1)[7D6A3E9B-D1CD-3F8B-9800-C4B943806679]@0xffffff7f84704000

dependency: com.apple.iokit.IOReportFamily(47)[75A625B5-0DEB-343A-A723-9D72533F098C]@0xffffff7f84e10000

BSD process name corresponding to current thread: kernel_task

Mac OS version:

18C54

Kernel version:

Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:46 PST 2018; root:xnu-4903.231.4~2/RELEASE_X86_64

Kernel UUID: 56B30885-F9BA-30E8-AD1C-5D59EC243BA9

Kernel slide: 0x0000000003600000

Kernel text base: 0xffffff8003800000

__HIB text base: 0xffffff8003700000

System model name: MacBookPro14,3 (Mac-551B86E5744E2388)

System uptime in nanoseconds: 8748312472538

last loaded kext at 2317912341700: com.apple.driver.AppleXsanScheme 3 (addr 0xffffff7f86eb4000, size 32768)

last unloaded kext at 3857571767387: com.apple.driver.AppleUSBAudio 315.6 (addr 0xffffff7f86abf000, size 413696)

loaded kexts:

com.paragon-software.filesystems.ntfs 11.4.15

.....

Posted on Dec 16, 2018 9:01 PM

Reply

Answer 1

JJTOKC

Level 1

4 points

Feb 6, 2019 8:48 AM in response to tcol1234

Apple Support determined that my solid state drive was failing. I had to replace it.

Reply

Answer 2

Jan 30, 2019 1:22 PM in response to FortKnUX

There is a Service program in progress, but at this writing, it only applies to a limited set of serial numbers in the MacBook pro 13-in models:

Apple has determined that a limited number of 128GB and 256GB solid-state drives (SSD) used in 13-inch MacBook Pro (non Touch Bar) units have an issue that may result in data loss and failure of the drive. 13-inch MacBook Pro units with affected drives were sold between June 2017 and June 2018.

13-inch MacBook Pro (non Touch Bar) Solid-State Drive Service Program - Apple Support

.

Reply

Answer 3

dwhitla

Level 1

20 points

Apr 1, 2019 4:01 AM in response to FortKnUX

I doubt this is a hardware issue. There have been numerous issues with the NVMe driver just crapping out. I recently upgraded my Macbook Pro 11,3 1TB Apple SSD to an OWC Aura Pro X 2TB NVMe SSD and couldn't successfully complete Migration Assistant at the end of a clean Mojave install. Tried 6 times - 6 kernel panics in the NVMe driver.

Any time I try to transfer a large block of data from a fast external device - eg the old 1TB SSD in a USB enclosure - I get a kernel panic. If the laptop goes to sleep while connected to power half the time it kernel panics - in the NVMe driver.

I swapped out the NVMe SSD for a replacement. Same problem. Now I see this is happening to Macs with factory Apple NVMe SSDs also so blaming OWC seems a stretch. I suspect the NVMe driver just performs some unsafe write operation under high load that corrupts data and it crashes.

Reply

Answer 4

dwhitla

Level 1

20 points

Apr 1, 2019 7:13 AM in response to Grant Bennet-Alder

I have contacted them and they are trying to assist, but your assertion that my situation has nothing in common with the previous posters is plainly false. We all use NVMe (as opposed to ACPI) SSDs and all have started to regularly experience kernel panics at exactly the same point in the NVMe driver.

Reply

Answer 5

JJTOKC

Level 1

4 points

Jan 9, 2019 7:31 AM in response to FortKnUX

I have been having the exact same problem for the past two weeks, with the same kernel panic message. I also have a MacBook Pro (15-inch, 2016). I am in contact with Apple Support and hope to resolve this as soon as possible.

Reply

Answer 6

yao48

Level 1

4 points

Jan 30, 2019 12:27 PM in response to JJTOKC

I also had the same problem with my MacBook Pro 15 2016. it happens every now and then, but I did not find any patterns. When I restart, I saw a question mark blinking on the folder icon. Took it to Apple when it is still under warranty, but cannot reproduce the problem at apple store so they did not repair it. I had to take it back and the problem still exists.

VERY DISAPPOINTED TO THE NEW MacBook Pro

Reply

Answer 7

yao48

Level 1

4 points

Feb 6, 2019 8:54 AM in response to JJTOKC

That's too bad, do you have a warranty or how much does it cost?

I took it to Apple store when the Mac is still under warranty and they told me there is no hardware issues. Now it seems that I have to change it and paying them extra money.

Reply

Answer 8

Dec 18, 2018 7:28 AM in response to FortKnUX

Little snitch does not have a reputation for being benign. You should try running without it.

*** Panic Report ***

panic(cpu 0 [...]): nvme: "Fatal error occurred. CSTS=0xffffffff [...]

NVME is the new drive type and Boot drive interface used in these and some other new Macs. it has not been troublesome, and I have not seen a panic report for this reason posted here.

You should at least use Disk Utility to repair your drive, and watch for any additional drive problems. As I understand it, the Drive Controller is implemented inside the Apple custom T2 chip, so any identity or encryption problems are worth watching as well.

A Trusted Backup is essential to have on hand in this situation. I expect you have that covered, but if you need advice, just ask and Readers will be happy to help with that as well.

Reply

Answer 9

tcol1234

Level 1

4 points

Feb 6, 2019 8:40 AM in response to Grant Bennet-Alder

I've been having this exact problem periodically on a 15 inch MacBook Pro 2017. Any fixes for that?????

Reply

Answer 10

FortKnUX Author

Level 1

47 points

Dec 18, 2018 8:37 AM in response to Grant Bennet-Alder

Thanks Grant, did DU repair couple of times, no errors, with the last message: "The drives appears to be Ok"

I will uninstall Little Snitch and see if the problem continues. I had this issue pretty much since I got it, just a sporadic NVME "panic" reboot once in a while but lately almost weekly. Had an infamous popcorn pop sound coming from the laptop last summer, Apple replaced the display to fix that, but no faults were found on the other parts of hardware.

Reply

Answer 11

kaz-k

Level 9

51,084 points

Dec 17, 2018 8:59 PM in response to FortKnUX

Hi,

I suppose your MacBook Pro has hardware related problem. Try to check with Apple Diagnostics if it reports something.

https://support.apple.com/en-us/HT202731

Reply

Answer 12

JJTOKC

Level 1

4 points

Feb 6, 2019 8:58 AM in response to yao48

Mine was under warranty. Otherwise, I believe the repair would have been around $800.

Apple Support diagnosed the problem online, and they did so by capturing a sample of my computer's activity and then sending it to the "Engineers" for review.

Incidentally, because I cannot work without my computer for even one day I bought a second MacBook as a backup.

Good luck!

Reply

Answer 13

RNBR

Level 1

11 points

Mar 6, 2019 12:17 PM in response to FortKnUX

My macbook 12 (2017) started with this same issue 2 weeks ago. Trying to solve with Apple support but it looks like a hardware issue. Clean install (Sierra or Mojave) and still happening. My macbook is 18 months old without any drop or scratch. No warranty in my case and a little boring that maybe I have to pay for this kind of problem. Missing old Macbook Pro where you can change HD/SSD or RAM when necessary... nowadays with all parts welded is so expensive to change motherboard.... 1st time in 10 year I have serious issue with Apple products... maybe next one will have Apple Care plan...

Reply

Answer 14

Apr 1, 2019 5:18 AM in response to dwhitla

dwhitla-

Your situation appears to have Nothing in common with the previous posters on this thread. Their MacBook pros do not have a replaceable SSD part -- they are all soldered to the mainboard.

In your case, you should contact OWC for more help. They pride themselves on their support.

Reply

Answer 15

FortKnUX Author

Level 1

47 points

Dec 18, 2018 6:58 AM in response to kaz-k

thanks Kaz-k. Did that, all clean, no issues reported.

Reply