Interesting. CCC uses rsync, which should be clean with macOS.

thanks for the info.

Another file system related panic:

last started kext at 418446427925: com.apple.filesystems.udf 2.5 (addr 0xfffffe002227f830, size

I think the file system panic thread is a red herring. But what is triggering it, I don't know.

As I was writing this it crashed again while the thunderbay was not connected to the computer. I'll attach another kernel panic report. 

Usually when it crashes while I'm using the computer it's unpredictable. Everything is normal then it all shuts down without warning. This most recent time the computer locked up for a minute then restarted. There was a pink screen that flashed for a fraction of a second. 

Thanks for the info on the other devices.

There is the possibility that something going on in the hardware.

How old is the enclosure?

Have you seen any of the panics? If you are transferring data, does the system stop copying data for a period of time, then it panics?

Right now I'm trying to back everything up from my thunderbay to a NAS. I'm transferring many TB's of data so I'm letting it run over night. Lately every time I come back to the computer it has restarted itself and the apple dialogue that says "your computer restarted because of a problem" pops up. It has crashed once or twice while I was working on it but it seems to be more common when I'm away. I think every time it has crashed has been while the thunderbay was reading/writing a lot of data. 

You are using a G-Speed (Hitachi), with a Promise driver? I would not think they would be compatible, the Promise RAID is tied to the hardware. (curious)

To your panic....

In the backtrace:

Kernel Extensions in backtrace:
com.apple.driver.AppleInterruptController(1.0d1)@0xfffffe001f6fd8b0->0xfffffe001f700fcb
dependency: com.apple.driver.AppleARMPlatform(1.0.2)@0xfffffe001eeb8af0->0xfffffe001ef03137
com.apple.driver.AppleARMWatchdogTimer(1.0)@0xfffffe001ef03140->0xfffffe001ef0796b
dependency: com.apple.driver.AppleARMPlatform(1.0.2)@0xfffffe001eeb8af0->0xfffffe001ef03137

last started kext at 758560134704: com.apple.filesystems.smbfs 4.0 (addr 0xfffffe001e3d24d0, size 64493)

And the kernel panic log header:

panic(cpu 4 caller 0xfffffe001ef0749c): watchdog timeout: no checkins from watchdogd in 91 seconds (183 total checkins since monitoring last enabled)

Both point to a timeout. (Watchdog)

What work are you doing on this computer? Does it crash when sitting there, or when you are working?

The only difference in the way that I'm using the macbook is that I'm plugging in my RAIDs to it now, (I used to only edit off of an external SSD). The RAIDs that I'm using are a thunderbay 4 controlled by softraid and a g-speed studio, which uses a promise driver. It was not plugged in during the last crash though, so the softraid kext was the only 3rd party kext loaded. 

I also just re-installed macos monterey from scratch on the macbook. 

Its a pretty "generic" kernel panic. I don't see any cause, except kernel_task

Kernel trap at 0xffffffa0a714be00, type 14=page fault, registers
Process name corresponding to current thread: kernel_task

there is this line:
Fault CR2: 0xffffffa0a714be00, Error code: 0x0000000000000011, Fault CPU: 0x3 Kernel NX fault, PL: 0, VF: 2

Maybe run the built in hardware test (command d) and see if anything registers. I did some searching on the Apple forums, but not much that gives any clues.