Constant Kernel Panics – userspace watchdog timeout: no successful checkins from com.apple.WindowServer

[Hennesie2000]

I’ll chime in here too. I recently upgraded my GTX 970 to a RX 5700 XT and also upgraded to 10.15.4 in the process from 10.13.x. I’ve been getting this same kernel panic. It usually happens when opening an app that utilizes the GPU for acceleration, the browser, VideoProc, etc. Prior to making the updates my build has been completely stable for 5yrs.

Also, I dual boot Win 10 and haven’t had any issues when gaming or waking from sleep there.

-slim.jim

 

[martinocando]

Hello, in my case, my only problem (so far) is that when the computer sleeps, every time it wakes up it crashes to the point that I need to press the power button to turn it on. Every single time. Is the same panic user space watchdog timeout.

I have it connected to a brand new OWC Thunderbolt 3 dock, but I was using a Caldigit TB3+ yesterday, and it crashes with both docks. I only have it connected to a single HP ZH2440w monitor. Is annoying, since I have all my programs running before going to bed, and when coming back in the morning, I have to start reloading, deleting recovery files, etc. Thankfully MacOS do a pretty good job of restoring all open programs to the last state, and thanks God for Safari's restore las opened tabs, but is still a bug that shouldn't happen.

I've been reading this whole thread in full, and so far, nothing has worked for me. Just waiting for an update from Apple that might finally fix it. Hopefully.

BTW, I'm on Catalina's latest public beta.

 

[jjhny]

Hello, in my case, my only problem (so far) is that when the computer sleeps, every time it wakes up it crashes to the point that I need to press the power button to turn it on. Every single time. Is the same panic user space watchdog timeout.

I have it connected to a brand new OWC Thunderbolt 3 dock, but I was using a Caldigit TB3+ yesterday, and it crashes with both docks. I only have it connected to a single HP ZH2440w monitor. Is annoying, since I have all my programs running before going to bed, and when coming back in the morning, I have to start reloading, deleting recovery files, etc. Thankfully MacOS do a pretty good job of restoring all open programs to the last state, and thanks God for Safari's restore las opened tabs, but is still a bug that shouldn't happen.

I've been reading this whole thread in full, and so far, nothing has worked for me. Just waiting for an update from Apple that might finally fix it. Hopefully.

BTW, I'm on Catalina's latest public beta.

I had that problem with the new MacPro (2019) and 10.15.2. Apple contacted me and it now works with the 10.15.3 release with external enclosures, etc. Sleeps fairly well (takes a bit to wake. My other trick to make things work was to boot in recovery mode and disable the T2 chip (check->"no security" and check->"allow booting from external devices", also disabled SIP (in recovery boot, in terminal "csrutil disableable") and disabled Gatekeeper (in Terminal "sudo spctl --master-disable").

I find that as long as you are using Apple's apps in their walled garden (prison) you are fine. But if you leave the walled pit Apple has made, you will have many troubles. I am hoping 10.15.5 fixes more of theses problems. At this point I am stuck on 10.15.3 and can't go back to Mojave because Apple decided to release the Mac Pro with this FUBAR OS called Catalina.

Can you try doing what I wrote above on the beta and see if that fixes your problems. Their 'security' is just making it difficult to use and other company's hardware and software.

 

[makdeniss]

Latest beta is aok for me. Panics gone

 

[SnackTime]

Hey everyone. I had the same issue, it seems like (for me anyway) it was due to the Google Drive desktop extension. I uninstalled it and all seems to be fine since.

Hope it helps.

I can't really confirm or deny this, but I did get a kernel panic after having Google Drive filesystem open for ~1-2hrs. I don't normally use it, but it does kind of coincide with this hypothesis.

 

[prdg.alex]

I can't really confirm or deny this, but I did get a kernel panic after having Google Drive filesystem open for ~1-2hrs. I don't normally use it, but it does kind of coincide with this hypothesis.

See this thread on the Google Community https://support.google.com/drive/thread/40534889?hl=en&dark=0. People are reporting that if they exclude the Google Drive volume in spotlight they have experienced no crashes since doing so.

 

[HackinDoge]

Latest beta is aok for me. Panics gone

Unfortunately this is not the case for me. I'm still getting crashes on 10.15.5 Build 19F72f:

Spoiler

panic(cpu 2 caller 0xffffff7f81456ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (3210 seconds ago): 322, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since load (3180 seconds ago): 306, last successful checkin: 120 seconds ago

Backtrace (CPU 2), Frame : Return Address
0xffffff8726e33720 : 0xffffff800031e6dd mach_kernel : _handle_debugger_trap + 0x49d
0xffffff8726e33770 : 0xffffff8000457c25 mach_kernel : _kdp_i386_trap + 0x155
0xffffff8726e337b0 : 0xffffff80004497de mach_kernel : _kernel_trap + 0x4ee
0xffffff8726e33800 : 0xffffff80002c4a40 mach_kernel : _return_from_trap + 0xe0
0xffffff8726e33820 : 0xffffff800031dda7 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff8726e33920 : 0xffffff800031e197 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff8726e33970 : 0xffffff8000ac14c8 mach_kernel : _panic_with_thread_context
0xffffff8726e339e0 : 0xffffff7f81456ad5 com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1 + 0x27
0xffffff8726e339f0 : 0xffffff7f814567fa com.apple.driver.watchdog : __ZN10IOWatchdog35userspaceDisableUserspaceMonitoringEP8OSObjectPvP25IOExternalMethodArguments
0xffffff8726e33a10 : 0xffffff8000a5371e mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x1de
0xffffff8726e33a60 : 0xffffff7f81455cfe com.apple.driver.watchdog : __ZN20IOWatchdogUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x7c
0xffffff8726e33b60 : 0xffffff8000a5c943 mach_kernel : _is_io_connect_method + 0x223
0xffffff8726e33ca0 : 0xffffff8000407412 mach_kernel : _iokit_server_routine + 0x4e72
0xffffff8726e33db0 : 0xffffff8000324438 mach_kernel : _ipc_kobject_server + 0x238
0xffffff8726e33e10 : 0xffffff80002facc5 mach_kernel : _ipc_kmsg_send + 0x135
0xffffff8726e33e70 : 0xffffff8000311bb2 mach_kernel : _mach_msg_overwrite_trap + 0x2d2
0xffffff8726e33f00 : 0xffffff800042fe65 mach_kernel : _mach_call_munger64 + 0x205
0xffffff8726e33fa0 : 0xffffff80002c5226 mach_kernel : _hndl_mach_scall64 + 0x16
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[87C6D09A-72A7-3CEE-94F5-B8395E420958]@0xffffff7f81455000->0xffffff7f8145dfff

BSD process name corresponding to current thread: watchdogd
Boot args: debug=0x100 keepsyms=1 npci=0x2000 shikigva=128

Mac OS version:
19F72f

Kernel version:
Darwin Kernel Version 19.5.0: Sun Apr 19 22:51:38 PDT 2020; root:xnu-6153.120.31~14/RELEASE_X86_64
Kernel UUID: FFC5BCD5-8D44-32EE-8F36-A2B8372C434C
__HIB  text base: 0xffffff8000100000
System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 4156219811740

 

[Smitty72]

Been following this thread for a while. Tried just about everything suggested short of full wipe and reinstall - PRAM, SMC, Reinstall of OS, Safe mode, etc. Thought the power settings suggestion sounded promising and made those changes last night. Made it through the night and some of today, but has since crashed twice with the same KP pointing to watchdog.
Running OS 10.15.4 (19E287) on a nearly factory fresh 2019 MBP 16" with nothing else connected - no external displays, no peripherals, almost no third party software. Makes no difference whether on external power supply or battery.

Willing to try something else that sounds promising, but from the sounds of things on this thread it doesn't look good. And Apple support is useless so far.

 

[Arthurian Legend]

I have a Mac Pro 6,1 and have been having this issue since upgrading to Catalina. Based on these forums, it sounds like it's related to having an external display connected (which is challenging for a Mac with no internal display). I found a post in this forum https://discussions.apple.com/thread/250715149?page=20 that says to go to System Preferences > Notifications and turn ON the setting for Turn On Do Not Disturb When the screen is locked (the 3rd checkbox down). I did this and have not had a crash in several days.

I have a Mac Mini (late 2014) and this worked for me too. Thanks!

 

[Simon Creely]

Installed Catalina 10.15.4 yesterday on Macbook Pro - system crashing ever since - have carried out many of the powersave recommendations etc with no change.

Unplugged external monitor and have been stable ever since. As soon as any external monitor reconnected Kernel Panic error and restart returns

 

[Jacob Roy]

Same problem here on a 2015 Macbook Pro with dGPU (R9 M370X), on 10.15.5 Beta (19F83c).

Everytime I use a 'Video' app (Teams, Facetime, Aerial Screensaver, etc), while plugged-in an external monitor (Apple Cinema Display 24inch, mini Displayport), I have the same kernel panic.

If needed, I can post crashlogs, record the crash, etc).

 

[WalkTheDogs]

Same here, at least twice a week and usually while the monitors are sleeping.

panic(cpu 10 caller 0xffffff7f9afbaad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (54420 seconds ago): 5443, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since load (54390 seconds ago): 5427, last successful checkin: 120 seconds ago

Backtrace (CPU 10), Frame : Return Address
0xffffffa77b8ab720 : 0xffffff801a5215cd
0xffffffa77b8ab770 : 0xffffff801a65a3c5
0xffffffa77b8ab7b0 : 0xffffff801a64bf7e
0xffffffa77b8ab800 : 0xffffff801a4c7a40
0xffffffa77b8ab820 : 0xffffff801a520c97
0xffffffa77b8ab920 : 0xffffff801a521087
0xffffffa77b8ab970 : 0xffffff801acc2ce8
0xffffffa77b8ab9e0 : 0xffffff7f9afbaad5
0xffffffa77b8ab9f0 : 0xffffff7f9afba7fa
0xffffffa77b8aba10 : 0xffffff801ac54f3e
0xffffffa77b8aba60 : 0xffffff7f9afb9cfe
0xffffffa77b8abb60 : 0xffffff801ac5e163
0xffffffa77b8abca0 : 0xffffff801a609bb2
0xffffffa77b8abdb0 : 0xffffff801a527328
0xffffffa77b8abe10 : 0xffffff801a4fdcc5
0xffffffa77b8abe70 : 0xffffff801a514aa2
0xffffffa77b8abf00 : 0xffffff801a632605
0xffffffa77b8abfa0 : 0xffffff801a4c8226
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[99A75EFF-7734-31A0-80BF-FF8288E30D9B]@0xffffff7f9afb9000->0xffffff7f9afc1fff

BSD process name corresponding to current thread: watchdogd

Mac OS version:
19E287

Kernel version:
Darwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64
Kernel UUID: AB0AA7EE-3D03-3C21-91AD-5719D79D7AF6
Kernel slide: 0x000000001a200000
Kernel text base: 0xffffff801a400000
__HIB text base: 0xffffff801a300000
System model name: MacPro6,1 (Mac-F60DEB81FF30ACF6)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 54440102779120
last loaded kext at 196524192106: @filesystems.smbfs 3.4.2 (addr 0xffffff7f9ee14000, size 450560)
last unloaded kext at 54386148012773: >usb.!UHostPacketFilter 1.0 (addr 0xffffff7f9bc55000, size 24576)
loaded kexts:
com.getdropbox.dropbox.kext 1.10.3
com.google.drivefs.filesystems.dfsfuse 32.0.11
com.vmware.kext.vmioplug.18.7.0 18.7.0
com.vmware.kext.vmx86 1587.03.45
com.vmware.kext.vmnet 1587.03.45
com.avast.PacketForwarder 2.1
com.avast.FileShield 4.0.0
@filesystems.smbfs 3.4.2
@fileutil 20.036.15
>!ATopCaseHIDEventDriver 3430.1
>AGPM 111.4.4
>!APlatformEnabler 2.7.0d0
>X86PlatformShim 1.0.0
@filesystems.autofs 3.0
>!AHDA 283.15
>!AUpstreamUserClient 3.6.8
>!AMCCSControl 1.11
@kext.AMDFramebuffer 3.0.8
@kext.AMDRadeonX4000 3.0.8
@kext.AMDRadeonServiceManager 3.0.8
>!AGraphicsDevicePolicy 5.1.16
@AGDCPluginDisplayMetrics 5.1.16
>!AHV 1
|IOUserEthernet 1.0.1
|IO!BSerialManager 7.0.4f6
>pmtelemetry 1
@Dont_Steal_Mac_OS_X 7.0.0
>eficheck 1
@kext.AMD7000!C 3.0.8
>!ALPC 3.1
>!AThunderboltIP 3.1.4
>!A!ISlowAdaptiveClocking 4.0.0
>!AMGPUPowerControl 5.1.16
>!A!IMCEReporter 115
>AudioAUUC 1.70
>!U!SCoexistentDriver 489.101.1
|SCSITaskUserClient 422.101.1
>!AVirtIO 1.0
@filesystems.hfs.kext 522.100.5
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@filesystems.apfs 1412.101.1
@private.KextAudit 1.0
|!ABCM5701Ethernet 10.3.5
>AirPort.BrcmNIC 1400.1.1
>!AAHCIPort 341.0.2
>!AACPIButtons 6.1
>!AACPIEC 6.1
>!ARTC 2.0
>!AHPET 1.8
>!ASMBIOS 2.1
>!AAPIC 1.7
>!A!ICPUPowerManagementClient 222.0.0
$!AImage4 1
@nke.applicationfirewall 303
$TMSafetyNet 8
@!ASystemPolicy 2.0.0
>!A!ICPUPowerManagement 222.0.0
|EndpointSecurity 1
>!AMultitouchDriver 3440.1
>!AInputDeviceSupport 3440.8
>!AHS!BDriver 3430.1
>IO!BHIDDriver 7.0.4f6
>!AHIDKeyboard 209
@kext.triggers 1.0
>DspFuncLib 283.15
@kext.OSvKernDSPLib 529
>!ASMBus!C 1.0.18d1
@kext.AMDRadeonX4030HWLibs 1.0
|IOAccelerator!F2 438.4.5
@kext.AMDRadeonX4000HWServices 3.0.8
|IOAVB!F 840.3
>!ASSE 1.0
@!AGPUWrangler 5.1.16
@kext.AMDSupport 3.0.8
@!AGraphicsDeviceControl 5.1.16
>!AHDA!C 283.15
|IOHDA!F 283.15
>X86PlatformPlugin 1.0.0
>IOPlatformPlugin!F 6.0.0d8
|IOSlowAdaptiveClocking!F 1.0.0
>!ABacklightExpert 1.1.0
|IONDRVSupport 575.1
>!AGraphicsControl 5.1.16
|IOGraphics!F 575.1
@plugin.IOgPTPPlugin 840.3
|IOUSBMass!SClass 4.0.4
|Broadcom!BHost!CUSBTransport 7.0.4f6
|IO!BHost!CUSBTransport 7.0.4f6
|IO!BHost!CTransport 7.0.4f6
|IO!B!F 7.0.4f6
|IO!BPacketLogger 7.0.4f6
>!UAudio 322.2
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>usb.!UHub 1.2
|IOAudio!F 300.2
@vecLib.kext 1.2.0
|IOSerial!F 11
|IOSurface 269.11
@filesystems.hfs.encodings.kext 1
>!AThunderboltDPInAdapter 6.2.6
>!AThunderboltDPAdapter!F 6.2.6
>!AThunderboltPCIDownAdapter 2.5.4
|IOAHCIBlock!S 316.100.5
>!AThunderboltNHI 5.8.6
|IOThunderbolt!F 7.6.0
|IOEthernetAVB!C 1.1.0
|IO80211!F 1200.12.2b1
>mDNSOffloadUserClient 1.0.1b8
>corecapture 1.0.4
|IOSkywalk!F 1
|IOAHCI!F 290.0.1
>usb.!UEHCIPCI 1.2
>usb.!UEHCI 1.2
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
|IOUSB!F 900.4.2
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
|IOSMBus!F 1.1
|IOHID!F 2.0.0
$quarantine 4
$sandbox 300.0
@Kext.!AMatch 1.0.0d1
>DiskImages 493.0.0
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!AKeyStore 2
>!UTDM 489.101.1
|IOSCSIBlockCommandsDevice 422.101.1
>!ACredentialManager 1.0
>KernelRelayHost 1
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
|IOUSBMass!SDriver 157.101.3
|IOSCSIArchitectureModel!F 422.101.1
|IO!S!F 2.1
|IOUSBHost!F 1.2
>!UHostMergeProperties 1.2
>usb.!UCommon 1.0
>!ABusPower!C 1.0
|CoreAnalytics!F 1
>!AMobileFileIntegrity 1.0.5
@kext.CoreTrust 1
|IOTimeSync!F 840.3
|IONetworking!F 3.4
|IOReport!F 47
>!AACPIPlatform 6.1
>!ASMC 3.1.9
>watchdog 1
|IOPCI!F 2.9
|IOACPI!F 1.4
@kec.pthread 1
@kec.corecrypto 1.0
@kec.Libm 1

 

[tommiy]

I just noticed that there is a thread on Apple Communities with many pages of responses related to this particular issue. Hopefully it may attract apples attention to fix in 10.16. Seems from the 10.15.5 page that the problem still persists there.

 

[jandrisani]

Late 2012 Mac Mini running headless 24/7/365 as a media server. It has been crashing daily for months with the same "userspace watchdog timeout" kernel panic. I've done everything in this thread... SMC, power settings, DND, etc etc. Nothing worked. Ran hardware tests, disk checks, everything I could think of. Was about to punt and just buy a new mini.

I downloaded Kext Wizard and ran Repair Permissions and Rebuild Cache on kernel extensions and it has been up for 14 days straight now with no issues. Knock on wood.

 

[aspromatis]

Disabling 'Put hard disks to sleep when possible' in System Preferences seems to help on my end. I have tried most of the other solutions proposed as well and kept letting Panics. Think this requires multiple tactics.

 

[GDubya3]

I'm getting the same type panics with a MacBook Pro (15-inch, 2018), 2.9 GHz 6-Core Intel Core i9, with Radeon Pro Vega 20 4 GB/ Intel UHD Graphics 630 1536 MB.

I've been able to decrease but not eliminate the freeze up by not using the Caldigit T3 I have as a power source (as well as for an external display, a RAID and other peripherals).

While powering the system with the standard power cable, I seem only to get rashes of crashes. Regularly, irregular bunches still.

This is pretty a pretty brutal issue, thanks y'all for sharing the work arounds.

 

[Jacob Roy]

Since I ran a Repair Permissions and Rebuild Kernel Cache, I've had no crashes.
I've also changed the default keychain, and disabled 'Put hard disks to sleep when possible' yesterday.
Last week and Monday, I was averaging 4 crashes/day, and I had none since Tuesday morning when I ran repair permissions and rebuild kernel cache.

I advise to try the Repair & Rebuild, it's a non-destructive action and is what I beleive fixed my problem on my mid-2015 15'' Macbook Pro on 10.15.5.

 

[daveytheg]

Every time the wifi stops working for 30 seconds and the fans produce an audible hiss once it crashes.

 

[IAMDAVE1969]

I think I solved it on my 16" MacBook Pro.

-Turned off PowerNap for both Battery and Power Adapter in Energy Saver Preferences
-Turned off Put Hard Disks to Sleep when Possible Energy Saver Preferences
-Entered Recovery Mode, ran First Aid in Disk Utility
-Entered Recovery Mode and performed a clean reinstall of Mac OS Catalina 10.15.4
-Installed Mac OS Catalina 10.15.5 Public Beta 4

No crashes for two days now. Fingers crossed.

 

[Jacob Roy]

After almost a week without crashes, my 2015 15" Macbook Pro started to crash every 5 minutes this morning.

I tried every thing that worked in the past (Repair Disk, Repair Permissions, Rebuild Kernel Cache, Turned off powernap / Put Hard disk to sleep) but this time it doesn't work anymore...

 

[CMMChris]

Was using my Hackintosh with the Radeon VII for three Betas now and had it running for weeks without rebooting and no kernel panics. Now put back in my RX 5700 XT for testing. Result of second sleep / wake cycle I did:

That is with the latest 10.15.5 Dev Beta 5. Retards...

 

[roderik]

Not sure what did it but this worked:

- disk permission fix -> nothing found so probably not it
- kext permission fix -> nothing found so probably not it
- Disabling 'Put hard disks to sleep when possible' -> and now it stays up as wxpected

 

[CMMChris]

Here we go again. Wake from sleep, starting hardware decoding / encoding process, freeze, kernel panic. (RX 5700 XT)

Need to put my Radeon VII back in... Navi drivers are just **** like on first day of support (October 2019). FU Apple.

 

[bug]

Just to add my data to the conversation:

I have a 2018 Mac mini with a 5700XT in an eGPU. This problem happened to me on occasion months ago, and then seemed to go away for a while with 10.15.3.

Suddenly it started happening again a lot. It seemed to be when I added a 3rd screen to my setup. Previously I had one hooked up to the 5700XT via DisplayPort and one via HDMI. Now I have 2 via DisplayPort and 1 via HDMI. Note that the 2 original screens were Dells and the new one is an LG (unlikely to matter, but hey, its information).

...I haven't done a lot of testing to see if this was specifically the issue but I'll try a few things and see what changes.

For the record I never had Power Nap turned on with this machine as it caused me problems with previous computers.

In my case, while the error is the same, I see slightly different behaviour in that all three screens come on when coming out of sleep, then the LG goes to sleep again. Sometimes the computer will survive for a minute or two after this but eventually it panics and reboots.

 

[bug]

...and after having read this entire thread, fixing my Kext and turning off 'put hard disks to sleep when possible', it panicked at literally the next sleep. So those things didn't seem to do anything.