You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
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.
[Re-Titled by Moderator]
My MacBook M2 (Pro 13" 2022 release) has crashed once a day since the update to MacOS Sonoma, it's surprising that there hasn't been a patch update to fix this problem considering the amount of people that are vocalizing their concerns.
Usually upon opening the lid for the first time after having my computer on the charger overnight, I am prompted to re-enter my password, which tells me that it has been restarted. After logging in, I am greeted with a message stating that _windowserver has crashed, and I can submit a report to Apple or ignore.
This absolutely is not a hardware or application issue as I have had this computer since its release last year, and haven't begun to experience problems until this update.
This is ridiculous, if I could regress back to MacOS Ventura I would do it in a heartbeat.
If your mac is a week old and is crashing frequently, there could be a hardware issue. Take advantage of the 14 day window and return it.
I've got two Gen2 Apple Watches staring back at me on my desk right now. Can't pair them with anything. Big waste if they cannot be used. I thought Apple was environmentally conscious.
Upgraded a MacBook Pro 16” Intel 2019 to Sonoma a week ago. Hasn’t stayed up longer than 45 minutes since then. Have filed detailed crash reports repeatedly. At the user level, the machine was not running anything other than a zsh script to log the date every 60s. Fastest crash so far was 5m. With my screen saver set to 15m, I think that’s a red herring. At least 5 crashes/hangs when attempting to do something and the screen saver didn’t kick in.
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.
i have NOTHING unusual installed. So there is no need to blame it on something special you have going. It’s not your fault! It’s not hardware! It’s Sonoma!
i have not seen such core instability from a Mac os upgrade in many years. In the early days, we all expected serious bugs in .0 and would wait for others to find them and then an all clear to use a later release. But this is 2023! The kernel is supposed to be well protected!
To all of you take head what Nosferatum said! Also everybody with crashing download the free version of https://etrecheck.com/en/index.html and run that run to see if a old Intel program is serving up your install!
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.
Apple, i hope you are in this !
Again here during overnight sleep. I guess this time due to lack of “satisfaction”
panic(cpu 1 caller 0xfffffe00249766cc): "skr.umd.upipe:539:IDSClientChannelNexusOS": skr 0x0xfffffe2990a45600 sg 0x0xfffffe29908d85e8 (idx 2) unable to satisfy mandatory allocation
I have the same issue, freezing daily 3 times. Literally Ihave the same programs as 2 weeks ago, on ventura. Tried numerous things to solve it, but did not succeed.
Secondly, LAN ethernet is not working as well. Really disturbing... First time I am not satisfied AT ALL with the new update.
One thing worth trying is Sonoma Cache Cleaner. MacOS aggregates data into caches, much like your browser caches web pages that you have viewed. These caches seem to be able to become corrupt. Over the last decade-and-a-half I've found clearing them has resolved many puzzling issues.
Oh and I should mention the reinstall was from Safe Mode running Disk Repair before install. Since my Mac has shut down 1-2 time a day for two weeks - it's not surprising Disk Repair found a number of errors.
Currawong. Thanks for responding. I guess it could be hardware. However, I've never had this issue prior to installing Sonoma last week. Unfortunately Disk repair did not fix the problem and I've already gone two rounds with Apple Support.
I guess I'll need to call them a third time... :(
Respectfully disagree. Combining logic and probabilistic reasoning inevitably gets you to just one highly likely outcome: more likely than not the root cause of all the problems you are reading about here is Sonoma. Just don’t keep defending the indefensible, please. Apple messed it up.
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.
MacBook Pro with macOS Sonoma crashes frequently and randomly.
