kernel panic

I have a same problem too. Mine is also 12 inch MacBook early 2016.

I have disappointed. I didn't do anything wrong.

In addition, Mac cleaner apps said there are malware called OSX.Robsnap.A which is under pathway of Prey. since then I deleted prey.

but today, in my CONSOLE log it shows like that: I am fear!

Farcus5--

I am pretty sure I suggested you install (at least temporarily) High Sierra 10.13.6 on an external drive, and that was very deliberate.

10.13.6 is a requirement for similar Macs to introduce those firmware updates, as described in this article:

Install macOS 10.14 Mojave on Mac Pro (Mid 2010) and Mac Pro (Mid 2012) - Apple Support

The firmware update may not be supplied in 10.14. If you continue to have problems, that would still be my recommendation..

exactly which model MacBook Pro 13-in. If the 2017 model-year "two ThunderBolt, no Touchbar" model, see this:

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

.

There is no SSD recall available for the 15-in models.

It's not the same issue unless your panic report looks EXACTLY the same as the one posted. Please post the entire panic report. Use the "Additional text" Icon on the forum (looks like a page with paragraphs).

It would be better still if you started a NEW discussion and posted it there, so readers (who read a lot of different discussions every day) don't get confused about whose is whose.

In stark contrast to most users who say, "I have the same problem", you appear to have the same or a very similar problem with your nVME device, the boot drive.

There is no published recall program for your 15-in MacBook Pro 2017 model computer. be sure to ask if there is a Service Bulletin (similar to that other recall, but not published).

The components representing the SSD drive are soldered to the mainboard. If you present your Mac for service, it is unlikely to return to you with ANY of your data on board -- they will likely swap the mainboard including the drive.

NB>> be certain to make at least one backup, and ideally two by different methods.

I Have a Macbook 12 (2017) I have the same issue (below). It happened in February and Apple support can figure it out. To reinstall Mojave (via internet boot) it still crashing all time. Then one day I installed and the problem disappear until this week. Only yesterday 17 panic killer events... I will probably need to buy a new macbook... Very disappointed as a Apple user. My macbook look like new (no drops, scratches, etc).

Fri Jun 28 12:49:44 2019

*** Panic Report ***

panic(cpu 0 caller 0xffffff7f8db9ac0c): nvme: "Fatal error occurred. ID=0x843 ARG1=0xa53e ARG2=0x5d ARG3=0xdd EDD0=0x0 EDD1=0x0 EDD2=0x0 EDD3=0x0 EDD4=0x0 EDD5=0x0 EDD6=0x0 EDD7=0x0 NANDV=0x2, DRAMV=0x2, SSDC=256GB. FW Revision=16.14.01\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-387.260.15/IONVMeController.cpp:5334

Backtrace (CPU 0), Frame : Return Address

0xffffff912a7a3a10 : 0xffffff800abaea2d

0xffffff912a7a3a60 : 0xffffff800ace9e95

0xffffff912a7a3aa0 : 0xffffff800acdb70a

0xffffff912a7a3b10 : 0xffffff800ab5bb40

0xffffff912a7a3b30 : 0xffffff800abae447

0xffffff912a7a3c50 : 0xffffff800abae293

0xffffff912a7a3cc0 : 0xffffff7f8db9ac0c

0xffffff912a7a3e20 : 0xffffff800b25e877

0xffffff912a7a3e90 : 0xffffff800b25e799

0xffffff912a7a3ec0 : 0xffffff800abed9b5

0xffffff912a7a3f40 : 0xffffff800abed555

0xffffff912a7a3fa0 : 0xffffff800ab5b0ce

Kernel Extensions in backtrace:

com.apple.iokit.IONVMeFamily(2.1)[FAFF8EA6-B8EF-314D-886A-DEAB39FF3EA9]@0xffffff7f8db8d000->0xffffff7f8dbccfff

dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A367CF6B-B3EA-36FE-86E6-03B771CA8A69]@0xffffff7f8b988000

dependency: com.apple.iokit.IOPCIFamily(2.9)[CC6A465F-5A24-304D-B9DF-8C27819CC214]@0xffffff7f8b495000

dependency: com.apple.driver.AppleEFINVRAM(2.1)[C3C74D36-E06B-3753-A373-5BC9D486DD9C]@0xffffff7f8bb5e000

dependency: com.apple.iokit.IOStorageFamily(2.1)[D43332F2-2D40-3DF1-8F77-D633BCDAE660]@0xffffff7f8b77e000

dependency: com.apple.iokit.IOReportFamily(47)[5772C11C-ED28-322A-910F-874583B23101]@0xffffff7f8c0b3000

I have the same problem with a re-manufactured Mac Pro from OtherWorldComputing (10-core xeon with 2xAMD FirePro D500, 64 GB RAM) - the system doesn't crash completely, but the mouse response becomes erratic, the CPUs are taken up with a "kernel_task", and the sound is choppy. Re-booting fixes the issue, but it is happening more frequently (has been going on for 2 years now); I also notice that the usual "chime" at booting disappears, and can be made to re-appear by resetting the PRAM.

I haven't noticed any consistent thing (i.e. software or computer use) that triggers this - it can happen overnight when I am not even using the computer.

Panic (system crashes) log:

Source: /Library/Logs/DiagnosticReports/Kernel_2019-09-06-091151_Tartarus.panic

Size: 10 KB (9,803 bytes)

Last Modified: 06-09-2019, 09:58

Recent Contents: Anonymous UUID: 2B0482EB-06AF-C051-8955-436D7750B072

Fri Sep 6 09:11:51 2019

*** Panic Report ***

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

. FW Revision=C2.3.21\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-387.270.1/IONVMeController.cpp:5334

Backtrace (CPU 14), Frame : Return Address

0xffffff8760043a40 : 0xffffff80155ae6ed

0xffffff8760043a90 : 0xffffff80156ea185

0xffffff8760043ad0 : 0xffffff80156db8ba

0xffffff8760043b40 : 0xffffff801555bb40

0xffffff8760043b60 : 0xffffff80155ae107

0xffffff8760043c80 : 0xffffff80155adf53

0xffffff8760043cf0 : 0xffffff7f98ce6b30

0xffffff8760043e50 : 0xffffff7f98ceaa3b

0xffffff8760043e80 : 0xffffff7f98ce68cd

0xffffff8760043ec0 : 0xffffff80155ed885

0xffffff8760043f40 : 0xffffff80155ed425

0xffffff8760043fa0 : 0xffffff801555b0ce

Kernel Extensions in backtrace:

com.apple.iokit.IONVMeFamily(2.1)[A67B3600-6FE3-3037-AC41-8C2D353B6250]@0xffffff7f98cd9000->0xffffff7f98d18fff

dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[1D716047-7F62-3FFA-8C01-26C166B3739A]@0xffffff7f96526000

dependency: com.apple.iokit.IOPCIFamily(2.9)[BFDEB8D4-50FE-3DDB-87B7-F6A504393830]@0xffffff7f95e95000

dependency: com.apple.driver.AppleEFINVRAM(2.1)[B83F29B8-24AC-303B-BBBA-CF332168FDE6]@0xffffff7f96667000

dependency: com.apple.iokit.IOStorageFamily(2.1)[71BB22B0-3075-35A1-B04E-FBAC574DA80D]@0xffffff7f96183000

dependency: com.apple.iokit.IOReportFamily(47)[0BC9F93B-456A-3D97-BE4C-69DCBB5E8A3C]@0xffffff7f96b14000

BSD process name corresponding to current thread: kernel_task

Mac OS version:

18G95

Kernel version:

Darwin Kernel Version 18.7.0: Tue Aug 20 16:57:14 PDT 2019; root:xnu-4903.271.2~2/RELEASE_X86_64

Kernel UUID: C41337A1-0EC3-3896-A954-A1F85E849D53

Kernel slide: 0x0000000015200000

Kernel text base: 0xffffff8015400000

__HIB text base: 0xffffff8015300000

System model name: MacPro6,1 (Mac-F60DEB81FF30ACF6)

System uptime in nanoseconds: 43749601696140

last loaded kext at 384706921633: com.apple.driver.AppleUSBTopCaseDriver

Farkus5--

for your situation on a Mac Pro 6,1 ONLY, Firmware Version 120 is too old for proper nVME device support.

You should contact OWC for assistance, or install 10.13.6 onto a regular rotating drive, which should update your firmware in the process. if memory serves me, it should be version 132.

Thanks for the advice Grant - I just wanted to follow up on this...I put 10.14.6 onto a regular disk (thunderbolt) and booted with that, but the firmware was not updated. Then I tried going into recovery mode and re-installing 10.14.6 onto the SSD (OWC Aura Pro X SSD) in the Mac Pro, but again the firmware was not updated. Looks the Firmware does not get updated if there is a non-Apple SSD in the machine. From what I read online, the solution is to swap out the OWC SSD and put in the old Apple one (which I don't have, so it would mean buying one just to update the firmware), and then resinstalling the system. Too much money and work for right now!

In any case, the computer has been running for a couple of days now without a kernel panic, so it seems that doing the system re-install fixed something.

I'll go to see apple technical center today.

Here is the kernel Panic.

Sorry, here is the full report

The kernel panic does indeed indicate an issue with the SSD as you suspect. I would second Grant Bennet-Adler's suggestion to review the link that was provided to help get this resolved.

Same issue with mojave 10.14.5 update but with MackBoo Pro 15-inch, 2017 and 1 TB SSD :-(

Where is the rest of the report?