Random restarts of M4 Mac Mini with "SOCD report detected: (iBoot async abort)"

TL'DR: M4 Mac Mini has random restarts indicating "SOCD report detected: (iBoot async abort)", since last 6 months and it has only got worse over time. ChatGPT says only option might be to get logic-board replaced, but that is prohibitively expensive. Anyone found a solution to that problem ?


Long read:


My M4 Mac Mini is the base model (256GB SSD) but with 24GB unified RAM. This is my first macOS device, and I was (still am), relatively new to this OS. My background is Windows user of 2 decades, so some of my fumbling around with the issue being described is tainted with that background.


This Mac Mini is running macOS 15.7 since the very beginning (and currently at 15.7.4 -- latest maintenance release). The unit was received in early Dec'2024 and it ran perfectly fine until about July'25. However, from Aug'25 I started observing some periodic random restarts. Initially, I did not pay much attention assuming it to be a random occurrence, like once in every 10-12 days (something that was a bit common in Windows world). The frequency however kept creeping up to about once in every 3-4 days until Dec'25. By early Feb'26, the restarts were happening randomly, but on bad days happened 15-20 times a day, sometimes 1-2 apart. Since then, I've raised a case with Apple Support who made me run Diagnostics remotely which identified no hardware issues or other issues, other than the fact that I am NOT running macOS 26 (which is deliberate, as 15.7.4 is very much in support currently). I've wiped the mac drive completely and reinstalled macOS 15.7.4. The problem frequency went down, now back to random restarts every 3-4 days, but this is barebones macOS, with almost no 3rd party software. As the load on the system (I guess) increases, s.a. run few OrbStack Linux VMs, some docker containers, also LM-Studio running some light models locally, which is essentially what I was doing earlier, I suspect I'd be back at the problem. Apple Support, made me take the device to Genius Bar, who did exactly the same steps I did with Apple Support on phone, then kept it under observation for a week, found nothing and returned the device, after reinstalling MacOS yet again. I was however given an option to get the Logic-board replaced at full cost, which in my local currency (Indian Rupees) is about 75% the cost of a new Mac Mini, but an additional 10% of diagnostic fee. I cannot afford that sum at this time. Wondering if anyone found any solution to this problem.


I've found many other threads here, which seem to indicate that I am not the only one facing such (or similar) issue:

https://discussions.apple.com/thread/256095678

https://discussions.apple.com/thread/255870964

https://discussions.apple.com/thread/256215985

https://discussions.apple.com/thread/255887282

https://discussions.apple.com/thread/255910274

https://discussions.apple.com/thread/255425869

https://discussions.apple.com/thread/256026767


Mac mini, macOS 15.7

Posted on Mar 18, 2026 5:52 AM

Reply
Question marked as Top-ranking reply

Posted on Mar 18, 2026 7:00 PM

See the post by @Grant Bennet-Alder here:

https://discussions.apple.com/thread/256261346?answerId=261867117022&sortBy=oldest_first#261867117022


It provides details on what is involved to get Apple to perform a hardware repair....the General Debugging tips sections doesn't really apply to you here due to the type of Kernel Panic your computer is having as described by @Servant of Cats. Your best option to have Apple go more quickly to a hardware repair is to do the following:


Perform a clean install of macOS where you do not install any third party software, you do not restore from a backup, and you do not sign into your AppleID/iCloud. If you can reproduce the Kernel Panic under these very strict conditions, then it is much more likely Apple will start replacing hardware components (most likely the Logic Board).


With an Apple Silicon Mac a clean install can done with several different methods.....the quickest methods are also the least definitive, but may be enough to convince Apple....of course the most definitive method may have the greatest impact with Apple. Here are the clean install options starting with the quickest & least definitive:


  • Perform an "Erase All Content & Settings" which just deletes all of your data & customizations to macOS...only the Data volume file system is recreated. It leaves the macOS system volume & two other hidden Containers (one is for the early boot process) intact.
  • Use Disk Utility to erase the disk (aka "Macintosh HD" and its Volume Group) followed by reinstalling macOS....this results in the file system for the entire APFS Container holding macOS & your Data volume to be recreated. It leaves the two other hidden Containers (one is for the early boot process) intact.
  • Perform a DFU Firmware Restore....requires access to another Mac currently running macOS 26.x Tahoe (may be able to also use macOS 15.7.2+ Sequoia....maybe if using Apple Configurator). This option resets the security enclave chip, system firmware, and internal SSD (destroying all data & system files on it)...it will also push a clean copy of macOS onto the internal SSD. This can be very tricky to perform as it can take multiple attempts to place the Mac into DFU Mode. Even when selecting "Restore" on the host Mac, you may not always get an error message or one that makes any sense. Everything is reset & recreated here including the two hidden Containers.



Here is the Apple article containing instructions for "Erasing All Content & Settings" as well as using Disk Utility to erase the disk:

Erase your Mac and reset it to factory settings - Apple Support


Here is the Apple article with instructions for performing a DFU Firmware Revive (using the Apple Configurator app is best as it works better & provides more feedback when trying to put a Mac into DFU Mode):

How to revive or restore Mac firmware - Apple Support


FYI, if you can reproduce the Kernel Panic on demand in front of an Apple tech under these conditions for a clean install, then you will have the best chance of having them repair the hardware issue. Pay attention to when those Kernel Panics tend to occur to see if you can notice a pattern. Even if you cannot reproduce it on demand, at least if it has occurred under those conditions it should have Apple sit up & notice.


Good luck and please keep us updated on your progress.


2 replies
Question marked as Top-ranking reply

Mar 18, 2026 7:00 PM in response to b_dutta

See the post by @Grant Bennet-Alder here:

https://discussions.apple.com/thread/256261346?answerId=261867117022&sortBy=oldest_first#261867117022


It provides details on what is involved to get Apple to perform a hardware repair....the General Debugging tips sections doesn't really apply to you here due to the type of Kernel Panic your computer is having as described by @Servant of Cats. Your best option to have Apple go more quickly to a hardware repair is to do the following:


Perform a clean install of macOS where you do not install any third party software, you do not restore from a backup, and you do not sign into your AppleID/iCloud. If you can reproduce the Kernel Panic under these very strict conditions, then it is much more likely Apple will start replacing hardware components (most likely the Logic Board).


With an Apple Silicon Mac a clean install can done with several different methods.....the quickest methods are also the least definitive, but may be enough to convince Apple....of course the most definitive method may have the greatest impact with Apple. Here are the clean install options starting with the quickest & least definitive:


  • Perform an "Erase All Content & Settings" which just deletes all of your data & customizations to macOS...only the Data volume file system is recreated. It leaves the macOS system volume & two other hidden Containers (one is for the early boot process) intact.
  • Use Disk Utility to erase the disk (aka "Macintosh HD" and its Volume Group) followed by reinstalling macOS....this results in the file system for the entire APFS Container holding macOS & your Data volume to be recreated. It leaves the two other hidden Containers (one is for the early boot process) intact.
  • Perform a DFU Firmware Restore....requires access to another Mac currently running macOS 26.x Tahoe (may be able to also use macOS 15.7.2+ Sequoia....maybe if using Apple Configurator). This option resets the security enclave chip, system firmware, and internal SSD (destroying all data & system files on it)...it will also push a clean copy of macOS onto the internal SSD. This can be very tricky to perform as it can take multiple attempts to place the Mac into DFU Mode. Even when selecting "Restore" on the host Mac, you may not always get an error message or one that makes any sense. Everything is reset & recreated here including the two hidden Containers.



Here is the Apple article containing instructions for "Erasing All Content & Settings" as well as using Disk Utility to erase the disk:

Erase your Mac and reset it to factory settings - Apple Support


Here is the Apple article with instructions for performing a DFU Firmware Revive (using the Apple Configurator app is best as it works better & provides more feedback when trying to put a Mac into DFU Mode):

How to revive or restore Mac firmware - Apple Support


FYI, if you can reproduce the Kernel Panic on demand in front of an Apple tech under these conditions for a clean install, then you will have the best chance of having them repair the hardware issue. Pay attention to when those Kernel Panics tend to occur to see if you can notice a pattern. Even if you cannot reproduce it on demand, at least if it has occurred under those conditions it should have Apple sit up & notice.


Good luck and please keep us updated on your progress.


Mar 18, 2026 6:21 PM in response to b_dutta

b_dutta wrote:

M4 Mac Mini has random restarts indicating "SOCD report detected: (iBoot async abort)",


I'm guessing that the "SOC" in "SOCD" stands for "System on Chip". In the case of your M4 Mac mini, that would be the M4 chip, which contains CPU cores, GPU cores, and other important pieces of hardware such as RAM and I/O controllers.


According to Wikipedia, iBoot is the stage 1 and stage 2 boot loader for your Mac, and for other Apple devices that have Apple Silicon processors or T2 security chips.


You could try experiments like disconnecting peripherals, or not putting the Mac mini to sleep (shut down all of the way, or use Lock Screen and turn the monitor off, instead), to see if you can identify possible "triggers". But my gut instinct is that we are dealing with a hardware error that will require chip (and logic board) replacement.


I would suggest reading the replies by Mr. Bennet-Alder in this thread:

repeated message "SOCD report detected: (iBoot panic)" when starting – Apple Discussions

Especially this one:

"System On a chip Daemon (SOCD) reports SERIOUS Hardware errors that occur in the Apple-Silicon System On a Chip.


if it occurs once and is gone, just ignore it.


if it is occurring often, you need to contact Apple Support and work with them. The ideal outcome is for them to DIRECT an Apple Service Provider to repair (by replacing) your mainboard.


The risk of going to the Genius Bar directly with this is that they may run their diagnostics, not see it happen, and return your computer to you un-repaired. The Genius Bar technicians generally do not read panic reports.


You MUST have backups before submitting your Mac for this service. Your boot drive will NOT be returned to you, and your files will NOT automatically be saved."

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Random restarts of M4 Mac Mini with "SOCD report detected: (iBoot async abort)"

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.