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

I use my ipad pro as an external display. When it works as a wireless external display, all things are fine. But if the ipad connect with the Macbook via a usb-c cable, and works as a wired external display, randomly restarts and freezes comes. Sry for my bad English, hope you can read it.

MBP 16'' 2019 i9 16GB 1TB 5500M

iPad Pro 12.9" 2018 256GB WiFi

My view is to wait for an OS fix; This all started after 10.15.4 update and things just seemingly are random but for me it is always a kernel panic in the bridgeaudiod always the same where there is no watchdog checkin.

It is useless to bring it in for repair or try things with setting x or y. All you can do is wait. Just every time submit your crash report so the frequency is known and so raises the criticality. Other than that nothing you can do and wait for a fix. I have a brand new MacBook pro 2019 16" and after the 10.15.4 it is a total disaster with kernel panics. It is clearly an OS problem.

Similar issue as stated with the "panic(cpu 1 caller 0xfffffff01c4577b4): x86 CPU CATERR detected" error.

Brand new MacBook Pro 16" with 16 gigs of memory, just pulled it out of the box a week ago. The first day I had it reboot 4 times or so. 2 times during a zoom call with family. All went well for a last 5 days or so then it appears to have rebooted last night when inactive, same error.

Really hoping it is a software issue that can be corrected with an update.

Good LUCK!! Tried it before and it will clear it for a couple of days then it comes back.. lost stretch was for 3 weeks in March 2020.

I just read an article that it could be the power saving part of it.. I'll play with it

It is an OS issue so no need to reinstall, no need to reset SMC, no need to change power settings. For me the only way to reduce panics now is to reduce audio usage and don't use FaceTime for now (all my panics are caused by bridgeaudiod ). If I use FaceTime during the day I know in about 45 minutes I have a panic. When I don't use audio at all then I can run all day and no issues.

I use WebEx and Zoom and no panics; As soon as I use FaceTime I can 100% reproduce the issue. It will in 10 to 30 minutes create a panic in the bridgeaudiod.

Not using FaceTime means for me zero panics.

I have had the same error with my Macbook Air 2019 before this happens because your logic board in your macbook is faulty and your cpu is failing so send it to apple it costs nothing with warranty but otherwise it is 1,111 US or it is 1700 AUD dollars to repair. The name of this error is a Kernel Panic

Got hit by case 2 today. Brought my MBP 2019 out of sleep attached a USB C drive to run a weekly time machine backup.

Hardcore crash.

panic(cpu 1 caller 0xfffffff00df677b4): x86 CPU CATERR detected (automatic restart)

Lucky you! I can no longer send reports, it freezes!

For me it all started after I upgraded to 10.15.4 and when I ran out of battery while working on Photoshop (unplugged)

I realised I had 1% left of battery only and ran to get my charger and to plug my mac, which took a bit of time.

I was happily surprised as it didn't shut down (while Photoshop usually drains the battery so fast).

The charging icon showed up and I resumed working thinking everything was ok.

30 seconds later, the mac turned off (while it was charging or supposed to).

It woke up to say it didn't shut down properly and would send a report.

Since that episode, my MBP 15 2017 keeps on restarting whenever it's in sleep mode.

The worst being that it even reboot when the screen is closed which cause an additional overheating.

Guys, It's time to publish an update with a fix!

As it was said earlier we don't buy 3-4K computer to play videogames but to work.

And each time our computer restarts, it a total waste of our time in a period where we need everything but this.

Where is the support?

Finally decided to just call Apple and see what they would do for me. After sending it to them for repair, they replaced the logic board and touch ID. I’m not sure if it’s completely fixed yet so I will update after a few days of using it. I do have to say though… Apple customer service was really really good this time around. I had it back after only 3 days at no cost. If you’re having this problem and can still buy AppleCare, do it before your warranty runs out!

Same issue after plugging in a USB cable into my Hyperdrive dongle... there wasn't even anything plugged in at the other end... just instant crash.

What I have noticed in the logs posted is that they seem all to have the Darwin Kernel Version 19.4.0... my 16" MBP as well... so I wonder if that is the issue...

Ok, I I have deduced mine down to the following: I bought a Laci 2Big 8TB backup drive / dock from the Apple Store prior to upgrading to 10.15.4. My machine was able to remained docked via Thunderbolt 3, the Lacie 2Big all has a Displayport out for video. My CPU panic issue happens when the machine / macOS goes to sleep. There is something triggering this in 10.15.4 that was not there in 10.15.3. I left my machine plugged in all weekend, overnight and such, UNPLUGGED from the Lacie 2Big dock (Thunderbolt 3/Displayport video), and my machine is still up and running as I left it Friday 5/8. I am upset that items purchased from the Apple store cause these driver issues, I am torn between sending the Lacie 2Big dock back or waiting for Lacie AND Apple to get their sh*t together and fix the driver issues that macOS 10.15.4 is clearly having across a number of fronts from the replies here. There has been a pattern emerging with Apple, their hw and sw are no longer the gold standard of stability. Current Apple devices may very well be my last if these do not improve over their lifecycle.

It is RANDOM! It has NOTHING to do with your Lacie drive. The 16"mbp can be fine for days or crash every hour. People blame what they were doing when it happens, but if you read enough of the posts you will see it is RANDOM!

In my case it happens when I am running Webstorm with node server inside. When I run node server in iTerm instead of Webstorm terminal I am running smoothly for days. I hope new generation of MacOS will get rid of this issue.

And it tends to happen when you are working in smelting that you have NOT yet saved or updated... freezes, reboots and you lost not only your work, but your train of thought just went out the window.... Frustrating as heck