MacBook Pro with macOS Sonoma crashes frequently and randomly.

Did you migrate all your stuff from the old mac?

If you migrated everything, you brought along old system extensions and daemons that may not run well on the new mac.

Please run Etrecheck and post its full report here. Use the "additional text" button and paste the report into the text box.

mhompesch1 wrote:

Sonoma keeps crashing frequently and randomly. Never had any such issue with Ventura. Issues started after installing Sonoma on my Mac Book Pro (Apple M1 Max, 16 inch). Clearly a buggy OS, all apps up to date.

Don't point at apps, please ...it's a Sonoma problem.

Not sure how you can you separate the two I do not know....

if it is not software then it is hardware, in that case take it in for assessment.

I have had very minor glitches with Sonoma, most have resolved them selves by shutting down and re-starting the Mac as the code settles in...

if you want to explore more in an effort to resolve your issue:

most common causes—

Uninstall all third party apps that are Cleaners/Optimizers/VPN/Anti-Virus

all known to cause issues on the macOS.

To trouble shoot further you can:

—A SafeBoot Use safe mode on your Mac - Apple Support will sort many anomalies

Does a quick disk repair before it fully boots up, and certain system caches get cleared and rebuilt, third party system modifications and system accelerations are disabled.

Login and test. Reboot as normal and test. Caches get rebuilt automatically.

This test will tell you if third party interference; most* extensions etc are not loaded in safe boot mode.

—Test issue in another user (or guest user) account Change Users & Groups settings on Mac - Apple Support

This will tell you if it a universal issue or isolated to your user/admin account. 

After reading all replies to this post and some other blogs, I did not find a conclusive answer. In my case, the continuous crashing with Sonoma started yesterday. I have a macbook air M2, 2022 Apple M2 chip. My system is updated to the last release.

I did all the different steps suggested here, but when I tried to reinstall SONOMA as the last option, the systems said I had not enough free space on my SDD, that was not accurate. I went back to safe boot to check storage under system settings, and it said that just my apps used 800 GB, but my SDD is 500 GB.

I found several users have same issue, but there is not a single or direct cause for this or how to fix it.

At the end, I this this>

1. I erase as much apps that I could.
2. Disabled my email accounts, so attachments are deleted from my mac, but not from my server.
3. Install a clean up app to erase apps leftovers, cache, and as much junk files as I could. (I used Clean My Mac, but any app should work fine).
4. Reinstalled SONOMA and reboot.

The crashing stoped and the wrong storage calculation is now fixed. I still have a crash if I am trying to cleanup junk files with Clean My Mac, otherwise it is working great all day long. Hopefully it stands like that while Apple fix this issue.

I hope it is helpful for you guys.

This has been occurring on 3 separate 2020 MacBook Air M1 systems since upgrading to Sonoma. None of these MacBooks had any issues before and the Apple Store couldn't find hardware issues with them. Ventura was working fine before and reinstalling it (after going to the painful process of wiping each MacBook) works fine for each.

Hi all - I've been one of the people experiencing this problem, and it seems to have gone away now. Since my crash report always started with a message about a network issue, I had a hard look at my network settings, and realized that I had a third-party driver installed for a USB-C hub with an ethernet port. I removed that driver; experienced at least one more crash; but thereafter it's been stable. So, that's something to look at for some of you. It seems clear that not everyone experiences this problem in the same way, so I don't imagine it'll be a solve for everyone.

(And I weigh in agnostic on how much responsibility Apple/Sonoma has for this issue... Perhaps they changed the way that drivers work in the OS such that different kinds of drivers are now experiencing this very similar intermittent crash... Or perhaps there are a series of unrelated errors from driver developers that are only now coming to light... Can't really assign blame from the outside. But I do hope someone from Apple is having a good look at these reports.)

when working with an external 4K HDMI monitor or USB-C port (Macbook Pro 16 M1 Max 64 Gb 4 Tb MacOS 14.0 (23A344)

:

panic(cpu 1 caller 0xfffffe00276483b4): DCPEXT0 PANIC - apt firmware: apt.c:369 apt_vbi() -- - iomfb_mailbox(67)

apt firmware: apt.c:369 apt_vbi() --

RTKit: RTKit-2413.1.1.release - Client: local-t600xdcp.release

!UUID: 4bcc7a73-3ced-3fd9-a1c7-3238cf8e94ac

Time: 0x000000e0b05e2312

A brief update on my prior answer/post:

I have proceeded with the following changes:

• cleared Safari cache
• disable/changed the Sonoma 'slow-motion' original wallpaper

To this day, since the prior post:

• I haven't had any crashes anymore i.e. neither UI slowdown/semi-freezing or crash/reboot
• No crashes overnight during backup: (i) with Safari closed and (ii) with Safari opened... with the side note that I checked beforehand if one tab/website was the reason for Safari's memory constantly growing. Finding the culprit website in time ensured no crash overnight it seems.
• Also of note is that the 'memory leaks' in Safari have been less occurring, meaning I witnessed less often the ballooning of Safari used memory. I would attribute this to the cache clearing.
• Of note also: no system element(s) crash reports in the console reporting application
• The odd 'read clipboard' behavior still occuring

If it's any help, on my 2019 iMac, the loginwindow process was going from tens of megabytes of memory usage to gigabytes. After searching around, I found an old post online mentioning using an animoji for one's account picture as a possible culprit. Removing that from my account, and going back to a regular picture for my profile fixed the issue.

In Activity Monitor, the bloat seemed to start with loginwindow accessing a lot of things to do with graphics in macos, which ties in with this.

It seems the animated wallpaper is another culprit.

Macbook Prob 16" M1 Max, Sonoma 14.1

I'm starting to suspect that this is a problem related to the "Brave" app, a Chrome-based web browser. After installing Sonoma, Brave started randomly rebooting, and so did Sonoma. I used Brave as my default browser but have now switched back to Safari to see if Sonoma's situation improves. Well, apparently it works, I haven't had random restarts anymore...

My MacBook Air has been crashing once a day since Sonoma came out.

It was the "unable to satisfy mandatory allocation" problem.

I tried disabling various background tasks, and deleting unused VPN stuff.

No joy. Ran

Etrecheck and started deleting stuff it suggested.

Finally deleted some files beginning with "aviatainc".

Computer has been up for four DAYS!

Here is an update.

I've done a clean install of Sonoma 14.3 after completely formatting the hard drive.

The OS still crashes and the Touch Bar often flicks. Interestingly, the Activity Monitor starts crashing.

Two interesting findings.

1. The crash seems related to the sleep mode. In most of the cases, the rebooting occurred when the laptop came back from the sleep mode.
2. While the Touch Bar was flickering, I put flash light to the light sensor, and it came back to normal. This must be related to the functional automatically adjusting the display brightness.

Now I have the very final check, which is the hardware investigation, although I don't think there was any accident that might have caused hardware damage.

I don't know what to do if there is no hardware damage detected.

I've tried several methods, and one of them is working for me.

Many users point out that Mac freezes when it is playing videos. The common setting is that the Macbook is attached to an external display and it is using "mirroring".

My preferred solution: You could download applications like better display and turn the main display (Macbook) off, so far this is the best solution for me and it mimics "mirroring". I've been using this solution for almost a week and there is no crash at all while playing videos.

Alternately, other users suggest to change the setting to extended display instead of mirroring and arrange the displays diagonally if you are not using the main display. However, I've not tried this method for a prolong period of time. May be it works for you.

I find it helpful to look at what is in the crash reports, and see if it is related to something specific.

My Mac got to Ventura after years of full system updates and started becoming unbearably unstable, even after removing software and looking into crashes and errors. Eventually I came to the conclusion that various hidden databases that are used in the system had become corrupt, so I backed up my computer and restarted from scratch. It was painful, but the upgrade to Sonoma has been painless.

Maybe if you post a crash report showing what crashed, we can see what might actually be causing the issue.

DillonBrice wrote:

Just wanted to post here and say that after an insane number of crashes from kernel panics over a two week period I finally bit the bullet and re-installed the OS cleanly. And my Mac Studio M1 Max is now happily running 14.2 without any more issues. I had previously tried just updating from 14.1 to 14.2 and that made no difference. I also tried a ton of the other recommendations in this thread, but to no avail.

Thank you for this. People always blame the updates, and forget that it's usually all the old stuff that was installed before (sometimes years before) that breaks after the update.

Last post for me: Every morning since I loaded Sonoma my M1 Mini has opened with a crash report. My other Mac has an intel chip and hasn't crashed once.

I started over with a clean install...still crashed. Two days ago I saw a comment here concerning the possibility that widgets are causing problems, so I removed all widgets.

I haven't had a crash since then. Anecdotal only; I'm not good at reading crash reports etc, but it seems to be (knock wood) running well now.

I really appreciate all the "me too" notes, actually, and definitely admire those of you with creative ideas on steps to at least try. Thanks to everyone.