Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Update from me:
It was getting way worse, the whole partition gets deactivated. Guessed it was hardware than since my bootcamp was freezing too. I went to a doc and there was nothing found. Clean installed mojave - counting days without any hint of a crash now.
 
Update having received my machine back from repair...

  • The Job Sheet shows that the logic board and Touch Bar was replaced.
  • It came back yesterday, with 10.15.1 installed. No panics.
  • I've since updated to 10.15.6. No panics, so far.
Recap: I originally had just the "PowerPlay Failed Resume" panic when waking from sleep, then started getting the "userspace watchdog timeout" panics at random during normal use, then started getting "PowerPlay failed to Initialize" at startup, and eventually the machine failed to boot entirely, even from a clean formatted install of 10.15.6. My machine passed the on-board hardware diagnostics test every time, yet still the above issues persisted.

It took 4 calls with Apple support (approx 6hrs on phone in total) plus 10's of hours of attempted fixes to finally get apple to accept the machine for repair. There was significant confusion it seems between these separate issues. However once they received the machine they issued a logic board replacement immediately.

If anyone reading this is getting a "PowerPlay failed to initialise" panic I'd strongly suggest not wasting your time on attempted fixes related to other powerplay issues.

To fully confirm if hardware is the issue, once you've backed everything up (as you will have to do in order to return it to service), perform a clean formatted install of 10.15.6 (using either USB or internet recovery method) and if it panics during boot (before you've installed any 3rd party software) then your issue was the same as mine and Apple should repair or replace your machine.

If the issues resurface, I'll update, but obviously hoping this is behind me now. Good luck to all others getting your issues resolved.
 
  • Like
Reactions: star-affinity
I've now started to have these issues with 10.15.6. First started a week ago etc

What is with this operating system? - Same issue as y'all with the WindowServer kernel panics.
 
Catalina 10.15.6 (19G73), 2018 15" MBP plugged into my external display. I have been having issues with the display randomly waking back up in 30Hz mode instead of 60Hz mode, set by the computer. (The monitor's menu clearly states it is capable of 4K at 60Hz but is only getting 4K at 30Hz). Finally I option+clicked on 'Scaled' in SysPrefs>Displays to show the non-Retina resolutions. This worked the first time, but yesterday it happened again and I had to use DisplayMenu to over-ride it. This yielded a really blurry image for some reason, but after I set it in DisplayMenu, going back into SysPrefs and doing the Option+Click fixed it.

Fast forward to right now and I could not get the machine to wake up while in clamshell mode. Opened it up and was greeted by the Apple logo.

Code:
panic(cpu 4 caller 0xffffff7f94da1ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since wake (130 seconds ago): 14, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since wake (130 seconds ago): 2, last successful checkin: 120 seconds ago

Backtrace (CPU 4), Frame : Return Address
0xffffff9239293720 : 0xffffff801431a65d
0xffffff9239293770 : 0xffffff8014454a75
0xffffff92392937b0 : 0xffffff80144465fe
0xffffff9239293800 : 0xffffff80142c0a40
0xffffff9239293820 : 0xffffff8014319d27
0xffffff9239293920 : 0xffffff801431a117
0xffffff9239293970 : 0xffffff8014ac1b28
0xffffff92392939e0 : 0xffffff7f94da1ad5
0xffffff92392939f0 : 0xffffff7f94da17fa
0xffffff9239293a10 : 0xffffff8014a539ce
0xffffff9239293a60 : 0xffffff7f94da0cfe
0xffffff9239293b60 : 0xffffff8014a5cbf3
0xffffff9239293ca0 : 0xffffff80144035e2
0xffffff9239293db0 : 0xffffff80143203c8
0xffffff9239293e10 : 0xffffff80142f6d15
0xffffff9239293e70 : 0xffffff801430db22
0xffffff9239293f00 : 0xffffff801442c065
0xffffff9239293fa0 : 0xffffff80142c1226
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[832CC890-EE61-33E0-8FD4-8D354BCD0921]@0xffffff7f94da0000->0xffffff7f94da8fff

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

Mac OS version:
19G73

Kernel version:
Darwin Kernel Version 19.6.0: Sun Jul  5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64
Kernel UUID: 783946EA-6F11-3647-BF90-787AEA14B954
Kernel slide:     0x0000000014000000
Kernel text base: 0xffffff8014200000
__HIB  text base: 0xffffff8014100000
System model name: MacBookPro15,1 (Mac-937A206F2EE63C01)
System shutdown begun: NO

System uptime in nanoseconds: 56182701383882
last loaded kext at 56087032308455: >!AXsanScheme    3 (addr 0xffffff7f986d3000, size 32768)
last unloaded kext at 53972495896244: >AudioAUUC    1.70 (addr 0xffffff7f986d3000, size 20480)
loaded kexts:
com.intel.driver.EnergyDriver    2.0
>usb.!UHostBillboardDevice    1.0
@filesystems.smbfs    3.4.4
@kext.AMDFramebuffer    3.1.0
@kext.AMDRadeonX4000    3.1.0
@kext.AMDRadeonServiceManager    3.1.0
>!AGraphicsDevicePolicy    5.2.6
@fileutil    20.036.15
@AGDCPluginDisplayMetrics    5.2.6
>!AHV    1
|IOUserEthernet    1.0.1
|IO!BSerialManager    7.0.6f7
>pmtelemetry    1
>AGPM    111.4.4
>!APlatformEnabler    2.7.0d0
>X86PlatformShim    1.0.0
@Dont_Steal_Mac_OS_X    7.0.0
>!AUpstreamUserClient    3.6.8
>AGDCBacklightControl    5.2.6
>!A!IKBLGraphics    14.0.7
>!AThunderboltIP    3.1.4
@kext.AMD9500!C    3.1.0
>BridgeAudioCommunication    6.70.7
>!AHIDALSService    1
>!A!ISlowAdaptiveClocking    4.0.0
>!AMuxControl2    5.2.6
>!AMCCSControl    1.14
>!ATopCaseHIDEventDriver    3430.1
>!ABridgeAudio!C    6.70.7
>!AGFXHDA    100.1.429
>!A!IPCHPMC    2.0.1
>!A!ICFLGraphicsFramebuffer    14.0.7
>!AAVEBridge    6.1
@filesystems.autofs    3.0
>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
>!ABCMWLANBusInterfacePCIe    1
@filesystems.apfs    1412.141.1
@private.KextAudit    1.0
>!ASmartBatteryManager    161.0.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
>usb.IOUSBHostHIDDevice    1.2
>!UAudio    323.4
@plugin.IOAVBDiscoveryPlugin    850.1
@kext.AMDRadeonX4100HWLibs    1.0
@kext.AMDRadeonX4000HWServices    3.1.0
|IOAVB!F    850.1
@!AGPUWrangler    5.2.6
>!ABacklightExpert    1.1.0
>!AActuatorDriver    3440.1
>X86PlatformPlugin    1.0.0
|IOSlowAdaptiveClocking!F    1.0.0
>!AGraphicsControl    5.2.6
>!ASMBus!C    1.0.18d1
>!AHIDKeyboard    209
>!AHS!BDriver    3430.1
>IO!BHIDDriver    7.0.6f7
>!AMultitouchDriver    3440.1
>!AInputDeviceSupport    3440.8
|IONDRVSupport    576.1
>IOPlatformPlugin!F    6.0.0d8
|IO!BHost!CUARTTransport    7.0.6f7
|IO!BHost!CTransport    7.0.6f7
>!A!ILpssUARTv1    3.0.60
>!A!ILpssUARTCommon    3.0.60
>!AOnboardSerial    1.0
@kext.AMDSupport    3.1.0
@!AGraphicsDeviceControl    5.2.6
|IOAccelerator!F2    438.7.3
|IOGraphics!F    576.1
@plugin.IOgPTPPlugin    840.3
|IOEthernetAVB!C    1.1.0
@kext.triggers    1.0
>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
>!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.1
|IOUSB!F    900.4.2
>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
>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.120.1
|IOSCSIBlockCommandsDevice    422.120.3
>!ACredentialManager    1.0
>!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.6f7
|IO!BPacketLogger    7.0.6f7
>!ASSE    1.0
>KernelRelayHost    1
>!ASEPManager    1.0.1
>IOSlaveProcessor    1
|IOUSBMass!SDriver    157.140.1
|IOSCSIArchitectureModel!F    422.120.3
|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
 
I'm getting this error since I updated my MiniLate2012 to 10.15.6 everytime a Windows10 VM is running in VMware Fusion 11.5. The Mini is headless with an HDMI dongle. Sleep and other stuff are disabled.
After some time the system is doing a self initiated restart. Was searching since one week now for the root cause.
Damn...

Mine is nearly the same configuration - late 2012 mac mini, 10.15.6, and headless with an HDMI dongle. I don't - however - run any virtualization on this machine. I thought (when I saw you were also using an HDMI dongle) that might be it - so I've unplugged it. Still get a reboot each day. Watchdogd.

I'm considering disabling SIP so I can disable watchdogd...but I don't know what other impact that might have. I really don't like the nightly reboot.
 
I don’t get crashes on my rMBP if I disconnect my external monitor. So everytime I work on it i have the cables for the monitor attached. If I let it sleep, I remove the cable and have zero crashes.
 
What USB-C cable/adapter are you using?


I don’t get crashes on my rMBP if I disconnect my external monitor. So everytime I work on it i have the cables for the monitor attached. If I let it sleep, I remove the cable and have zero crashes.
 
Im working with Apple now on an issue similar to everyone. I updated to 10.15.6 last week and every night my machine KP's. its strange though, half the times I arrive at my desk to find the machine off, not just sleeping at the log-in screen.

The KP's all revolve around the Watchdog and/or WindowServer timeout. but last night I closed all apps, did a Nvram & Pram reset, unplugged my USB-C to HDMI adapter, thus disconnecting my external display, left the MBP Plugged into power and the lid open and it still KP'd & shut down.

I have a list of things to try over the next few days and report to my apple advisor so we'll see... I should mention that "put hard discs to sleep" and "Enable Power Nap" are UNCHECKED, Auto Graphics Switching is UNCHECKED and the MBP is set to never sleep.

I have an interesting note as their first recommendation was to unplug the external display and see if it still happens, they mentioned that this kind of thing isn't normal, but connecting the dots between MacRumors and the information that was given to me it seems like they might be hiding that they are aware of this problem. Im probably just reading into that though.

BTW - this a 2019 16" MacBook Pro. Ive already had the logic Board replaced in April.
 
  • Like
Reactions: Guy Brush
Issue Description
I'm getting the panic message as well. It happens while I'm using the Mac, like today I was shopping online using Safari on external display, then I clicked on a youtube video in Safari on external display 2. The mouse got very laggy, with about 3 seconds from the time I moved it until the time it moved. I slowly did a Force Quit on Safari. At that point my Macbook Pro rebooted. It had the "you system was restarted message" when I logged back in.

I had been watching youtube video earlier today with no problem. But this time my system become unresponsive for some reason.

This has happened before, I but I didn't write log the event until today. I'm going to keep a log in case Apple needs it. Also, I'm going to set up a Genius Bar appointment to get Apple to look at it.

Specs:
* Laptop: MacBook Pro (16-inch, 2019) 32GB RAM/2TB SSD/2.4 GHz 8-Core Intel Core i9 Graphics GPU Radeon RX 5700 XT 8 GB/Intel UHD Graphics 630 1536 MB
* OS: Catalina 10.15.6
* TB Hub: Caldigit TS+
* LG Ultrafine 4k


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


I'm using my Macbook Pro in clamshell mode connected to a Caldigit Dock TS+ via thunderbolt 3 ( right hand port ) . A Thunderbolt 3 cable goes from the dock to my Razer GPU enclosure. The enclosure has a Radeon card and 2 expensive bidirectional DP to Thunderbolt cables that go to my LG Ultrafine 4k displays.

I read several of the previous posts. I'm not running Parallels when it crashes ( but Parallels 15 is installed ) , and I am not running Little Snitch.
 

Attachments

  • Screen Shot 2020-08-01 at 5.08.49 PM.png
    Screen Shot 2020-08-01 at 5.08.49 PM.png
    879.9 KB · Views: 200
Can you post the list so we can all compare and test ourselves as well?
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.
 
Seems we're all having the same issue. I wonder if it's related to the virtual memory corruption thing. I know a lot of apps now utilise virtual machine extensions present in modern processors for extra security and it appears there's a bug there (as reported by vmware).

I'm curious if the secure sandboxing of modern browsers utilises frameworks that use these processor extensions for protected and segmented virtual memory.
 
I was having the KP problem on a 2017 iMac running 10.15.6. After a little research I tried:

  • Resetting the SMC
  • Resetting the NVRAM
  • Reinstalling the OS with the combo updater
Since then (three days ago), I haven't had any middle-of-the-night KPs, but when I got back from lunch today I was greeted with a machine either in the middle of shutting down or restarting and the following:

screenshot 2020-08-02 at 13.02.17.jpg

About two dozen instances

screenshot 2020-08-02 at 13.02.22.jpg

Also a couple dozen instances

screenshot 2020-08-02 at 13.04.15.jpg

Half a dozen times

Finally the machine failed to either shut down or restart or whatever it was trying to do, so I used the power button to shut it down and then restart. Since then, none of the above messages have reappeared and the machine is operating normally.
 
I was having the KP problem on a 2017 iMac running 10.15.6. After a little research I tried:

  • Resetting the SMC
  • Resetting the NVRAM
  • Reinstalling the OS with the combo updater
Since then (three days ago), I haven't had any middle-of-the-night KPs, but when I got back from lunch today I was greeted with a machine either in the middle of shutting down or restarting and the following:

View attachment 939730
About two dozen instances

View attachment 939731
Also a couple dozen instances

View attachment 939732
Half a dozen times

Finally the machine failed to either shut down or restart or whatever it was trying to do, so I used the power button to shut it down and then restart. Since then, none of the above messages have reappeared and the machine is operating normally.

The Unapproved caller error is what sparked my call to Apple. I was getting quite a few iCloud messaged on my phone about my MBP being signed into iMessage & Facetime. During that same time I was having problems transferring files from iCloud to various apps or external drives.

After an SMC / Nvram reset with my external monitor plugged in, i've been KP free for two days and haven't seen anymore iCloud errors.

There have been a few instance of apps freezing and "low memory" errors (Im running 64g) over the last two days which makes me thing theres still something deeper here.
 
  • Like
Reactions: Buadhai
So it happened again.
After being KP-free for weeks now by not letting the displays sleep by itself
1596548493616.png

and manually putting the machine to sleep when needed,
1596548540502.png

it happened again. When arriving at my desk today, the machine was shut down due to the dreaded WindowServer-Watchdog-Timeout-KP.
To that time, I was still on 10.15.5, obeying to the motto "never touch a running system".
As it eventually did KP, I figured I could as well update to 10.15.6 and - got my next Kernel Panic shutdown the first time I left the machine with Displays going to sleep automatically after doing the update.

This is so sad...

The full "Problem Details and System Configuration" of the latest KP are as follows - maybe someone can derive some info from this:

Code:
panic(cpu 6 caller 0xffffff7f9b1a1ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (11880 seconds ago): 1189, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since load (11810 seconds ago): 1158, last successful checkin: 120 seconds ago

Backtrace (CPU 6), Frame : Return Address
0xffffff804e81b720 : 0xffffff801a71a65d
0xffffff804e81b770 : 0xffffff801a854a75
0xffffff804e81b7b0 : 0xffffff801a8465fe
0xffffff804e81b800 : 0xffffff801a6c0a40
0xffffff804e81b820 : 0xffffff801a719d27
0xffffff804e81b920 : 0xffffff801a71a117
0xffffff804e81b970 : 0xffffff801aec1b28
0xffffff804e81b9e0 : 0xffffff7f9b1a1ad5
0xffffff804e81b9f0 : 0xffffff7f9b1a17fa
0xffffff804e81ba10 : 0xffffff801ae539ce
0xffffff804e81ba60 : 0xffffff7f9b1a0cfe
0xffffff804e81bb60 : 0xffffff801ae5cbf3
0xffffff804e81bca0 : 0xffffff801a8035e2
0xffffff804e81bdb0 : 0xffffff801a7203c8
0xffffff804e81be10 : 0xffffff801a6f6d15
0xffffff804e81be70 : 0xffffff801a70db22
0xffffff804e81bf00 : 0xffffff801a82c065
0xffffff804e81bfa0 : 0xffffff801a6c1226
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[832CC890-EE61-33E0-8FD4-8D354BCD0921]@0xffffff7f9b1a0000->0xffffff7f9b1a8fff

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

Mac OS version:
19G73

Kernel version:
Darwin Kernel Version 19.6.0: Sun Jul  5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64
Kernel UUID: 783946EA-6F11-3647-BF90-787AEA14B954
Kernel slide:     0x000000001a400000
Kernel text base: 0xffffff801a600000
__HIB  text base: 0xffffff801a500000
System model name: MacBookPro15,3 (Mac-1E7E29AD0135F9BC)
System shutdown begun: NO

System uptime in nanoseconds: 11908898697920
last loaded kext at 70403345627: @kext.AMDFramebuffer    3.1.0 (addr 0xffffff7fa196e000, size 245760)
last unloaded kext at 292706164910: >usb.IOUSBHostHIDDevice    1.2 (addr 0xffffff7f9b2f6000, size 49152)
loaded kexts:
com.intel.driver.EnergyDriver    3.5.5
@kext.AMDFramebuffer    3.1.0
@kext.AMDRadeonX5000    3.1.0
@kext.AMDRadeonServiceManager    3.1.0
>!AGraphicsDevicePolicy    5.2.6
@AGDCPluginDisplayMetrics    5.2.6
@fileutil    20.036.15
>!AHV    1
|IOUserEthernet    1.0.1
|IO!BSerialManager    7.0.6f7
>pmtelemetry    1
>AGPM    111.4.4
>X86PlatformShim    1.0.0
>!APlatformEnabler    2.7.0d0
@Dont_Steal_Mac_OS_X    7.0.0
>!AUpstreamUserClient    3.6.8
>AGDCBacklightControl    5.2.6
>AudioAUUC    1.70
>!A!IKBLGraphics    14.0.7
>!AHIDALSService    1
>!ATopCaseHIDEventDriver    3430.1
@kext.AMD10000!C    3.1.0
>BridgeAudioCommunication    6.70.7
>!AThunderboltIP    3.1.4
>!A!ICFLGraphicsFramebuffer    14.0.7
>!AMCCSControl    1.14
>!AMuxControl2    5.2.6
>!ABridgeAudio!C    6.70.7
>!AGFXHDA    100.1.429
>!A!IPCHPMC    2.0.1
>!A!ISlowAdaptiveClocking    4.0.0
>!AAVEBridge    6.1
@filesystems.autofs    3.0
>usb.realtek8153patcher    5.0.0
>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
>!ABCMWLANBusInterfacePCIe    1
@filesystems.apfs    1412.141.1
@private.KextAudit    1.0
>!ASmartBatteryManager    161.0.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
@kext.AMDRadeonX5000HWLibs    1.0
@kext.AMDRadeonX5000HWServices    3.1.0
|IOAVB!F    850.1
@!AGPUWrangler    5.2.6
>!AActuatorDriver    3440.1
>!ABacklightExpert    1.1.0
>!AHIDKeyboard    209
>!AHS!BDriver    3430.1
>IO!BHIDDriver    7.0.6f7
>!AMultitouchDriver    3440.1
>!AInputDeviceSupport    3440.8
|IO!BHost!CUARTTransport    7.0.6f7
|IO!BHost!CTransport    7.0.6f7
>!UAudio    323.4
|IOAccelerator!F2    438.7.3
>!ASMBus!C    1.0.18d1
>X86PlatformPlugin    1.0.0
>!AGraphicsControl    5.2.6
|IONDRVSupport    576.1
>IOPlatformPlugin!F    6.0.0d8
>!A!ILpssUARTv1    3.0.60
>!A!ILpssUARTCommon    3.0.60
>!AOnboardSerial    1.0
@kext.AMDSupport    3.1.0
@!AGraphicsDeviceControl    5.2.6
|IOGraphics!F    576.1
|IOSlowAdaptiveClocking!F    1.0.0
@plugin.IOgPTPPlugin    840.3
|IOEthernetAVB!C    1.1.0
@kext.triggers    1.0
>usb.cdc.ncm    5.0.0
>usb.!UHub    1.2
>usb.cdc    5.0.0
>usb.networking    5.0.0
>usb.!UHostCompositeDevice    1.2
>!AThunderboltDPOutAdapter    6.2.6
>!AThunderboltPCIUpAdapter    2.5.4
|IOSurface    269.11
@filesystems.hfs.encodings.kext    1
|IOAudio!F    300.2
@vecLib.kext    1.2.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
>!AThunderboltDPInAdapter    6.2.6
>!AThunderboltDPAdapter!F    6.2.6
>!AThunderboltPCIDownAdapter    2.5.4
>!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.1
>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.120.1
|IOSCSIBlockCommandsDevice    422.120.3
>!ACredentialManager    1.0
>!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.6f7
|IO!BPacketLogger    7.0.6f7
>!ASSE    1.0
>KernelRelayHost    1
>!ASEPManager    1.0.1
>IOSlaveProcessor    1
|IOUSBMass!SDriver    157.140.1
|IOSCSIArchitectureModel!F    422.120.3
|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
 
Last edited:
Hi,

Did you guys use vmware fusion or another solution (aka Virtual Box, parallels) to virtualise environments?

I was following this thread https://communities.vmware.com/message/2973190#2973190

That is what exactly happening with me.

Sound to be (no news) a bug in Catalina. For now i will try to monitor the real memory allocation for kernel_task and do some reboots to try to minimize that.

Best Regards!
 
Hi,

Did you guys use vmware fusion or another solution (aka Virtual Box, parallels) to virtualise environments?

I was following this thread https://communities.vmware.com/message/2973190#2973190

That is what exactly happening with me.

Sound to be (no news) a bug in Catalina. For now i will try to monitor the real memory allocation for kernel_task and do some reboots to try to minimize that.

Best Regards!

vmware memory leak is a known issue, but its a different issue than these Window-Server KP issues with external Monitor
 
Edit:

OK, the below didn't help at all, so don't bother – still getting the Kernel Panic mostly in conjunction with sleep.

Just aming from the hip, but I thought I'd try cleaning the kernel cache in an attempt to see if that would make any difference. Wouldn't make any conclusions yet, but so far the Kernel Panic has stayed away. Maybe you could give it a try and see? It's a bit more complicated in Catalina than previously, so do it at your own risk – see this post:


Or maybe use one of the cache cleaning software tools that's avaliable also for Catalina.
 
Last edited:
Just wanted to share how I (hopefully) solved it. All results seem good for now.

I run an iMac Pro with 2 Dell 4k 27" screens connected via startech displayport to USB-c wires. I had crashes every time my computer "rested". I say rested since all sleep options etc were turned off like this thread described. So much that I hate the startup chime now...

I tried clean installs and upgrades from everything over Catalina, Catalina beta, and Big Sur betas. No joy.

After a clean Big Sur install, and all energy settings set to prevent sleeping -> constant crashes (even in a 5min toilet trip...)

- So in the end, running that same beta 2 of Bug Sur install, I decoupled both screens -> rock solid, all energy settings to default
- I added one screen -> rock solid

So I bought https://www.coolblue.be/nl/product/...rbolt-3-naar-displayport-docking-station.html and connected it to both screens with the original mini displayport to displayport wires. And all appears solid for a few hours now.

My guess, (one of) the wires was/were bad, or using 2 usbc ports is an issue, don't know, but no software fix solved anything for me, but this hardware change seems to hit the spot.

Hope it helps someone!

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
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.