WindowServer crashing repeatedly since upgrade to Ventura

I believe that the problem comes from the external screen when it is in "main display" and not in "extended display". Before the Ventura update it was in extended and it moved to main view with the update. Since I put it back in extended display, I no longer have windowServer crashes.

I have been having different flavors of the WindowServer crashes with both 13.0 and 13.0.1. To be honest I think that the patch has made the issue even worse!

In general I get about 10 crashes a day, although they are not all from WindowServer. Docker Desktop Helper (Renderer) also crashes regularly despite updating to the latest version.

Here is my setup:

• MacBook Pro 2019
• Dell P2421D external monitor
• Initial connection: generic active USB-C to HDMI cable
• Current connection: Apple USB-C Digital AV Multiport Adapter + HDMI cable (with Ethernet)

What works:

• Just using the Mac seems to do the trick.
• Using the external monitor only, regardless if I use full screen apps or any number of browsers/code editors...

Patterns that I identified:

• when using the USB-C cable it used to crash even when closing the lid.
• using the apple AV adapter looked to have solved it, but clearly not for long.
• since 13.0.1, when coming back from sleep the os would try to restore the desktops or reconnect the external display, but it gets stuck in what looks like an infinite loop flickering the displays on/off alternatively. This did not lead to any crashes.. so nothing to send to Apple.
• in most cases the crashes happen when switching tabs with cmd+tab.

Crash frequency: It varies wildly, sometimes 3 times in a minute, sometimes after an hour or so.

Crash flavors:

1. I have 2 of these although they seem to crash at a different point in the execution stack.

Crashed Thread:        13  com.apple.windowserver.root_queue  Dispatch queue: com.apple.coreanimation.mtl_dealloc

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

2.

Crashed Thread:        0  ws_main_thread  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

3. this one looks different, could not get the exact thread that cause the crash.

"exception" : {"codes":"0x0000000000000000, 0x0000000000000000","rawCodes":[0,0],"type":"EXC_CRASH","signal":"SIGABRT"},

4. another one that looks completely different

"exception" : {"codes":"0x0000000000000001, 0x0000000000000000","rawCodes":[1,0],"type":"EXC_BAD_ACCESS","signal":"SIGSEGV","subtype":"KERN_INVALID_ADDRESS at 0x0000000000000000"},
  "termination" : {"flags":0,"code":11,"namespace":"SIGNAL","indicator":"Segmentation fault: 11","byProc":"exc handler","byPid":8022},

My 2020 Macbook Air kept crashing with sudden disconnection when using the USB-C docking station with an external display every so often (like once every 45 minutes to one hour) after I upgraded to Ventura OS. I suspect it may be due to the USB-C privacy protection feature from the new OS. The docking station I use is the Totu USB-C Dock TT-DC002A (https://www.amazon.com/TOTU-Upgraded-Universal-Charging-Extended/dp/B0838WTFD1/ref=sr_1_3_sspa?crid=10T4MHAMHEUDS&keywords=Totu%2BUSB-C%2BDock%2BTT-DC002A&qid=1666989763&qu=eyJxc2MiOiIwLjg3IiwicXNhIjoiMC4wMCIsInFzcCI6IjAuMDAifQ%3D%3D&s=electronics&sprefix=totu%2Busb-c%2Bdock%2Btt-dc002a%2Celectronics%2C890&sr=1-3-spons&th=1). I have tried using two different docking stations of the exact same model and reverted back to the Monterey OS without the disconnection, so I have confirmed the hardware is functional. I appreciate it if someone could have a solution to the issue. Thanks!

I saw a reddit thread that said that it was related to command-tab and apps running in full-screen mode. I have a 16" 2019 MBP (i9), and have stopped running any apps in full-screen mode. I haven't had a window server crash since then.

To coin a phrase from another post, I'm cautiously optimistic :-)

Here's a link to the thread: https://www.reddit.com/r/MacOS/comments/yczalk/ventura_random_window_server_crash/

Thank you for making my comment as a solution, although I would only qualify it as a workaround.

Maybe to add some hints to work around some other inconveniences:

• I have enabled Unlock your Mac with your Apple Watch - Apple Support. You can also use this method to approve password requests.
• For webcam you can use your iPhone , but it is the shortest way to replace your battery - for some reason the phone CPU load is so high that the phone(iPhone 13 mini) gets quite toasty. Use your iPhone as a webcam on your Mac - Apple Support. Works very consistently.
• Alternatively, use a GoPro as webcam - I am using a GoPro 9. The experience is a bit patchy.

Really looking forward to the fix from Apple!

Interesting datapoint - I went back to my old two external monitor set up for a work reason. USB C to HDMI. The only thing different is that they are 1080P monitors - 27in. I have been free of crashes since the change back (knocking on wood).

My home and office had been using Samsung UHD widescreen displays and the problem seemed to begin around the time I made that change. I can't say exactly, but that seems right.

I am going to try the MBP at home this weekend on the UHD and leave the dual monitor set up running at the office and see if the problem continues in one location but not the other.

Curious - how many of you with this problem are plugged into 1080P monitors vs something bigger/better?

I oversee about 50 Macbook Pros for the company I work for. Oddly, only one user is experiencing this. At first it was mainly happening during Zoom meetings, but has now started happening randomly over the course of the day. The Macbook in question is a 2020 model, 13 inch. Many of my users work with multiple displays.

No. Have you installed and run any "cleaning", "optimizing", "speed-up", anti-virus or VPN apps on your Mac?

Give this a try: boot into Safe Mode according to How to use safe mode on your Mac and test to see if the problem persists. Reboot normally and test again.

NOTE 1: Safe Mode boot can take up to 3 - 5 minutes as it's doing the following; 

• Verifies your startup disk and attempts to repair directory issues, if needed

• Loads only required kernel extensions (prevents 3rd party kernel/extensions from loading)

• Prevents Startup Items and Login Items from opening automatically

• Disables user-installed fonts 

• Deletes font caches, kernel cache, and other system cache files

NOTE 2: if you have a wireless keyboard with rechargeable batteries connect it with its charging cable before booting into Safe Mode. This makes it act as a wired keyboard as will insure a successful boot into Safe Mode.

Hi. For what it is worth, just contacted apple support via chat. I received the following suggestions:

1. Reset SMC
2. Reset NVRAM 

Anyone already tested this or spoke to apple support as well? SMC doesn't seem to be making sense to me (but then who knows). NVRAm maybe more but not sure. The support guy initially didn't know what the Window Server is, so the advice seems to be a standard suggestion.

Just thought I'll post it here as the window crash really is annoying. I have it also for Apple Studio Display.

I have this issue as well, only on external monitor (HP in my case).

A possible workaround, which has worked for me so far (no crash in 2 weeks):

Enable "Displays have separate Spaces" in System Settings -> Desktop & Dock