Random Reboot Bridge OS on Ventura

My 2019 MacBook Pro is dual booting macOS Ventura and Tahoe. It used to run Ventura and Sonoma just fine, but after an upgrade, Ventura started randomly rebooting.

Sometimes the uptime lasts 2-3 hours before a reboot, other times it's barely 30 minutes before it crashes with a panic report (pasted below). This has had me worried for days.

I've already tried a PRAM reset and an SMC reset, but it's still happening. I suspect the version of BridgeOS might be the culprit.

I even created a partition to try and downgrade to Big Sur, thinking that might fix the BridgeOS version and the random reboots. But now the Big Sur installation just gets stuck on the loading screen. I read somewhere bridge os can be downgraded I don't have access to another Mac to create a bridge os version downgrade, and I'm honestly out of ideas.

Here is the panic report: """panic(cpu 1 caller 0xfffffff018c6d838): macOS watchdog detected

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 23P350

macOS version: 22H730

Kernel version: Darwin Kernel Version 25.0.0: Mon Aug 25 20:39:26 PDT 2025; root:xnu-12377.1.9~1/RELEASE_ARM64_T8010

KernelCache UUID: 2BCA7A7BC3C63D30CC560F5044E0FD67

Kernel UUID: C2C941F8-228D-3DAC-B8E3-559706364B15

Boot session UUID: 5837AA9E-988F-43F9-BCA6-60E49A9403F8

iBoot version: iBoot-13822.1.2

iBoot Stage 2 version:

secure boot?: YES

roots installed: 0

x86 EFI Boot State: 0x16

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0x1

x86 Previous Power Transitions: 0x70707060400

PCIeUp link state: 0x89271614

macOS kernel slide: 0x7800000

Paniclog version: 15

Kernel slide: 0x0000000012a9c000

Kernel text base: 0xfffffff019aa0000

mach_absolute_time: 0x2fdae02465

Epoch Time: sec usec

Boot : 0x68e620ba 0x0006ea2c

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x68e64225 0x00095eda

Zone info:

Zone map: 0xffffffdc6072c000 - 0xffffffe26072c000

. VM : 0xffffffdc6072c000 - 0xffffffdd46d90000

. RO : 0xffffffdd46d90000 - 0xffffffdd93a64000

. GEN0 : 0xffffffdd93a64000 - 0xffffffde7a0c8000

. GEN1 : 0xffffffde7a0c8000 - 0xffffffdf6072c000

. GEN2 : 0xffffffdf6072c000 - 0xffffffe046d94000

. GEN3 : 0xffffffe046d94000 - 0xffffffe12d3fc000

. DATA : 0xffffffe12d3fc000 - 0xffffffe26072c000

Metadata: 0xffffffe26073c000 - 0xffffffe261f3c000

Bitmaps : 0xffffffe261f3c000 - 0xffffffe262064000

Extra : 0 - 0

TPIDRx_ELy = {1: 0xffffffe12d14c268 0: 0x0000000000000001 0ro: 0x0000000000000000 }

CORE 0: PC=0xfffffff01a1875e8, LR=0xfffffff01a2e23a8, FP=0xffffffe49e0ef8f0

CORE 1 is the one that panicked. Check the full backtrace for details.

Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space

Panicked task 0xffffffde7a054f20: 0 pages, 233 threads: pid 0: kernel_task

Panicked thread: 0xffffffe12d14c268, backtrace: 0xffffffe49de5b650, tid: 575

lr: 0xfffffff019cc8d30 fp: 0xffffffe49de5b6c0

lr: 0xfffffff019e0a244 fp: 0xffffffe49de5b730

lr: 0xfffffff019e091a0 fp: 0xffffffe49de5b820

lr: 0xfffffff019c856b8 fp: 0xffffffe49de5b830

lr: 0xfffffff019cc8e18 fp: 0xffffffe49de5bc00

lr: 0xfffffff01a41708c fp: 0xffffffe49de5bc20

lr: 0xfffffff018c6d838 fp: 0xffffffe49de5bc50

lr: 0xfffffff018c552d4 fp: 0xffffffe49de5bcb0

lr: 0xfffffff018c56408 fp: 0xffffffe49de5bcf0

lr: 0xfffffff018c5c544 fp: 0xffffffe49de5bd40

lr: 0xfffffff018c55df8 fp: 0xffffffe49de5be00

lr: 0xfffffff018c54ab4 fp: 0xffffffe49de5be30

lr: 0xfffffff019d24680 fp: 0xffffffe49de5bf20

lr: 0xfffffff019c906cc fp: 0x0000000000000000

""" thank you for advice and help