WindowsServer crashes and kernel panics on 2017 iMac with macOS Ventura

Retina 5k, 27-inch 2017 iMac, MacOS Ventura 13.6.7


I've had ongoing issues with repeated WindowsServer crashes and kernel panics. Sometimes the Mac will run fine for hours, other times it will die a short time into use. I'm also getting random beachballing.


One thing to note is that I have two internal hard drives, but both have come up healthy in tests.


I am really hoping it's not a hardware issue, but it would be nice to get some answers at least.


EtreCheck:


Thank you!


[Edited by Moderator]

Original Title: WindowsServer constant crashes

iMac 27″ 5K, macOS 13.6

Posted on Aug 29, 2025 3:49 AM

Reply
Question marked as Top-ranking reply

Posted on Aug 29, 2025 11:38 AM

Based on a quick review of your EtreCheck report:


Short version: you’ve got a perfect storm of I/O stalls + legacy audio/USB cruft + disabled security, and it’s tipping macOS into a userspace-watchdog panic. The panic you captured (“no successful checkins from logd in 120 seconds”) is classic when storage or low-level drivers wedge the system. Your EtreCheck shows a filesystem call that literally timed out (120.55 s), heavy Photos background indexing (photoanalysisd/photolibraryd), Backblaze activity, and a pile of old audio kexts (Soundflower, iShowU, RemotePCSound, ACE) plus USB hubs/devices. That cocktail, together with unsigned/system mods and translocated apps (Hej Stylus), explains the beachballs, WindowServer/bluetoothd crashes, and the panic.


I’d also flag software hygiene: automatic and security updates are disabled, hosts file is heavily modified, and there’s “AntiCC [HCiSO]” on the install list. Aside from the obvious risk, those tools often patch services that touch login/windowing and networking, and they regularly break notarization/Gatekeeper paths—exactly the kind of thing that shows up here as “Unsigned files / Apple security disabled.” Finally, storage: your NVMe 980 PRO is fast on reads, but the timed-out filesystem call plus constant Photos/Backblaze churn suggest periodic I/O hiccups. The secondary SATA BX500 (HFS+, no TRIM) is another likely source of stalls if any libraries live there.

5 replies
Question marked as Top-ranking reply

Aug 29, 2025 11:38 AM in response to blueybirdy

Based on a quick review of your EtreCheck report:


Short version: you’ve got a perfect storm of I/O stalls + legacy audio/USB cruft + disabled security, and it’s tipping macOS into a userspace-watchdog panic. The panic you captured (“no successful checkins from logd in 120 seconds”) is classic when storage or low-level drivers wedge the system. Your EtreCheck shows a filesystem call that literally timed out (120.55 s), heavy Photos background indexing (photoanalysisd/photolibraryd), Backblaze activity, and a pile of old audio kexts (Soundflower, iShowU, RemotePCSound, ACE) plus USB hubs/devices. That cocktail, together with unsigned/system mods and translocated apps (Hej Stylus), explains the beachballs, WindowServer/bluetoothd crashes, and the panic.


I’d also flag software hygiene: automatic and security updates are disabled, hosts file is heavily modified, and there’s “AntiCC [HCiSO]” on the install list. Aside from the obvious risk, those tools often patch services that touch login/windowing and networking, and they regularly break notarization/Gatekeeper paths—exactly the kind of thing that shows up here as “Unsigned files / Apple security disabled.” Finally, storage: your NVMe 980 PRO is fast on reads, but the timed-out filesystem call plus constant Photos/Backblaze churn suggest periodic I/O hiccups. The secondary SATA BX500 (HFS+, no TRIM) is another likely source of stalls if any libraries live there.

Aug 29, 2025 12:40 PM in response to blueybirdy

There is no nice way to say it, but that Crucial BX500 SSD is pure & utter junk. The BX500 easily overheats if you write to it for more than about 30 seconds, the performance can easily drop to 40MB/s and stay there for hours before recovering, plus I have seen many of the BX500 SSDs fail completely. I really don't know why Crucial would tarnish their brand & reputation with that junk.


The Crucial MX500 SSD is Ok (at least it was before 2020....I have not really tested the newer models to confirm since SSD manufacturers are now changing the internal components without any corresponding change to the model number).


Also, TRIM is not enabled on the Crucial BX500 SSD, but is enabled on the Seagate.


I don't know if or how much a difference it may make, but the APFS file system is optimized for SSDs. Your Crucial SSD is using HFS+. Theoretically it should be possible to convert it to APFS without data loss, there is an option in Disk Utility on one of the menus. Just make sure you have the data backed up just to be safe.


Aug 29, 2025 1:45 PM in response to Tesserax

Yowch. Well, the data has been transferred over and over again from Mac to Mac (been a Mac user my entire life), so it doesn’t surprise me that there’s that much chaff. It has never caused serious problems before though so I guess I was lucky.


Thank you a ton for the help. I guess I start with software and work my way along. That’s a lot to process, haha!

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

WindowsServer crashes and kernel panics on 2017 iMac with macOS Ventura

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.