Kernel Panic after upgrading to 10.14.4

I recently updated two 2013 Mac Pros to 10.14.4 and immediately they started having kernel panics after about five minutes. It even happens in recovery mode. I eventually swapped hard drives with another Mac Pro that hadn't been upgraded, and it seems to run stable there. The hard drive without 10.14.4 seems to be running fine in the machine that was panicking. Currently I've at least got one machine up and going, but it's frustrating. Anyone else ran into this problem?


The panic I'm getting can be seen at this Github gist. It seems to always be a different process, and sometimes the panic message is slightly different, but it always seems to be some form the NMIPI for Unresponsive Processor panic.



Mac Pro, macOS 10.14

Posted on Apr 2, 2019 7:05 AM

Reply
Question marked as Top-ranking reply

Posted on Jun 5, 2019 10:22 PM

I have swapped my 64GBs of aftermarket RAM with the same amount of OEM Apple RAM borrowed from another Mac Pro. So far so good after 24 hours.


I have also upgraded to 10.4.6, but I am more inclined to believe that it is the OEM RAM that is making things more stable. It would make sense that Apple tests their OS with mostly stock hardware, and some odd bug fell through the cracks and is hitting systems with aftermarket RAM/SSD.


I will circle back if anything changes. By the way, the donor Mac Pro is currently running El Capitan with my original aftermarket RAM, no issues to report.

Similar questions

194 replies

May 20, 2019 5:51 AM in response to mikehar

Kryptotoek - I have another machine that had not been upgraded, the installer existed there and I was able to make an installation thumb drive.


Two weeks of crashes with 10.14.4, 10.14.5 beta(s), and 10.14.5 (final). New installation of 10.14.3 and not a single crash (yet). Good news for me though, my last time machine backup finished before my first 10.14.4 upgrade so I was able to restore everything using time machine.

Jun 5, 2019 8:13 AM in response to Ataylor35

The strongest correlation I have seen in these postings is with a particular version of firmware.

(Firmware is not stored on a drive, its stored in its own private store on the Processor board.)


Some users obtained relief by installing and running 10.13.6, which comes with a firmware update, if not already installed. Then when they upgraded to 10.14 Mojave, the problem was fixed. Your mileage may vary.

Jun 13, 2019 5:54 AM in response to interactiveWebs

I just downgraded to 10.14.3 and my Mac is stable again. No more crashes. Hope it stays that way.

I shout out to Apple: PLEASE give us an update without these issues.

In the meantime, it would be nice to admit something's wrong with .4 & .5.

Communicating with your (pro) users instead of denying problems is a better way to keep your customers satisfied.


Jun 13, 2019 4:12 PM in response to darthsabbath

This may sound odd, but I had similar problems with my Mac pro 2013. I solved them by cleaning my Mac pro: essentially taking it apart according to iFixit and blowing the different parts with compressed air. All the Kernel panics are gone.


My suspicion is, that Apple changed something in the thermal management which leads to over-sensitivity and hence kernel panics. The temperatures were not necessarily excessive.


My $0.02

Jun 14, 2019 10:04 AM in response to sidfrombellevue

I absolutely agree, this is a software issue and should be addressed by Apple. And you are correct that downgrading is the only fully confirmed fix at this point.


That said, downgrading the OS requires wiping out the SSD and brings additional software compatibility issues for some. If anybody wants to try a quicker patch first (albeit one not 100% bulletproof like downgrading), swapping the RAM might be an option worth considering. It luckily worked for me, although your mileage may vary. For all we know this might be just one of a number of triggers for the bug.


My old RAM by the way is still being used in another Mac Pro running El Capitan. After more than a week, one of the modules still shows ECC errors there, but this system does not crash as a result. This comes to confirm that there is a software issue with the newer OS.

Jun 15, 2019 4:06 AM in response to Werner from Belgium

I gave it a go after reading reports that Beta 2 seems to address the problem. I'm cautiously happy to report that my system has not crashed since updating to 10.14.6 beta 2. Furthermore, I noticed that the Boot ROM has been updated to 131.0.0.0.0. Perhaps this is where the real fix has been applied. Also, for reference, I have 64GB OWC RAM and never had an issue until updating to 10.14.4. The SSD is original.


If it crashes, I real report back but hopefully tomorrow evening I will report that the system is still running smoothly (I'm in Japan).


  Model Name: Mac Pro

  Model Identifier: MacPro6,1

  Processor Name: 8-Core Intel Xeon E5

  Processor Speed: 3 GHz

  Number of Processors: 1

  Total Number of Cores: 8

  L2 Cache (per Core): 256 KB

  L3 Cache: 25 MB

  Hyper-Threading Technology: Enabled

  Memory: 64 GB

  Boot ROM Version: 131.0.0.0.0

Jun 15, 2019 4:11 PM in response to neuronaut

What I said was that before 10.14.6 B2 it was somewhat stable for me, but not 100% If I started my Mac Pro is a certain way (let it wait at login, and then wait until all startup processes were done), it would only crash once in a while.


When I updated to 10.14.6 B2, Boot ROM 131.0.0.0.0, a few days ago, I have started up as normal, immediately logging in, and immediately starting to use applications, and I have NOT had a single panic. No freezes, and no problems.


I run Adobe Creative Suite apps (LightRoom, PhotoShop, Bridge), MS Office, Chrome, iTunes, etc. usually all at the same time, and everything is stable.

Jul 17, 2019 2:05 PM in response to darthsabbath

I started having this problem on 10.14.5 yesterday. After reading through all the options and trying various things, I believe that one or more of the following helped me (sorry I couldn't be more scientific as I didn't have time to figure out precisely which one):


  1. Reset the SMC How to reset the System Management Controller (SMC) on your Mac - Apple Support
  2. Physically cleaned the Mac Pro by removing the case and using compressed air on it.
  3. Reformatted one of my external backup drives.


I also tried turning off SecuritySpy (just upgraded it) and turning off VMWare Fusion. I even pointed a fan at it.


Once this problem started, the machine only stayed up for a few hours; I'm going on 18 hours without a problem and with decent load and disk I/O.


Based on my reading of the thread, I tend to think there is/was a thermal issue (my office did get hot yesterday), so resetting the SMC and cleaning out the machine may have helped get the fans going at the right time and keeping the temperature within reasonable limits.


I hope this helps someone.


Apr 29, 2019 7:02 PM in response to darthsabbath

I have the same issue since upgrading to 10.14.4 and after reading some of the posts here, I updated to 10.14.5 beta 3. Since the beta update, the panic attacks completely stopped for over a week until I updated to beta 4. After the last update, it immediately crashed after booting up. Prior to the start of this issue, I had made zero system changes or software updates/installations. So, if you are on beta 3 and seem to be doing fine, probably should refrain from updating to beta 4.


*** Panic Report ***

Panic(CPU 11, time 6131464400742): NMIPI for unresponsive processor: TLB flush timeout, TLB state:0x0


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 after upgrading to 10.14.4

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