Mac Pro 2019 shuts down Panic CPU 0

Hello everyone, I'm looking to see if anyone is having the same issue am having with my Mac Pro 2019. It keeps shutting down after 5 minutes or so. I get the following report every time it boots up on its own.

anic(cpu 0 caller 0xfffffff0252211e4): "void AppleEmbeddedPCIeUpLinkMgmt::_functionInterruptAction(IOInterruptEventSource *, int): " "Completion timeout seen! [Device index = 0x0] [Link up = true] [CPL timeout = 0x0]" @AppleEmbeddedPCIeUpLinkMgmt.cpp:3659

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 22P3051

macOS version: 24D70

Kernel version: Darwin Kernel Version 24.3.0: Thu Jan 2 20:06:28 PST 2025; root:xnu-11215.81.4~2/RELEASE_ARM64_T8010

KernelCache UUID: C4927E81A8EF71EF971180EB427BDEAA

Kernel UUID: 5E0311EE-A5B2-37BF-A7AE-F303066BB6B6

Boot session UUID: 094F892B-6DEA-47EC-BFA0-CDB16AA2B5E7

iBoot version: iBoot-11881.81.2

secure boot?: YES

roots installed: 0

x86 EFI Boot State: 0x16

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0xec

x86 Previous Power Transitions: 0x70707060400

PCIeUp link state: 0x89271611

macOS kernel slide: 0x17a00000

Paniclog version: 14

Kernel slide: 0x000000001eea8000

Kernel text base: 0xfffffff025eac000

mach_absolute_time: 0x34a25110f

Epoch Time: sec usec

Boot : 0x67c25bdf 0x0001c0c1

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x67c25e26 0x000dddf5

Zone info:

Zone map: 0xffffffdc01acc000 - 0xffffffe201acc000

. VM : 0xffffffdc01acc000 - 0xffffffdce8130000

. RO : 0xffffffdce8130000 - 0xffffffdd34dfc000

. GEN0 : 0xffffffdd34dfc000 - 0xffffffde1b460000

. GEN1 : 0xffffffde1b460000 - 0xffffffdf01ac4000

. GEN2 : 0xffffffdf01ac4000 - 0xffffffdfe812c000

. GEN3 : 0xffffffdfe812c000 - 0xffffffe0ce794000

. DATA : 0xffffffe0ce794000 - 0xffffffe201acc000

Metadata: 0xffffffdc0019c000 - 0xffffffdc0199c000

Bitmaps : 0xffffffdc0199c000 - 0xffffffdc01abc000

Extra : 0 - 0

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

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

CORE 1: PC=0xfffffff025518c28, LR=0xfffffff02551d2a8, FP=0xffffffefcd297c70

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

Panicked task 0xffffffde1b520fa8: 0 pages, 174 threads: pid 0: kernel_task

Panicked thread: 0xffffffdfe82a64c0, backtrace: 0xffffffefcd0937b0, tid: 331

lr: 0xfffffff0260ba020 fp: 0xffffffefcd093820

lr: 0xfffffff0261f48fc fp: 0xffffffefcd093890

lr: 0xfffffff0261f39f0 fp: 0xffffffefcd093980

lr: 0xfffffff0260796bc fp: 0xffffffefcd093990

lr: 0xfffffff0260b9a60 fp: 0xffffffefcd093d60

lr: 0xfffffff0267a93a0 fp: 0xffffffefcd093d80

lr: 0xfffffff0252211e4 fp: 0xffffffefcd093e10

lr: 0xfffffff0266ddbc0 fp: 0xffffffefcd093e60

lr: 0xfffffff0266dc564 fp: 0xffffffefcd093ec0

lr: 0xfffffff0266dbd48 fp: 0xffffffefcd093f20

lr: 0xfffffff0260846c4 fp: 0x0000000000000000