Mac OS 10.15.4: Random restarts due to panic(cpu 1 caller

Same here!! For months now same issue.

panic(cpu 0 caller 0xfffffff014c1b7b4): x86 CPU CATERR detected

Debugger message: panic

Memory ID: 0x6

OS version: 17P4281

macOS version: 19E287

Kernel version: Darwin Kernel Version 19.4.0: Mon Mar 2 20:38:56 PST 2020; root:xnu-6153.101.6~2/RELEASE_ARM64_T8010

Kernel UUID: 3695E9D9-323E-350E-9A6E-65819BE397D7

iBoot version: iBoot-5540.105.2

secure boot?: YES

x86 EFI Boot State: 0x16

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0x3

x86 Previous Power Transitions: 0x70707060400

PCIeUp link state: 0x1614

Paniclog version: 13

Kernel slide: 0x000000000cbe4000

Kernel text base: 0xfffffff013be8000

mach_absolute_time: 0x11c7f394a49

Epoch Time: sec usec

Boot : 0x5e9a1e93 0x000c5547

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x5e9ae570 0x00004bf1

Panicked task 0xffffffe0005f5400: 3204 pages, 214 threads: pid 0: kernel_task

Panicked thread: 0xffffffe0009d2f88, backtrace: 0xffffffe016e1b4b0, tid: 332

lr: 0xfffffff0144ac764 fp: 0xffffffe016e1b4f0

lr: 0xfffffff0144ac5c0 fp: 0xffffffe016e1b560

lr: 0xfffffff0145c6e7c fp: 0xffffffe016e1b610

lr: 0xfffffff014a7562c fp: 0xffffffe016e1b620

lr: 0xfffffff0144abf28 fp: 0xffffffe016e1b990

lr: 0xfffffff0144ac280 fp: 0xffffffe016e1b9e0

lr: 0xfffffff0152e2934 fp: 0xffffffe016e1ba00

lr: 0xfffffff014c1b7b4 fp: 0xffffffe016e1ba30

lr: 0xfffffff014c0cbe4 fp: 0xffffffe016e1baa0

lr: 0xfffffff014c0eb0c fp: 0xffffffe016e1bb50

lr: 0xfffffff014c0c31c fp: 0xffffffe016e1bbe0

lr: 0xfffffff014bd3780 fp: 0xffffffe016e1bc10

lr: 0xfffffff0149e2abc fp: 0xffffffe016e1bc50

lr: 0xfffffff0149e2340 fp: 0xffffffe016e1bc90

lr: 0xfffffff014a80514 fp: 0x0000000000000000

I’ve already tried all those things with no positive results, nor should I have to.

I did try to limit my external display usage and noticed it happens less frequently but that could just be a coincidence.

Apple needs to get it together and make this right. I didn’t pay $3000+ For a mac to have to use tricks to get it to work properly. Unacceptable.

Add me to this for this issue as well. Less-than-a-month-old 2019 16" MacBook Pro (i7/32GB RAM/5300M). Received Mac right around 10.15.4 OS update. Updated macOS. Initially, I experienced issues with the Mac rebooting on it's own after waking the Mac from sleep while attached to my external display. Panic messages referred to: " userspace watchdog timeout: no successful checkins from com.apple.WindowServer"

Code:

panic(cpu 6 caller 0xffffff7f8f1a0ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
...etc etc ...

The 10.15.4 Supplemental Update came out, and perhaps that fixed this issue, or maybe due to me changing some of the Energy Saver setting (one suggestion I found said disabling Power Nap help). Needless to say, I haven't had this exact issue now for a week or so.

HOWEVER, now I'm seeing another odd rebooting issue. Over the weekend, I had been using my MacBook Pro by itself, disconnected from my external LG UltraFine 4K monitor. This morning, I brought my Mac back to my desk, connected monitor and attempted to wake the system with mouse/keyboard. Initially it worked, I entered password and saw the desktop. However almost immediately, the system was basically frozen. Mouse & keboard unresponsive. Then screen goes black. Reboot. And I see this error message:

"panic(cpu 1 caller 0xfffffff01e2cb7b4): x86 CPU CATERR detected"

panic(cpu 1 caller 0xfffffff01e2cb7b4): x86 CPU CATERR detected
Debugger message: panic
Memory ID: 0x6
OS version: 17P4281
macOS version: 19E287
Kernel version: Darwin Kernel Version 19.4.0: Mon Mar  2 20:38:56 PST 2020; root:xnu-6153.101.6~2/RELEASE_ARM64_T8010
Kernel UUID: 3695E9D9-323E-350E-9A6E-65819BE397D7
iBoot version: iBoot-5540.105.2
secure boot?: YES
x86 EFI Boot State: 0xd
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0x5
x86 Previous Power Transitions: 0x10001000100
PCIeUp link state: 0x89473614
Paniclog version: 13
Kernel slide:     0x0000000016294000
Kernel text base: 0xfffffff01d298000
mach_absolute_time: 0x1e03492014e
Epoch Time:        sec       usec
  Boot    : 0x5e99c322 0x0000ff4f
  Sleep   : 0x5e9d969e 0x000dc0e6
  Wake    : 0x5e9d96cc 0x00056e35
  Calendar: 0x5e9d96f7 0x00018901

Panicked task 0xffffffe000893c00: 3270 pages, 220 threads: pid 0: kernel_task
Panicked thread: 0xffffffe000c65520, backtrace: 0xffffffe01755b4b0, tid: 336
		  lr: 0xfffffff01db5c764  fp: 0xffffffe01755b4f0
		  lr: 0xfffffff01db5c5c0  fp: 0xffffffe01755b560
		  lr: 0xfffffff01dc76e7c  fp: 0xffffffe01755b610
		  lr: 0xfffffff01e12562c  fp: 0xffffffe01755b620
		  lr: 0xfffffff01db5bf28  fp: 0xffffffe01755b990
		  lr: 0xfffffff01db5c280  fp: 0xffffffe01755b9e0
		  lr: 0xfffffff01e992934  fp: 0xffffffe01755ba00
		  lr: 0xfffffff01e2cb7b4  fp: 0xffffffe01755ba30
		  lr: 0xfffffff01e2bcbe4  fp: 0xffffffe01755baa0
		  lr: 0xfffffff01e2beb0c  fp: 0xffffffe01755bb50
		  lr: 0xfffffff01e2bc31c  fp: 0xffffffe01755bbe0
		  lr: 0xfffffff01e283780  fp: 0xffffffe01755bc10
		  lr: 0xfffffff01e092abc  fp: 0xffffffe01755bc50
		  lr: 0xfffffff01e092340  fp: 0xffffffe01755bc90
		  lr: 0xfffffff01e130514  fp: 0x0000000000000000

UGH. And this is the second time this has happened; after reconnecting Mac to external display while it's asleep and trying to wake the machine. Never had this issue with my previous Apple MacBooks.

I don't use Google drive. For me the crash only happens when using FaceTime and lots of network packet drops. It seems to make FaceTime unhappy in the bridgeaudiod

I am on a brand new MacBook Pro so a bit frustrating this is happening. Anyway every crash I have is a report to Apple.

Same thing here. Third one tonight, probably 10-20 of them in the last few days. Mac Mini 2018 running 10.15.4 -- had been quite a stable machine until very recently, is crashing like crazy lately. Here's my latest:

panic(cpu 0 caller 0xfffffff00e36afa4): x86 CPU CATERR detected
Debugger message: panic
Memory ID: 0x6
OS version: 17P4281
macOS version: 19E287
Kernel version: Darwin Kernel Version 19.4.0: Mon Mar  2 20:38:56 PST 2020; root:xnu-6153.101.6~2/RELEASE_ARM64_T8010
Kernel UUID: 24BEA3DB-10C2-36A4-A7D5-C71CE0D00021
iBoot version: iBoot-5540.105.2
secure boot?: YES
x86 EFI Boot State: 0x16
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0xc1
x86 Previous Power Transitions: 0x70707060400
PCIeUp link state: 0x1614
Paniclog version: 13
Kernel slide:     0x00000000063a8000
Kernel text base: 0xfffffff00d3ac000
mach_absolute_time: 0x3f96950f4f
Epoch Time:        sec       usec
  Boot    : 0x5e9eb107 0x0008c6d0
  Sleep   : 0x00000000 0x00000000
  Wake    : 0x00000000 0x00000000
  Calendar: 0x5e9edd72 0x000e75b9

Panicked task 0xffffffe00053c800: 2393 pages, 158 threads: pid 0: kernel_task
Panicked thread: 0xffffffe0008b9fb0, backtrace: 0xffffffe0163cb4b0, tid: 326
		  lr: 0xfffffff00dbfc764  fp: 0xffffffe0163cb4f0
		  lr: 0xfffffff00dbfc5c0  fp: 0xffffffe0163cb560
		  lr: 0xfffffff00dd16e7c  fp: 0xffffffe0163cb610
		  lr: 0xfffffff00e1c562c  fp: 0xffffffe0163cb620
		  lr: 0xfffffff00dbfbf28  fp: 0xffffffe0163cb990
		  lr: 0xfffffff00dbfc280  fp: 0xffffffe0163cb9e0
		  lr: 0xfffffff00e946934  fp: 0xffffffe0163cba00
		  lr: 0xfffffff00e36afa4  fp: 0xffffffe0163cba30
		  lr: 0xfffffff00e35c3d4  fp: 0xffffffe0163cbaa0
		  lr: 0xfffffff00e35e2fc  fp: 0xffffffe0163cbb50
		  lr: 0xfffffff00e35bb0c  fp: 0xffffffe0163cbbe0
		  lr: 0xfffffff00e322f70  fp: 0xffffffe0163cbc10
		  lr: 0xfffffff00e132abc  fp: 0xffffffe0163cbc50
		  lr: 0xfffffff00e132340  fp: 0xffffffe0163cbc90
		  lr: 0xfffffff00e1d0514  fp: 0x0000000000000000

Copying this from my post today over at MacRumors (https://forums.macrumors.com/threads/new-macbook-kernel-panics.2228308/page-3?post=28390194#post-28390194)

#

Disabling Power Nap seems to solved my initial panic issue related to "watchdog timeout: no checkins from watchdogd..." but there seems to be more than one issue with 10.15.4 (https://mrmacintosh.com/10-15-4-update-wake-from-sleep-kernel-panic-in-16-mbpro-2019/).

However, I have experienced an unexpected reboot after reconnecting my still-sleeping MacBook Pro to my external monitor and then trying to wake it...

Interestingly, today I tried a different order of operations, starting with mac asleep & disconnected from the display once more: first opening the lid and waking the mac up (login via touch id), then shutting the lid and quickly connecting the mac to my external monitor and re-waking it with the mouse and keyboard. I managed to do it quickly enough that the system didn't sleep (didn't have to re-enter user password with keyboard), and I didn't experience any freeze or panic/reboot like I did the other day. Hmm..

#

Anyone else seeing sleep/wake reboots upon connecting a sleeping MacBook to an external display? If so have you all tried waking the MacBook first and then re-connecting the Mac back to the display quickly right after closing the lid? Not a solution, but just a workaround.

-William

^ EDIT: Something just occurred to me... I should add that my current privacy & security settings are set so that my system requires my password for 5 seconds after sleep or screen saver starts. I'm guessing that if I increase this time limit, I wouldn't need to "rush" plugging my Mac back into the displays after shutting the lid.

I have the same issues as well on my macbook pro 13" 2019 (with touch bar).

All 3 error messages. Where I got the cpu 1 caller after I updated to 10.15.4.

Did it help for any of you guys to reinstall macOS as earlier suggested by Apple??

Having the same issue on and of with my MacBook Pro (15-inch,2018) macOS Catalina Ver 10.15.4 since Summer 2019. On the phone with Apple Tech for hrs, never got it solved, they tried everything. Took it in to Apple store for tech support for 3 days in a row, spent about 12 hrs, reinstalled, tried everything never found anything and it kept on happening. They asked me to create another user and dump the old one... I did.. 3 times.. nothing.. I have a log of all the times I freeze and copies of the print screen from Neve to date.. still no answer and apple has no idea what it is...

This is my first Mac . I switched over from Windows because I got tired of windows coming or updating every day, and the blue screen ...at least I knew what it was with them, and that I would loose 20-30 min.. but with apple I thought it be different...

Just to confirm, My freeze times have nothing to do with sleeping, I got it when I was working with the macbook pro. I have an external display though.

BUT what seems to be working so far, I did an SMC reset 2 days ago. No more restarts. Hopefully it sticks.

Update on my laptop. Apple support told me to go to a 3rd party computer repair service, due to Apple stores being closed in my country. The 3rd party repair store is using my Apple warranty so it will be free.

Apple provided no solutions

I have the same situation since being upgraded to 10.15.4. Seem that the issue is still not fixed with the Beta 1 (even the kernel panic they talk about here is about after waking from sleep): https://mrmacintosh.com/category/10-15-catalina-beta/

It sometimes happens 2 times a day, sometimes only once every 5-7 days. It is driving me crazy and thanks Apple for deploying crappy software!