Kernel Panic Sleep/Wake Hang Detected - Forced Restarts During Sleep

I have a MacBook Pro 2018 running Sequoia 15.4. It keeps going through forced restarts while asleep. This never happens when I'm actively using the computer. Below is the most recent kernel panic message. I've tried running disk repair and using Apple Diagnostic but nothing seems to help. In searching around I've found that BridgeOS seems to cause similar problems for this model MacBook but I haven't found a successful solution. Happy to provide more info as needed. Thanks for the help!

panic(cpu 0 caller 0xfffffff01b41b2cc): Sleep/Wake hang detected @IOPMrootDomain.cpp:12946

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 22P4248

macOS version: 24E248

Kernel version: Darwin Kernel Version 24.4.0: Fri Mar 14 18:21:55 PDT 2025; root:xnu-11417.101.14~1/RELEASE_ARM64_T8010

KernelCache UUID: 559F48FC0E53452D134FB3D7C1BB67F4

Kernel UUID: 4ED489B1-A8E5-31AD-9354-6E81AC8B41DD

Boot session UUID: 97FDAEDC-E9D0-4F35-AB34-E56661D89DB8

iBoot version: iBoot-11881.101.1

iBoot Stage 2 version:

secure boot?: YES

roots installed: 0

x86 EFI Boot State: 0x16

x86 System State: 0x1

x86 Power State: 0x1

x86 Shutdown Cause: 0xec

x86 Previous Power Transitions: 0x100010001

PCIeUp link state: not available

macOS kernel slide: 0x11200000

Paniclog version: 14

Kernel slide: 0x0000000013bf4000

Kernel text base: 0xfffffff01abf8000

mach_absolute_time: 0xc6c32721e4

Epoch Time: sec usec

Boot : 0x681171da 0x000b3c16

Sleep : 0x68142785 0x0001aeb7

Wake : 0x68142877 0x0002a58a

Calendar: 0x681428cf 0x000946f9

Zone info:

Zone map: 0xffffffe0d82a4000 - 0xffffffe6d82a4000

. VM : 0xffffffe0d82a4000 - 0xffffffe1be908000

. RO : 0xffffffe1be908000 - 0xffffffe20b5dc000

. GEN0 : 0xffffffe20b5dc000 - 0xffffffe2f1c40000

. GEN1 : 0xffffffe2f1c40000 - 0xffffffe3d82a4000

. GEN2 : 0xffffffe3d82a4000 - 0xffffffe4be90c000

. GEN3 : 0xffffffe4be90c000 - 0xffffffe5a4f74000

. DATA : 0xffffffe5a4f74000 - 0xffffffe6d82a4000

Metadata: 0xffffffde9bb38000 - 0xffffffde9d338000

Bitmaps : 0xffffffde9d338000 - 0xffffffde9d454000

Extra : 0 - 0

TPIDRx_ELy = {1: 0xffffffe3d7a69dc8 0: 0x0000000000000000 0ro: 0x0000000000000000 }

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

CORE 1: PC=0xfffffff01af44c30, LR=0xfffffff01af44c2c, FP=0xffffffeff3c3fe60

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

Panicked task 0xffffffe2f1c52920: 0 pages, 230 threads: pid 0: kernel_task

Panicked thread: 0xffffffe3d7a69dc8, backtrace: 0xffffffeff3e1f820, tid: 62717

lr: 0xfffffff01ae06c8c fp: 0xffffffeff3e1f890

lr: 0xfffffff01af42bbc fp: 0xffffffeff3e1f900

lr: 0xfffffff01af41be4 fp: 0xffffffeff3e1f9f0

lr: 0xfffffff01adc56c8 fp: 0xffffffeff3e1fa00

lr: 0xfffffff01ae066bc fp: 0xffffffeff3e1fdd0

lr: 0xfffffff01b4ff85c fp: 0xffffffeff3e1fdf0

lr: 0xfffffff01b41b2cc fp: 0xffffffeff3e1fe30

lr: 0xfffffff01ae61b84 fp: 0xffffffeff3e1ff20

lr: 0xfffffff01add06c4 fp: 0x0000000000000000