What is SOCD report detected: (AP watchdog expired)?

Had to replace my mother board.

Thanks for this update. Looks like more severe cases really need a logic board replacement. Maybe this is an hardware problem after all? This would be unfortunate. It hasn't happened to me again yet

Yep, same here. I had a nice stretch of a few weeks without it happening, then yesterday hit. My computer restarted on its own 17 time in a row. Comp would restart and within 15-20 seconds each time it would restart. Just did it again today.

Same here every day I get back to my Mac mini M1 it got restarted and shows this error message. Wonder if it's not also related to the Bluetooth issues everyone is experiencing... I do have a USB hub maybe you are right... but not using that is not an option!

I am also experiencing this with an M1 barely 6 months old. However, this issue is fairly new. I don't recall when exactly, but it started perhaps two macOS updates ago. And it has been happening more frequently now.

M1 Mac mini, macOS 11.3.1; Watch, series 5 GPS/cellular, watchOS 7.4.1; iPad Pro 2nd Gen, iPadOS 14.5.1; iPad Air 2, iPadOS 14.5.1; iPhone 12 Pro, iOS 14.5.1; TV 4th Gen, tvOS 14.5  HomePods, audioOS 14.5 and Airport Express w/ Airplay 2

Just happened to me on a brand new M1. The same thing happened on my other computer, which I purchased 6 months ago. Took it to the apple store and they replaced it with a new one ( less than a month ago) I'm not exactly sure why they offered to do this but it just happened again. I wasn't on Big Sur with the last one but am now.

I have a Mini M1 and never had this issue. Yesterday, I added a Caldigit Element Hub (TB4/C and USB A 3.2) that also has a power supply engaged. Today, my system did as what happened to many others here - a reboot and an error about "AP watchdog expired."

I'm curious if others who noticed it happening with docks/hubs if

1) the device was supporting Thunderbolt or only up to USB C 3.2 or...?

2) the device used its own power supply and if so, was it being used when the problem happened?

3) did you simply have an external drive and no hub attached when it happened and if so, Thunderbolt, USB C 3.2 or ...?

Obviously looking for any possible specifics associated or if it is random or if several combinations are generating this problem. I sure hope this is not like the issue with the monitors many have had and Apple didn't make any real effort to fix (on going for months)

I've had my M1 mini 16GB 1TB (OS 11.4) for just over 3 months now. Just got this restart/error for the first time. I was running the same apps that I always have open 24/7. I haven't done anything odd in the last day. I wasn't even at my computer when it rebooted.

I do not have a hub, but I do have a monitor with extra USB ports, so essentially a hub. I have had this monitor plugged in since day 1.

I also have a Kensington trackball and an external USB drive, also plugged in since day 1.

Just bought this Mac mini 3 weeks ago. Right in the middle of working my screen went green and this came up after it restarted. Just an hour ago I updated the OS to version 11.4. First time this is happened so I think it’s a issue with this new version of Big Sur. :(

It just happened to me and in my search came across this thread. I have the latest OS and was just browsing the web. This is my first time. Is this going to continue to be a problem or can this be fixed via a firmware update?

I've just experienced same. Have had my M1 MacBook Air for over six months. Have a back-up drive attached (since day 1) and added an external hub some months ago, but have not had the problem previously. Came up with a green screen, then restarted and got the AP watchdog expired message.

It is looking like externals are likely not the cause (though there could be more than 1 cause). What apps are we running? Here are the apps I was running at the time:

Thunderbird

Firefox

Vienna

BBEdit

It seems that this is a pretty complicated situation and what works for some people doesn't work for others. I can tell you're frustrated (I would be too if I were still having this issue) but lashing out at everyone else who has managed to solve it for themselves and are sharing their solutions isn't helping matters.

Sounds like you have misunderstood me @fluffy. I have no frustrations at all. Nor am I "lashing out" at other users. In fact, what I am doing is letting Apple know that the issues identified by other users to be fixes, are in fact, not fixes. If you are debugging code, you need as much help as possible. Since this is such a new issue, I would assume that Apple techs are monitoring this thread and using feedback to try and identify the issue. With all these "random" fixes listed by users, the techs are on a wild goose chase. So I am just trying to help those folks figure it out more quickly.

But thanks for letting me know how you perceive my input and please consider my motivation. Cheers!