Become a MacRumors Supporter for $25/year with no ads, private forums, and more!

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

vincebio

macrumors 6502a
Jun 27, 2005
792
47
Glasgow
Sad to report that after seeing this thread a while ago and praying I was immune, my 16" started Its KP's yesterday.
Bad Magic is in the code.

I use mines remotely with only the power plugged in sometimes.

I updated to 10.15.6 yesterday and was the biggest mistake on this new laptop yet.

Shameful apple, seriously. Get your ****ing heads out your asses. Unacceptable for a €3500 machine.
 
  • Like
Reactions: johnalan
Comment

tommiy

macrumors 6502
Dec 11, 2015
275
87
Get yourself a remote wifi power switch so you can reboot the MAC with these issues persisting into the next release it is obvious that there is no resolution from apple in sight.
 
Comment

tommiy

macrumors 6502
Dec 11, 2015
275
87
In the past it seems Apple responds to class action law suits more easily than bug reports. Perhaps some one should organise something which may result in progress.
 
Comment

vincebio

macrumors 6502a
Jun 27, 2005
792
47
Glasgow
Right its getting beyond ridiculous now.

Yesterday I could maintain the machine running without KP's as long as it never went to sleep or had anything plugged in.

Now its only 1200 and have had 8 KP's since 7am.

As a teacher, im seriously pissed off right now. This machine is going directly back to the store
 
Comment

tommiy

macrumors 6502
Dec 11, 2015
275
87
I feel for you. Stand your ground until they replace it with one that works.
 
Comment

Kenjutsuz

macrumors newbie
Aug 16, 2020
19
4
Just updated 2012 Mac book Air 2012. 1015.7 from 10.15.5,, no probs yet
Macbook Air 2020 tomorrow
 
Comment

star-affinity

macrumors 65816
Nov 14, 2007
1,324
606
Just updated 2012 Mac book Air 2012. 1015.7 from 10.15.5,, no probs yet
Macbook Air 2020 tomorrow
Also on 10.15.7 now. No crashes so far, but not making any conclusions yet of course.

Seems to run as snappy as ever though and the update was quite big for me (over 2 GB), so one can hope I guess…
 
Last edited:
Comment

YsHaNg

macrumors newbie
Sep 25, 2020
4
2
Also on 10.15.7 now. No crashes so far, but not making any conclusions yet of course.

Seems to run as snappy as ever though and the update was quite big for me (over 2 GB), so one can hope I guess…
Just registered to tell that 10.15.7 does not fix it. I upgraded last night and let my 2015 mbp13 slept over night. Then I got a fresh KP this morning during shut down, same as before.
 
  • Angry
Reactions: star-affinity
Comment

kernelpanicffs

macrumors newbie
Sep 17, 2020
3
1
Updated to Big Sur 8 last night. Still not fixed.

Since it seems to be an issue just when the displays are idle/sleep I turned on Amphetamine, turned off screensaver, and set the computer never to sleep. Left it idle for a short while and came back and still panicked.

Code:
panic(cpu 2 caller 0xffffff801bf13a13): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (3820 seconds ago): 383, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since load (3790 seconds ago): 367, last successful checkin: 120 seconds ago

Backtrace (CPU 2), Frame : Return Address
0xffffffa108103670 : 0xffffff8018cbb65d
0xffffffa1081036c0 : 0xffffff8018dfdb33
0xffffffa108103700 : 0xffffff8018dedf4a
0xffffffa108103750 : 0xffffff8018c60a2f
0xffffffa108103770 : 0xffffff8018cbaefd
0xffffffa108103890 : 0xffffff8018cbb1e8
0xffffffa108103900 : 0xffffff80194b9bf4
0xffffffa108103970 : 0xffffff801bf13a13
0xffffffa108103980 : 0xffffff801bf136ba
0xffffffa1081039a0 : 0xffffff801944138e
0xffffffa1081039f0 : 0xffffff801bf12b0a
0xffffffa108103b20 : 0xffffff801944b41b
0xffffffa108103c80 : 0xffffff8018da93f1
0xffffffa108103d90 : 0xffffff8018cc0c87
0xffffffa108103e00 : 0xffffff8018c975b5
0xffffffa108103e60 : 0xffffff8018caeb62
0xffffffa108103ef0 : 0xffffff8018dd2183
0xffffffa108103fa0 : 0xffffff8018c61216
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[6CB1722A-2CA3-31BF-88AD-EE8DACDE3B68]@0xffffff801bf12000->0xffffff801bf13fff

Process name corresponding to current thread: watchdogd

Mac OS version:
20A5374i

Kernel version:
Darwin Kernel Version 20.1.0: Thu Sep 17 22:14:18 PDT 2020; root:xnu-7195.40.84.171.5~4/RELEASE_X86_64
Kernel UUID: 1BEB2151-70F0-3656-AF8F-9BF853F1F2C1
KernelCache slide: 0x0000000018a00000
KernelCache base:  0xffffff8018c00000
Kernel slide:      0x0000000018a10000
Kernel text base:  0xffffff8018c10000
__HIB  text base: 0xffffff8018b00000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 3830516955659
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x0000037bdc9a3d2f
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x000000067eeab672 0x0000000000000000
last started kext at 26197803033: >!AHIDKeyboard    222 (addr 0xffffff801a068000, size 16384)
last stopped kext at 321320107386: >!ASMCRTC    1.0 (addr 0xffffff801a28a000, size 16384)
loaded kexts:
>AudioAUUC    1.70
>!ATopCaseHIDEventDriver    4000.21
>!APlatformEnabler    2.7.0d0
>AGPM    119
>X86PlatformShim    1.0.0
>!AUpstreamUserClient    3.6.8
@fileutil    20.036.15
@kext.AMDFramebuffer    4.0.0
@filesystems.autofs    3.0
@kext.AMDRadeonX5000    4.0.0
>!AHDA    283.15
@kext.AMDRadeonServiceManager    4.0.0
>!AGraphicsDevicePolicy    6.1.23
>!A!IKBLGraphics    16.0.0
@AGDCPluginDisplayMetrics    6.1.23
>eficheck    1
>pmtelemetry    1
>LuaHardwareAccess    1.0.16
|IOUserEthernet    1.0.1
>usb.!UUserHCI    1
|IO!BSerialManager    8.0.0d53
@Dont_Steal_Mac_OS_X    7.0.0
>!AHV    1
>!A!IPCHPMC    2.0.1
>!ASMCLMU    212
>!A!ICFLGraphicsFramebuffer    16.0.0
>!ADiskImages2    1
>!AThunderboltIP    4.0.3
@kext.AMD10000!C    4.0.0
>!A!ISlowAdaptiveClocking    4.0.0
>!AGFXHDA    100.1.431
>!AMCCSControl    1.14
>usb.!UHostBillboardDevice    1.0
>BCMWLANFirmware4378.Hashstore    1
>BCMWLANFirmware4377.Hashstore    1
>BCMWLANFirmware4364.Hashstore    1
>BCMWLANFirmware4355.Hashstore    1
@filesystems.tmpfs    1
@filesystems.hfs.kext    556.40.4
@BootCache    40
@!AFSCompression.!AFSCompressionTypeZlib    1.0.0
@!AFSCompression.!AFSCompressionTypeDataless    1.0.0d1
>!ASDXC    1.9.0
|!ABCM5701Ethernet    11.0.0
>!ABCMWLANBusInterfacePCIeMac    1
@filesystems.apfs    1677.40.31
>!AAHCIPort    346
@private.KextAudit    1.0
>!AACPIButtons    6.1
>!ARTC    2.0
>!ASMBIOS    2.1
>!AACPIEC    6.1
>!AAPIC    1.7
@!ASystemPolicy    2.0.0
@nke.applicationfirewall    310
|IOKitRegistryCompatibility    1
|EndpointSecurity    1
>!AHIDKeyboard    222
>!AMultitouchDriver    4400.23
>!AInputDeviceSupport    4400.28
>!AHS!BDriver    4000.21
>IO!BHIDDriver    8.0.0d53
@kext.triggers    1.0
@kext.AMDRadeonX5400HWLibs    1.0
@kext.AMDRadeonX5000HWServices    4.0.0
>DspFuncLib    283.15
@kext.OSvKernDSPLib    529
>!AGraphicsControl    6.1.23
>X86PlatformPlugin    1.0.0
|IOAVB!F    900.11
@plugin.IOgPTPPlugin    900.10
|IOEthernetAVB!C    1.1.0
>IOPlatformPlugin!F    6.0.0d8
|IO!BHost!CUARTTransport    8.0.0d53
|IO!BHost!CTransport    8.0.0d53
|IOAccelerator!F2    439.35.1
@kext.AMDSupport    4.0.0
>!ASMBusPCI    1.0.14d1
@!AGPUWrangler    6.1.23
|IOSlowAdaptiveClocking!F    1.0.0
>!A!ILpssUARTv1    3.0.60
>!A!ILpssUARTCommon    3.0.60
>!AOnboardSerial    1.0
>!AHDA!C    283.15
|IOHDA!F    283.15
|IOAudio!F    300.6.1
@vecLib.kext    1.2.0
@!AGraphicsDeviceControl    6.1.23
|IONDRVSupport    585
|IOGraphics!F    585
>!ASMBus!C    1.0.18d1
>usb.networking    5.0.0
>usb.!UHostCompositeDevice    1.2
>!AThunderboltPCIDownAdapter    4.1.1
>!AThunderboltDPInAdapter    8.1.3
>!AThunderboltDPAdapter!F    8.1.3
>!AHPM    3.4.4
>!A!ILpssI2C!C    3.0.60
>!A!ILpssI2C    3.0.60
>!A!ILpssDmac    3.0.60
>!ABSDKextStarter    3
|IOSurface    289.2
@filesystems.hfs.encodings.kext    1
>!AThunderboltNHI    7.2.8
|IOThunderbolt!F    9.3.2
>!ABCMWLANCoreMac    1.0.0
|IOSerial!F    11
|IO80211!FV2    1200.12.2b1
|IOSkywalk!F    1
>mDNSOffloadUserClient    1.0.1b8
>IOImageLoader    1.0.0
>corecapture    1.0.4
|IOAHCIBlock!S    332
|IONVMe!F    2.1.0
|IOAHCI!F    294
>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
$!AImage4    3.0.0
|IOTimeSync!F    900.10
|IONetworking!F    3.4
>DiskImages    493.0.0
|IO!B!F    8.0.0d53
|IOReport!F    47
|IO!BPacketLogger    8.0.0d53
$quarantine    4
$sandbox    300.0
@kext.!AMatch    1.0.0d1
|CoreAnalytics!F    1
>!ASSE    1.0
>!AKeyStore    2
>!UTDM    511.40.3
|IOUSBMass!SDriver    184.40.4
|IOSCSIBlockCommandsDevice    436.40.2
|IO!S!F    2.1
|IOSCSIArchitectureModel!F    436.40.2
>!AMobileFileIntegrity    1.0.5
@kext.CoreTrust    1
>!AFDEKeyStore    28.30
>!AEffaceable!S    1.0
>!ACredentialManager    1.0
>KernelRelayHost    1
|IOUSBHost!F    1.2
>!UHostMergeProperties    1.2
>usb.!UCommon    1.0
>!ABusPower!C    1.0
>!ASEPManager    1.0.1
>IOSlaveProcessor    1
>!AACPIPlatform    6.1
>!ASMC    3.1.9
|IOPCI!F    2.9
|IOACPI!F    1.4
>watchdog    1
@kec.pthread    1
@kec.corecrypto    1.0
@kec.Libm    1
 
Comment

Kenjutsuz

macrumors newbie
Aug 16, 2020
19
4
Updated to Big Sur 8 last night. Still not fixed.

Since it seems to be an issue just when the displays are idle/sleep I turned on Amphetamine, turned off screensaver, and set the computer never to sleep. Left it idle for a short while and came back and still panicked.

Code:
panic(cpu 2 caller 0xffffff801bf13a13): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (3820 seconds ago): 383, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since load (3790 seconds ago): 367, last successful checkin: 120 seconds ago

Backtrace (CPU 2), Frame : Return Address
0xffffffa108103670 : 0xffffff8018cbb65d
0xffffffa1081036c0 : 0xffffff8018dfdb33
0xffffffa108103700 : 0xffffff8018dedf4a
0xffffffa108103750 : 0xffffff8018c60a2f
0xffffffa108103770 : 0xffffff8018cbaefd
0xffffffa108103890 : 0xffffff8018cbb1e8
0xffffffa108103900 : 0xffffff80194b9bf4
0xffffffa108103970 : 0xffffff801bf13a13
0xffffffa108103980 : 0xffffff801bf136ba
0xffffffa1081039a0 : 0xffffff801944138e
0xffffffa1081039f0 : 0xffffff801bf12b0a
0xffffffa108103b20 : 0xffffff801944b41b
0xffffffa108103c80 : 0xffffff8018da93f1
0xffffffa108103d90 : 0xffffff8018cc0c87
0xffffffa108103e00 : 0xffffff8018c975b5
0xffffffa108103e60 : 0xffffff8018caeb62
0xffffffa108103ef0 : 0xffffff8018dd2183
0xffffffa108103fa0 : 0xffffff8018c61216
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[6CB1722A-2CA3-31BF-88AD-EE8DACDE3B68]@0xffffff801bf12000->0xffffff801bf13fff

Process name corresponding to current thread: watchdogd

Mac OS version:
20A5374i

Kernel version:
Darwin Kernel Version 20.1.0: Thu Sep 17 22:14:18 PDT 2020; root:xnu-7195.40.84.171.5~4/RELEASE_X86_64
Kernel UUID: 1BEB2151-70F0-3656-AF8F-9BF853F1F2C1
KernelCache slide: 0x0000000018a00000
KernelCache base:  0xffffff8018c00000
Kernel slide:      0x0000000018a10000
Kernel text base:  0xffffff8018c10000
__HIB  text base: 0xffffff8018b00000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 3830516955659
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x0000037bdc9a3d2f
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x000000067eeab672 0x0000000000000000
last started kext at 26197803033: >!AHIDKeyboard    222 (addr 0xffffff801a068000, size 16384)
last stopped kext at 321320107386: >!ASMCRTC    1.0 (addr 0xffffff801a28a000, size 16384)
loaded kexts:
>AudioAUUC    1.70
>!ATopCaseHIDEventDriver    4000.21
>!APlatformEnabler    2.7.0d0
>AGPM    119
>X86PlatformShim    1.0.0
>!AUpstreamUserClient    3.6.8
@fileutil    20.036.15
@kext.AMDFramebuffer    4.0.0
@filesystems.autofs    3.0
@kext.AMDRadeonX5000    4.0.0
>!AHDA    283.15
@kext.AMDRadeonServiceManager    4.0.0
>!AGraphicsDevicePolicy    6.1.23
>!A!IKBLGraphics    16.0.0
@AGDCPluginDisplayMetrics    6.1.23
>eficheck    1
>pmtelemetry    1
>LuaHardwareAccess    1.0.16
|IOUserEthernet    1.0.1
>usb.!UUserHCI    1
|IO!BSerialManager    8.0.0d53
@Dont_Steal_Mac_OS_X    7.0.0
>!AHV    1
>!A!IPCHPMC    2.0.1
>!ASMCLMU    212
>!A!ICFLGraphicsFramebuffer    16.0.0
>!ADiskImages2    1
>!AThunderboltIP    4.0.3
@kext.AMD10000!C    4.0.0
>!A!ISlowAdaptiveClocking    4.0.0
>!AGFXHDA    100.1.431
>!AMCCSControl    1.14
>usb.!UHostBillboardDevice    1.0
>BCMWLANFirmware4378.Hashstore    1
>BCMWLANFirmware4377.Hashstore    1
>BCMWLANFirmware4364.Hashstore    1
>BCMWLANFirmware4355.Hashstore    1
@filesystems.tmpfs    1
@filesystems.hfs.kext    556.40.4
@BootCache    40
@!AFSCompression.!AFSCompressionTypeZlib    1.0.0
@!AFSCompression.!AFSCompressionTypeDataless    1.0.0d1
>!ASDXC    1.9.0
|!ABCM5701Ethernet    11.0.0
>!ABCMWLANBusInterfacePCIeMac    1
@filesystems.apfs    1677.40.31
>!AAHCIPort    346
@private.KextAudit    1.0
>!AACPIButtons    6.1
>!ARTC    2.0
>!ASMBIOS    2.1
>!AACPIEC    6.1
>!AAPIC    1.7
@!ASystemPolicy    2.0.0
@nke.applicationfirewall    310
|IOKitRegistryCompatibility    1
|EndpointSecurity    1
>!AHIDKeyboard    222
>!AMultitouchDriver    4400.23
>!AInputDeviceSupport    4400.28
>!AHS!BDriver    4000.21
>IO!BHIDDriver    8.0.0d53
@kext.triggers    1.0
@kext.AMDRadeonX5400HWLibs    1.0
@kext.AMDRadeonX5000HWServices    4.0.0
>DspFuncLib    283.15
@kext.OSvKernDSPLib    529
>!AGraphicsControl    6.1.23
>X86PlatformPlugin    1.0.0
|IOAVB!F    900.11
@plugin.IOgPTPPlugin    900.10
|IOEthernetAVB!C    1.1.0
>IOPlatformPlugin!F    6.0.0d8
|IO!BHost!CUARTTransport    8.0.0d53
|IO!BHost!CTransport    8.0.0d53
|IOAccelerator!F2    439.35.1
@kext.AMDSupport    4.0.0
>!ASMBusPCI    1.0.14d1
@!AGPUWrangler    6.1.23
|IOSlowAdaptiveClocking!F    1.0.0
>!A!ILpssUARTv1    3.0.60
>!A!ILpssUARTCommon    3.0.60
>!AOnboardSerial    1.0
>!AHDA!C    283.15
|IOHDA!F    283.15
|IOAudio!F    300.6.1
@vecLib.kext    1.2.0
@!AGraphicsDeviceControl    6.1.23
|IONDRVSupport    585
|IOGraphics!F    585
>!ASMBus!C    1.0.18d1
>usb.networking    5.0.0
>usb.!UHostCompositeDevice    1.2
>!AThunderboltPCIDownAdapter    4.1.1
>!AThunderboltDPInAdapter    8.1.3
>!AThunderboltDPAdapter!F    8.1.3
>!AHPM    3.4.4
>!A!ILpssI2C!C    3.0.60
>!A!ILpssI2C    3.0.60
>!A!ILpssDmac    3.0.60
>!ABSDKextStarter    3
|IOSurface    289.2
@filesystems.hfs.encodings.kext    1
>!AThunderboltNHI    7.2.8
|IOThunderbolt!F    9.3.2
>!ABCMWLANCoreMac    1.0.0
|IOSerial!F    11
|IO80211!FV2    1200.12.2b1
|IOSkywalk!F    1
>mDNSOffloadUserClient    1.0.1b8
>IOImageLoader    1.0.0
>corecapture    1.0.4
|IOAHCIBlock!S    332
|IONVMe!F    2.1.0
|IOAHCI!F    294
>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
$!AImage4    3.0.0
|IOTimeSync!F    900.10
|IONetworking!F    3.4
>DiskImages    493.0.0
|IO!B!F    8.0.0d53
|IOReport!F    47
|IO!BPacketLogger    8.0.0d53
$quarantine    4
$sandbox    300.0
@kext.!AMatch    1.0.0d1
|CoreAnalytics!F    1
>!ASSE    1.0
>!AKeyStore    2
>!UTDM    511.40.3
|IOUSBMass!SDriver    184.40.4
|IOSCSIBlockCommandsDevice    436.40.2
|IO!S!F    2.1
|IOSCSIArchitectureModel!F    436.40.2
>!AMobileFileIntegrity    1.0.5
@kext.CoreTrust    1
>!AFDEKeyStore    28.30
>!AEffaceable!S    1.0
>!ACredentialManager    1.0
>KernelRelayHost    1
|IOUSBHost!F    1.2
>!UHostMergeProperties    1.2
>usb.!UCommon    1.0
>!ABusPower!C    1.0
>!ASEPManager    1.0.1
>IOSlaveProcessor    1
>!AACPIPlatform    6.1
>!ASMC    3.1.9
|IOPCI!F    2.9
|IOACPI!F    1.4
>watchdog    1
@kec.pthread    1
@kec.corecrypto    1.0
@kec.Libm    1
sighs..
 
Comment

Guy Brush

macrumors member
Mar 11, 2019
33
23
Haven't had a single KP for weeks now since quitting using Slack, despite using all default energy saving settings (including automatic and manual display and system sleep).
Yesterday, I had to disconnect the machine from the Thunderbolt-Dock (CalDigit USB-C ProDock, which is USB-C as well as TB3, depending on the host's capabilities) after I sent it to system sleep; sometime down the road, it apparently KP'd as I had to boot it up after reconnecting it to the TB-dock today. The KP message wasn't watchdog or WindowServer, it was something about Bluetooth; unfortunately, I can't find it anymore in the console - the report is gone (as are a lot of other KP reports, only one report about Adobe Acrobat crashing back in May...

I then started the download of 10.15.7 and left the machine; guess what: it KP'd before it had finished downloading the update when it was unattended. However, this KP was also not from watchdog oder WindowServer, instead it read something about "x86 CPU CATERR detected" - this report is also not present in Console, but luckily I took a photo of it (see below).
This and the bluetooth KP were the first non-WindowServer-KPs I've experienced with this machine so far.

The update to 10.15.7 went through fine, though, and since then no KP (but it has only been a few hours since, though).
Now I'm wondering if it could really have to do something with the Hardware - which would be awful as I'm not under warranty anymore (2018 MBP 15") and this machine was really, really expensive (north of 5.000 USD - i9 with 32GB, 2TB SSD and Vega 20)...

1601062986019.png
 
Comment

tommiy

macrumors 6502
Dec 11, 2015
275
87
Seems Apple has no intent of fixing whatever this is given its present in the last update and BigSur. As its present on brand new 16 inch MBP then I guess the only answer to these problems is either continually get the MBP replaced or try to get your $ back for faulty goods. I doubt this will be addressed in the next few years. Looking in the past history when there is a hardware issue Apple does not come forward early on and fix things to satisfy customers. My guess is in a few years time we will have an answer to what the cause is. I think after the bug fix and BigSur there is definitely no recognition that this needs to be addressed. The answer of course is to go and purchase a new MBP and replace the old faulty one.
 
  • Like
Reactions: johnalan
Comment

star-affinity

macrumors 65816
Nov 14, 2007
1,324
606
Haven't had a single KP for weeks now since quitting using Slack, despite using all default energy saving settings (including automatic and manual display and system sleep).
Yesterday, I had to disconnect the machine from the Thunderbolt-Dock (CalDigit USB-C ProDock, which is USB-C as well as TB3, depending on the host's capabilities) after I sent it to system sleep; sometime down the road, it apparently KP'd as I had to boot it up after reconnecting it to the TB-dock today. The KP message wasn't watchdog or WindowServer, it was something about Bluetooth; unfortunately, I can't find it anymore in the console - the report is gone (as are a lot of other KP reports, only one report about Adobe Acrobat crashing back in May...

I then started the download of 10.15.7 and left the machine; guess what: it KP'd before it had finished downloading the update when it was unattended. However, this KP was also not from watchdog oder WindowServer, instead it read something about "x86 CPU CATERR detected" - this report is also not present in Console, but luckily I took a photo of it (see below).
This and the bluetooth KP were the first non-WindowServer-KPs I've experienced with this machine so far.

The update to 10.15.7 went through fine, though, and since then no KP (but it has only been a few hours since, though).
Now I'm wondering if it could really have to do something with the Hardware - which would be awful as I'm not under warranty anymore (2018 MBP 15") and this machine was really, really expensive (north of 5.000 USD - i9 with 32GB, 2TB SSD and Vega 20)...

View attachment 959425

Sorry about that. But seems like a different kind of panic for sure.

Seems Apple has no intent of fixing whatever this is given its present in the last update and BigSur. As its present on brand new 16 inch MBP then I guess the only answer to these problems is either continually get the MBP replaced or try to get your $ back for faulty goods. I doubt this will be addressed in the next few years. Looking in the past history when there is a hardware issue Apple does not come forward early on and fix things to satisfy customers. My guess is in a few years time we will have an answer to what the cause is. I think after the bug fix and BigSur there is definitely no recognition that this needs to be addressed. The answer of course is to go and purchase a new MBP and replace the old faulty one.

The thing is, the watchdog related panic isn't confined to the MBP 16" – it happens an several different kinds of Mac models. If it's a hardware related problem one would in my case think instability should also be seen in Windows 10 which I also run on this machine. There I see no similar instability problems since replacing the RX 5700 XT graphics I have – my first card was faulty and I was hoping that since things got stable in Windows after the replacement it would affect stability in macOS too, but no… At the same time, I haven't seen a panic in 10.15.7, but I think it's only a matter of time since other's still see it.
 
  • Like
Reactions: johnalan
Comment

CMMChris

macrumors 6502
Oct 28, 2019
277
213
As explained like 100 times or so: This watchdog panic is a software issue. The bug was introduced with the release of first Navi GPU drivers. Hackintosh and Mac Pro users thus have been the first group to experience the panic. I myself was able to reproduce this. Using an RX 5700 XT my machine often freezed after sleep, mostly when starting some hardware accelerated decoding or encoding process. After a while it would then panic, reboot and throw the well known watchdog window server panic at me. With other GPUs this does not happen. Me and others opened bug reports with Apple regarding this way before they released Navi based Macs. They did not react to any of those reports up until today, which is more than a year now (I kept reporting the issue again and again and even tried starting a fresh report in May 2020).

At first only Navi based products have been affected (MBP16). Later on, the watchdog panic for some reason started spreading to other MacBooks as well, probably because they ported the bug over to other GPU drivers. It also got harder to reproduce the issue, so they definitely did something. On my Hackintosh when using an RX 5700 XT it is very hard to reproduce the freeze now. The issue can't be reproduced every time now by just waking from sleep and starting some hardware accelerated video encoding / decoding process. I need to repeat the sleep / wake /encoding or decoding cycle many times until it will eventually crash.

Anyhow, it's a shame that Apple is ignoring the issues with their crappy drivers instead of doing something. It's just totally unacceptable given they sell you what is supposed to be premium machines and one of the big reasons why I am not buying Macs anymore and build Hackintoshes instead. Their software quality has been going down for a long time now and I am not willing to pay the Apple tax any longer for ******** like this.

Bear in mind that this watchdog panic stuff isn't the only issue with their GPU drivers. Since day one of support, the Navi drivers in macOS have some serious graphics glitching (e.g. texture flickering, issues with particle effects) in a number of games (Shadow of the Tomb Raider, Dirt4). Me and others have filed bug reports regarding this as well and - you guess it - no response from Apple. More than a year after initial Navi support, there is still not a single fix for this. Instead, they even managed to port (in macOS 10.15.4) the graphics glitching to other GPUs based on Vega20 which affects not only Radeon VII users but even Mac Pro customers with a Radeon Pro Vega II (Duo). Meanwhile, the glitching does not only affect games but even the system UI. And yes, this has been reported to Apple as well with - you guess it - no reaction from them.

Bildschirmfoto 2020-09-26 um 09.17.50.png Bildschirmfoto 2020-09-26 um 09.18.02.png Bildschirmfoto 2020-09-26 um 09.18.12.png Bildschirmfoto 2020-09-26 um 09.18.24.png Bildschirmfoto 2020-09-26 um 09.18.34.png Bildschirmfoto 2020-09-26 um 09.18.44.png
 
Comment

star-affinity

macrumors 65816
Nov 14, 2007
1,324
606
Meanwhile, the glitching does not only affect games but even the system UI. And yes, this has been reported to Apple as well with - you guess it - no reaction from them.

Thanks for sharing your insight!
I've also reported about it for soon a year now and have heard nothing back. :(

But regarding the UI glitches you speak if – weren't those fixed in 10.15.7?

 
  • Love
Reactions: johnalan
Comment

CMMChris

macrumors 6502
Oct 28, 2019
277
213
Haven't tested it with the 5700 XT because I am tired of swapping GPUs. But issues are still there on Vega20.

Edit: Here is an example of the Catalina UI glitches with Radeon VII
It still is the same on 10.15.7.

Some in game glitching which still happens on 10.15.7 and the latest Big Sur Beta:

More in game glitching:

Some Big Sur UI Glitching, see attachements.







 
Last edited:
Comment

vincebio

macrumors 6502a
Jun 27, 2005
792
47
Glasgow
Seems my KP's have been solved (for now at least) by zapping the PRAM x3 times in a row. Ive now been sleeping and waking for 3 days without any KPs' and the Mac is noticeably as fast as it was when I bought it.

I hope this works for some of you guys.

For clarity, doing it x2 still didn't fix it. 3 times in a row has most definitely done something positive.

Still ridiculous that we have to but ill take it.
 
Comment

Zippy3505

macrumors 6502
Oct 20, 2015
342
116
Indiana
Seems my KP's have been solved (for now at least) by zapping the PRAM x3 times in a row. Ive now been sleeping and waking for 3 days without any KPs' and the Mac is noticeably as fast as it was when I bought it.

I hope this works for some of you guys.

For clarity, doing it x2 still didn't fix it. 3 times in a row has most definitely done something positive.

Still ridiculous that we have to but ill take it.
I just tried that, we'll see how it goes.
 
Comment
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.