New MacBook Air (M1, 2020) crashing all the time!

New M1 MacBook Air keeps crashing and freezing... I can't force quit as the keyboard becomes unresponsive.


Help!


Anyone else out there struggling with this?


I keep checking for system updates but nothing yet...

MacBook Air 13″, 11.0

Posted on Dec 3, 2020 2:19 AM

Reply
Question marked as Top-ranking reply

Posted on Feb 2, 2021 1:22 PM

Erased and reinstalled OS at last 10

times. Apple sent it off for repairs twice. They couldn’t find any issues but still replaced logic board and touchpad both times. It still came back with same problems of freezing as soon as I used keyboard or touchpad. I was without a usable machine for almost two months from I bought it new. Spent many hours on phone with Apple support who didn’t have a clue and passed me around, often never getting back to me. They constantly refused to exchange it even though it was obvious the machine was a dud. Eventually they relented and I finally got a replacement. It works fine just as it should. And that was on 11.1 I remain convinced it was a hardware issue.

215 replies

Apr 22, 2021 5:36 PM in response to billykioso

I have had a similar experience. The MacBook Pro M1 8 GB ram locks up with video still running and the touchpad cursor still moving around but no response to clicks. Keyboard works for a while then locks as well. I have to shut down with the power button. Happens about once a week, more often if I use it for many consecutive hours. I have reinstalled Big Sur and uninstalled non-Apple program as my chats and Genius Bar sessions have requested. It is off having its mainboard replaced after having the trackpad replaced a week ago. Many of the descriptions to date mention seeing beachballs and crashing.

Apr 23, 2021 12:03 AM in response to kk_uu_

So just to give you my feedback, if you look up in this thread you will see that I got a macbook M1 returned it, got a PC as replacement, returned it and got another macbook M1, I will not re-enter in the details, but what I get out of that : My first macbook M1 was crashing, the new one is working perfectly, not a single crash since I got it two weeks ago... it is just perfect, I use it for heavy computation (AI research) and it works fast and nicely ... I suspect that Apple may have some issue with the new processor (especially as it is the only processor engraved so small )... so I think if you have issue it means that your processor or motherboard has an issue, and I will advice you to : return your computer and get a new one (if you bought it from a nice company like Mediamarkt where you have 100 days no question return policy) or go back to apple store and have them fix it ... it is unacceptable to experience this type of issues on a computer in this price range ... (I think that by now apple is well aware of the issue, so they should not make any problem to replace the motherboard ...)

Feb 27, 2021 11:12 AM in response to jbilello

It might help to understand the probable reason this is happening. Moving to a new chip means all the software has to be recompiled, basically rewritten. Apple did that with theirs, but cannot compel third parties. In the interim, Apple wrote an emulator, so the old software would run on the new chip - an essential, but inefficient and problematic temporary solution. In summary? Apple had no choice, It is probably going worse then they hoped. You should avoid 3rd party software as much as possible, and don't expect a quick easy fix.

Personally a complete clean install and only using Apple apps with no migration solved all of my problems. But that isn't a solution for many people.

Apr 13, 2021 7:39 AM in response to billykioso

Same issue here. Beachballs appear when there is memory pressure - look at activity monitor (memory used). Once it hits 7GB of my 8GB, watch out! Firefox is the main offender on my mac but safari doesn't work with an important support site I have to use. Even with low memory pressure Safari is unreliable. You would think the browser shipped with the OS would be most stable but that's not it case - It is near rubbish. So frustrating.


I see below that 16GB machines are having similar issues so this may not just be memory pressure but memory management in general. Disappointing that this has not been addressed by apple, it may be design related. If that's the case, they'll never come out and say it.

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.

New MacBook Air (M1, 2020) crashing all the time!

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