MacBook Pro with macOS Sonoma crashes frequently and randomly.

I reported many days ago that removing the widgets was my fix. Sonoma crashed every night while I was in bed beginning the day I upgraded (that same day I configured widgets for the first time).

Since removing widgets, I haven't had a problem...so I'm adding widgets tonight to see if I return to the crash problem. So far I think my fix has been anecdotal...A doesn't always equal B...but I'll report in a few days to see if the widgets are now holding their own. By the way, by now I've updated to 14.1.1. Who knows if that matters.

I can relate to Ferhan01. I have an Intel late 2018 15.6" mbp with 32GB RAM and 6-core i7 chip, and it actually started crashing on the last version of Ventura...and each version of Sonoma made it worse..although now, 14.2.1 has gotten better but still having same crash behaviour as the last version of Ventura.

The consistent crash has always been in this scenario: Regardless of external monitors, or wiped hd with fresh install of OS, if I put it to sleep manually, or set the "display to switch off after X minutes", it would just go dead in few hours, and I had to power it back up, upon which it would always show me a crash trouble report that said "AMDFrameBufferVIB::SetPowerState" panic etc.

Currently, I am on Sonoma 14.2.1 and I am able to work around it by setting "switch off display" to never. So the mbp never sleeps, and so never crashes. This is working out quite well. Although, occasionally, every other night or so, I pity my mbp, and manually put it to sleep, expecting fully to have a crash next day, and indeed it does crash as expected with the same error log, but I live with it.

My daughter who works for Apple (cyber security group, nothing to do with OS) is home for the holidays, and she keeps arguing vehemently for Apple, makes for good holiday fun. I am excitedly waiting for 14.3 (apparently in January?) and hoping that will fix the crash on wake problem.

No. As someone mentioned i discovered the problem: it's that **** iCloud. I disabled it and now the system is another system, fast, no crash at all. 4 hours has passed so fingers crossed. But before i had crash at every 10 minutes , on every application, often when you used the virtual desktops. So i think the problem is indeed iCloud

Turn off the new types of screensaver solved the problem for me. Use the same screensaver you had with Ventura. Those new screensavers looks good but its buggy.

If it's any consolation, 14.1 upgrade released today.

About the security content of macOS Sonoma 14.1 - Apple Support

Turning off iCloud Drive stopped the crashing for me on a MacBook Pro 14" M2 Max running Sonoma 14.2

An unstable OS that doesn't work with iCloud is basically not fit for purpose... Come on Apple !!

That crash log doesn't have any obvious giveaways, so if I were you, I’d back everything up to another drive (or, to be safe, another couple of drives) and do an erase-install of the system like I did. It might take a few days to get everything up and running again, but I found it less painful than continuing to troubleshoot what is now a very complex OS.

Prior to that though, it might be an idea to run a hardware diagnostic. Use Apple Diagnostics to test your Mac - Apple Support

Unless the cause of the crash is the same thing in each case, and the exact cause is known, we can't say anything beyond what we know, which is that some people who have upgraded to Sonoma are experiencing crashes.

So far, people who have posted crash logs have had multiple different parts of the software crashing, which may mean disk errors, cache errors, or a hardware fault.

Searching for related crashes, so far we know that people with M1 Macs that have a possible hardware fault crash when Sonoma is installed.

@currawong ... (i) Apple has about a dozen crash report logs from me, all correlated with a unique string that I included in my problem report. While we can take stabs in the dark by looking at the info that the crash logger is sending to the mothership, and we can poke around in the .diag files in the DiagnosticReports directory, only Apple staff have the full context (ie source code) and tools to do a proper analysis (once escalated from Support into the core Engineering team). If you can share what we should look for, please do. Recall, the crash reporter does not always appear -- about 50/50 for me.

FYI, I've changed my uptime logging script to capture the first ten lines of 'top' in an attempt to get more info on the state of the machine before it hangs/crashes. Because it sure looks like something is leaking memory quite badly (not the screensaver; I turned that off long ago). Ok, maybe not a memory leak, but something is bogging the machine down over time. Here's my (hacky but might be helpful) script:

#!/bin/zsh

cd /Users/KTyyz

echo >> uptimelog.txt

echo "----- ----- ----- ---- ----- ----- ----- ----- -----" >> uptimelog.txt

echo >> uptimelog.txt

while true; do

# uptime >> uptimelog.txt

top -l 1 | head -10 >> uptimelog.txt

echo >> uptimelog.txt

sleep 60

done

Before I switched from a simple uptime to top, it logged this just before a crash/hang:

17:20 up 40 mins, 4 users, load averages: 1.83 1.77 1.86

17:21 up 41 mins, 4 users, load averages: 1.76 1.79 1.86

17:22 up 42 mins, 4 users, load averages: 1.81 1.80 1.85

17:23 up 43 mins, 4 users, load averages: 1.55 1.71 1.81

17:24 up 44 mins, 4 users, load averages: 1.62 1.72 1.81

17:33 up 53 mins, 4 users, load averages: 1.75 1.70 1.80

17:55 up 1:15, 4 users, load averages: 2.19 1.84 1.84

18:04 up 1:25, 4 users, load averages: 3.49 2.27 2.00

9 then 12 then 9-10 minutes to execute "sleep 60" ??? Something's "not right". This script was the only user-level process happening at the time.

It is certainly an issue with Sonoma... no response from Apple yet. I submitted several reports plus feedback thru developer assistance. This ignorance by Apple is similar to the iOS Maps back then...

panic(cpu 4 caller 0xfffffe002825f030): "LLC Bus error from cpu2: FAR=0xa00100018 LLC_ERR_STS/ADR/INF=0x11000ffc00000080/0x4300080a00100018/0x1 addr=0xa00100018 cmd=0x18(acc_cifl2c_cmd_rd_ld)" @AppleFireStormErrorHandler.cpp:424
Debugger message: panic
Memory ID: 0x1
OS release type: User
OS version: 23A344
Kernel version: Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:43 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6000
...
...
Panicked task 0xfffffe200fa9b4a8: 151 pages, 6 threads: pid 66931: com.apple.Driver
Panicked thread: 0xfffffe1b3de188a8, backtrace: 0xfffffe8e0256e3c0, tid: 1003796
...
...
Kernel Extensions in backtrace:
         com.apple.driver.AppleARMPlatform(1.0.2) ...
            dependency: com.apple.iokit.IOReportFamily(47) ...
            dependency: com.apple.iokit.IOSlowAdaptiveClockingFamily(1.0.0) ...
            dependency: com.apple.iokit.IOStorageFamily(2.1) ...
         com.apple.iokit.IOPCIFamily(2.9) ...
         com.apple.driver.AppleFireStormErrorHandler(1.0)...
            dependency: com.apple.driver.AppleARMPlatform(1.0.2) ...
            dependency: com.apple.iokit.IOReportFamily(47) ...

As previously reported:

My crashes were most often in sleep, given the machine is not used a lot.

My crashes were resolved by participating in the early OS updates program.

Word has it that the final 14.2 is about ready, which should make it easy for everyone to get the fix.

MacBook Pro M1 Max 32GB, 1TB SSD

I solved formatting SSD and reinstalling from scratch. Not very helpful, I know, but it was the only way.

I’m generally finding that Sonoma is to blame, but the issues are caused by things specific to a given user’s set up, such as various ways you can use an external drive , Finder settings, screen sharing, settings, and even storage and memory configurations, etc. For example: Electric Light Factory found there’s a major memory leak when you set the Finder to larger icon views. Something that people who are in visually impaired, or just like big icons, should be able to use perfectly fine. However, Apple seems to have very little quality control these days, and misses things like this.

Myself, I have been reporting to Apple. Example is the fact that I can’t go to the Applications folder on my Mac Mini, and my Mac Studio’s screen sharing agent and Dock crash a lot, so I switched over to remote management, but I noticed that the remote management agent was using 600% of my CPU today, while I wasn’t connected through another computer.

Any issue I’m having on every computer running Sonoma is accessing external drives, especially those with folders with medium to large numbers of files, deeply nested folders, have incredibly slow access times. As a test, I test, I disconnected a USB 3.1 8TB RAID from my Mac Studio, then plugged it into my 2008 MacBook (that only has USB 2.0), and all of the files and folders are much faster on that old thing. Raw trans speeds were slower, but when you take into account file in the Finder, lock up for several minutes, and copying and modifying files, and Sonoma freezes up often, overall the 2008 MacBook running 10.8 mountain lion (which wasn’t even officially supported on that computer) much better.

Jagato00 - I might suggest: before going to get HW inspection...backup, and erase you hard drive, and reinstall OS fresh, make sure it is still crashing, and then take that laptop to get HW tested...and if it passes, then you have something to discuss and demo to the Apple support guy.

I just wish I could go back to Sonoma 14.2.1 where it didn't crash at all for me.

You can, but it may not be easy.

Create a USB Installer from

softwareupdate --fetch-full-installer --full-installer-version 14.2.1

Startup from the USB Installer and erase your drive.

Reinstall macOS from the USB Installer.

Migrate your data from a backup you made prior to updating past 14.2.1.

Or, manually copy your data from a current backup.

Migration Assistant may or may not work going backwards.