I think I'm experiencing something very similar with my brand new 2020 13" MacBook Pro, running macOS 10.15.6.
I have an Apple 27" Thunderbolt Display (which I still really like and don't want to upgrade) which is plugged-in to a Belkin Thunderbolt 3 Express Dock HD via the Apple USB C to Thunderbolt adapter. My new MBP is then connected via a single Thunderbolt 3 cable to the Belkin dock. Everything worked perfectly with my old work 2017 MBP (apart from the keyboard, of course) but since I got this new 2020 model for personal use, it is impossible to connect and disconnect the cable from the dock to the MBP without the MBP having a kernel panic.
Apple Hardware Test finds no issues with the new machine and macOS appears to be working fine in standalone mode (as a laptop). The issues start as soon as I attempt to use the MBP in clamshell mode, connected to my Apple 27" Thunderbolt Display.
What normal seems to happen is this:
- I plug the sleeping MBP into the Belkin dock via the Thunderbolt 3 cable
- The desktop is visible, momentarily, on the Apple 27" Thunderbolt Display
- The display then flashes a few times
- Then it goes dead
If I then disconnect the Thunderbolt 3 cable, and open the lid of the MBP, everything appears to be frozen. The fans spin-up for a brief second and the screen goes blank.
When I press the power button on the MBP, I then see the multiple language "Your Mac shut down because of a problem" black screen of death. Once the Mac reboots successfully, I then see the error reporting screen:
https://support.apple.com/en-gb/HT200553
Obviously, I report this to Apple every time it happens.
I'm fairly confident this is not an issue with the Thunderbolt Display or the Belkin dock since both worked flawlessly a couple of weeks ago with the old 2017 MBP. I believe the issue is with this new 2020 13" MBP I just bought. I guess I could try bypassing the dock and plug the USB C adapter directly into the MBP.
I've tried turning off the well-documented "power nap" options in Energy Saver preferences but this does nothing to help my situation.
Does anybody else have any ideas what might be going on here, please?
Thanks,
Steve