Unfortunately no answer here, just here to tell that I'm experiencing the same and know how to reproduce it without even using a dock. I need to connect my Dell monitor via USB-C on one of the 2 DisplayPort connections on the monitor. Then I need to turn the display on and off and then it will crash (not all the time, but quite soon). I've raised a call with Apple Support about this. But apple claims it's a problem with my hardware and not with their software. So now I need to visit a service center to proof that it's their software and not my hardware that is causing the issue.

Question to all who have this issue: does your macbook pro have the extra AMD video card in it? Since I went to an apple support center today, assuming I would be able to crash one of their systems as well. Unfortunately I was not able to. But they didn’t have a model with the AMD Radeon Pro in it. I’m going to an Apple Store next Monday to see if I’ll be able to crash one of their systems, with an AMD onboard. I assume it will be a success, seeing so many here and on reddit having the same issue. But if you have this issue also on macbooks without the AMD in it, then I’m less confident that I’ve isolated the causing factors.

Alas Apple Support is not able to help me any further. The only fix they can provide is connecting via HDMI and not via usb-c -> DisplayPort (so far I've not been able to crash my system once it's connected via HDMI). The Senior Advisers are not able to get through to Engineering, the feedback stays: it's a problem with the 3rd party hardware, not our system. If only this happened to a famous streamer. The HDMI solution sucks, since it means I'll only have 1 usb-c port free. But it's better than crashes.

Today I was working at the office and I got a new kernel panic while reconnecting my USB-C dock: panic(cpu 1 caller 0xfffffff00efe8d90): x86 CPU CATERR detected Debugger message: panic Memory ID: 0x6 OS release type: User OS version: 19P50284g macOS version: 20G95 Kernel version: Darwin Kernel Version 21.0.0: Sun Jun 20 18:32:24 PDT 2021; root:xnu-8011.0.0.121.4~1/RELEASE_ARM64_T8010 Kernel UUID: 46970279-CCEF-30AD-822F-1A1053068BC2 iBoot version: iBoot-7429.0.133.121.1 secure boot?: YES x86 EFI Boot State: 0x16 x86 System State: 0x0 x86 Power State: 0x0 x86 Shutdown Cause: 0xec x86 Previous Power Transitions: 0x10001000100 PCIeUp link state: 0x89473611 Paniclog version: 13 Kernel slide: 0x0000000006fa4000 Kernel text base: 0xfffffff00dfa8000 mach_absolute_time: 0x864ad301482 Epoch Time: sec usec Boot : 0x61155c50 0x000b0ffb Sleep : 0x611b8616 0x00045947 Wake : 0x611b8787 0x00089b09 Calendar: 0x611bd3e6 0x000d5c26 CORE 0: PC=0xfffffff00e8aa138, LR=0xfffffff00e7a685c, FP=0xffffffeb0ee63ee0 CORE 1 is the one that panicked. Check the full backtrace for details. Panicked task 0xffffffe133564648: 0 pages, 233 threads: pid 0: kernel_task Panicked thread: 0xffffffe133861550, backtrace: 0xffffffeb03f5b6b0, tid: 392 lr: 0xfffffff00e776af4 fp: 0xffffffeb03f5b6f0 lr: 0xfffffff00e776878 fp: 0xffffffeb03f5b760 lr: 0xfffffff00e8a7b7c fp: 0xffffffeb03f5b840 lr: 0xfffffff00edc55fc fp: 0xffffffeb03f5b850 lr: 0xfffffff00e77658c fp: 0xffffffeb03f5bbd0 lr: 0xfffffff00e77658c fp: 0xffffffeb03f5bc30 lr: 0xfffffff00f89b440 fp: 0xffffffeb03f5bc50 lr: 0xfffffff00efe8d90 fp: 0xffffffeb03f5bc80 lr: 0xfffffff00efd636c fp: 0xffffffeb03f5bce0 lr: 0xfffffff00efdc800 fp: 0xffffffeb03f5bd30 lr: 0xfffffff00efd8258 fp: 0xffffffeb03f5bdd0 lr: 0xfffffff00efd5a50 fp: 0xffffffeb03f5be50 lr: 0xfffffff00ee9e7c4 fp: 0xffffffeb03f5be80 lr: 0xfffffff00ed128e4 fp: 0xffffffeb03f5bec0 lr: 0xfffffff00ed120f0 fp: 0xffffffeb03f5bf00 lr: 0xfffffff00edd05c0 fp: 0x0000000000000000 This sounds more serious though :(