Buggy MacBook or MacOS????

[beanbaguk]

Am I the only one getting utterly fed up with the buggy nature of my new M1????

Apps constantly crashing (native and non-native), external displays not waking after sleep, sometimes not even seen yet a moment ago they were there.

Hanging apps forcing you to reboot to get some sense of stability and now today, I wake my MacBook and only part of the display is shown so it’s impossible to access the dock.

I tried to reboot but only a forced shutdown was possible.

While I love the battery life and speed, I do long for an Intel MacBook again for stability as that overweigh’s all the other benefits!

Utterly fed up, even as far as going back to use my Windows Lenovo machine!!!

 

[The Cockney Rebel]

I don't wanna be "that guy" but I have no issues with my M1 Pro.

Except for a bit of Safari stuttering when scrolling, there's nothing wrong with the machine.

If you can return it for an exchange, then I'd say give that a try.

 

[jdb8167]

Am I the only one getting utterly fed up with the buggy nature of my new M1????

Apps constantly crashing (native and non-native), external displays not waking after sleep, sometimes not even seen yet a moment ago they were there.

Hanging apps forcing you to reboot to get some sense of stability and now today, I wake my MacBook and only part of the display is shown so it’s impossible to access the dock.

I tried to reboot but only a forced shutdown was possible.

While I love the battery life and speed, I do long for an Intel MacBook again for stability as that overweigh’s all the other benefits!

Utterly fed up, even as far as going back to use my Windows Lenovo machine!!!

The displays not waking from sleep is widely reported and I had some significant problems until I started using a USB-C dock but crashing apps isn’t something I’ve seen or heard of a lot. Is it specific apps or in general? If it is a general problem then I suspect either a bad OS installation or some software utility is incompatible.

Shutdown and reboot problems seem to be a Big Sur issue not related to the M1 since I have the same problem on my 2013 Mac Pro.