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.
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) ...
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.
I'd agree but all the same hard drives, monitors and tablets that were attached in the prior system were stable. Sonoma... unstable.
My computer is crashing if I leave it on at night. and all day too.
Hey team: can we agree on this?
"A modern OS should be stable and unlikely to crash under any condition, with it's kernel protected from application issues."
This was not the case in early Mac and Windows, but for many years has been solved. Until Sonoma.
We certainly are not well-positioned to diagnose the problem - we have reports of it happening with really ordinary and other fancier application use cases, and with and without "special" hardware attached.
If exploring the logs leads us to some conclusion of what Apple screwed up in Sonoma, that would be fun.
But let's not "blame" any of the externalities.
Clearly, Apple owns this.
Very well stated and I am very much in agreement. Let me add that after several conversations with Apple support (as recently as yesterday), it is stunning to experience how clueless Apple support is in responding to this issue and how unbelievable it is that Apple doesn’t care to communicate with their user base about what most obviously is a massive quality issue in developing and releasing MacOS. Apple: Communicate with us! This is not your every other OS update patch situation. Sonoma is negatively impacting productivity and usability of your hardware.
As previously reported, I've had the fancy screen saver off from the beginning. Yesterday, I cleared the Safari cache. Today, Sonoma crashed while reading a boring web page in Safari.
The debugger message looked familiar "unable to satisfy mandatory allocation"
SO....I started my computer in Safe Mode. It stopped crashing. Meaning, first, it's a software issue. And second, it's either Sonoma or some piece of software that isn't updated for Sonoma. Good times.
amys6 wrote:
SO....I started my computer in Safe Mode. It stopped crashing. Meaning, first, it's a software issue. And second, it's either Sonoma or some piece of software that isn't updated for Sonoma. Good times.
Well, not any software. Just System Modifications, like kernel extensions.
You can find those in /Library/Extensions--note that there are three in there installed by Apple, two HighPoint and one SoftRAID. If you find anything else, they could be the problem.
EtreCheck will also list any third-party kernel extensions.
It is free, isn't it?
Yes. There is an upgraded version you can pay for, but it isn't necessary. The free version does everything anyone needs. It was designed to provide a snapshot of your system to allow people here to try to figure out what is going on with your system. etresoft has never expressed any desire to charge for those features.
This is not the place to discuss outside software. Stop talking about EtreWhatever.
We're discussing an issue with Sonoma. Hoping Apple monitors some of these conversations.
Feeling trolled here. Trying to solve a Sonoma issue.
amys6 wrote:
This is not the place to discuss outside software. Stop talking about EtreWhatever.
You’re the only one trying to discuss it. I suggested a tool smart people use to help identify what third-party system modifications are causing the problems you are experiencing.
You didn’t have to discuss it at all. But, then you did by lying about it.
I have been reading through the threads and it seems like you're the only one trolling here. Personally I'm glad someone mentioned EtreCheck because I certainly haven't seen any official help come from Apple on this issue yet and I'm a bit fed up with 5 - 7 restarts a day on my expensive Apple Hardware. It's not like they don't have the resources to help us out or maybe 2.7 trillion doesn't go as far as it used to...
Re: RMFenwick
Yes that is one of the patterns. Some say turning off the screen saver works. I haven't had luck with that. Thought the issue was hooking my monitor to CalDigit's Hub - but I just had another crash. As far as I can tell this is an OSX issue and will only be solved by apple. I'm going to try Apple Care for a fourth time and see if they've escalated this issue yet. I'm kind of running out of ideas.
People are so naive giving Apple an upper hand in breaking things and getting away… oh boy I can’t believe how people are assuming Operating System (macOS) crashes can be caused by some application settings. On top of that, Apple doesn’t give me option to unsubscribe from this thread making sure I never comment on another threads in future. Apple’s version, if you comment on any of my threads, we will spam you with unnecessary responses.
Folks, being loyal doesn’t mean becoming blind. I am a full Apple house, an Operating System developer, trust me Apple have screwed up Sonoma stability. Crashes happen because something try to write into a protected memory, in this case it being the macOS itself. It’s possible they will fix it in 14.1 release, but never acknowledge.
can someone please tell me how do I unsubscribe from this thread?
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.
MacBook Pro with macOS Sonoma crashes frequently and randomly.
