Level 1

11 points

Kernel Panic Mac Mini M1 8GB Ram in Final Cut Pro

Hey,

Anyone else had issues with Final Cut Pro on an M1 computer?

Have had 6 Kernel Panics in 24 hours with my New Mac Mini M1. All has happened in Final Cut Pro while editing XAVC files in 8-bit 4:2:0 from Sony a7siii.

Never been an issue on my Macbook Pro from 2018 running Mojave.

I don't know if this is related to hardware in my specific computer, if something is wrong, or if it's software. Have seen many others being able to edit flawlessly on their new M1 computers. I can edit for about a minute before the whole computer freezes for 1-2 minutes and then shutting down and restarting. I have a report log from one incident. If anyone can read it it would be very helpful.

I had two connected hard drives at the time that specific incident happened. One LaCie Rugged 2TB and one Samsung T7 1TB.

I later unplugged the LaCie drive while troubleshooting but it got Kernel Panic again with only the Samsung T7 was plugged in. I have all my footage and library on that drive, so I can't unplug it.

Really need to get this to work, since I need to send my Macbook Pro to service this week and I have work that has to be done in Final Cut Pro during the time it's away.

Posting a video of an incident and a report log down below.

Thanks in advance,

Kevin

Panic report

Mac mini, macOS 11.0

Posted on Nov 28, 2020 5:24 PM

Top-ranking reply

kevinmuturi Author

Level 1

11 points

Posted on Nov 30, 2020 1:55 PM

Thank you Tom!

I feel very stupid right now, but I seem to have found where the issue is. I have since tried other troubleshooting steps, as it did not seem to be related to either my user, the OS and hardware.

I tried (which I should have from the beginning) to create a new project with different files, coming from different sources. I found other projects to be working without crashing. Looks like it's the library that does not work with the M1 Mac. I could not really switch library in the middle of the project I was working on, but I tried to import the same files into new library, and voilá. Seems to have been the library that was the issue (still don't know what part of the library since it does work on macOS Big Sur on my MacBook. However, that does not concern me anymore since I know that from now on, I have to start new, fresh libraries for upcoming projects that I will do on my new M1 Mac Mini.

Thanks for all your help guys, I really appreciate it!

View in context

Similar questions

47 replies

kevinmuturi Author

Level 1

11 points

Nov 30, 2020 9:06 AM in response to Meg The Dog

Thanks, but it was the same result unfortunately. Here is the report for that crash.

Crash

kevinmuturi Author

Level 1

11 points

Nov 30, 2020 2:00 PM in response to Tom Wolsky

Totally agree, will speak to Apple tomorrow! :) Thanks again!

kevinmuturi Author

Level 1

11 points

Dec 5, 2020 1:58 AM in response to Ian R. Brown

It is an ultra wide curved monitor!

Dec 5, 2020 2:03 AM in response to kevinmuturi

Thanks. I have just googled it. Didn't know such things existed.

ville226

Level 1

4 points

Dec 18, 2020 7:06 PM in response to kevinmuturi

Does this mean, it is not possible to switch libraries between intel and M1 macs ?

Tom Wolsky

Level 10

152,780 points

Dec 29, 2020 6:50 AM in response to iNVisO

There is a known problem with the minis and curved widescreen monitors. Apple has said it will be fixed in a software update.

Dec 30, 2020 8:35 AM in response to kgapol

Do you also have one of the large curved displays?

If not, then it is probably not the same issue as the OP.

Dec 30, 2020 1:47 PM in response to iNVisO

Same here. No curved screen. Flat 4k Philips screen...

Jan 8, 2021 1:14 PM in response to kevinmuturi

In this moment I have some issue. No Chrome ran. But I used Apple USB-C to multiport adapter with external display and Apple bluetooth keyboard+mouse.

So I think problem is not Chrome related.

Meg The Dog

Level 6

13,796 points

Nov 30, 2020 8:55 AM in response to kevinmuturi

Have you tried getting the Samsung SSD out of the configuration?

Try making a small project using the some of the source files you are having trouble with placed on the mini internal drive.

If that works, then see what happens if you can copy the material that was on the Samsung SSD to another drive and edit from that clone.

MtD

Dec 4, 2020 11:31 PM in response to BradSP

Yes, I have those problems since March or so on a rMBP Late 2013, this is not hardware related. What “fixes” it for me and many others is unplugging the monitor, then it’s stable.

Many people report that it has to do with Thunderbolt.

For many, the machine crashes when sleeping and if a monitor is attached. If the cable is removed, it does not crash.

I thought this was not going to happen on M1 Macs :(

kevinmuturi Author

Level 1

11 points

Dec 20, 2020 2:06 PM in response to Luis Sequeira1

Apparently there is a problem, either with the library itself or the files.

I have since created multiple libraries on the M1 and successfully being able to work with it on both machines. Not saying all libraries have this issue, just that this particular library have the issue.

Nov 30, 2020 7:53 AM in response to kevinmuturi

Please run Etrecheck and post its full report here.

I am thinking that the issue is more likely due to a software conflict.

One mac could be a dud, but it is unlikely that this would happen twice.

Nov 30, 2020 8:25 AM in response to kevinmuturi

Uninstall Chrome, uninstall Final Cut Pro and reinstall from the App Store.

See if the problem persists.

Dec 19, 2020 2:14 AM in response to ville226

Libraries have nothing to do with a mac being intel or m1. As long as you are using the same version of FCP on both macs, there is no problem in using a library on both.

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.

Kernel Panic Mac Mini M1 8GB Ram in Final Cut Pro