Big Sur Mac Crash 4 times in the last 6 hours - 2 no-report and 2 reports

Same error for me.

panic(cpu 2 caller 0xffffff801377999f): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds service: logd, total successful checkins since load (200 seconds ago): 21, last successful checkin: 0 seconds ago service: WindowServer, total successful checkins since load (170 seconds ago): 5, last successful checkin: 120 seconds ago service: opendirectoryd, total successful checkins since load (200 seconds ago): 20, last successful checkin: 0 seconds ago

Panicked task 0xffffff9525be4030: 3 threads: pid 110: watchdogd Backtrace (CPU 2), panicked thread: 0xffffff8b8c93daa0, Frame : Return Address 0xfffffffffb75b690 : 0xffffff801027fd6d 0xfffffffffb75b6e0 : 0xffffff80103e1086 0xfffffffffb75b720 : 0xffffff80103d03f3 0xfffffffffb75b770 : 0xffffff801021fa70 0xfffffffffb75b790 : 0xffffff801028013d 0xfffffffffb75b8b0 : 0xffffff801027f8f6 0xfffffffffb75b910 : 0xffffff8010b14ec3 0xfffffffffb75ba00 : 0xffffff801377999f 0xfffffffffb75ba10 : 0xffffff80137795f2 0xfffffffffb75ba30 : 0xffffff8013778971 0xfffffffffb75bb60 : 0xffffff8010a8365c 0xfffffffffb75bcc0 : 0xffffff8010386d86 0xfffffffffb75bdd0 : 0xffffff801025a9ab 0xfffffffffb75be60 : 0xffffff80102711a9 0xfffffffffb75bef0 : 0xffffff80103b305a 0xfffffffffb75bfa0 : 0xffffff8010220256 Kernel Extensions in backtrace: com.apple.driver.watchdog(1.0)[8BE4EE7F-9150-3161-BE84-36874BF82DE2]@0xffffff8013777000->0xffffff8013779fff

Process name corresponding to current thread (0xffffff8b8c93daa0): watchdogd

Mac OS version: 21G83

Kernel version: Darwin Kernel Version 21.6.0: Wed Aug 10 14:25:27 PDT 2022; root:xnu-8020.141.5~2/RELEASE_X86_64 Kernel UUID: D0DC2052-71F4-3DCB-B189-BEE5A59B3B42 KernelCache slide: 0x0000000010000000 KernelCache base: 0xffffff8010200000 Kernel slide: 0x0000000010010000 Kernel text base: 0xffffff8010210000 __HIB text base: 0xffffff8010100000 System model name: iMac17,1 (Mac-DB15BD556843C820) System shutdown begun: NO Panic diags file available: YES (0x0) Hibernation exit count: 0

System uptime in nanoseconds: 203715217517 Last Sleep: absolute base_tsc base_nano Uptime : 0x0000002f6e5f8c5e Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000 Wake : 0x0000000000000000 0x0000001520b9124d 0x0000000000000000 Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space Zone info: Zone map: 0xffffff8057ddc000 - 0xffffffa057ddc000 . PGZ : 0xffffff8057ddc000 - 0xffffff805addd000 . VM : 0xffffff805addd000 - 0xffffff8527376000 . RO : 0xffffff8527376000 - 0xffffff86c0aa9000 . GEN0 : 0xffffff86c0aa9000 - 0xffffff8b8d042000 . GEN1 : 0xffffff8b8d042000 - 0xffffff90595db000 . GEN2 : 0xffffff90595db000 - 0xffffff9525b74000 . GEN3 : 0xffffff9525b74000 - 0xffffff99f210e000 . DATA : 0xffffff99f210e000 - 0xffffffa057ddc000 Metadata: 0xffffff802edcc000 - 0xffffff804edcc000 Bitmaps : 0xffffff804edcc000 - 0xffffff8057dcc000

last started kext at 35643890241: >driverkit.serial 6.0.0 (addr 0xffffff7fa94b5000, size 28672) last stopped kext at 107344913691: >IOPlatformPluginLegacy 1.0.0 (addr 0xffffff7fa93b1000, size 36864) loaded kexts: com.Cycling74.driver.Soundflower 2

etc.

Same issue. MacBook (Pro, 15-inch, 2016, Monterey 12.6) often shuts down overnight. Sometimes it restarts, sometimes it doesn't. This morning it hadn't restarted after a shutdown. Only thing running was Mozilla Firefox.

I started seeing the "no successful checkins from WindowServer in 120 seconds WindowServer" with Ventura. Prior to that it had been rock solid.

panic(cpu 4 caller 0xffffff8013cd3941): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds WindowServer has not exited since first loaded service: logd, total successful checkins in 525739 seconds: 52573, last successful checkin: 0 seconds ago service: WindowServer, total successful checkins in 525702 seconds: 52557, last successful checkin: 120 seconds ago service: remoted, total successful checkins in 525739 seconds: 52571, last successful checkin: 0 seconds ago service: opendirectoryd, total successful checkins in 525739 seconds: 52573, last successful checkin: 0 seconds ago service: configd, total successful checkins in 525739 seconds: 52572, last successful checkin: 0 seconds ago

Panicked task 0xffffff99fc8a99d8: 3 threads: pid 134: watchdogd Backtrace (CPU 4), panicked thread: 0xffffff9065d2db30, Frame : Return Address 0xfffffff54fa7f590 : 0xffffff80109edf9d 0xfffffff54fa7f5e0 : 0xffffff8010b5b786 0xfffffff54fa7f620 : 0xffffff8010b4aa10 0xfffffff54fa7f670 : 0xffffff8010988951 0xfffffff54fa7f690 : 0xffffff80109ee27d 0xfffffff54fa7f780 : 0xffffff80109ed929 0xfffffff54fa7f7e0 : 0xffffff80111e0f93 0xfffffff54fa7f8d0 : 0xffffff8013cd3941 0xfffffff54fa7f8e0 : 0xffffff8013cd35e0 0xfffffff54fa7f900 : 0xffffff8013cd26cd 0xfffffff54fa7fa30 : 0xffffff80111544ca 0xfffffff54fa7fb90 : 0xffffff8010b02319 0xfffffff54fa7fca0 : 0xffffff80109c5999 0xfffffff54fa7fd50 : 0xffffff80109de892 0xfffffff54fa7fdc0 : 0xffffff80109def9a 0xfffffff54fa7fef0 : 0xffffff8010b2d02a 0xfffffff54fa7ffa0 : 0xffffff8010988db6 Kernel Extensions in backtrace: com.apple.driver.watchdog(1.0)[A71DE745-044D-37DB-B730-8F8FFB66B24A]@0xffffff8013cd1000->0xffffff8013cd3fff

Process name corresponding to current thread (0xffffff9065d2db30): watchdogd

Mac OS version: 22A400

Kernel version: Darwin Kernel Version 22.1.0: Sun Oct 9 20:14:54 PDT 2022; root:xnu-8792.41.9~2/RELEASE_X86_64 Kernel UUID: BF7C9676-EF23-3E8D-A2E2-25DAC63091B6 roots installed: 0 KernelCache slide: 0x0000000010600000 KernelCache base: 0xffffff8010800000 Kernel slide: 0x00000000106dc000 Kernel text base: 0xffffff80108dc000 __HIB text base: 0xffffff8010700000 System model name: MacBookPro16,1 (Mac-E1008331FDC96864) System shutdown begun: NO Hibernation exit count: 0

....

Try searching for something which is using really high CPU in your Activity Monitor and stop the process and/or uninstall it. I have seen "lrs.personalprint.service" as a possible culprit. Hope this helps!

panic(cpu 4 caller 0xffffff80074d7941): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds service: logd, total successful checkins in 189095 seconds: 13924, last successful checkin: 0 seconds ago service: WindowServer, total successful checkins in 189060 seconds: 13900, last successful checkin: 120 seconds ago service: remoted, total successful checkins in 189095 seconds: 13922, last successful checkin: 0 seconds ago service: opendirectoryd, total successful checkins in 189095 seconds: 13923, last successful checkin: 0 seconds ago service: configd, total successful checkins in 189095 seconds: 13923, last successful checkin: 0 seconds ago

Panicked task 0xffffff94f5d12620: 3 threads: pid 137: watchdogd Backtrace (CPU 4), panicked thread: 0xffffff9029396598, Frame : Return Address 0。。。

interesting answer from ChatGPT, any comment from apple dev? : If you haven't received a resolution from the Apple Developer website, there are a few other steps you can try to resolve the issue with your MacBook Pro crashing when connected to an external display. Here are a few suggestions: Check for software updates: Go to the Apple menu and select "Software Update" to see if there are any available updates for your MacBook Pro. Reset the NVRAM/PRAM: This can help resolve issues with display settings and connections. To reset the NVRAM/PRAM, shut down your MacBook Pro, hold down the Command + Option + P + R keys, and then press the power button to start up your computer. Continue holding the keys until you hear the startup sound twice. Try a different cable or display: If the issue is with the cable or display, try connecting to a different cable or display to see if the issue persists. Check for hardware issues: If none of the above solutions work, it's possible that there may be a hardware issue with your MacBook Pro that is causing the crashes. In this case, you may need to have it serviced by an Apple-authorized repair center. I hope these suggestions help resolve the issue you are experiencing with your MacBook Pro. If the issue persists, you may want to consider reaching out to Apple Support for further assistance.