Hello,
My Mac Studio M1 Max restarts itself and gives me the report below.
Can anyone help me to decode this message so that I can understand where the problem is ?
This happens about once a week.
Thank you for your help.
Pascal
Mac Studio (2022)
Pascal67 wrote:
It would be nice if someone could look at the error report I posted in my first message.
You've been given as much information as can be gleaned from the Kernel Panic log. Only the programmer of the software referenced would be able to assist you and even then it probably wouldn't be simple. Anything else is just a generalized guess.
panic(cpu 3 caller 0xfffffe001f5cde40): DCPEXT1 PANIC - ASSERT!AFKSerialize.cpp:548 - iomfb_video_async(13)
From my reading of the beginning of the panic report something in the "serialize" section of the code (the error occurred in a section of code called AFKSerialize.cpp) which seems to involve syncing the video frame buffer. What that means....who knows. Sounds like maybe the display is not properly syncing or communicating with the computer.
Maybe some other externally connected device is interfering. Try disconnecting all other external devices. Try connecting the display to another port if possible. There is always a slim chance some third party software is interfering, but I don't see any listed in the Kernel Panic report.
Performing a firmware "Restore" of your computer and testing it thoroughly with the clean OS is the only real way to figure out whether this is a hardware issue or software issue (excluding a bug with macOS). You need to thoroughly test things before installing any third party software and before restoring from a backup, otherwise you may bring the problem back. Once you have reproduced the issue under these conditions, then Apple will be forced to look at the computer and the display for a hardware issue or some unknown bug with the latest OS update or firmwares. FYI, the "Restore" will destroy all data on the internal SSD so make sure to have a good backup. You could try installing & booting macOS from an external USB3 SSD, but this is not as thorough of a test since it is not resetting the security enclave or system firmware. Unfortunately the "Restore" also requires access to another Mac running macOS 12.4+.
Pascal67 wrote:
It would be nice if someone could look at the error report I posted in my first message.
You've been given as much information as can be gleaned from the Kernel Panic log. Only the programmer of the software referenced would be able to assist you and even then it probably wouldn't be simple. Anything else is just a generalized guess.
panic(cpu 3 caller 0xfffffe001f5cde40): DCPEXT1 PANIC - ASSERT!AFKSerialize.cpp:548 - iomfb_video_async(13)
From my reading of the beginning of the panic report something in the "serialize" section of the code (the error occurred in a section of code called AFKSerialize.cpp) which seems to involve syncing the video frame buffer. What that means....who knows. Sounds like maybe the display is not properly syncing or communicating with the computer.
Maybe some other externally connected device is interfering. Try disconnecting all other external devices. Try connecting the display to another port if possible. There is always a slim chance some third party software is interfering, but I don't see any listed in the Kernel Panic report.
Performing a firmware "Restore" of your computer and testing it thoroughly with the clean OS is the only real way to figure out whether this is a hardware issue or software issue (excluding a bug with macOS). You need to thoroughly test things before installing any third party software and before restoring from a backup, otherwise you may bring the problem back. Once you have reproduced the issue under these conditions, then Apple will be forced to look at the computer and the display for a hardware issue or some unknown bug with the latest OS update or firmwares. FYI, the "Restore" will destroy all data on the internal SSD so make sure to have a good backup. You could try installing & booting macOS from an external USB3 SSD, but this is not as thorough of a test since it is not resetting the security enclave or system firmware. Unfortunately the "Restore" also requires access to another Mac running macOS 12.4+.
I contacted Apple Support. They don't blame the monitor directly. They ask me to follow the general procedure, which involves Safe Mode and reinstalling Mac OS.
It would be really helpful if you could tell me what you think is wrong with the monitor in the report.
Some have reported the same issue when connected to third-party monitors, but those users have had their issues fixed by a macOS update.
Are you running the latest version of macOS Ventura, which as I write is 13.4?
I have a Studio Display myself and see no such issues, so that would tend to implicate another factor.
Is this occurring when your Studio is asleep?
Yes, this issue occurs always when my Mac Studio is supposing asleep.
Actually, the Studio is running Ventura 13.4.
It would be nice if someone could look at the error report I posted in my first message.
Thank you for this answer.
The restore procedure seems to be the last chance step.
I'll first try to fix the issue by reinstalling Ventura 13.4 via MacOS Recovery.
I have an SSD and HDD connected via the USB-C ports on the back of the Mac Studio.
I wonder if the fault could be linked to the presence of these discs. It's just a supposition on my part.
Some monitors appear to cause this issue.
You should contact Apple Support directly:
Contact - Official Apple Support
Hi,
Thank you for your feedback.
My monitor is a Studio Display.
Which line in this report allows you to attribute the fault to the monitor ?
Pascal
My computer was restarted because of a problem
