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