M1 MacBook Pro crashes and restarts a few times a day

You have a clear case of drivers causing a panic. Is trackpad driver called actuator?

i suggest you should do a clean install after formatting the boot disk and check if it stabiles the system.

It has been two weeks without one crash. The only reliable solution is to completely erase both parts of the hard disks and clean install . Than restore from a backup

I have the same issue. The M1 13" MacBook Pro is extremely unstable.

The issue is an out of bounds memory write. This is really bad. Some code is not checking bounds and not failing gracefully.

panic(cpu 4 caller 0xfffffe00276f0320): "vm_page_insert_internal: (page=0xfffffe00314156b0,obj=0xfffffe1003c2a100,off=0x10000,size=0x10000) inserted at offset past object bounds"

Debugger message: panic

My M1 Mini using a Dell 4K Monitor worked fine (using HDMI but not USB-C) until the 11.1 update. Now crashes with purple screen flash then restart. I reinstalled Big Sur and the issue still happens. I found that quitting Safari and just using Firefox reduces the number of times it crashes, but Apple needs to address this issue. I am going to keep using Firefox and wait for another Big Sur update.

I think there is something else going on. My replacement M1 crashed when it started (kernel panic), froze, then crashed again (kernel panic). This is a just unpacked M1 with only a power supply and a USBC connected. Migration Assistant had not even started. It crashes less that my previous M1.

I have been struggling for almost 2 months with Apple support people and I have spent countless hours including getting a replacement M1, buying new hubs on their suggestion to see if it would reduce the problem, USBC cables, etc.

Apple is fully aware of the problem. It hasn't crashed (yet) after I updated to 11.2 today but others are not having the same luck.

This means that their testing was not good enough when they shipped. And systems do ship with tons of bugs, many of them very difficult to fix.

What you have done, carlmurr, sounds like part of the Safe Mode boot process.

Regardless, it sounds like it found and fixed a filesystem issue!

I would run the Disk Utility, with the view set to All Devices, and see what it shows.

You could post a screenshot of what it shows, and we can provide the expert opinion on whether it all looks the way it should.

Okay, Please don't ry this unless you are desperate and groveling in front of the Apple Tech support engineers for 2 months:

I did something bad and (hopefully) something good came out it:

1. Went into system recovery and then  Utilities > Terminal
2. Type in nvram -c

Okay I was desperate.

It gave a few errors and then, on restart, said that I needed to reinstall the OS.

So I reinstalled the OS.

No crashes for 24 hours.

Wow!!! I have done 4 presentations over video conferencing, many hours of working, and no crashes ...

Warning: it worked for me today. May not work tomorrow.

carlmurr wrote:

…

… NOTHING WORKED until i FULLY ERASED everything from the disk utililty . Reinstalled from scratch and restored the backup . STOP WASTING YOUR TIME WITH SOMETHING ELSE. its the only way believe me

I would not recommend an indiscriminate «restore [from] backup» because that is likely to restore the problem.

However. I’m very glad that you were among the lucky few where the «restore» appears to have not «restored» the problem.

Welcome, elip_aka, to Apple Support Communities!

Do you have the crash report that you could share with us, by posting using the “Additional Text” button in a comment?

This may either be a plain crash report, or a Kernel Panic report.

Whatever it is, it should help us to better diagnose your particular issue.

What keyboard are you using? Only the built-in MacBook Pro keyboard, or some other keyboard?

I can assure you that this is not a common issue, except in cases with hardware or software issues.

Install SwitchResX, launch its daemon and there you go. It feels crazy that a multimillion dollar company can't fix this stuff on their multi thousand laptops and a micro developer does first. Lol.

To add:

Don’t restore any software, settings, etc.

Don’t use any add-on hardware, such as Bluetooth or USB devices. (Fortunately, that’s easier to do on MacBooks than desktops.)

Return it and wait till Apple stabilizes their system. Happens all the time to me.

Sound like a good catch, alexywang!

I doubt, but cannot be certain, that it is a matter of «too many devices connected at once». That certainly shouldn’t cause any sort of crashes.

However, new devices—whether Bluetooth or USB—can require installation of new “drivers”. Drivers work at the “kernel” level, and can certainly cause system crashes, kernel panics (that error log is a kernel panic).

Unfortunately, kernel panics are not intended to be diagnosed by users—they simply are not supposed to happen!

So, they are not “user friendly”! 😏

Rajesh Kanungo wrote:

I really don’t understand where you are coming from. This is an M1 Mac with a fresh install of OS as a few other users have talked about.

There are no third party drivers.

It still crashes.

The whole reinstallation process was guided by Apple level 3 support because of the crashes.

So this installation is as clean as it gets.

There are no third party extensions misbehaving.

There could be a hardware fault somewhere. Or it could be a software issue as was clearly indicated by the out of bounds check failing in the crash dump. or something in hw is triggering the software or exposing a software fault.

What we have determined with Apple support is that it is definitely not a third party problem in my case.

So. No third-party software at all?

If so, then there is an issue.

The odd thing is that a truly clean—no third-party software at all, and no added hardware (almost always involves additional drivers, downloaded in the background)—is the most tested configuration of all! Bar none!

I have yet to see any reports truly claim any such issue at such a level.

If you have such, then you should return your machine, while still within the return window. If possible.

I just bought my M1 MBP on January 9, 2021 and this has happened to me 6 times since I have bought the unit. the 5th and 6th time happened today and I will do a full restore to verify that it's not hardware. There is a good chance that this is firmware related and that it can be fixed however I will return it if and when it happens again. I love the performance and battery life of the M1 but I can't have this happening when I do most of my work on it.

My Mac:

13" MBP

16GB RAM

1TB Storage

Connected devices:

CalDigit Thunderbolt 3 Dock

Samsung 32 Display via Caldigit

Samsung T7 Drive Was not connected during the 3rd and 4th reboots

1TB G Drive - Time Machine backup via CalDigit

"The unit freezes when waking from sleep, the screen turns purple then reboots to Apple logo and Boot loader. "