Macbook Air 2019 Repeatedly Experiencing "Panic" x86 CPU CATERR Shutdowns

My MacBook Air just started repeatedly shutting down multiple time a day with the notation "x86 CPU CATERR detected." There's a suggestion here about how to use Apple to self-check my hardware if I have "silicon" on my computer but mine is older. Others suggest it might be due to a software error. All that is happening is a message saying "Your computer shut down due to a problem" and the error message set out below. I've never had this issue before. How can I diagnose the issue?

FYI: My computer was professionally checked for viruses about four weeks ago. This started after trying to download a new version of Adobe Pro.

Thanks in advance for any help you can give me.

Here's the entire error message:

panic(cpu 1 caller 0xfffffff0289d81b4): x86 CPU CATERR detected

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 21P4222

macOS version: 23E224

Kernel version: Darwin Kernel Version 23.4.0: Wed Feb 21 19:08:27 PST 2024; root:xnu-10063.101.15~1/RELEASE_ARM64_T8010

KernelCache UUID: F6F06A530618C404DA8786EB4B97B15F

Kernel UUID: 95195E00-3880-32D0-881D-D62671898152

Boot session UUID: F1A5A25F-951A-4CFC-9169-A9B6FCF48954

iBoot version: iBoot-10151.101.3

secure boot?: YES

roots installed: 0

x86 EFI Boot State: 0xd

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0x3

x86 Previous Power Transitions: 0x70707060400

PCIeUp link state: 0x1614

macOS kernel slide: 0x17a00000

Paniclog version: 14

Kernel slide:      0x000000002277c000

Kernel text base:  0xfffffff029780000

mach_absolute_time: 0x1219ce2f153

Epoch Time:        sec       usec

  Boot    : 0x6647afcc 0x00009235

  Sleep   : 0x00000000 0x00000000

  Wake    : 0x00000000 0x00000000

  Calendar: 0x66487a37 0x00070130

Zone info:

  Zone map: 0xffffffe157368000 - 0xffffffe757368000

  . VM    : 0xffffffe157368000 - 0xffffffe23d9cc000

  . RO    : 0xffffffe23d9cc000 - 0xffffffe28a698000

  . GEN0  : 0xffffffe28a698000 - 0xffffffe370cfc000

  . GEN1  : 0xffffffe370cfc000 - 0xffffffe457360000

  . GEN2  : 0xffffffe457360000 - 0xffffffe53d9c8000

  . GEN3  : 0xffffffe53d9c8000 - 0xffffffe624030000

  . DATA  : 0xffffffe624030000 - 0xffffffe757368000

  Metadata: 0xffffffdc243bc000 - 0xffffffdc25bbc000

  Bitmaps : 0xffffffdc25bbc000 - 0xffffffdc25ce8000

  Extra   : 0 - 0

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

CORE 0: PC=0xfffffff029aac528, LR=0xfffffff0299abb28, FP=0xffffffefefad3ef0

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 0xffffffe623fa1e30: 0 pages, 204 threads: pid 0: kernel_task

Panicked thread: 0xffffffe53e05ab90, backtrace: 0xffffffefefd376e0, tid: 489

                          lr: 0xfffffff02997b17c  fp: 0xffffffefefd37750

                          lr: 0xfffffff029aaad3c  fp: 0xffffffefefd377c0

                          lr: 0xfffffff029aa9d88  fp: 0xffffffefefd378a0

                          lr: 0xfffffff02993d630  fp: 0xffffffefefd378b0

                          lr: 0xfffffff02997abb8  fp: 0xffffffefefd37c60

                          lr: 0xfffffff02a002fc4  fp: 0xffffffefefd37c80

                          lr: 0xfffffff0289d81b4  fp: 0xffffffefefd37cb0

                          lr: 0xfffffff0289befb4  fp: 0xffffffefefd37d10

                          lr: 0xfffffff0289c55cc  fp: 0xffffffefefd37d60

                          lr: 0xfffffff0289bf9ec  fp: 0xffffffefefd37e00

                          lr: 0xfffffff0289be7d4  fp: 0xffffffefefd37e30

                          lr: 0xfffffff0299d0a08  fp: 0xffffffefefd37f20

                          lr: 0xfffffff0299486c4  fp: 0x0000000000000000