Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

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

roderik said:
It worked for a while, but alas. Currently thinking Docker For Mac might be the (an additional) culprit: https://forums.macrumors.com/threads/big-sur-working-not-working-apps.2242312/post-28745096
Click to expand...

I have it installed, but don't let it start on boot, and don't run it normally. Same KPs on a 2014 MBP and 2012 Mac Mini on 10.5.6.

I have another 2017 MBP on 10.5.5 that does not seem to be experiencing the same issues, running 90% of the time with VMWare and External displays hooked up.
 
I'm facing the similar issue. Tried everything, fresh installation, disabled the sleep mode, etc. I'm getting the kernel panics randomly, mostly when using the vmware fusion with windows 10 running. My configuration is a MacBook Pro 2019 i7, 16GB RAM, 1TB SSD with OWC dock connected through thunderbolt 3 + 38" Monitor. I've tried to reconnect the OWC dock to a different thunderbolt port 3 days ago and i didn't receive any kernel panic since.

Anyway, it's a shame that Apple didn't respond in timely manner with a proper sw patch/hw replacement. They're even not able to identify the source. I've gone through the various forums and it looks like this issue is there since January 2019, it's more than a year and some users reported that the Mojave is affected as well. Better to have a backup PC/Laptop around with a different OS.

ARM Silicon, new APIs, ARM emulation, bash to zsh migration and any other useless crap... but the basic features simply don't work. Same for Windows, they're constantly feeding us with useless stuff, start menu is different every major release. Looks like a development teams have some mental disorder.
 
  • Like
Reactions: johnalan and Buadhai
2014 10.15.6 MBP KP'd again last night - This machine runs 2 debian VMs
I keep a thunderbolt cable and hdmi hooked up to it
I reset pram this morning before booting it back up.

2012 Mac Mini - Uptime 1 day - I leave an hdmi cable hooked up to it
This machine runs 3 debian VMs and a Windows 10 VM

2017 MBP 10.15.5 - I leave a USB-C dongle + hdmi hookup attached to it.
This machine runs a Windows 10 VM constantly.

I also have a 2015 10.15.4 MBP that hasn't experience a single KP, and it runs 3 debian vms constantly.

All 4 of these machines have been upgraded from a previous MacOS versions. No clean Catalina installs. All 4 run VMWare and VBox. But mainly VMware.

10.15.5 uptime on the 2017 MBP is 13 days.


Process: WindowServer [299]
Path: /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer
Identifier: WindowServer
Version: 600.00 (451.4)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: WindowServer [299]
User ID: 88

Date/Time: 2020-08-06 05:34:06.732 -0500
OS Version: Mac OS X 10.15.6 (19G73)
Report Version: 12
Anonymous UUID: 6ED228C4-3852-030B-19CE-5007CE7E8135


Time Awake Since Boot: 150000 seconds

System Integrity Protection: enabled

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

Exception Type: EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: WATCHDOG, [0x1] monitoring timed out for service
Termination Details: WATCHDOG, checkin with service: WindowServer returned not alive with context:
unresponsive work processor(s): WindowServer main thread
40 seconds since last successful checkin, 15621 total successsful checkins since load (0 induced crashes)
 
It sounds like some people are having problems related to their virtual machine software. I'm not running any Virtual Machine software, and had another reboot and "userspace watchdog timeout: no successful checkins from com.apple.WindowServer" error message today.

I suspect that it's related to my Razer eGPU . Previously I had the eGPU connected to the TB3 port on my CalDigit Doc. I moved it to the left rear TB3 power on my MacBook, so it has it's own port now. That apparently didn't fix the issue.
 
I get this every few days on a late 2014 Mac Mini (the one with the nearly impossible to replace hard drive) - Completely Headless unit running as a server. It resets itself every 3-4 days with this:

panic(cpu 2 caller 0xffffff7f81cfaad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds

I'm on 10.15.6
 
I am getting this on a 2018 15 inch mbp running 10.15.6. I am not using any virtual machine, no monitor, nothing.

I see WindowServer error in my case, but this

Code: 
panic(cpu 2 caller 0xffffff7f8f9a1aae): watchdog timeout: no checkins from watchdogd in 310 seconds (176 totalcheckins since monitoring last enabled), shutdown in progress
Backtrace (CPU 2), Frame : Return Address
0xffffff83b7d73c40 : 0xffffff800ef1a65d
0xffffff83b7d73c90 : 0xffffff800f054a75
0xffffff83b7d73cd0 : 0xffffff800f0465fe
0xffffff83b7d73d20 : 0xffffff800eec0a40
0xffffff83b7d73d40 : 0xffffff800ef19d27
0xffffff83b7d73e40 : 0xffffff800ef1a117
0xffffff83b7d73e90 : 0xffffff800f6c1b28
0xffffff83b7d73f00 : 0xffffff7f8f9a1aae
0xffffff83b7d73f10 : 0xffffff7f8f9a1486
0xffffff83b7d73f50 : 0xffffff7f8f9b6d9c
0xffffff83b7d73fa0 : 0xffffff800eec013e
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[832CC890-EE61-33E0-8FD4-8D354BCD0921]@0xffffff7f8f9a0000->0xffffff7f8f9a8fff
         com.apple.driver.AppleSMC(3.1.9)[AB612149-B321-3B95-8741-B99E79274FCD]@0xffffff7f8f9a9000->0xffffff7f8f9c7fff
            dependency: com.apple.driver.watchdog(1)[832CC890-EE61-33E0-8FD4-8D354BCD0921]@0xffffff7f8f9a0000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[68557A36-4EE1-372A-983B-BB2769FDB8E0]@0xffffff7f8f909000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[B130A8B7-967F-330E-942F-E0BB93C71C56]@0xffffff7f8f912000

Crash happens only when I shut down at end of day. It reboots itself. Then it will shutdown properly.

Tried everything, smc/nvram reset, combo update, no luck.

Apple support says reinstall, but others have not had luck with this also. waste of time.
 
cfdlab said:
I am getting this on a 2018 15 inch mbp running 10.15.6. I am not using any virtual machine, no monitor, nothing.

I see WindowServer error in my case, but this

Code: 
panic(cpu 2 caller 0xffffff7f8f9a1aae): watchdog timeout: no checkins from watchdogd in 310 seconds (176 totalcheckins since monitoring last enabled), shutdown in progress
Backtrace (CPU 2), Frame : Return Address
0xffffff83b7d73c40 : 0xffffff800ef1a65d
0xffffff83b7d73c90 : 0xffffff800f054a75
0xffffff83b7d73cd0 : 0xffffff800f0465fe
0xffffff83b7d73d20 : 0xffffff800eec0a40
0xffffff83b7d73d40 : 0xffffff800ef19d27
0xffffff83b7d73e40 : 0xffffff800ef1a117
0xffffff83b7d73e90 : 0xffffff800f6c1b28
0xffffff83b7d73f00 : 0xffffff7f8f9a1aae
0xffffff83b7d73f10 : 0xffffff7f8f9a1486
0xffffff83b7d73f50 : 0xffffff7f8f9b6d9c
0xffffff83b7d73fa0 : 0xffffff800eec013e
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[832CC890-EE61-33E0-8FD4-8D354BCD0921]@0xffffff7f8f9a0000->0xffffff7f8f9a8fff
         com.apple.driver.AppleSMC(3.1.9)[AB612149-B321-3B95-8741-B99E79274FCD]@0xffffff7f8f9a9000->0xffffff7f8f9c7fff
            dependency: com.apple.driver.watchdog(1)[832CC890-EE61-33E0-8FD4-8D354BCD0921]@0xffffff7f8f9a0000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[68557A36-4EE1-372A-983B-BB2769FDB8E0]@0xffffff7f8f909000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[B130A8B7-967F-330E-942F-E0BB93C71C56]@0xffffff7f8f912000

Crash happens only when I shut down at end of day. It reboots itself. Then it will shutdown properly.

Tried everything, smc/nvram reset, combo update, no luck.

Apple support says reinstall, but others have not had luck with this also. waste of time.
Click to expand...

One thing you could try is creating a new Container in Disk Utility and clean install Catalina to the new Container. Restart to the new install (leave it clean) and see if the issue happens with a clean install. When you are done boot back to old install and remove the new Container.
 
  • Like
Reactions: star-affinity
IAmArney said:
I can, so far it’s only two and they may be specific to my configuration. But I suspect the list will go on as list 1 concluded in normal KP activity and list 2 is my normal set-up which has resulted in KP’s
For the last week.

Since this issue happens over-night for me, I basically set-up the task, pass out and report in the AM.


close apps
Nvram reset
Pram reset
SMC reset
Unplug external display
Plugged into power, on and lid open

close apps
Nvram reset
Pram reset
SMC reset
Plug-in external display
Plugged into power, on and lid open

I assume we’ll run this routine through each peripheral device until we find or don’t find the culprit.
Click to expand...

an SMC and Nvram/Pram Reset with my external display plugged in has seemed to do the trick for me. Apple got back to me asking to remove Dropbox.kext, UAD2System.kext and UAFWaudio.kext. Unfortunately, the later 2 removed my ability to use my audio interface which doesn't give the computer much use for me so I reinstalled the software.

Been KP free for about a week now.

If you are having this issue please get in touch with Apple and do everything you can to escalate the issue to a Senior Advisor. at the very least they should be able to help bridge the gap between you and Apple Engineering. The individual I worked with has kept my case open to help further diagnose what was causing the problem for me.
 
This is happening on my 2019 27" iMac with Catalina 10.15.6, twice in the last two days, both times while I was away from the computer. No analysis yet but I have sent a report to Apple. If its GPU related then it might be Lightroom in my case. I have Virtualbox VM but not running atm.
 
  • Like
Reactions: jagooch
PhilDN said:
This is happening on my 2019 27" iMac with Catalina 10.15.6, twice in the last two days, both times while I was away from the computer. No analysis yet but I have sent a report to Apple. If its GPU related then it might be Lightroom in my case. I have Virtualbox VM but not running atm.
Click to expand...

Could be the kernel extension that causes the crashes, so it might not be relevant wether Virtual Box is actually running or not. If you don't depend on it you could try to temporarily uninstall it.
 
I have a brand new 16" MBP (purchased in April) and actually JUST started being affected by the no successful checkins problem and a complete system freeze. Gaining back control of the system requires a power cycle or the system may just shut down on its own. But, of course, the problem happens again.

I noticed in my case that the problem happens when the computer attempts to sleep while running on battery power. If the computer is running on AC power, it's able to transition to the screen saver without issue and readily awakes when swiping the touchpad (for the power adapter setting, I have it configured prevent sleep when display is off and the display shuts off after 3 hours, but screen saver triggers after 20 min of inactivity).

In my limited experience with this problem, I think I just started noticing the issue because I usually have my MBP running on AC power set to switch to screen saver after 20 minutes. And when I am running battery power and not actively using the machine, I close the lid and the machine sleeps just fine and awakes as expected when re-opening the lid.

When I inadvertently left the machine to sleep while it was running on battery power, this new problem, which seems to have been around for a while now, started happening. If I do what I normally do, there's no problem. I'd be interested if others could re-produce this problem as I described it. Obviously Apple needs to fix this, but if a slight usage change is possible, it's worth it to avoid the headache.
 
ssv2 said:
I have a brand new 16" MBP (purchased in April) and actually JUST started being affected by the no successful checkins problem and a complete system freeze. Gaining back control of the system requires a power cycle or the system may just shut down on its own. But, of course, the problem happens again.

I noticed in my case that the problem happens when the computer attempts to sleep while running on battery power. If the computer is running on AC power, it's able to transition to the screen saver without issue and readily awakes when swiping the touchpad (for the power adapter setting, I have it configured prevent sleep when display is off and the display shuts off after 3 hours, but screen saver triggers after 20 min of inactivity).

In my limited experience with this problem, I think I just started noticing the issue because I usually have my MBP running on AC power set to switch to screen saver after 20 minutes. And when I am running battery power and not actively using the machine, I close the lid and the machine sleeps just fine and awakes as expected when re-opening the lid.

When I inadvertently left the machine to sleep while it was running on battery power, this new problem, which seems to have been around for a while now, started happening. If I do what I normally do, there's no problem. I'd be interested if others could re-produce this problem as I described it. Obviously Apple needs to fix this, but if a slight usage change is possible, it's worth it to avoid the headache.
Click to expand...

Catalina is *******.
 
kenny113 said:
Yeah, same thing as it has always been for me unfortunately... Watchdog timeout on shutdown/reboot (seemingly only if the iMac has been in use for ~20+ min).

Code: 
"Stackshot source : disk","macOSPanicString":"panic(cpu 1 caller 0xffffff7f9504faae): watchdog timeout: no checkins from watchdogd in 304 seconds (51 totalcheckins since monitoring last enabled), shutdown in progress
Backtrace (CPU 1), Frame : Return Address
0xffffff82d2953c40 : 0xffffff8013f215cd
0xffffff82d2953c90 : 0xffffff801405a3c5
0xffffff82d2953cd0 : 0xffffff801404bf7e
0xffffff82d2953d20 : 0xffffff8013ec7a40
0xffffff82d2953d40 : 0xffffff8013f20c97
0xffffff82d2953e40 : 0xffffff8013f21087
0xffffff82d2953e90 : 0xffffff80146c2ce8
0xffffff82d2953f00 : 0xffffff7f9504faae
0xffffff82d2953f10 : 0xffffff7f9504f486
0xffffff82d2953f50 : 0xffffff7f95064d9c
0xffffff82d2953fa0 : 0xffffff8013ec713e
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[99A75EFF-7734-31A0-80BF-FF8288E30D9B]@0xffffff7f9504e000->0xffffff7f95056fff
         com.apple.driver.AppleSMC(3.1.9)[601E041E-0A5C-3B6A-A4E6-45ECC7F48A2B]@0xffffff7f95057000->0xffffff7f95075fff
            dependency: com.apple.iokit.IOACPIFamily(1.4)[9D1FF279-C4A2-3344-902F-E0B22B508689]@0xffffff7f95045000
            dependency: com.apple.driver.watchdog(1)[99A75EFF-7734-31A0-80BF-FF8288E30D9B]@0xffffff7f9504e000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f94931000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
19E266

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:     0x0000000013c00000
Kernel text base: 0xffffff8013e00000
__HIB  text base: 0xffffff8013d00000
System model name: iMac15,1 (Mac-42FD25EABCABB274)
System shutdown begun: YES
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 810719675669
last loaded kext at 479161928387: @filesystems.afpfs\t11.2
Click to expand...


Ever get anywhere with this?
 
cinaplenrek said:
Brand new Mac Mini, fresh install of 10.15.4 (19E266). Restarted the thing twice so far and on each one of them I got the kernel panic. The behaviours is that it stays a while on a "black screen".

The panic looks similar to everyone elses. This is pretty ridiculous, there's nothing on the machine as I just unpacked it and installed the OS update.

Code: 
panic(cpu 2 caller 0xffffff7f879a0aae): watchdog timeout: no checkins from watchdogd in 301 seconds (4210 totalcheckins since monitoring last enabled), shutdown in progress
Backtrace (CPU 2), Frame : Return Address
0xffffff83aff2bc40 : 0xffffff8006f215cd
0xffffff83aff2bc90 : 0xffffff800705a3c5
0xffffff83aff2bcd0 : 0xffffff800704bf7e
0xffffff83aff2bd20 : 0xffffff8006ec7a40
0xffffff83aff2bd40 : 0xffffff8006f20c97
0xffffff83aff2be40 : 0xffffff8006f21087
0xffffff83aff2be90 : 0xffffff80076c2ce8
0xffffff83aff2bf00 : 0xffffff7f879a0aae
0xffffff83aff2bf10 : 0xffffff7f879a0486
0xffffff83aff2bf50 : 0xffffff7f879b5d9c
0xffffff83aff2bfa0 : 0xffffff8006ec713e
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[99A75EFF-7734-31A0-80BF-FF8288E30D9B]@0xffffff7f8799f000->0xffffff7f879a7fff
         com.apple.driver.AppleSMC(3.1.9)[601E041E-0A5C-3B6A-A4E6-45ECC7F48A2B]@0xffffff7f879a8000->0xffffff7f879c6fff
            dependency: com.apple.driver.watchdog(1)[99A75EFF-7734-31A0-80BF-FF8288E30D9B]@0xffffff7f8799f000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[9D1FF279-C4A2-3344-902F-E0B22B508689]@0xffffff7f87908000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f87911000

BSD process name corresponding to current thread: kernel_task
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
19E266

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:     0x0000000006c00000
Kernel text base: 0xffffff8006e00000
__HIB  text base: 0xffffff8006d00000
System model name: Macmini8,1 (Mac-7BA5B2DFE22DDD8C)
System shutdown begun: YES

System uptime in nanoseconds: 42386957787901
last loaded kext at 40688957856515: @filesystems.smbfs    3.4.2 (addr 0xffffff7f8b2fb000, size 450560)
last unloaded kext at 31637755178551: >!UAudio    322.2 (addr 0xffffff7f8afe5000, size 434176)
loaded kexts:
@filesystems.smbfs    3.4.2
>!ATopCaseHIDEventDriver    3430.1
>!UTopCaseDriver    3430.1
>AudioAUUC    1.70
>!AGraphicsDevicePolicy    5.1.16
@fileutil    20.036.15
@AGDCPluginDisplayMetrics    5.1.16
>!AHV    1
|IOUserEthernet    1.0.1
|IO!BSerialManager    7.0.4f6
>!AUpstreamUserClient    3.6.8
>!APlatformEnabler    2.7.0d0
>AGPM    111.4.4
>X86PlatformShim    1.0.0
>pmtelemetry    1
>!AMCCSControl    1.11
@Dont_Steal_Mac_OS_X    7.0.0
>!A!IKBLGraphics    14.0.5
>!AThunderboltIP    3.1.4
>BridgeAudioCommunication    6.70.3
>!A!ICFLGraphicsFramebuffer    14.0.5
>!ABridgeAudio!C    6.70.3
>!AGFXHDA    100.1.426
>!A!IPCHPMC    2.0.1
>!A!ISlowAdaptiveClocking    4.0.0
>!AAVEBridge    6.1
@filesystems.autofs    3.0
>!U!SCoexistentDriver    489.101.1
>BCMWLANFirmware4355.Hashstore    1
>BCMWLANFirmware4364.Hashstore    1
>BCMWLANFirmware4377.Hashstore    1
@filesystems.hfs.kext    522.100.5
@BootCache    40
@!AFSCompression.!AFSCompressionTypeDataless    1.0.0d1
@!AFSCompression.!AFSCompressionTypeZlib    1.0.0
>!AVirtIO    1.0
|!ABCM5701Ethernet    10.3.5
>!ABCMWLANBusInterfacePCIe    1
@filesystems.apfs    1412.101.1
@private.KextAudit    1.0
>!AACPIButtons    6.1
>!ASMBIOS    2.1
>!AACPIEC    6.1
>!AAPIC    1.7
$!AImage4    1
@nke.applicationfirewall    303
$TMSafetyNet    8
@!ASystemPolicy    2.0.0
|EndpointSecurity    1
>!AXsanScheme    3
>!A!BHIDKeyboard    209
>!AHS!BDriver    3430.1
>IO!BHIDDriver    7.0.4f6
>!AActuatorDriver    3440.1
>usb.IOUSBHostHIDDevice    1.2
>!AMultitouchDriver    3440.1
>!AInputDeviceSupport    3440.8
>!AHIDKeyboard    209
>!UAudio    322.2
>!AGraphicsControl    5.1.16
|IOAVB!F    840.3
>!ASSE    1.0
>!ASMBus!C    1.0.18d1
@!AGPUWrangler    5.1.16
@!AGraphicsDeviceControl    5.1.16
|IOAccelerator!F2    438.4.5
>X86PlatformPlugin    1.0.0
|IONDRVSupport    575.1
|IOGraphics!F    575.1
|IO!BHost!CUARTTransport    7.0.4f6
|IO!BHost!CTransport    7.0.4f6
>!A!ILpssUARTv1    3.0.60
>!A!ILpssUARTCommon    3.0.60
>!AOnboardSerial    1.0
>IOPlatformPlugin!F    6.0.0d8
|IOSlowAdaptiveClocking!F    1.0.0
@plugin.IOgPTPPlugin    840.3
@kext.triggers    1.0
|IOUSBMass!SClass    4.0.4
>usb.cdc.ncm    5.0.0
>usb.cdc    5.0.0
>usb.networking    5.0.0
>usb.!UHostCompositeDevice    1.2
|IOSurface    269.11
@filesystems.hfs.encodings.kext    1
|IOAudio!F    300.2
@vecLib.kext    1.2.0
|IOEthernetAVB!C    1.1.0
>!ABCMWLANCore    1.0.0
>mDNSOffloadUserClient    1.0.1b8
>IOImageLoader    1.0.0
|IOSerial!F    11
|IO80211!FV2    1200.12.2b1
>corecapture    1.0.4
|IOSkywalk!F    1
>!AThunderboltPCIDownAdapter    2.5.4
>!AThunderboltDPInAdapter    6.2.6
>!AThunderboltDPAdapter!F    6.2.6
>!AHPM    3.4.4
>!A!ILpssI2C!C    3.0.60
>!A!ILpssDmac    3.0.60
>!A!ILpssI2C    3.0.60
>!AThunderboltNHI    5.8.6
|IOThunderbolt!F    7.6.0
>usb.!UVHCIBCE    1.2
>usb.!UVHCI    1.2
>usb.!UVHCICommonBCE    1.0
>usb.!UVHCICommon    1.0
>!AEffaceableNOR    1.0
|IOBufferCopy!C    1.1.0
|IOBufferCopyEngine!F    1
|IONVMe!F    2.1.0
|IOUSB!F    900.4.2
>usb.!UXHCIPCI    1.2
>usb.!UXHCI    1.2
>!AEFINVRAM    2.1
>!AEFIRuntime    2.1
>!ASMCRTC    1.0
|IOSMBus!F    1.1
|IOHID!F    2.0.0
$quarantine    4
$sandbox    300.0
@kext.!AMatch    1.0.0d1
>!AKeyStore    2
>!UTDM    489.101.1
|IOSCSIBlockCommandsDevice    422.101.1
>!ACredentialManager    1.0
>KernelRelayHost    1
>!ASEPManager    1.0.1
>IOSlaveProcessor    1
>!AFDEKeyStore    28.30
>!AEffaceable!S    1.0
>!AMobileFileIntegrity    1.0.5
@kext.CoreTrust    1
|CoreAnalytics!F    1
|IOTimeSync!F    840.3
|IONetworking!F    3.4
>DiskImages    493.0.0
|IO!B!F    7.0.4f6
|IO!BPacketLogger    7.0.4f6
|IOUSBMass!SDriver    157.101.3
|IOSCSIArchitectureModel!F    422.101.1
|IO!S!F    2.1
|IOUSBHost!F    1.2
>usb.!UCommon    1.0
>!UHostMergeProperties    1.2
>!ABusPower!C    1.0
|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
Click to expand...


Exactly the same issue as you.
 
My 2012 Mac Mini Server has been running on Catalina fine until I installed the 10.15.6 update, now it seems every 24-48 hours it crashes and I end up having to log back in. Same thing everytime: WatchdogD and WindowServer
 
Taz Mangus said:
One thing you could try is creating a new Container in Disk Utility and clean install Catalina to the new Container. Restart to the new install (leave it clean) and see if the issue happens with a clean install. When you are done boot back to old install and remove the new Container.
Click to expand...

This sounds like a great way to try a clean install without having to erase the drive. I'll give that a go I think.
 
monstermac77 said:
I got the following message from the Apple Support Forums, saying that they're about to delete my account if I keep posting something that is very reasonable: the way I've been able to reproduce this issue (which is an essential part of discovering a fix for the bug and testing when the bug has been fixed).

Can you contact the moderators for me and have them approve this message?
Click to expand...

Apple Support Forums are pretty much trash in my experience. Lots of gatekeeping, lots of territorial troll behavior. I tend to come to the MacRumors forums instead -- just tends to be a lot more productive, frankly.
 
  • Like
Reactions: monstermac77, Kenjutsuz, bug and 1 other person
star-affinity said:
I wonder if the just released supplemental update will help for the watchdog timeout too?
Click to expand...

I really hope so. The watchdog timeout has been killing my 2018 Mini. I run no virtualization software whatsoever, so it was disappointing to see only that mentioned in the release notes.
 
I am anxious to even write this, but macOS Big Sur beta 4 has resolved my issues with panics. I updated and haven’t had a panic since updating. To recap - I had a 2018 Mac mini that would panic on any software after 10.15.4.
 
  • Like
  • Wow
Reactions: johnalan and Silverstring
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back