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.
Thanks much for the clarification, I hope it's helpful for many users that are on this thread.
Few words of caution: What works for you might not work for everyone who is experiencing this issue.
While this may qualify as a 'fix', it wouldn't qualify as a solution with a view on the underlying root cause (which most certainly is a buggy MacOS / Sonoma).
In no world (except for the Windows universe maybe...) should an operating system be crashing because it can't handle operational load or exceptions created by an app or a piece of hardware. By doing what you have done, you've obviously been able to eliminate factors that contributed to the load that Sonoma can't handle....but....you / no one should have to do that...and wouldn't have to, if Apple would not have released an OS that obviously has a quality problem.
Oh I agree. I deeply resent having to mess around searching through countless threads looking for all these off-the-wall remedies after paying thousands of dollars for a computer.
And I also agree this may not work for everyone (I have a MacBook with the silicon chip and I didn't have to do anything--Sonoma worked fine on mine). But I don't think any of what I tried is particularly invasive.
I know...but thought this one would be relevant enough to be mentioned if addressed....
....and now the bad news (at least on my end)....the crashing after coming back from sleep continues after upgrading to 14.1......so much, so bad, so disappointing....I just shared my first crash report with Apple....
Everyone, please, keep reporting and invite others with the 'crashing problem' to report to this thread....it appears Apple hasn't taken notice yet....
You should understand that Sonoma for x64 environment - Intel and AMD, is different from Sonoma for ARM. Apple had been writing MacOS for x86/x64 since 2006, or at least a few years earlier, as the first Macs with Intel arrived in 2006, so has a long experience in that, > 14 years. First was Tiger, now it is Sonoma. The OS is written specifically for a given chip.
Apple M chips - Arm based system on a chip (SoC) came in 2020. Testing must've been few years before, and writing MacOS for it. The first M1 chip Mac came with Big Sur. And, you were the experiments. Some users were happy, some were not. MacOS for ARM went on from Big Sur, Monterey, Ventura to Sonoma. For most, who come here, it appears to be a troublesome OS. You'd have to keep on testing and give feedback, if of course, you want the MacOS for ARM to be good on your M chip Macs.
Lots of crashing here on a Mac Studio after upgrading from Monterey to Sonoma 14.1. I see a lot of people with the issue, in my case it’s related it IO. Apple needs to stop this year OS upgrade cycle, they can’t maintain it.
RickKarrer wrote:
Apple needs to stop this year OS upgrade cycle, they can’t maintain it.
Really?
Which one? MacOS for ARM or MacOS for Intel?
Mine is an Intel MBP and of 2018, Sonoma 14.1 is doing quite well. no glitches, no battery drains, no heating...and, one day after the update, it went back to the Desktop Mode and stays there...
I’m having a similar issue. I’ve noticed it while using HBO Max on my computer monitor when I attach my MacBook Pro and put on a streaming service while I exercise, it inevitably freezes when I try to escape from the streaming service. It didn’t do this at all until I updated to Sonoma. I also have a MacBook Pro M1 one terabytes, 16 gig ram.
My original comment was removed. Apple is going to remove all mention of b / e / t / a / s, even if it’s a detriment to them by not letting me say that the next B word stopped the crashing for me, however, accessing external drives, particularly subfolders, still very slow. If you have a critical system that is constantly crashing, it’s probably worth trying out the B word.
I suppose, you should start a new thread. Too many posts, and all these "Me too" will not be read by most users. After all, this is a users for users community, and user can help another, only h/she asks a concrete question. I'm also going to unsubscribe from this thread, just after this post.
The answer marked as the best answer in this thread is not at all the best answer.
If you are interested in getting an answer, please ask a concrete question, in your own thread. Take care!
I have a MacBook Air 15-inch with an M2 chip that I got when it launched a few months ago, so it's not just laptops with the M1 that are having this problem. It regularly locks up, screen goes purplish, as it crashes on Sonoma with a very similar message at the top of the crash as others are getting. Here are 3 recent ones (note that the cpu number is different on these, though I've gotten many with cpu 0, 2, etc.):
panic(cpu 0 caller 0xfffffe001768f158): "skr.umd.upipe:578:com.apple.bluetooth.Pipe": skr 0x0xfffffe1b62315400 sg 0x0xfffffe24efe9b6b8 (idx 1) unable to satisfy mandatory allocation
panic(cpu 2 caller 0xfffffe00246a76d0): "skr.ubft.fsw_2:16": skr 0x0xfffffe16727ba000 sg 0x0xfffffe24e7eacb68 (idx 1) unable to satisfy mandatory allocation
panic(cpu 4 caller 0xfffffe002411b6d0): "skr.ustats.stats-0.Safari.3577": skr 0x0xfffffe24fe055200 sg 0x0xfffffe24fe03d508 (idx 0) unable to satisfy mandatory allocation
Yeah, it's just that the rule stop making sense once they started practicing public b words for all their major software. If it were a developer only, or specific kind of thing like an insider program, then I would understand. However, anyone can go get the b word, and for anyone who's completely screwed, because their computer isn't functioning the way it's supposed to, the ability to discuss such software benefits both end users and Apple. Running the b word as taking me from an unusable computer, to a very usable, although slightly hindered, machine.
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.
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.
It could very well be something installed that conflicts with Sonoma, however, I bought my Mac Studio in February, and set it up, clean without using migration, assistant, or carrying over any settings files. Prior to that, I had been migrating my systems over from one computer to the next all the way up to from 10.0 Cheetah to 10.15 Catalina, without any kind of issues like this.
I definitely would prefer to fix this, I really don’t want to spend another 16 to 24 hours setting up my computer all over again, for it to work sleight. They’ve introduced something that broke the system at a very fundamental level, even if it is caused by conflicting software, it seems to be enough people with the issue for them to work through it with the crash log data.
So far, the next release seems to be holding up for me as far as crashing goes, but accessing external drives is horribly slow, and I can’t imagine I have anything installed that could be breaking it at that level.
My chrome is crashing every 10 minutes now, it's completely unusable. Only started when upgrading to Sonoma, brand new 16" top spec MacBook Pro, and can't even browse the internet. I have a lot of tabs open, unsure whether that is the issue, but when cycling through screens, I'm getting the wheel of death. Your OS needs an update.
MacBook Pro with macOS Sonoma crashes frequently and randomly.
