Kernel Panic after upgrading to 10.14.4

Check the Mac App Store for a security update in the last two days.

Same issue here. Kernel panic as soon as I installed 10.14.4. Had to restore a TimeMachine backup.

System has had no modifications and a recent rebuild. About My Mac below,

Hardware Overview:

  Model Name: Mac Pro

  Model Identifier: MacPro6,1

  Processor Name: 6-Core Intel Xeon E5

  Processor Speed: 3.5 GHz

  Number of Processors: 1

  Total Number of Cores: 6

  L2 Cache (per Core): 256 KB

  L3 Cache: 12 MB

  Memory: 64 GB

  Boot ROM Version: 129.0.0.0.0

  SMC Version (system): 2.20f18

  Illumination Version: 1.4a6

  Serial Number (system): F5***694

  Hardware UUID: 2155E20C-96D4-5AF8-814D-05B2077009BB

[Personal Information Edited by Host]

I am having the exact same issue. NMIPI for Unresponsive Processor on my 2013 MacPro. It was completely stable on 10.14.3 - installed 10.14.4 and immediately the machine started suddenly rebooting from kernel panics. I rebuilt fresh Mojave with 10.14.3 and I was back to stable. Upgraded again to 10.14.4 (no 3rd party software) and I immediately went back to constant cpu panics and immediate reboots. I have tested this with both OWC and Transcend 420GB - both drives are stable on .3 but then suffer from the same CPU panic after the .4 OS update. Please help. I can obviously revert back to 10.14.3 - but can then no longer update my Mac??

Neither, which is strange.

/usr/libexec/firmwarecheckers/eficheck/eficheck --integrity-check

EFI Version: MP61.88Z.0120.B00.1708080652

Matching allowlist not found in EFIAllowListShipping. Searching in EFIAllowListAll.

Fetching allowlist data update.

Waiting for allowlist data download to complete.

Allowlist data update failed with error = 102.

Primary allowlist version match not found for version MP61.88Z.0120.B00.1708080652.

same issue here ever since I updated to 10.14.4. I brought it to apple for checking, they first told me either SSD or power supply, quoted me 4-500 for fix it, after ship it away to service center, came back with over 1200 for replace logic board. I was ****** then declined the fix, took it home and replaced SSD and logic board by myself with apple parts. Same issue, after I read this forum, I then start to think of apple bugs. I'm going to roll back to previous IOS for now until apple fix it.

High Sierra and 10.14.3 are both safe. I will continue to follow up with my engineering case.

From an Apple tech’s perspective, faulty hardware would almost always be the cause of an issue like this and if they haven’t had enough reports to reproduce & document this internally then every tech is starting from scratch. Please don’t fault the techs for doing their jobs.

Not exactly... I have the CPU Panics happen in Safe Mode, and sometimes under no workload at all.

Other times I can leave my Mac Pro running for hours, with no issues, even under moderate workload.

so, I think it is a kext, but one of the basic Apple ones, and I think it is related to HW, in that the issues seemed to start when Apple started testing the new Boot version.

Small observation:

I have a small utility running, Little Snitch, and I have it set so it shows up- and download in the taskbar, and when I experience the Panics, right before, the up- and download goes grey (as supposed to red and green), and shows 0 kbps. Then the crash happens...

I don't know if this is a coincidence, but that's what I am seeing...

My Mac Pro is connected to two networks; via Ethernet to my switch and router, and via Thunderbolt to my NAS/DAS.

Any chance we all share something in common? ie, 3rd party RAM?

The only thing custom on mine is a 3rd party RAM upgrade (which I believe might be a tad slower than the original).

I'm skeptical its related since its very specific to the MacOS upgrade ... but ... grasping for straws.

For what it's worth, I have only had a single panic since upgrading to 10.14.6 Beta (18G29g). I had the one crash on the day of the installation, about a week ago. Since then I ran OnyX maintenance, and I haven't had a crash since then... I log straight in, I use Adobe Creative Suite, MS Office, iTunes, Chrome, etc. all at once. I have 64GB of non-Apple RAM, and it is smooth sailings for me:)

Exact same problem here. The kernel panic will happen by itself at random, even if I just turn on the machine an leave it sitting without any apps running. At least it is good to know that it is a software issue. I was fearing that my processor was toast.

Please this is not the place for a rant. While support may not resolve the issue directly, having as many people report the issue is absolutely critical, so hopefully everyone here is patiently working with a tech and doing everything they say regardless of how dumb they think it is.

Perhaps there will be a fix in a future version, for now just run 10.14.3 (or earlier) and stay calm. For most of us Apple's platform is the best & easiest tool for the job.

Many of us are also out of warranty as well which makes it upsetting that we can't go into the Apple store for a free diagnostic and repair. Most companies wouldn't offer online support for out-of-warranty devices but Apple is, so give them credit for that.

Back in late March, my Mac Mini completely died. Luckily i had a time machine back up and restored a new Mac Pro (Late 2013) from that. Pretty much since I got the new computer, it has had panic shutdowns at night or when i leave for 40 mins during the day from work. It does not happen every night but it happens every few days. I'm pretty sure the computer has always been running on 10.14.4 and 10.14.5. After all of the "basic" troubleshooting, Apple says to bring it in but based on what i'm reading, it will be a giant waste of time.

All hardware is brand new from Apple

• Processor: 2.7 GHz 12-Core Intel Xeon E5
• Memory: 64 GB 1866 Mhz DDR3
• FirePro D700 6 GB
• 1 TB Flash Storage

I can provide panic reports if anyone else thinks it would be helpful. Even though mine does not crash as much as others, I wanted to provide the info that i have all factory hardware from Apple within the last 3 months and mine still has panic crashes also.

Just scan the panic reasons (near the fromt of the panic report. If you are having the SAME problem as others on this thread, the reason will be machine check and "some form the NMIPI for Unresponsive Processor panic" darthsabbath coined in the initial post.

If something else, you have a different problem.

I have a few different ones from the 6 panic reports i saved over the last 5 weeks.

• Panic(CPU 0, time 122953388614781): NMIPI for unresponsive processor: cross-call timeout
• Panic(CPU 0, time 195958478922161): NMIPI for spinlock acquisition timeout, spinlock: 
• Panic(CPU 0, time 58634348287864): NMIPI for unresponsive processor: cross-call timeout
• panic(cpu 0 caller 0xffffff7f88dfefe5): pmLock: waited too long, held by 3@0xffffff80058dd929