Since installing Catalina yesterday, multiple crashes from userspace watchdog timeout

I'm getting this too, and I think it may be related to going into screen saver mode. I have had lots of issues related to accessing media from external hard disks on my Mac Pro desktop. Wondering if people seeing this problem have their screen savers set up to access photos on an external hard disk, just to see if there is any commonality.

In my opinion this has nothing to do with the screensaver. The error also appears to me in the middle of work processes.

But I also saved a lot on external hard disks and wondered if it could have something to do with one of these hard disks or with TimeMachine.

Why is no one from Apple, Parallels or Microsoft responding to this error? The bug is very popular, obviously.

I have the same problem since updating MacBook Air to Catalina, currently will all updates at 10.15.1.

panic(cpu 2 caller 0xffffff7f91aecad5): userspace watchdog timeout: no successful checkins from com.apple.logd in 130 seconds

service returned not alive with context : unresponsive dispatch queue(s): com.apple.firehose.drain-mem, com.apple.firehose.io-wl

service: com.apple.logd, total successful checkins since load (3890 seconds ago): 377, last successful checkin: 130 seconds ago

service: com.apple.WindowServer, total successful checkins since load (3860 seconds ago): 386, last successful checkin: 0 seconds ago

Backtrace (CPU 2), Frame : Return Address

0xffffff801bb9b820 : 0xffffff8010f39a3b

0xffffff801bb9b870 : 0xffffff8011070fe5

0xffffff801bb9b8b0 : 0xffffff8011062a5e

0xffffff801bb9b900 : 0xffffff8010ee0a40

0xffffff801bb9b920 : 0xffffff8010f39127

0xffffff801bb9ba20 : 0xffffff8010f3950b

0xffffff801bb9ba70 : 0xffffff80116d1875

0xffffff801bb9bae0 : 0xffffff7f91aecad5

0xffffff801bb9baf0 : 0xffffff7f91aec7e6

0xffffff801bb9bb10 : 0xffffff80116663fb

0xffffff801bb9bb60 : 0xffffff801166f393

0xffffff801bb9bca0 : 0xffffff8011020b92

0xffffff801bb9bdb0 : 0xffffff8010f3f8b8

0xffffff801bb9be10 : 0xffffff8010f16545

0xffffff801bb9be70 : 0xffffff8010f2cff5

0xffffff801bb9bf00 : 0xffffff8011049085

0xffffff801bb9bfa0 : 0xffffff8010ee1226

Kernel Extensions in backtrace:

com.apple.driver.watchdog(1.0)[AA44EEB8-57FA-3CAC-9105-C7AB21900B9A]@0xffffff7f91aeb000->0xffffff7f91af3fff

BSD process name corresponding to current thread: watchdogd

Mac OS version:

19B88

Kernel version:

Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64

Kernel UUID: 7503CD47-851F-321E-8747-50DB4299165F

Kernel slide: 0x0000000010c00000

Kernel text base: 0xffffff8010e00000

__HIB text base: 0xffffff8010d00000

System model name: MacBookAir6,2 (Mac-7DF21CB3ED6977E5)

System shutdown begun: NO

Panic diags file available: YES (0x0)

System uptime in nanoseconds: 3905745129049

last loaded kext at 962845543546: @filesystems.afpfs 11.1 (addr 0xffffff7f945e1000, size 360448)

last unloaded kext at 2389568961504: >!A!ILpssI2C 3.0.60 (addr 0xffffff7f91e21000, size 40960)

loaded kexts:

@filesystems.afpfs 11.1

@nke.asp-tcp 8.0.2

>AudioAUUC 1.70

>!AGraphicsDevicePolicy 4.5.9

@AGDCPluginDisplayMetrics 4.5.9

@fileutil 20.036.15

Hi - I think I have a workaround. I reinstalled Catalina. That did not fix the problem. I deleted the account that is crashing and created a new account. (As the other account on the MacBook is not crashing).

I noticed that the background accountsd or something like that is consuming lot of CPU and memory. It is pulling data from my iCloud for the new account. I disabled photos sync from iCloud. Everything seems very stable now, it did not crash almost the whole day, previously it would have crashed 2 or 3 times by now. I am going to enable photos in iCloud settings tonight and leave it on overnight and see what happens. The new photos is generating something like "moments" that is basically taking over the resources, but that should not crash. The panic message kind of indicating that the resources are swamped, something timed out, trying to make sense of the panic message.

Hello, Thanks for Infos at all...

More info from here:

I work a lot with MySQL Navicat.

Constantly when I have Navicat running, the PC blocks me again and again. But no panic error.

I have a remote session with Parallels this afternoon. I'm curious if they can tell me anything.

I have a Late 2014 MacBook Air without an external monitor, keyboard, mouse, or anything else. Just plain vanilla. I get this same panic every time I shutdown. It started when I upgraded to Catalina 10.15.1 from Mojave 10.14.6. I have gone through every application listed in the System Information and have removed all apps that are 32 bit or 32/64 bit. Still fails on shutdown with the spinning white lined circle for several minutes. The provides a message that something happened and the system automatically restarts. I have reset the SMC, started up in safe mode, reviewed the admin id (the only id I have on the system). For me, there is some fundamental issue unrelated to extra monitors, etc.

So after switching from the USBC-DisplayPort to the USB-HDMI cables with the two 4k monitors, I was still getting crashes every time the iMac goes to sleep. However after disconnecting my external HDD that I use for TimeMachine backups and Photos library storage, it seems to have improved things. No crashes so far today anyway..

Same exact issue here. Two external monitors connected. Full panic crash at auto sleep, every time.

panic(cpu 14 caller 0xffffff7f8419dad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 140 secondsservice: com.apple.logd, total successful checkins since wake (150 seconds ago): 16, last successful checkin: 0 seconds agoservice: com.apple.WindowServer, total successful checkins since wake (150 seconds ago): 2, last successful checkin: 140 seconds ago

The memory you have in your machine - is it something that came with the default configuration from Apple or did you add some memory at a later point.?

Hypothesis - Its not proven yet but it might be a bad memory stick, so I am polling others that have the same problem ( I have it too error, except its CPU #2.) to see if they have configured the memory with after purchase memory.

My 2017 iMac does have some additional 3rd party Ram memory that I installed when I bought it. However I have never had problems until updating to Catalina.

I was also wondering about this and tempted to take it out. Any luck with that?

If I manually put my computer to sleep it does not crash overnight. If I leave it on and let it go to sleep it crashes every night.

I'm not sure how this could be related to memory. Could be related to screen saver. I'm assuming that Time Machine runs while the machine is in sleep mode. Maybe not.

From my calls with Apple I have discovered, they do not read these threads, nor do they care about them (they said so), support ignores our crash submissions (they said so) and the engineers only read the data from their capture tool, which ironically pulls similar data. The issue seems to affect any machine from 2012-2019 with multiple monitors.

While many can stop the screen saver and power options to reduce the crashes with one monitor, if you have TWO monitors, this procedure does not resolve the issue. Users will still receive a watch dog kernel panic with two monitors and all energy settings turned off. It is not non-Apple memory, it is not cache, it isn't upgrade, it isn't a clean install, it isn't PRAM, isn't SMC, nor is it the 50 other troubleshooting steps the Apple support team will make you do.

I'm unsubscribing from this thread as it has just made me sad.

I'll file another ticket with Apple and send the data again. I'll keep opening tickets daily until maybe they will listen.

If you have this issue, you should consider following their process and opening a ticket.

Wow ... thanks MegaJustice for the feedback, quite astonishing if it is true ...

I have to say that I participated to this thread as I had also this problem without having any external monitor plugged, only Time Machine...

And I have to mention also that since I switched from my 2019 MBP 15" to a 2019 MBP 16" I never have had this problem again...

Could this be machine/harwdware related ?

Anyway I will follow you advice, and if it happen again I will open a ticket at Apple support.

Thanks to the community anyway to always report and give feedbacks.

I was having similar issues on my iMac 5k (10.15.1) with similar error messages. After reading this thread I turned off Time Machine backups to my network drive (an external drive attached to a Time Capsule), and since then the iMac has run flawlessly (knock on wood!).

I've noticed more by now.

My iMac 27 has crashed a lot less since I took off my external screen. However, it sometimes reacts extremely slowly when TimeMachine backup is running.

On MacBook Pro I have no crashes at all with parallels 14 and the same external screen on Catalina. TimeMachine is not used here.

Maybe the problem comes from TimeMachine on an external hard disk? I have a normal USB 3.1 Western Digital 3TB disk. Maybe conflicts between TimeMachine and Parallels or Windows files?