FCPX Crashing my entire OS CONSTANTLY

[Aaron Rock]

Thank you for all the feedback on this. It has yet to be pegged down. My boss believes it’s a raid issue, I disagree. Ive used 2 separate raids with no permission errors and this issue still occurs. Another anomaly of X that goes unanswered.

[Doug Metz]

Out of curiosity, how are you connecting to the RAID?

Doug Metz

Anode

[Aaron Rock]

E-sata is the only connection option for our raids. HDMI would probably be less problematic.

[T. Payton]

I just noticed that you have an older Mac Pro. This looks like the 2006 model. I just recently retired my 2006 Mac Pro because after 7 years of use it was starting to have some odd issues. Adobe Creative Suite just stopped working and would become unauthorized. Even after a system reinstall. I have seen bad RAM module problems only appear when an App is apparently using a portion of the RAM that is normally not used. Once I couldn’t get the machine to startup unless I rebooted the machine with my PCI cards in a certain slot combination.

I would defiantly say there is a correlation between FCPX and your problem, but it is probably exposing a bad component somewhere on your system.

Machines do fail.

Just my 2 cents.

——
T. Payton
OneCreative, Albuquerque

[Doug Metz]

I concur. I’ve had some weird occurrences with eSATA cards as well… might be that a driver update and/or new shielded cable would stabilize things.

Doug Metz

Anode

[Alexei Berteig]

Someone out there suggested (of course) trashing the preferences and relaunching. Failing this, if you have Perian installed go to your Mac’s preferences pane, find Perian, and uninstall it. I did this a couple hours ago and so far no more crashes. (Fingers crossed)
– FCX 10.0.9 on MacBook Pro 17″ etc…

[Ernest Jones]

I have an idea… A simple one.

It seems that repeated crash on FCPX are caused by RAM issue.

The point is that at the beginning, FCPX pre-load all the project in the background.

I think that this process is responsible for a huge RAM consumption.

The solution can simply be : put all the project datas out of the FCPX folder.

This way, FCPX won’t pre load the projects and save some RAM…

After I don’t know…

You guys talk about stuff way too far from my understanding… I don’t know if my little technic will do anything

[Mark Smith]

FWIW Perian seems to be toxic to FCP 7 and FCPX among other things. Ditch that application if you have it installed. I once spent a very tense 3 days recovering from damage done by Perian.

[Kevin Greutert]

I, too, am having this problem with this despicable program (I’m stuck for one project on Final Cut Pro X). Mid-2014 Retina macbook Pro, 16 gig ram, solid state drive. Just playing back a sequence, suddenly the keyboard and mouse do nothing. The sequence keeps playing, but I can’t stop it, crash out of FCP, or anything else. Only recourse is hard reboot. Never happened on any other software. I wish Cupertino would drop into a sinkhole.

[T. Payton]

Hi Kevin,

Bummer you are having trouble. It has to be frustrating. This original thread was likely the result of failing hardware, not FCPX specifically.

Regarding things now, I’ve haven’t specifically heard of this issue. We use FCPX all day on iMac’s, MacPros, MacBook Pro Retina’s etc.

Are you saying that command-option-escape is not giving you the chance to force-quit the app?

Can you let me know your OS version as well as your FCPX version?
Are you using any third-party FX Plugins? like Coremelt Lock & Load, Slice X, Track X, FX Factory plugins?

– T.

——
T. Payton
OneCreative, Albuquerque