M1 MacBook Pro crashes and restarts a few times a day

Can you try driving the monitor using the M1’s usbc port and use a usbc hub with no video out and see if it works.

i just fully erased the hard disk , and reinstalled from zero. restored and now will test for a couple of days ( looks smoother)

after i fully restored the system . no crashes so far. it has been 3 days. i think its the only solution

An Aside for your issue but related. Showing Big Sur 11.01 which is way out dated. The most recent version is 11.4 and fixes bugs and Security Issues in previous versions.

Continue with my last post, yesterday night I been in the console and analyze the errors that make restart, in my case there are two, but one that repeats all the time, it seams there are a conflict with star micronics printer driver, TS100. Wow 😳 ... can the simple driver make restart the most stable OS ?

I will check today, let the computer run and see if restart as before or not.

i have a macbook pro 13 M1 512 Gb 8 gb ram .

i think i have found a solution with restarting and first aid . It did repair something like afps was not found and was built again . Something like that on the first aid utility on the restart with long press on the power button.

i will test these two days and see

My system has been running fine since I updated it to11.2 . My theory is that when I uploaded my sysdiagnose they were able to fix the bugs they found.

You may have a slightly different set of bugs showing up.

My suggestion is to call Apple Support and upload all your sysdiagnose files up to them.

They definitely haven’t done their jobs and I really reached my limit this time.

I’m very sorry, Rajesh Kanungo, that you are having such trouble.

With a frequency of «on an average, 2-3 times a day», have you tried running in Safe Mode?

Did the Apple Techs ask you to try Safe Mode? (It is a fairly common test, along with creating a new User account, for testing.)

(As I recall, booting into Safe Mode on M1 based Macs is somewhat different than for Intel based Macs.)

If you don’t have any such crashes, under Safe Mode, then you will have narrowed the possibilities to software that is prevented from running in Safe Mode.

(Since booting into Safe Mode performs a full drive repair, it can take a while for your system to boot into Safe Mode. So, be patient.

However, if it actually repaired an issue on your drive, there is a possibility that it could fix a problem that will remain fixed when you boot into “regular mode”, after your test.)

If you continue to have crashes under Safe Mode, the likelihood that the issue is hardware related is increased, but not absolutely confirmed.

I agree its a CVM Crash log. Since it runs in kernel mode it does cause the system to panic and reboot.

I formatted the SSD and reinstalled the OS. CVMServer crash happened on a clean system *before* installing any 3rd party apps.

I had crashes before the OS reinstall in *safe mode* as well. They are random and I have several instances of crashes while using the laptop on battery with nothing attached to it.

While the laptop normally has chrome/zoom (native arm64) and Spotify (this app being a rosetta2 one) I see no app crashes as such just kernel crashes.

Hardware intermittent errors are really a pain to diagnose and almost impossible to get repaired as apple's front end support is non technical and cannot infer any technical deductions beyond the ones documented in their runbook. They have no concept of kernel let alone what a crash does or to diagnose its signature.

This machine passes hardware diags however crashes occasionally - Its not a 100% "reproducible at will" event. I am not sure what are my next steps.

Tobsn wrote:

switch to display port version 1.2

dont ask why, we don’t know exactly, just try it. report back how it goes :)

(before you say but it’s tb3! - we know - dp is used by tb to send the video signal)

Actually. The USB-C connectors on the M1 Macs are USB4 ports. They are not the USB-C/Thunderbolt-3 ports of the old Intel based Macs.

USB4 supports several alternate modes, and tunneled modes.

However, the set and nature of the modes are not, necessarily, the same as the old USB-C/Thunderbolt-3 ports. (The cable and adapter requirements are not, necessarily, the same, either.)

Lookup the USB4 standard. (The official name does not have a space in it, nor a “.0”. However, many non-official sources do add such “decoration”.)

My Macbook Air M1 crashed several times when I was using a bluetooth headset with dongle. Dongle was in a Thunderbolt dock. Using a USB headset I had no crash so far for a day, so the problem was probably bluetooth related.

Nöppel wrote:

My Macbook Air M1 crashed several times when I was using a bluetooth headset with dongle. Dongle was in a Thunderbolt dock. Using a USB headset I had no crash so far for a day, so the problem was probably bluetooth related.

Actually, since the problem occurred with «a bluetooth headset with dongle» where the «Dongle was in a Thunderbolt [actually, USB4, or, as Intel likes to call it, Thunderbolt-4] dock», the problem is like so many others: USB driver related.

Rajesh Kanungo:

It’s not, actually, the hubs, per se. It’s the third-party driver software that is loaded and run—at the Kernel level of the Operating System (OS)—that is the actual culprit.

If drivers, or, at least, these sorts of drivers, could be run outside of the Kernel, then such would not cause Kernel panics (practically by definition).

Unfortunately, the experiments I know of, where people tried to devise Kernels that could function in this way, found such Kernels to be far too slow! (Too much communication going in and out of the Kernel.)

Maybe, someday, we’ll be able to isolate such drivers, somehow, in such a way that poorly written drivers will not cause such issues.

Unfortunately, such is not, presently, the case.

So. Poorly written driver software will take your system down.

Make sure you vet your hardware—and their accompanying drivers (which you will, typically, never see, as a user)—well, for your systems!

Fortunately, this issue will diminish over time, as these drivers are updated for the new OS (and, in the case of Apple Silicon systems, for the new hardware).

Hi Kjoope,

You should read in attention the report errors in the console. In my case I have noticed that a printer driver cause a panic crash.

I believe this new architecture is quite sensitive with any application or driver that was built for intel architecture. Whatever I'm not an expert, just a Mac user. Please extract conclusion by yourself, in my case I didn't return my computer expecting the printer company should release a new driver to print, that isn't after 3 months.

I still do not have choice to print in any thermal printer of the market. Epson, Star Micronics, etc.. No one have compatibility with OS 11 Same point I spent 1300€ and still waiting,

In your case I advice you to uninstall whatever that makes conflict with new OS, if you start from scratch with you will find that crashes descend near zero. You have 15 days to try by yourself. Also let you known that I had recently 2 panic crashes as you can read in this other article in Mac rumours : link

I suspect mine is related to either Focusrite drivers (external audio interface).

If I keep that system extension disabled (even though it's supposed to support M1 and Big Sur) things seem more stable. I can't use the audio interface of course though :(

11.4 might also have helped too.