SOCD report detected: (AP watchdog expired)

I see this tread is still active, I have this issue also since using the M1 Mac mini. did the reinstall, (several times, even completely new so not from the iCloud backup) nothing seemed to work, I was using a thunderbolt 2 drive array... thought this was the problem, so removed the drive array. I noticed tere is also an issue when getting out of sleep mode!, so disabled the sleep mode.. this didnt help. removing the drive array appears to solve the problem, got a USB3 flash drive, same issue again... have installed the Elecife USBc hub (with SSD drive option) still (not as often ) crashes, and reboots...removed the SSD, and now have NOTHING connected seems working... (but the device is also doing nothing...LOL) attach a USB stick (USB3) problem is back...

a note: all drives (even the USB sticks) are formatted with MAcOS extended journaled)

so my guess is at this time external drives are off limits thunderbolt or USB..

Need to perform a test with thunderbolt 3 drive , and have ordered one so will know more soon

After upgrading to 11.5.2 and stopped using Barrier KVM which is a 32bit app, I haven't had this problem anymore for a very long time.

I would encourage anyone with this problem to do a factory reset, and let it run stock for a few days before installing anything and see if it solves the problem. Then carefully add an app at a time and monitor it. I know it's a slow pain in the *** this way but you might just find the app that is causing the problem. I also found a problem with Spotlight that was flooding the logs with useless strings of garbage reports.

Apple really needs to stop innovating and start fixing up their code and make it STABLE. I'm getting near the end of my rope.

I have not experienced this crash since the last time I restored my machine over DFU using my Intel MBP and a USB-C to USB-A 3.1 gen 2 cable. It did take an incredibly long time to run, though, I don't know if it downloaded the image, since I supplied a pre-downloaded 11.5.1 .ipsw from Apple's servers.

I have since updated to 11.5.2, and again, no repeats of the KP.

(It is entirely possible I also got a firmware update from my attempts to restore a 12 beta .ipsw, but since I was using the stable Configurator 2 from App Store, it was failing at the actual Restore stage due to a protocol error.)

Received and tested the USB C to Mini DisplayPort cable, machine crashes with this setup more than with HDMI cable. It doesn't last 2 minutes before crashing. I really think this unit is defective. The MacBook Air works with no issues at all. I don't think getting a new monitor is going to resolve this. I am thinking the issue is bigger. Going to wipe and do a new software load and if that doesn't resolve it, I am sending it back.

My experience with this error on my Mac Mini M1 seems to only occur when I have my USB Blu-Ray plugged in. It does not happen when I have my SanDisk 480gb SSD USB plugged in (for time machine) all the time. I found just plugging in the Blu-Ray drive to read old CD/DVD/Blu-ray disks as needed and unplugging when done works fine. Only leaving the Blu-Ray drive plugged in all the time seems to matter in my experience. (I am using a USB-C to micro b cord for Blu-Ray and USB 3 cable for Sandisk)

BTW, the reason I didn't turn on FileVault on the new volume is that I this fix suggested by @d3cbgf a few pages back in this thread:

csrutil disable
bputil -nkcas

https://discussions.apple.com/thread/252437781?answerId=255944368022#255944368022)

...seemed to resolve the issue for me for a test period of at least 2-3 days.

This led me to suspect that it might be related to some low-level security stuff on M1 chips.

That's why I disabled FileVault. It was only a hunch though.

The only thing I know for sure is that reinstalling OS X on a new volume (Without FileVault enabled) solved it for me.

And since others seem to have tried reinstalling OS X without luck, I thought this might be the difference.

Good luck!

WD hard drives, especially when hooked up to the USB C port, do this every time. When u replaced by WD with a Seagate, it stopped. No more panics in over a month

You must hook it up to the USB 3 port or get a USB C drive.

In my experience, the SOCD REPORT restart issue is related to USB devices, but is clearly more frequent with some than others.

Devices that I've seen cause this, from most frequent to least frequent.

1. Unpowered USB hubs
2. Monitors with unpowered USB hubs
3. Monitors
4. WD external drives
5. Other USB devices
6. ? no USB devices

I realize some folks are very distraught and can't figure out the cause of their crashes. The above is only to relate my understanding of what's happening, and there are those who have this issue with no devices.

For me, I've achieved over a month without a crash even though I have a Seagate external HD attached. I know when I reconnect my WD external drive, I'll have a crash within a couple of hours. My plan is to buy a powered USB3 hub so I can leave it attached.

I wish everybody here affected by this problem good luck.

That is a good point. When it happened to me I had an external screen connected over USB-C and an additional screen on HDMI.

I have changed that since and am now using an older Apple Cinema screen connected through thunderbolt to USB-C adapter as main screen and the original USB-C screen over HDMI (you can't have 2 USB-C screens connected). The original USB-C screen is also connected over USB-C, but that is just to feed the USB hub in the screen. I have not had the Watchdog error since (but have had other panic's about once a week).

sajal101 wrote:

They will replace logic board..

Interesting, thanks. But if it's a logic board issue, why hasn't Apple instituted a program to replace, it rather than waste all the tech support person hours spent dealing with customers (like me) who have the issue? I've talked several times to high-level Apple support people, and sent system reports and sysdiagnose files - all to no avail of course, aside from reinstalls and updates. A big waste of time for everyone if the issue has nothing to do with software.

I’ll add my experience and say I have an HDMI issue. I have been having this issue since I first started to setup the Mini M1. My LG monitor was connected via HDMI and I could not complete the setup process before crashing. I used a portable monitor with a Thunderbolt cable and it did not crash. I was able to complete the setup and use it with no issues. After the setup, I used it this way for a day and it worked fine. Connected to my monitor via the HDMI port and it would work for a bit then crash. I then started to use a dongle from my work laptop and plugged in with the HDMI port. I could use it for longer and then inevitably it would crash.

After finding this in the support section, I disconnected everything (OWC hub, drives, etc.) and went straight back in with the HDMI cable, once it powered on the keyboard did not reconnect, plugged it in and it crashed. Next restart had the keyboard plugged in, it came up to the login screen then crashed. Went back to the dongle, was able to login, put notes in the crash report and it crashed.

I’ve reconnected the portable monitor and am downloading the latest beta to test, in case there are fixes in that. Once installed, I will go back to the HDMI connection to see how it fares. Got the unit on Thursday and it’s crashed at least 20 times if not more. This is really annoying. If this can’t get sorted I’m returning it. I got a base air for my wife and it works with out issues which is why I decided to get the Mini (16 Gb+ 1TB drive). They really need to figure out and fix this. I shouldn’t have to get a new monitor with a USB C port to use this.

To those having this issue with external USB hard drives attached: Do you have encryption (FileVault) enabled on the drive?

Turning off encryption has completely resolved my issue. I've confirmed that turning it back on again reintroduces the frequent but unpredictable reboots / kernel panics.

Curious if this experience is shared among others.

ssd bricked, which required a new logic board. once ssd dies, you cannot even access recovery options or boot from external drive. will test more on this new board to see if issue comes up.

on side note, if you use ethernet, try to use surge protectors. EMI is no joke

It never happened again on my iMac M1 24", just once. If you are still having all of these errors even with a clean install then I would contact Apple, it may very well be an hardware problem on some units.

After one visit overnight at an Apple repair partner (find nothing), one send in to Apple (find nothing), 100 resets and new and fresh installations the f… was still going on…. 6 phonecalls and many mails later, next send in to Apple, got it back after a week, complete new logicboard…. And, what could I say. Still working since that day. Shame on Apple, that it had took so much energy to get good support!