According to reports, MacBook users are experiencing random shut down issues with their devices.
This issue can be particularly frustrating for users, as it can interrupt their workflow and potentially result in data loss if they were working on important tasks before putting their device to sleep.
Social media reports of MacBook random shut down issues
Affected MacBook users are reporting an error message that pops up when they attempt to restart their device after putting it in sleep mode. This message indicates that the device has shut down due to a problem.
Users have only experienced this issue after updating their MacBook’s operating system to macOS 13 Ventura. Prior to the update, this problem did not occur.
Interestingly, the option to “prevent auto sleeping on power adapter when the display is off” is enabled, which adds to the mystery of what is causing these unexpected restarts.
“My touch bar has become glitchy, randomly flashing while the computer is in sleep mode. That’s been going on for many months. Recently, though, this 13″, 2019 model with 16GB of RAM and more than 200GB of free hard drive space has started crashing and restarting while asleep,” a user wrote on Apple’s community forum.
Another person reported: “Once a week my MacBook is getting stuck with pink screen and after shut down with this kind of error. What should I do?”
The issue is also being faced by macOS Big Sur users. Many wrote that their MacBook Pro shuts on its own even when it’s fully charged.
Here’s how you can prevent the issue
Hardware issues or defective third-party kernel extensions are the main culprits behind Kernel Panics. To troubleshoot the problem, users can perform a system diagnosis to identify any potential issues.
It is recommended that affected users report the problem to Apple Support, as they may be able to offer a solution or workaround.
In addition, disabling the “prevent auto sleeping on power adapter when the display is off” option could potentially resolve the issue and is worth trying.
A community specialist on the Apple Support forum has also recommended some workarounds.
There is no official acknowledgment from Apple at the moment.
