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

Nosferatu2212

macrumors newbie
Jul 22, 2020
7
1
Frankly speaking: 10.15.6 solved s*h*i*t!

MBP 2018 i7 2,6 Ghz 32GB, 560x 4GB
External Monitor via USB-C connected to Macbook
Belkin Docking Station connected via USB-C to Macbook
10.15.4: live was good and I never restarted my Laptop for weeks (uptimes of 4-5 weeks were the normal)
10.15.5 introduced: every other day watchdog Kernel Panics as many of you are getting
10.15.6: combo update installed, no more Kernel Panic (Live is good!! Yes? Reallly? No!)
10.15.6: introduced: spinning wheel of death every other day

I tried all the things that many people suggested here, SMC reset, Amphetamine, disable sleep, disable batter health etc.

I am at a point to through out my 4000EURO Macbook Pro. This is no longer a Pro, but a broken machine which is the most unreliable device I had for the past 10 Years.

I really don't get it why Apple is not investing time and effort into fixing this. This is extremly frustrating and will make me think twice weather to get another Apple Macbook next Year or to go for a Dell or Lenovo with Windows. At this point Windows 10 seems to be much more reliable than Apple.
 
Last edited:
  • Like
Reactions: jagooch

kristof46

macrumors member
Jul 19, 2015
81
6
I really don't get it why Apple is not investing time and effort into fixing this. This is extremly frustrating and will make me think twice weather to get another Apple Macbook next Year or to go for a Dell or Lenovo with Windows. At this point Windows 10 seems to be much more reliable than Apple.
Why do you think they are not working on this?
Windows looks really reliable especially when 2004 update crash your printer or something different.
It looks like both companies don't make enough trials before release.
 

bradleydelliott

macrumors newbie
Jul 22, 2020
2
1
I think I have the same issue. Video loop does not crash it... I think I have crashes, now... when the mac goes to sleep.

panic(cpu 12 caller 0xffffff7f9b7a1ad5): userspace watchdog timeout (google search got me to this forum)

MacBook Pro (16-inch, 2019)
10.15.6 (19G73)
2.3 GHz 8-Core Intel Core i9
16 GB 2667 MHz DDR4
AMD Radeon Pro 5500M 4 GB
Intel UHD Graphics 630 1536 MB

I have a direct 32" plug in displaport ASUS 32" 4K monitor, but have had the crash with jjust the laptop also.
 
  • Like
Reactions: jagooch

AgentMax

macrumors newbie
Nov 4, 2008
5
2
Germany
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...
 

Guy Brush

macrumors member
Mar 11, 2019
43
27
Ok I did a full clean reinstall (without migration assistant), it seems to have fixed my problems.
Maybe all those problems have something to do with migrating systems from ages?
How do you do that? Migration assistant = updating from within System Preferences/Software Update, right? "Full, clean install" = ?
And when you are talking about a "full clean reinstall", is there a way to get back your settings and your data from a backup, or does one have to do all that manually?
 
  • Like
Reactions: jagooch

Wxfds

macrumors newbie
Jul 17, 2020
4
0
How do you do that? Migration assistant = updating from within System Preferences/Software Update, right? "Full, clean install" = ?
And when you are talking about a "full clean reinstall", is there a way to get back your settings and your data from a backup, or does one have to do all that manually?

I reinstalled every manually, copied all my files and setting to an external hard drive, do a full install (with a usb drive installer, wiping the drive, etc) and copied back all my files, some non Apple app preferences and so on.
It's a hassle but now I'm 100% sure I don't have a very old file on my system or libraries.
And… everything seems to works as normal.
 

danius

macrumors newbie
Oct 13, 2016
7
4
Dublin, Ireland
fresh Catalina 10.15.6 install.

issue still there. crashes at some stage of iMac being left unused.
I do use external monitors and a good few non apple apps.

panic(cpu 2 caller 0xffffff7f963a1ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since wake (2500 seconds ago): 251, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since wake (2500 seconds ago): 225, last successful checkin: 120 seconds ago
 

bradleydelliott

macrumors newbie
Jul 22, 2020
2
1
pretty much every day in the morning... crash

panic(cpu 2 caller 0xffffff7f8c7a1ad5): userspace watchdog timeout: remoted connection watchdog expired, no updates from remoted monitoring thread in 69 seconds, 1646 checkins from thread since monitoring enabled 32970 seconds ago after wakeservice: com.apple.logd, total successful checkins since wake (32970 seconds ago): 3297, last successful checkin: 10 seconds ago
service: com.apple.WindowServer, total successful checkins since wake (32970 seconds ago): 3272, last successful checkin: 10 seconds ago

Backtrace (CPU 2), Frame : Return Address
0xffffff921f27b720 : 0xffffff800bd1a65d
0xffffff921f27b770 : 0xffffff800be54a75
0xffffff921f27b7b0 : 0xffffff800be465fe
0xffffff921f27b800 : 0xffffff800bcc0a40
0xffffff921f27b820 : 0xffffff800bd19d27
0xffffff921f27b920 : 0xffffff800bd1a117
0xffffff921f27b970 : 0xffffff800c4c1b28
0xffffff921f27b9e0 : 0xffffff7f8c7a1ad5
0xffffff921f27b9f0 : 0xffffff7f8c7a17fa
0xffffff921f27ba10 : 0xffffff800c4539ce
0xffffff921f27ba60 : 0xffffff7f8c7a0cfe
0xffffff921f27bb60 : 0xffffff800c45cbf3
0xffffff921f27bca0 : 0xffffff800be035e2
0xffffff921f27bdb0 : 0xffffff800bd203c8
0xffffff921f27be10 : 0xffffff800bcf6d15
0xffffff921f27be70 : 0xffffff800bd0db22
0xffffff921f27bf00 : 0xffffff800be2c065
0xffffff921f27bfa0 : 0xffffff800bcc1226
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[832CC890-EE61-33E0-8FD4-8D354BCD0921]@0xffffff7f8c7a0000->0xffffff7f8c7a8fff

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: 0x000000000ba00000
Kernel text base: 0xffffff800bc00000
__HIB text base: 0xffffff800bb00000
System model name: MacBookPro16,1 (Mac-xxxxxxxxxxxxxxxx)
System shutdown begun: NO

System uptime in nanoseconds: 39876014270536
last loaded kext at 7003435937184: @filesystems.smbfs 3.4.4 (addr 0xffffff7f930e6000, size 450560)
last unloaded kext at 39846625661352: >usb.!UHostPacketFilter 1.0 (addr 0xffffff7f8e5f4000, size 24576)
loaded kexts:
com.vmware.kext.vmx86 1626.94.56
com.vmware.kext.vmnet 1626.94.56

More...
 

AgentMax

macrumors newbie
Nov 4, 2008
5
2
Germany
You are running VMware. Thats, in my case, the root cause. I switched temporarily to Parallels with the same VM and running stable since over 24 hours now.
 
  • Like
Reactions: Taz Mangus

patrick00icx

macrumors newbie
Jul 24, 2020
1
0
pretty much every day in the morning... crash

panic(cpu 2 caller 0xffffff7f8c7a1ad5): userspace watchdog timeout: remoted connection watchdog expired, no updates from remoted monitoring thread in 69 seconds, 1646 checkins from thread since monitoring enabled 32970 seconds ago after wakeservice: com.apple.logd, total successful checkins since wake (32970 seconds ago): 3297, last successful checkin: 10 seconds ago
service: com.apple.WindowServer, total successful checkins since wake (32970 seconds ago): 3272, last successful checkin: 10 seconds ago

Backtrace (CPU 2), Frame : Return Address
0xffffff921f27b720 : 0xffffff800bd1a65d
0xffffff921f27b770 : 0xffffff800be54a75
0xffffff921f27b7b0 : 0xffffff800be465fe
0xffffff921f27b800 : 0xffffff800bcc0a40
0xffffff921f27b820 : 0xffffff800bd19d27
0xffffff921f27b920 : 0xffffff800bd1a117
0xffffff921f27b970 : 0xffffff800c4c1b28
0xffffff921f27b9e0 : 0xffffff7f8c7a1ad5
0xffffff921f27b9f0 : 0xffffff7f8c7a17fa
0xffffff921f27ba10 : 0xffffff800c4539ce
0xffffff921f27ba60 : 0xffffff7f8c7a0cfe
0xffffff921f27bb60 : 0xffffff800c45cbf3
0xffffff921f27bca0 : 0xffffff800be035e2
0xffffff921f27bdb0 : 0xffffff800bd203c8
0xffffff921f27be10 : 0xffffff800bcf6d15
0xffffff921f27be70 : 0xffffff800bd0db22
0xffffff921f27bf00 : 0xffffff800be2c065
0xffffff921f27bfa0 : 0xffffff800bcc1226
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[832CC890-EE61-33E0-8FD4-8D354BCD0921]@0xffffff7f8c7a0000->0xffffff7f8c7a8fff

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: 0x000000000ba00000
Kernel text base: 0xffffff800bc00000
__HIB text base: 0xffffff800bb00000
System model name: MacBookPro16,1 (Mac-xxxxxxxxxxxxxxxx)
System shutdown begun: NO

System uptime in nanoseconds: 39876014270536
last loaded kext at 7003435937184: @filesystems.smbfs 3.4.4 (addr 0xffffff7f930e6000, size 450560)
last unloaded kext at 39846625661352: >usb.!UHostPacketFilter 1.0 (addr 0xffffff7f8e5f4000, size 24576)
loaded kexts:
com.vmware.kext.vmx86 1626.94.56
com.vmware.kext.vmnet 1626.94.56

More...


I have the same problem.
The Vmware fusion 11.5.5 has being running on 2018 Macmini very fine until I upgraded to Catalina 10.15.6.
It crashed once a day generally. Sometimes it crashes twice or more!

I found there is a fix that could be helpful.

vmware kext files scan script:

and the python should help you to scan those related legacy vmware kext files, remove them and wait for one day to see if it works.
I removed vmware, cleaned the vmware kext files, and reinstall vmware.
Have to observe for a day.
 
Last edited:

petebocken

macrumors newbie
Jan 17, 2014
10
1
Guess I'll throw my datapoint in. Pretty much every morning my MBP 2016 is off completely and I get this report below. Fairly certain it started with 10.15.6.

Code:
panic(cpu 4 caller 0xffffff7f97efaad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (155212 seconds ago): 15522, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since load (155182 seconds ago): 15488, last successful checkin: 120 seconds ago

Backtrace (CPU 4), Frame : Return Address
0xffffff92094cb720 : 0xffffff801731a65d
0xffffff92094cb770 : 0xffffff8017454a75
0xffffff92094cb7b0 : 0xffffff80174465fe
0xffffff92094cb800 : 0xffffff80172c0a40
0xffffff92094cb820 : 0xffffff8017319d27
0xffffff92094cb920 : 0xffffff801731a117
0xffffff92094cb970 : 0xffffff8017ac1b28
0xffffff92094cb9e0 : 0xffffff7f97efaad5
0xffffff92094cb9f0 : 0xffffff7f97efa7fa
0xffffff92094cba10 : 0xffffff8017a539ce
0xffffff92094cba60 : 0xffffff7f97ef9cfe
0xffffff92094cbb60 : 0xffffff8017a5cbf3
0xffffff92094cbca0 : 0xffffff80174035e2
0xffffff92094cbdb0 : 0xffffff80173203c8
0xffffff92094cbe10 : 0xffffff80172f6d15
0xffffff92094cbe70 : 0xffffff801730db22
0xffffff92094cbf00 : 0xffffff801742c065
0xffffff92094cbfa0 : 0xffffff80172c1226
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[832CC890-EE61-33E0-8FD4-8D354BCD0921]@0xffffff7f97ef9000->0xffffff7f97f01fff

BSD process name corresponding to current thread: watchdogd

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:     0x0000000017000000
Kernel text base: 0xffffff8017200000
__HIB  text base: 0xffffff8017100000
System model name: MacBookPro13,3 (Mac-A5C67F76ED83108C)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 155245658343504
last loaded kext at 89117571660887: >!AXsanScheme    3 (addr 0xffffff7f99a1c000, size 32768)
last unloaded kext at 139676163088169: >!AXsanScheme    3 (addr 0xffffff7f99a1c000, size 32768)
loaded kexts:
com.github.osxfuse.filesystems.osxfuse    3.11.0
com.google.drivefs.filesystems.dfsfuse    40.0.8
com.Cycling74.driver.Soundflower    2
com.asix.driver.ax88179-178a    2.0.0
org.dungeon.driver.SATSMARTDriver    0.8.1
at.obdev.nke.LittleSnitch    5474
@filesystems.smbfs    3.4.4
@kext.AMDFramebuffer    3.1.0
@kext.AMDRadeonX4000    3.1.0
@kext.AMDRadeonServiceManager    3.1.0
>!AGraphicsDevicePolicy    5.2.6
@AGDCPluginDisplayMetrics    5.2.6
>AudioAUUC    1.70
@fileutil    20.036.15
>!AHV    1
|IOUserEthernet    1.0.1
|IO!BSerialManager    7.0.6f7
>AGPM    111.4.4
>!APlatformEnabler    2.7.0d0
>X86PlatformShim    1.0.0
>pmtelemetry    1
>!AUpstreamUserClient    3.6.8
@Dont_Steal_Mac_OS_X    7.0.0
>AGDCBacklightControl    5.2.6
>!A!ISKLGraphics    14.0.7
>!AHDA    283.15
@kext.AMD9500!C    3.1.0
>!AThunderboltIP    3.1.4
>eficheck    1
>!A!ISlowAdaptiveClocking    4.0.0
>!AMCCSControl    1.14
>!AMuxControl    5.2.6
>!A!IPCHPMC    2.0.1
>SMCMotionSensor    3.0.4d1
>!AGFXHDA    100.1.429
>!AHIDALSService    1
>!AEmbeddedOSSupportHost    1
>AirPort.BrcmNIC    1400.1.1
>!A!ISKLGraphicsFramebuffer    14.0.7
@filesystems.autofs    3.0
>usb.!UHostBillboardDevice    1.0
|SCSITaskUserClient    422.120.3
>!U!SCoexistentDriver    489.120.1
>!AVirtIO    1.0
@filesystems.hfs.kext    522.100.5
@!AFSCompression.!AFSCompressionTypeDataless    1.0.0d1
@BootCache    40
@!AFSCompression.!AFSCompressionTypeZlib    1.0.0
>!ATopCaseHIDEventDriver    3430.1
@filesystems.apfs    1412.141.1
@private.KextAudit    1.0
>!ASmartBatteryManager    161.0.0
>!AACPIButtons    6.1
>!ARTC    2.0
>!ASMBIOS    2.1
>!AACPIEC    6.1
>!AAPIC    1.7
$!AImage4    1
@nke.applicationfirewall    303
$TMSafetyNet    8
@!ASystemPolicy    2.0.0
|EndpointSecurity    1
@kext.AMDRadeonX4100HWLibs    1.0
@kext.AMDRadeonX4000HWServices    3.1.0
|IOAVB!F    850.1
>DspFuncLib    283.15
@kext.OSvKernDSPLib    529
@!AGPUWrangler    5.2.6
>!ABacklightExpert    1.1.0
>!AHDA!C    283.15
|IOHDA!F    283.15
>X86PlatformPlugin    1.0.0
|IOSlowAdaptiveClocking!F    1.0.0
@kext.AMDSupport    3.1.0
>!ASMBus!C    1.0.18d1
@plugin.IOgPTPPlugin    840.3
|IOEthernetAVB!C    1.1.0
>!AGraphicsControl    5.2.6
>IOPlatformPlugin!F    6.0.0d8
|IONDRVSupport    576.1
|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
|IO80211!F    1200.12.2b1
>mDNSOffloadUserClient    1.0.1b8
>corecapture    1.0.4
|IOSkywalk!F    1
@!AGraphicsDeviceControl    5.2.6
|IOAccelerator!F2    438.7.3
|IOGraphics!F    576.1
@kext.triggers    1.0
>Core!S    551
|IOUSBMass!SClass    4.0.4
>usb.cdc.ncm    5.0.0
>usb.!UiBridge    1.0
>usb.cdc    5.0.0
>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
>!AActuatorDriver    3440.1
>!AHIDKeyboard    209
>!AHS!BDriver    3430.1
>IO!BHIDDriver    7.0.6f7
|IO!B!F    7.0.6f7
|IO!BPacketLogger    7.0.6f7
>!AMultitouchDriver    3440.1
>!AInputDeviceSupport    3440.8
>!AHSSPIHIDDriver    59
>!AThunderboltDPInAdapter    6.2.6
>!AThunderboltDPAdapter!F    6.2.6
>!AThunderboltPCIDownAdapter    2.5.4
>!AHSSPISupport    59
|IONVMe!F    2.1.0
>!A!ILpssSpi!C    3.0.60
>!AThunderboltNHI    5.8.6
>!AHPM    3.4.4
|IOThunderbolt!F    7.6.1
>!A!ILpssI2C!C    3.0.60
>!A!ILpssDmac    3.0.60
>!A!ILpssGspi    3.0.60
>!A!ILpssI2C    3.0.60
>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
>!ASSE    1.0
>!AKeyStore    2
>!UTDM    489.120.1
|IOSCSIBlockCommandsDevice    422.120.3
>!ACredentialManager    1.0
>KernelRelayHost    1
>!ASEPManager    1.0.1
>IOSlaveProcessor    1
|IOTimeSync!F    840.3
|IONetworking!F    3.4
|IOUSBMass!SDriver    157.140.1
|IOSCSIArchitectureModel!F    422.120.3
|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
|IOReport!F    47
>!AACPIPlatform    6.1
>!ASMC    3.1.9
>watchdog    1
|IOPCI!F    2.9
|IOACPI!F    1.4
@kec.pthread    1
@kec.Libm    1
@kec.corecrypto    1.0
 

oneill-sg1

macrumors newbie
Jul 24, 2020
7
2
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...

Can confirm. 10.15.6 w/ VMWare and a Windows10 VM is continuously crashing my 2012 mini.
I have 3 other debian vm's running no problem, but if I leave the Win10 VM running it will eventually kernel panic with the same dump others have been posting here.
 

tommiy

macrumors 6502
Dec 11, 2015
412
127
Really is a sad state of affairs. This thread, and others like it on Apple communities, have been active for almost half a year. There seems still to be no resolve in sight. While windows has plenty of issues I'm not sure i remember when an issue has been outstanding for half a year. For my particular issues with Catalina and external monitor problems its now been 13 months waiting for a reliable OS to address the issues. I've stayed put on 10.15.1 after apples recommendation to solve wa to return to High Sierra give that the external monitor issues for myself started with the supplementary update to 10.14.6. Yes it was worked with Apple and supposedly fixed in Catalina. I upgraded once and found 4 other broken issues with external monitors with Catalina and ceased upgrading since then as I have manual work around for things that used to work. Sadly I'm not convinced that wasting my time to return to High Sierra would fix anything as the firware would remain at Catalina levels and there are threads in the Apple Communities where rolling back does not improve the situation and the only item it can be put down to is thee firmware updates. Sadly there is no way to roll these back to the version that comes with the OS so my answer for over a year is to simply not upgrade.
 

doyouspeakwingdings

macrumors newbie
Aug 11, 2018
25
6
Frankly speaking: 10.15.6 solved s*h*i*t!

MBP 2018 i7 2,6 Ghz 32GB, 560x 4GB
External Monitor via USB-C connected to Macbook
Belkin Docking Station connected via USB-C to Macbook
10.15.4: live was good and I never restarted my Laptop for weeks (uptimes of 4-5 weeks were the normal)
10.15.5 introduced: every other day watchdog Kernel Panics as many of you are getting
10.15.6: combo update installed, no more Kernel Panic (Live is good!! Yes? Reallly? No!)
10.15.6: introduced: spinning wheel of death every other day

I tried all the things that many people suggested here, SMC reset, Amphetamine, disable sleep, disable batter health etc.

I am at a point to through out my 4000EURO Macbook Pro. This is no longer a Pro, but a broken machine which is the most unreliable device I had for the past 10 Years.

I really don't get it why Apple is not investing time and effort into fixing this. This is extremly frustrating and will make me think twice weather to get another Apple Macbook next Year or to go for a Dell or Lenovo with Windows. At this point Windows 10 seems to be much more reliable than Apple.

so... why don’t you just revert to your known-stable configuration?
 

vaugha

macrumors 6502a
Nov 3, 2011
611
206
2019 15" mbp running 10.15.6. Unplugged it from the power adapter and opened the lid. When I tried to move the cursor around the screen, the cursor was jittery and after about 10 secs, screen went blank and heard the fans spinning at full blast and bam! rebooted by itself. Jesus, quality control on macos these years is worse than w10. I never experienced system crashes on wake from sleep on w10. I've experienced a quite a few on macos since catalina. macos quality control is definitely not what it used to be.
 

oneill-sg1

macrumors newbie
Jul 24, 2020
7
2
Really is a sad state of affairs. This thread, and others like it on Apple communities, have been active for almost half a year. There seems still to be no resolve in sight. While windows has plenty of issues I'm not sure i remember when an issue has been outstanding for half a year. For my particular issues with Catalina and external monitor problems its now been 13 months waiting for a reliable OS to address the issues. I've stayed put on 10.15.1 after apples recommendation to solve wa to return to High Sierra give that the external monitor issues for myself started with the supplementary update to 10.14.6. Yes it was worked with Apple and supposedly fixed in Catalina. I upgraded once and found 4 other broken issues with external monitors with Catalina and ceased upgrading since then as I have manual work around for things that used to work. Sadly I'm not convinced that wasting my time to return to High Sierra would fix anything as the firware would remain at Catalina levels and there are threads in the Apple Communities where rolling back does not improve the situation and the only item it can be put down to is thee firmware updates. Sadly there is no way to roll these back to the version that comes with the OS so my answer for over a year is to simply not upgrade.

I was finally able to resolve.

Steps
> Download linux ISO
> Flash to USB
> Overwrite MacOS
> Never look back

Jobs is dead, time to stop pretending like he's not. Maybe I'll come back around when Cook is dead.
 

oneill-sg1

macrumors newbie
Jul 24, 2020
7
2
I wonder how many people experiencing this issue are using something like LuLu, BlockBlock, or Little Snitch?

I block most outbound traffic to Apple that I don't explicitly allow.
 

petebocken

macrumors newbie
Jan 17, 2014
10
1
I'm using Little Snitch. I could try disabling it completely and see if it helps. Considering I'm coming to my Mac every morning and it's off, should be pretty quick to see if it helps.

I wonder how many people experiencing this issue are using something like LuLu, BlockBlock, or Little Snitch?

I block most outbound traffic to Apple that I don't explicitly allow.
 
  • Like
Reactions: jagooch

jeffjak25

macrumors member
Feb 3, 2006
72
12
For me, anything after 10.15.4 leads to panics. The kernel panics happen the same time every day - around 12 PM. I am on a 2018 Mac mini connected to an eGPU. I have even tried wiping and just running stock software, same issue. The only thing I haven't done is disconnect from the eGPU and just use an external monitor connected via HDMI. When it panics, The Mac mini will just freeze and then hard restart. After I updated to 10.15.6 I was getting different errors from the panic. For now I am back on 10.15.4.
 

petebocken

macrumors newbie
Jan 17, 2014
10
1
Well just came to my Mac tonight (6:30pm CDT) and Little Snitch crashed at 5:22pm. So seems like Little Snitch may be a culprit like I previously thought.

Looking at Console crash reports, Little Snitch has been crashing almost every day. I submitted a support request to Obdev and I'll see what they say.

Screen Shot 2020-07-28 at 19.50.14.png



Code:
Process:               Little Snitch Daemon [10752]
Path:                  /Library/Little Snitch/Little Snitch Daemon.bundle/Contents/MacOS/Little Snitch Daemon
Identifier:            Little Snitch Daemon
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
Responsible:           Little Snitch Daemon [10752]
User ID:               0

Date/Time:             2020-07-28 17:22:03.163 -0500
OS Version:            Mac OS X 10.15.6 (19G73)
Report Version:        12
Bridge OS Version:     3.0 (14Y908)
Anonymous UUID:        11C5178A-AF40-FF5A-15EC-D7BF2C25B589


Time Awake Since Boot: 97000 seconds

System Integrity Protection: enabled

Crashed Thread:        0

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

Thread 0 Crashed:
0   ???                               0x00007fff6f79733a __pthread_kill + 10

Thread 1:
0   ???                               0x00007fff6f790dfa mach_msg_trap + 10

Thread 2:
0   ???                               0x00007fff6f84fb68 start_wqthread + 0

Thread 3:
0   ???                               0x00007fff6f84fb68 start_wqthread + 0

Thread 4:
0   ???                               0x00007fff6f790dfa mach_msg_trap + 10

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x000000011ed44dc0  rcx: 0x00007ffedfcc7998  rdx: 0x0000000000000000
  rdi: 0x0000000000000307  rsi: 0x0000000000000006  rbp: 0x00007ffedfcc79c0  rsp: 0x00007ffedfcc7998
   r8: 0x00000000000004bf   r9: 0x0000000000000013  r10: 0x000000011ed44dc0  r11: 0x0000000000000246
  r12: 0x0000000000000307  r13: 0x00000000901fde0d  r14: 0x0000000000000006  r15: 0x0000000000000016
  rip: 0x00007fff6f79733a  rfl: 0x0000000000000246  cr2: 0x00007fff95d94600
 
Logical CPU:     0
Error Code:      0x020000b8
Trap Number:     133


Binary images description not available


External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 1
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 121675
    thread_create: 0
    thread_set_state: 0
 

star-affinity

macrumors 68000
Nov 14, 2007
1,996
1,333
I had exactly same problem, and after excluding the root folder of Google File Stream, the problem resolved.
My MBP 2014 and new MBP 2019 also had same problem, so I strongly expect that the problem is closely related to the Google File Stream and MacOS Catalina.

https://apple.stackexchange.com/que...eout-no-checkins-from-watchdogd/391652#391652

Doesn't explain this:

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.


#82

But maybe that particular ”watchdog timeout” has been resolved since then in a Catalina point update. ?‍♂️
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.