Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

coso

macrumors 65816
Feb 9, 2012
1,063
647
Ok. My current theory is that this occurs when connected to a USB-C PD device that does not fully comply with the USB-C PD spec. Occasionally, these devices may be sending weird power signals to the Mac disrupting sleep/wake cycles in unexpected ways leading to the issue. I cannot reproduce the SOCD report error at this time.

There is a long thread about Dell U3818W and U3419W monitors not following the spec as advertised leading to the sleep/wake power signal issue arising on Macs. The response from Dell on the matter is laughable.

On M1 it happened also to whom who had nothing attached to USB ports though. When happened to me I had two empty cables connected, the USB-C to lightning which came with my iMac, and the Apple Watch 5 USB-A charger connected to the official Apple USB-C to A converter
 

Spanther

macrumors regular
Dec 14, 2020
114
383
On M1 it happened also to whom who had nothing attached to USB ports though. When happened to me I had two empty cables connected, the USB-C to lightning which came with my iMac, and the Apple Watch 5 USB-A charger connected to the official Apple USB-C to A converter
Guh.

The USB/Thunderbolt "standards" being an absolute dumpster fire since the advent of Type-C is probably the real culprit here.
 
  • Like
Reactions: UltimateSyn

giffut

macrumors 6502
Apr 28, 2003
473
158
Germany
I suspect that this is a lousy implementation of USB and Thunderbolt specifications. Apple uses inhouse built hardware.

But I suspect that their hardware implementation is somewhat faulty, otherwise I can't comprehend that this isn't already solved in software.

The USB/Thunderbolt specifications are fine. We had many hickups and problems with M1 macs regarding cables and attached things, we couldn't reproduce any of those with PC counterparts running Windows or Linux.

This is completely on Apples tap.
 
Last edited:

Bob_DM

macrumors member
Nov 26, 2020
93
57
Kessel-lo - Belgium
I suspect that this is a lousy implementation of USB and Thunderbolt specifications. Apple uses inhouse built hardware.

But I suspect that their hardware implementation is somewhat faulty, otherwise I can't comprehend that this isn't already solved in software.

The USB/Thunderbolt specifications are fine. We had many hickups and problems with M1 macs regarding cables and attached things, we couldn't reproduce any of those with PC counterparts running Windows or Linux.

This is completely on Apples tap.
Never had a problem with M1 Mini and lots of connected devices:
Eizo screen via TB3 SSD-raid > TB3 to TB2 adapter >TB2 SSD-Raid > display port.
Cinema Display via HDMI > DVI adapter
3 x firewire 800 HDD in serie via TB3>TB2>FW800 adapters
USB 7 ports hub
USB 13 ports hub
Via those hubs and the ones in both displays:
Audio interface/Roland A500 usb/midi-keyboard/and two port usb/midi dongle
Keyboard/mouse/Wacom
SSD raid with two portable drives
Big USB HDD
Two portable usb-drives
Two printers (inkjet photo/laser)
Two scanners

Apart from cable-spaghetti everything’s playing fine together!
 

Wolf1701

macrumors regular
Sep 16, 2006
231
229
Apart from cable-spaghetti everything’s playing fine together!
yep the problem with this particular error is that is not easy to replicate. It appears to be somewhat random (with or without usb peripherals (any kind, wd hd, monitors, hubs), in waking up from sleep or on machines that run 24/7, with monterey or big sur, with M1/Pro/Max, in desktop or nb... Can happen in loop, once in a year or never... if Apple with the crash reports (send them Please!) can figure it out it would be great.
 

Eithanius

macrumors 68000
Nov 19, 2005
1,556
419
Just got this issue for the first time after 9 months owning an M1 MBA...

Connected to OWC Travel Dock with a USB-A mouse and USB-C PD plugged in... Connected another USB-C to Lightning to my iPhone 11, started syncing when suddenly a crackling sound occurred, display contains graphic artifacts, then my MBA promptly restarted...
 

TrueBlou

macrumors 601
Sep 16, 2014
4,531
3,619
Scotland
Curious, if it’s in any way related to storage, I wonder if it’s specific controllers that have an issue?

I’ve been running my M1 Mini off an external TB3 drive since I got it, there’s also a 6TB mechanical HDD attached for Time Machine backups and it’s often connected to a TB3 dock (only so I can use the DisplayPort output of the dock). So far, no issues whatsoever and it’s been running 24/7 for months as a server.

The MBA I was using this past year also exhibited no problems, and there have been numerous USB devices attached to it on an almost daily basis.

There must be an underlying cause, I’d be curious as to what, as it seems to be quite difficult to replicate reliably.
 

cocona20xx

macrumors newbie
Oct 10, 2021
2
1
Ok. My current theory is that this occurs when connected to a USB-C PD device that does not fully comply with the USB-C PD spec. Occasionally, these devices may be sending weird power signals to the Mac disrupting sleep/wake cycles in unexpected ways leading to the issue. I cannot reproduce the SOCD report error at this time.

There is a long thread about Dell U3818W and U3419W monitors not following the spec as advertised leading to the sleep/wake power signal issue arising on Macs. The response from Dell on the matter is laughable.
This is likely correct; and I'm quite sure it applies to all USB ports, not just USB-C.

EDIT:

Just got this issue for the first time after 9 months owning an M1 MBA...

Connected to OWC Travel Dock with a USB-A mouse and USB-C PD plugged in... Connected another USB-C to Lightning to my iPhone 11, started syncing when suddenly a crackling sound occurred, display contains graphic artifacts, then my MBA promptly restarted...
On the first ever time this happened, I had a similar issue with audio crackling, seemingly from the onboard speaker despite a speaker being plugged in via the Headphone port, alongside a long reload time and a green screen. The other two times it was an instant restart, no warning beforehand of any real sort. Furthermore, I used to get pink-colored visual glitches (2-3 pixel wide distortions that'd flicker on and off) for a short time after boot, but this mostly stopped when I switched to the correct refresh rate for my monitor (it's at 75 fps, but the computer didn't automatically pick that up) and after a system update.

I suspect said update may have made the issue more stable, as early in my Gen 1 Apple Silicon Mac Mini's usage (like March of this year?) a software/firmware update caused large amounts of visual distortions and took quite a bit longer than I would've expected, but graphical/sound stability and crashes became less common overall afterwards; furthermore I haven't seen anything like that when updating since.
 
Last edited:

Juice28

macrumors newbie
Nov 10, 2021
1
1
I am using the new MacBook 14in M1 Max, connected to an Odyssey G9 Neo through USB-C to DisplayPort. I leave them plugged together 24/7 with the MacBook closed. I get this error message almost 100% of the time I wake up my MacBook after I put it to sleep. I don't use an external hard drive. And I feel like this problem just started week despite having this setup for a couple weeks now...
 
  • Like
Reactions: coso

bananataffy

macrumors regular
Dec 18, 2012
126
66
Pretty worrying that this issue still hasn't been fixed in a year, and it's still happening with the latest M1 Max and Pro CPU's. I ended up returning my M1 Mac mini because it happened twice while I was transferring data on external HDD's, and that's a data risk I simply could not live with. I was planning on buying one of these newer MBP's but I guess I need to hold out until Apple addresses it.

Maybe this issue needs to be publicized at a wider level, like an article on Mac Rumors or The Verge, in order to get it escalated and for Apple to actually do something about it.
 

swejo

macrumors newbie
Dec 15, 2021
2
5
I got my MacBook Pro M1 max 10/32c 64gb 4tb yesterday. Every time the computer goes to sleep - be it due to inactivity, triggered manually or via closing the lid - it crashes and reboots with this "SOCD report detected: (AP watchdog expired)" message.

I reinstalled the OS (12.1) all possible ways (install on top, erase and install and DFU mode restore) to no avail. After the DFU restore sleep worked for a couple of reboots with no kernel panics. But after installing some apps (Logic Pro, Dropbox, some audio plugins and Rosetta 2) the issue is back. I even tried uninstalling Rosetta 2 but the issue persists.

Spoke to Apple today and have an appointment with the Genius Bar on Friday. Will update here if I learn anything new.
 

Spanther

macrumors regular
Dec 14, 2020
114
383
I got my MacBook Pro M1 max 10/32c 64gb 4tb yesterday. Every time the computer goes to sleep - be it due to inactivity, triggered manually or via closing the lid - it crashes and reboots with this "SOCD report detected: (AP watchdog expired)" message.

I reinstalled the OS (12.1) all possible ways (install on top, erase and install and DFU mode restore) to no avail. After the DFU restore sleep worked for a couple of reboots with no kernel panics. But after installing some apps (Logic Pro, Dropbox, some audio plugins and Rosetta 2) the issue is back. I even tried uninstalling Rosetta 2 but the issue persists.

Spoke to Apple today and have an appointment with the Genius Bar on Friday. Will update here if I learn anything new.
Thanks for keeping this thread alive. I think it's important and Apple has had difficulty tracking down the culprit.
 

lcubed

macrumors 6502a
Nov 19, 2020
540
326
But after installing some apps (Logic Pro, Dropbox, some audio plugins and Rosetta 2) the issue is back. I even tried uninstalling Rosetta 2 but the issue persists.
the third party software (dropbox, and the audio plugins) would be my suspect.
have you checked to make sure your versions are 12.x compliant
 

coso

macrumors 65816
Feb 9, 2012
1,063
647
I think there are software cases mixed to hardware ones. Errors so frequent definitely must be an hardware issue. I only had 1 single crash in 6 months
 

RumorConsumer

macrumors 68000
Jun 16, 2016
1,645
1,156
Just saw this for the first time on my Mac mini M1 just now. I have a USB C Lacie rugged drive connected that I have had on there for a month or so now doing nightly backups. First time having an issue. Also have a USB A keyboard and mouse switcher. Was in the middle of burning a LTO tape which is a pain in the ass to start over but we'll see if it was just a fluke here.
 

funkbass101

macrumors newbie
Dec 26, 2021
4
0
I just got a new MacBook Pro M1 max 10/32c 64gb 2TB and have two issues.
1. From the initial boot up onwards... Screen flicker. Non stop, even during boot up process ??‍♂️ I am surprised have not had a seizure yet.
2. Frequent crashing. 1-2 times daily (today had it 4 times). It crashes and reboots with this "SOCD report detected: (AP watchdog expired)". More frequent when connected to external monitors (one OR two).

I did take to the genius bar... They basically suggested I just return it. They probably won't even be able to repair it in a timely manner since these are brand new computers and backordered...

I have ordered another one just in case and this one is going back... But I wish there was a fix so I don't have to deal with a new computer setup when that happens... And of course, not having to wait another 6 weeks.

Thank you ??
 

RumorConsumer

macrumors 68000
Jun 16, 2016
1,645
1,156
I just got a new MacBook Pro M1 max 10/32c 64gb 2TB and have two issues.
1. From the initial boot up onwards... Screen flicker. Non stop, even during boot up process ??‍♂️ I am surprised have not had a seizure yet.
2. Frequent crashing. 1-2 times daily (today had it 4 times). It crashes and reboots with this "SOCD report detected: (AP watchdog expired)". More frequent when connected to external monitors (one OR two).

I did take to the genius bar... They basically suggested I just return it. They probably won't even be able to repair it in a timely manner since these are brand new computers and backordered...

I have ordered another one just in case and this one is going back... But I wish there was a fix so I don't have to deal with a new computer setup when that happens... And of course, not having to wait another 6 weeks.

Thank you ??
Dude lame sorry. Sounds like you got a defective unit. God speed.
 
  • Like
Reactions: funkbass101

swejo

macrumors newbie
Dec 15, 2021
2
5
I got my MacBook Pro M1 max 10/32c 64gb 4tb yesterday. Every time the computer goes to sleep - be it due to inactivity, triggered manually or via closing the lid - it crashes and reboots with this "SOCD report detected: (AP watchdog expired)" message.

I reinstalled the OS (12.1) all possible ways (install on top, erase and install and DFU mode restore) to no avail. After the DFU restore sleep worked for a couple of reboots with no kernel panics. But after installing some apps (Logic Pro, Dropbox, some audio plugins and Rosetta 2) the issue is back. I even tried uninstalling Rosetta 2 but the issue persists.

Spoke to Apple today and have an appointment with the Genius Bar on Friday. Will update here if I learn anything new.
Update: I reset the computer several times again after making this post, if I just let it sit with nothing but a clean OS and a local account (no iCloud) it kept crashing as soon as it sleeps, even on the login screen. So I took it to the Genius bar and after 3 minutes of showing them the crashing and crash logs, they simply stated "yeah this one is dead on arrival", he basically looked at the extended error report and the error code indicated faulty hardware.

Apple originally thought I would be ok with waiting another 2-3 months for a replacement unit, but after some arguments with various customer support agents over the phone they sped it up and I just got a brand new laptop to replace the faulty one. Currently I'm working abroad, so my colleagues have received it in my place and I'll be back home later this week to start it. Hopefully and most likely this new computer will not have the same issue.
 

sixtimes

macrumors newbie
Oct 23, 2020
11
14
This just happened to me for the first time after a month of owning a M1 Mini (16G/256G) with Monterey. Nothing totally out of the ordinary with my setup. I finally turned FileVault on this week. With regards to USB, my setup probably deviates from the norm:

My Mattias keyboard is a USB hub and is where my mouse is connected.
To the keyboard I have a Fiio headphone amp that uses one of the USB ports on the Mattias to draw 5v power only

This all worked for years on a 2014 Mac Mini without any similar system or application crashes.
 
Last edited:

tronicdude6

macrumors newbie
Jun 26, 2011
4
1
16in Macbook Pro M1 Max 32GB running 12.1 Monterey

Thunderbolt -> DisplayPort Samsung Neo Odyssey G9
Thunderbolt -> Ethernet Adapter
Thunderbolt -> USB-A 4x Hub -> Mouse & Keyboard & External Hard Drive

Happens frequently when connecting to that setup.

Tried:
  • Swapping DisplayPort cable.
    • Still crashed.
  • Disconnecting external hard drive.
    • Hasn't crashed yet after doing this. Hasn't been that long though.
    • Not practical, as backups won't happen unless this drive is plugged in.
Will Try:
  • Swapping out Thunderbolt-USB-A Hub.
  • Changing the specific thunderbolt port the USB-A Hub / Ext Drive is on.
If it persists I guess I'll get it swapped out? Not sure how that would work; I am covered by AppleCare I can't be without this machine for any length of time.

Does anyone have any updates on this?
 

tronicdude6

macrumors newbie
Jun 26, 2011
4
1
For future lurkers: The best workaround is either
  1. Only plug in your external HDD when you need it, or
  2. Only use an SSD.
I swapped out my ext HDD with an internal SSD with adapter for Time Machine backups and haven't had trouble since.
 
  • Like
Reactions: ignatius345

KernelG

macrumors member
Feb 8, 2008
50
87
SF Bay Area, CA
In my case, it also doesn't seem to be connected to my peripherals. I have the same 3 external SSDs operating all the time on my M1 mini. I've gone weeks/months with no problem, and then bam. It's usually when the machine has been on (but often idling) more than 1-2 days straight and I'm doing something with video; either editing, or just watching YouTube.

I'd be really curious to hear if this is still happening with the M1 Ultra.
 

coso

macrumors 65816
Feb 9, 2012
1,063
647
It happens with the M1 Pro and Max, so probably also the Ultra

I think if it's too often (like multiple times a day) it's just an hardware problem.

It happened once to me in 6 months, hopefully will stay that way (or will break while I'm still in the 2 years warranty, bless Europe)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.