Tulip CC resets after < 1 min of drum computer

My Tulip CC resets when I start using the drum computer. What I tried: * Updating to the latest version (now on v1.24.0-preview.409.g82e69df33.dirty)) * Different USB-C adapters * With or without Wifi (when trying to connect to Wifi sometimes it reboots suddenly) * Using less different sounds It seems the crashes don't happen when using only Maraca (the default when starting the drum computer). Reproduce: * As soon I start sounds close to each other, the snare and kick sounds first distort: * kick on 1.1 (measure 1, beat 1) and 2.1 * snare on 1.2 and 2.2 * soon after that the Tulip CC reboots Two dumps: ``` Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled. Core 1 register dump: PC : 0x4203d01c PS : 0x00060830 A0 : 0x82037d09 A1 : 0x3fcdafa0 A2 : 0x00000000 A3 : 0x3c4ad2a0 A4 : 0x00000000 A5 : 0x00000000 A6 : 0x00001ffa A7 : 0x00000101 A8 : 0x00000000 A9 : 0x00010000 A10 : 0x3c6b9628 A11 : 0x00000000 A12 : 0x00000100 A13 : 0x00000000 A14 : 0x3c4acea0 A15 : 0x00000200 SAR : 0x00000015 EXCCAUSE: 0x0000001c EXCVADDR: 0x00000200 LBEG : 0x400570e8 LEND : 0x400570f3 LCOUNT : 0x00000000 Backtrace: 0x4203d019:0x3fcdafa0 0x42037d06:0x3fcdafe0 0x42037e5d:0x3fcdb000 0x4203d69c:0x3fcdb040 ELF file SHA256: 2766233c9 Rebooting... ``` ``` Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled. Core 1 register dump: PC : 0x4203d01c PS : 0x00060f30 A0 : 0x82037d09 A1 : 0x3fcdafa0 A2 : 0x00000000 A3 : 0x3c4ad2a0 A4 : 0x00000000 A5 : 0x00000000 A6 : 0x000002c3 A7 : 0x00000181 A8 : 0x00000000 A9 : 0x00018000 A10 : 0x3c6b9cb8 A11 : 0x00000000 A12 : 0x00000180 A13 : 0x00000000 A14 : 0x3c4acea0 A15 : 0x00000300 SAR : 0x00000015 EXCCAUSE: 0x0000001c EXCVADDR: 0x00000300 LBEG : 0x400570e8 LEND : 0x400570f3 LCOUNT : 0x00000000 Backtrace: 0x4203d019:0x3fcdafa0 0x42037d06:0x3fcdafe0 0x42037e5d:0x3fcdb000 0x4203d69c:0x3fcdb040 ELF file SHA256: 2766233c9 Rebooting... ``` Any help on how I can analyze further what's wrong? (For example if this is a hardware fault or a firmware issue) (Not entirely sure if related, but on a clean boot issuing `tulip.cpu()` gives a panic as well - so I'm inclined to think there's a hardware fault)