MacBook Air 2019 panic reboots with audio codec error

Can anyone give me advice on what to do with my MacBook Air 2019 that keeps panic rebooting. It's gotten so bad that sometimes the laptop would just not turn on even by holding down the power button. My laptop turned on again today so id love to be able to find some kind of solution. Below is the error message given to me:

panic(cpu 0 caller 0xfffffff02881ee30): "i2c1::_checkBusStatus Bus is still in a bad state; last read status 00010110 int shadow 00010100 xfer 00000000 fifo 00000000 for device audio-codec-output" @AppleS5L8940XI2C.cpp:571

Debugger message: panic

Memory ID: 0x6

OS release type: Not set yet

OS version: Not set yet

macOS version: Not set

Kernel version: Darwin Kernel Version 25.4.0: Wed Mar 4 21:00:12 PST 2026; root:xnu-12377.101.14~1/RELEASE_ARM64_T8010

KernelCache UUID: D5918C78DE487948F02EC9C28C26C76E

Kernel UUID: 8988F27B-D524-3985-B6AC-E2F100747E6F

Boot session UUID: 8877C03C-24C3-4A04-B161-5BBB08005D29

iBoot version: iBoot-13822.101.1

iBoot Stage 2 version:

secure boot?: YES

roots installed: 0

x86 EFI Boot State: 0x0

x86 System State: 0x3

x86 Power State: 0x6

x86 Shutdown Cause: 0x80

x86 Previous Power Transitions: 0x70707070706

PCIeUp link state: not available

macOS kernel slide: not available

Paniclog version: 15

Kernel slide: 0x0000000022364000

Kernel text base: 0xfffffff029368000

mach_absolute_time: 0x76e2b9f

Epoch Time: sec usec

Boot : 0x00000000 0x00000000

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x00000000 0x00000000

Zone info:

Zone map: 0xffffffdc024c0000 - 0xffffffe2024c0000

. VM : 0xffffffdc024c0000 - 0xffffffdce8b24000

. RO : 0xffffffdce8b24000 - 0xffffffdd357f8000

. GEN0 : 0xffffffdd357f8000 - 0xffffffde1be5c000

. GEN1 : 0xffffffde1be5c000 - 0xffffffdf024c0000

. GEN2 : 0xffffffdf024c0000 - 0xffffffdfe8b28000

. GEN3 : 0xffffffdfe8b28000 - 0xffffffe0cf190000

. DATA : 0xffffffe0cf190000 - 0xffffffe2024c0000

Metadata: 0xffffffe2024d0000 - 0xffffffe203cd0000

Bitmaps : 0xffffffe203cd0000 - 0xffffffe203dfc000

Extra : 0 - 0

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

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

CORE 1: PC=0xfffffff028608218, LR=0xfffffff028608210, FP=0xffffffedb7d5be10

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

Panicked task 0xffffffdd358b1f18: 0 pages, 165 threads: pid 0: kernel_task

Panicked thread: 0xffffffdf026338c0, backtrace: 0xffffffedb7ecf190, tid: 370

lr: 0xfffffff0295a2024 fp: 0xffffffedb7ecf200

lr: 0xfffffff0296f42ac fp: 0xffffffedb7ecf270

lr: 0xfffffff0296f2fe4 fp: 0xffffffedb7ecf360

lr: 0xfffffff02955d6b8 fp: 0xffffffedb7ecf370

lr: 0xfffffff0295a210c fp: 0xffffffedb7ecf850

lr: 0xfffffff029cff458 fp: 0xffffffedb7ecf870

lr: 0xfffffff02881ee30 fp: 0xffffffedb7ecf910

lr: 0xfffffff02881ef9c fp: 0xffffffedb7ecf930

lr: 0xfffffff02881e9b0 fp: 0xffffffedb7ecf980

lr: 0xfffffff028288bb4 fp: 0xffffffedb7ecf9a0

lr: 0xfffffff028288a10 fp: 0xffffffedb7ecf9d0

lr: 0xfffffff029c34714 fp: 0xffffffedb7ecfa30

lr: 0xfffffff028289cac fp: 0xffffffedb7ecfa90

lr: 0xfffffff02866ffc0 fp: 0xffffffedb7ecfb00

lr: 0xfffffff0287fdaa0 fp: 0xffffffedb7ecfb30

lr: 0xfffffff0287fbb28 fp: 0xffffffedb7ecfb60

lr: 0xfffffff0287fb9c8 fp: 0xffffffedb7ecfba0

lr: 0xfffffff028674f40 fp: 0xffffffedb7ecfc70

lr: 0xfffffff029c0466c fp: 0xffffffedb7ecfcf0

lr: 0xfffffff029c0412c fp: 0xffffffedb7ecfe00

lr: 0xfffffff029c03128 fp: 0xffffffedb7ecfe70

lr: 0xfffffff029c06f34 fp: 0xffffffedb7ecff20

lr: 0xfffffff0295686ec fp: 0x0000000000000000