Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Mac Mini M1 crashes upon display sleep
- Thread starter usagora
- Start date
- Sort by reaction score
We’ll see. Their initial tests didn’t show anything wrong. I wonder if it was something that updated firmware, and is causing the issue.
So I think I figured it out, but I’ll have to test tonight/tomorrow. The M1 Mini ran fine for a year, no crashing, with a Samsung 27” 1080P monitor.
Then this January, I got a new LG 27” monitor. That’s when the problem started.
Turns out that the LG I have is 75Hz native, and I’m wondering if that’s what’s causing the issue. The Samsung is 60Hz.
Seems insane to me that a different refresh rate would actually cause a kernel panic, but I guess I’ll find out. I don’t recall ever really doing anything in properties for display; I just plugged in the monitor and it worked.
Then this January, I got a new LG 27” monitor. That’s when the problem started.
Turns out that the LG I have is 75Hz native, and I’m wondering if that’s what’s causing the issue. The Samsung is 60Hz.
Seems insane to me that a different refresh rate would actually cause a kernel panic, but I guess I’ll find out. I don’t recall ever really doing anything in properties for display; I just plugged in the monitor and it worked.
Very interesting. I also have a 27" LG monitor (UHD) but it's 60Hz. But I'll check out the display settings tomorrow and see what it's actually set to.
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Just checked and mine is indeed set to 60Hz, so at least for me I don't think the refresh rate is the issue. The only other settings are lower rates. Perhaps it's something else about the LG displays that's causing the issue.
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Not like yours is (in the middle of working) but it does still occasionally crash. Seems to only happen after it sits over the weekend when I'm not at work and not accessing it remotely. If I go less than 24-hours between sleeping/waking the display, it seems to be fine.
This is really frickin weird. I’ll have to see how it goes, and report back. Really am tempted to switch back to the older Samsung, but it’d be a shame not to be able to use this beautiful LG.
Agreed - it's bizarre. At least you still have the Samsung to test this, because that would confirm whether the display is actually the issue. It's really hard for me to imagine it's the display itself, but then again a recent thread reported that the Studio Display caused issues with someone running Catalina, so I guess it's possible for a display to cause problems:
Studio display does not work with older versions of MacOS
I have a Studio display which I just had to return because it does not work with my work laptop locked to Catalina due to a corporate policy. I had assumed the requirement for macOS 12.3 or higher was only for supporting things like center stage and hey Siri. This is not the case. When...
forums.macrumors.com
we'll see what happens. I've now got the Mac running in "Scaled" but at the native resolution (2560x1440), 60Hz, and HDR disabled. I'll report back on what it does (or doesn't) do, as it usually happens relatively quickly.Agreed - it's bizarre. At least you still have the Samsung to test this, because that would confirm whether the display is actually the issue. It's really hard for me to imagine it's the display itself, but then again a recent thread reported that the Studio Display caused issues with someone running Catalina, so I guess it's possible for a display to cause problems:
Studio display does not work with older versions of MacOS
I have a Studio display which I just had to return because it does not work with my work laptop locked to Catalina due to a corporate policy. I had assumed the requirement for macOS 12.3 or higher was only for supporting things like center stage and hey Siri. This is not the case. When...
Yup, crashed again. Monitor specifically set to 60Hz, no HDR. I guess my last resort is to switch back to the Samsung 60Hz/1080P monitor that it worked for a year with, and see if it fixes it. Otherwise, it’s going on eBay and I’m getting a Thinkpad or something. I’m tired of this BS.
"Ok, the bad news is it's still crashing. The good news is it survived max q and is now in low earth orbit" ?
But seriously, it will be very interesting to see how this test goes!
Yeah the only variable at this point is the monitor. Same install, same apps, same settings in power.
so.....I was wrong. The monitor was NOT the only variable. I had forgotten that I had given my son my USB keyboard, so that he could work on his Raspberry Pi (smart little kid). So I added my old Apple bluetooth keyboard to the Mac Mini.
Switched it out for another USB keyboard on Sunday, and removed (forget device) the Apple BT keyboard.
No crashes/freezes yet. WTF? I've NEVER in several years of IT and also being a Mac user, seen something this weird.
Ok, I think you're onto something here. Remember in my OP that I mentioned I couldn't get my Apple wireless Keyboard (A1314) to connect during setup? I wonder now in hindsight if that was a clue that the keyboard could be problematic. I just didn't think much of it because I was able to connect it without issue after completing the setup with a wired keyboard, and it has remained reliably connected ever since. But it may very well be sending some odd "messages" to the Mac Mini that is causing it to crash.
Still strange though how your experience seems worse, with crashes actually happening while you're using it. Mine as always been when I'm not using it.
Which model is your Apple wireless keyboard? Again, mine is A1314, which is an older one (came with my 2012 iMac) that uses 2 AA batteries.
I am having the exact same issue as you folks on a M1 Mac Mini.
Interestingly enough, I am also using the same keyboard as you, the A1314 that also came with my old 2012 iMac.
I'm going to try the same solution and switch out my keyboard.
Interestingly enough, I am also using the same keyboard as you, the A1314 that also came with my old 2012 iMac.
I'm going to try the same solution and switch out my keyboard.
Same one, A1314. Well, I assume that's the model; it's definitely old, and it definitely looks identical to the one when you Google Apple Keyboard A1314. I'd have to look tonight to confirm.
Still no crashes; uptime since last Saturday(?). Several days, so far so good. Even ordered a Microsoft ergonomic keyboard and Logitech trackball for it, which are working great
Awesome - so the only thing you changed was ceasing to use the A1314 keyboard and instead using a wired/USB keyboard? Are you using the Logitech trackball with Bluetooth or USB/RF? I hope it's not an issue of Bluetooth, period (and not just the specific Bluetooth keyboard and/or mouse we were both using . . . I'm using the Magic Mouse 2, btw), because I'd sure hate to have to go back to wired mice and keyboards. On the other hand, my Mac Mini hasn't crashed for about 2 weeks now, so I'm not in a critical situation.
USB Microsoft keyboard (which I was going to get anyway; love the ergo/natural splits). The Logitech is just using the RF dongle. I suppose I could try the BT aspect, which it does too.
My BT is still turned on with the Mac though, because I use the Apple Watch to unlock/approve apps, as well as my PowerBeats Pro earphones. No issues.
Got it. Yes I also do the same with my AW on the Mini. At some point I may just buy a new Apple Keyboard with TouchID and keep the old one as an emergency backup.
I was going to do that; but honestly I’m a little nervous about Bluetooth keyboards right now
Hi guys,
I'm so happy about finding this thread. I have a MacBookPro with M1 and have a similar problem. My Mac is working fine. But when I shutdown the Mac in the evening and restart it a the next morning I only get the beachball. So, I have to hard reset the Mac, then restart, then shutdown by command and reboot again. After that it is working for a day.
And, I also have LG monitors. I have two LG monitors and on both monitors I have the same issue. But I do not use a external keyboard.
Both of my monitors are using 60 Hz (sorry, I do not have a monitor from different manufacturer, so I cannot check this).
I also have the above setting NOT set in the preferences, I now enabled it.
One more aspect - I also use Splashdot, I read one of you guys also use it. Might this be the software which is playing a role in this issue?
I will be back to report my experiences with setting this preferences parameter.
I'm so happy about finding this thread. I have a MacBookPro with M1 and have a similar problem. My Mac is working fine. But when I shutdown the Mac in the evening and restart it a the next morning I only get the beachball. So, I have to hard reset the Mac, then restart, then shutdown by command and reboot again. After that it is working for a day.
And, I also have LG monitors. I have two LG monitors and on both monitors I have the same issue. But I do not use a external keyboard.
Both of my monitors are using 60 Hz (sorry, I do not have a monitor from different manufacturer, so I cannot check this).
I also have the above setting NOT set in the preferences, I now enabled it.
One more aspect - I also use Splashdot, I read one of you guys also use it. Might this be the software which is playing a role in this issue?
I will be back to report my experiences with setting this preferences parameter.