SOCD report detected: (AP watchdog expired)

i was in a zoom then my mac made a loud noise and then i got the error SOCD report detected: (AP watchdog expired) i have a imac in color and that happened once idk if my mac is gonna die but idk

Im not using an external harddrive but have this crash happening

Tired of these random restarts "SOCD report detected: (AP watchdog expired)"

I am with you in the boat. Also Mid Dec M1 14" Mac. someone has to put some pressure on this guy in Palo Alto!

@devinalexander

they already did the hardware diagnostics and it passed. This is the third time I'm going to the store for the same issue. Really frustrating to see this happen in this day and age!

@devinalexander

I also sent it (brought it to the store and left it for a few days) multiple times! they said it is not a hardware issue and just a software. Same problem persists.

I didn't take it to a store, they shipped me a box, I shipped it somewhere in Canada, they fixed it and shipped it back.

I'm using Firefox.

Same thing happened to me today, on a Zoom conference. 2021 16" M1 Pro :(

I have a Mac mini 16Gb/256GB.

It has happened to me only once.

I have:

• 2 x displays connected. One on USB-C and one on HDMI.
• 1 x USB-C, with an anker 8-1 hub with a Logitech Receiver and an ElGato Wave:3 connected to it.
• 1 x USB-A, with an sabrent 4-1 USB-A hub with a Logitech HD 1080p webcam connected.
• 1 x USB-A, Samsung memory stick (Not SSD) with 256GB.
• 1 x Ethernet cable connected.
• No time machine enabled.
• I turn it off manually every night.

Got the same error than everybody else, just: "SOCD report detected: (AP watchdog expired)"

I hope this information helps.

Happened to me for the first time yesterday. Have had my M1 MacBook Air for just over six months. Have an external LG monitor + Seagate back-up drive attached (since day 1) and added an Satechi external hub a few months ago. So far has only happened the once for me - came up with a green screen, then restarted and I got the AP watchdog expired message (see log entry below).

Panic (system crashes) log:

 Source: /Library/Logs/DiagnosticReports/.contents.panic

 Size: 247 bytes

 Last Modified: 29/6/21, 10:46 am

 Recent Contents: {"files_to_attach":["\/Library\/Logs\/DiagnosticReports\/panic-base-2021-06-29-104613.000.panic"],"log_path":"\/Library\/Logs\/DiagnosticReports\/panic-base-2021-06-29-104613.000.panic","panic_string":"SOCD report detected: (AP watchdog expired)"}

One thing I've wondered reading this thread and another (https://discussions.apple.com/thread/252511597?answerId=255469239022&login=true&page=1), is whether it is only happening to Macs with M1 chips? Haven't seen anyone who has posted yet talking about the problem with older Macs.

Also, I am powering via my external monitor with a USB cable. It regularly seems to lose connection and I have to pull the cable out and put back in to get the laptop to charge. So maybe a USB cable connection or some sort of power related issue?

Actually I had the issue with a monitor plugged in only via a HDMI converter. I'm the one saying that it's dependent on the power supply. Today I didn't have any issue as using the official charger of the Macbook Air instead of using the smaller iPad Pro charger.

Apple engineering is sending me my third M1 mini 16gb 1Tb. They want to analyze mine. Latest issue is firewire disks connected via usb and adapters drop out all the time and become read only. Plus restart causes USB devices to disappear and I can get them to come back if I unplug and replug the USB4 cable,

Methinks there is a serious USB issue with these otherwise fine Macs.

I just got my first crash with a SOCD error. My crash was without any HDD's connected so I'm not even sure it's an HDD issue. I did have an iPad Pro connected, apple's USB-C adapter to get another display (so 2 x HDMI connected).

1 week time period seems to be the frequency for most

i downgraded to 11.5.1 (20G80) maybe 5 days ago. fresh installed. woke up to a restart this morning.

if someone has 2 macs and likes rabbit holes, i suppose you could try leaving kernel debugging to further isolate this

https://dmaclach.medium.com/kernel-debugging-on-apple-silicon-ff5aa76c4429