New Apple M1 keeps on crashing - panic(cpu 3 caller..)

I bought a new MacBook Pro M1 in November 2023. It keeps on crashing all the time.

I think I figured out the issue. It's with ClamVax. Reading the error report - you can see the main error:

panic(cpu 3 caller 0xfffffe001e198324): uipc_send connected but no connection? socket state: 102 socket flags: 48000 socket flags1: 1000000. @uipc_usrreq.c:570

and if you look further, you can see the process that caused this:

Panicked task 0xfffffe24f855adf8: 54970 pages, 4 threads: pid 2491: clamd

So clamd is the process for ClamXAV malware and virus scan software that I had on my earlier MacBook Pro that I restored to this new MacBook. I had a 2015 MacBook with an Intel processor. I moved to 2022 MacBook with the M1 - which is amazing but it kept on crashing. I see several posts out there. Hope this helps the next person who bought a nice MacBook pro but it keeps crashing due to ClaimXAV.

I delete ClaimXAV and now I have no issues (at least not yet).

Jay

Here is the error report:

panic(cpu 3 caller 0xfffffe001e198324): uipc_send connected but no connection? socket state: 102 socket flags: 48000 socket flags1: 1000000. @uipc_usrreq.c:570

Debugger message: panic

Memory ID: 0x1

OS release type: User

OS version: 21G83

Kernel version: Darwin Kernel Version 21.6.0: Wed Aug 10 14:28:23 PDT 2022; root:xnu-8020.141.5~2/RELEASE_ARM64_T6000

Fileset Kernelcache UUID: B8D3CF665D55C117054C886F717D1966

Kernel UUID: E134793B-F17B-3E87-AE46-5968A6965173

iBoot version: iBoot-7459.141.1

secure boot?: YES

Paniclog version: 13

KernelCache slide: 0x00000000162cc000

KernelCache base:  0xfffffe001d2d0000

Kernel slide:      0x0000000016a90000

Kernel text base:  0xfffffe001da94000

Kernel text exec slide: 0x0000000016b78000

Kernel text exec base:  0xfffffe001db7c000

mach_absolute_time: 0x1be9ac6fc02

Epoch Time:        sec       usec

  Boot    : 0x641c98f0 0x0006f816

  Sleep   : 0x641e8222 0x0003807c

  Wake    : 0x641e82c7 0x00092d26

  Calendar: 0x641e9642 0x00004988

Zone info:

  Zone map: 0xfffffe102d438000 - 0xfffffe302d438000

  . VM    : 0xfffffe102d438000 - 0xfffffe14fa104000

  . RO    : 0xfffffe14fa104000 - 0xfffffe1693a9c000

  . GEN0  : 0xfffffe1693a9c000 - 0xfffffe1b60768000

  . GEN1  : 0xfffffe1b60768000 - 0xfffffe202d434000

  . GEN2  : 0xfffffe202d434000 - 0xfffffe24fa100000

  . GEN3  : 0xfffffe24fa100000 - 0xfffffe29c6dcc000

  . DATA  : 0xfffffe29c6dcc000 - 0xfffffe302d438000

  Metadata: 0xfffffe5a3b8e8000 - 0xfffffe5a438e8000

  Bitmaps : 0xfffffe5a438e8000 - 0xfffffe5a4f304000

CORE 0 PVH locks held: None

CORE 1 PVH locks held: None

CORE 2 PVH locks held: None

CORE 3 PVH locks held: None

CORE 4 PVH locks held: None

CORE 5 PVH locks held: None

CORE 6 PVH locks held: None

CORE 7 PVH locks held: None

CORE 8 PVH locks held: None

CORE 9 PVH locks held: None

CORE 0: PC=0x000000018c0f89c8, LR=0x000000018c8754ac, FP=0x000000016b7adcb0

CORE 1: PC=0xfffffe001e24dfa8, LR=0xfffffe001e2c0dcc, FP=0xfffffe4f7f8eb800

CORE 2: PC=0xfffffe001dcb1d50, LR=0xfffffe001dc82164, FP=0xfffffe5a4fa4b4b0

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

CORE 4: PC=0xfffffe001dc0b21c, LR=0xfffffe001dc0b218, FP=0xfffffe5a4fdb3f00

CORE 5: PC=0xfffffe001dc0b21c, LR=0xfffffe001dc0b218, FP=0xfffffe4f8028bf00

CORE 6: PC=0xfffffe001dc0b21c, LR=0xfffffe001dc0b218, FP=0xfffffe5a50453f00

CORE 7: PC=0xfffffe001dc0b21c, LR=0xfffffe001dc0b218, FP=0xfffffe5a3a823f00

CORE 8: PC=0xfffffe001dc0b21c, LR=0xfffffe001dc0b218, FP=0xfffffe4f7f023f00

CORE 9: PC=0xfffffe001dc0b21c, LR=0xfffffe001dc0b218, FP=0xfffffe5a50113f00

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

Panicked task 0xfffffe24f855adf8: 54970 pages, 4 threads: pid 2491: clamd

Panicked thread: 0xfffffe1697aa29a0, backtrace: 0xfffffe4f7f7ab360, tid: 21834

[Re-Titled by Moderator]