MBP Kernel panic
I have a 2016 MacBook Pro 13" Thunderbolt 3 version running Catalina 10.15.7. The MBP spends most of its time as a desktop computer linked to a fairly ancient (c. 10 years old) 27" Apple Cinema Display via a Caldigit USB-C dock 206/17 vintage (now superseded). I also run an Apple USB SuperDrive from the Caldigit.
This set up has run entirely reliably for several years until a few days ago when I started getting recurrent kernel panics and subsequent restarts very frequently (5 to 30 minutes apart.) These stopped occurring when I unhooked the MBP from the Caldigit leading me to think that that it was the Caldigit that was at fault. However when I plug the MBP into the mains via the standard power adapter the problem recurs, leading me to think it is something to do with the Thunderbolt ports/bus.
Other things I have tried/done are:
Swapping the cable around different Thunderbolt ports but it makes no difference
Downloading the latest Catalina security update. This seemed to take longer than I expected with a number of screen outages prior to it completing. I had the MBP running on the power adapter during the update but subsequently withdrew it whereupon the update completed. I have discovered an update crash log in the diagnostics folder which I am including
Starting up in recovery mode and running disk first aid over my hard drive (completed successfully but seemed to identify various issues)
Updating the Caldigit Docking Station Utility software to the latest, Catalina-compliant, versions
Downloaded and run EtreCheck, which has identified a major issue with a process that is using a large percentage of CPU
The problem didn't seem to related to any software update or other configuration change that I am aware of.
Also worth mentioning is that even in the brief periods when the MBP is running and attached the Caldigit I no longer can access the ethernet port, whereas ethernet is reliably available via my Belkin ethernet to USB-C adapter when plugged into one of the MBP's Thunderbolt port.
I am attaching the EtreCheck report, plus two recent relevant crash logs in the hope that someone can help me identify the problem. Thank you in anticipation.
MacBook Pro 13″, OS X 10.11