FCP Quits when simply clicking on a clip

Those were "microstackshot" diagnostic files, not crash files. They had some use (see below) but I need the .ips files or any file containing "Final Cut" in the name, in either of these folders:

This folder: ~/Library/Logs/DiagnosticReports

OR this folder:

~/Library/Logs/DiagnosticReports/Retired

If there are no files containing "Final Cut" or "FinalCut" in the name, that implies it hasn't crashed in a while. The next time it crashes, or just vanishes, *immediately* look in those folders and send me the crash files.

However: first, there are some complications based on your configuration we need to simplify -- just for purposes of troubleshooting. We only want crash files once these temporary changes are made.

• Put your library file .fcpbundle on the internal APFS with ownership enabled.
• Select the backup location on that internal APFS drive. To select FCP backup location, in FCP select the library in the left sidebar. Then in the Inspector (CMD+4 toggles), select Storage Locations>Modify Settings, and under "Backups" make sure that is on a local APFS drive. The default location is ~/Movies/Final Cut Backups.localized.
• For troubleshooting purposes, put your data files on a local APFS drive. Once we get this under control, we can discuss the possibility of putting your media files on a network drive, but for temporary troubleshooting purposes, don't do that.
• Why? See below.
• Temporarily bypass external video I/O. Unplug the UltraStudio and disable A/V Output in FCP (Playback prefs). If crashes stop, update/rollback Blackmagic Desktop Video and retest. (The device is present per USB tree.) Reason: Blackmagic Desktop Video normally works OK, but has been implicated in other FCP crashes.
• In Finder, Get Info on the current working volume(s) and ensure “Ignore ownership on this volume” is UNchecked.
• Is there any possibility FCP is running as an Intel process under Rosetta emulation? You can check for that by locating the FCP process in Activity Monitor, and in the CPU tab, look under the "Kind" column. For FCP that should state Apple, not Intel. If it is Intel, let us know immediately. Reason: some third-party plugin vendors after five years still have not ported their Intel plugins to Apple Silicon, and to avoid losing sales they tell the customers how to force the Apple Silicon FCP process to run as Intel, to allow their Intel plugins to run. However this often destabilizes FCP and makes crashes more likely.

Is the current FCP library on a local APFS or HFS+ drive? Has that same library *ever* been on a network drive? Reason: network-hosted FCP libraries may not have assured transactional integrity, so could be subject to gradual damage. If this library .fcbundle is now or has ever been on a network drive, the safe path is assume damage is possible and export a library XML and import to a new, blank library, where the .fcpbundle is on a local APFS or HFS+ drive.

A few things I'd check:

• Crowdstrike. There were a few posts not long ago where a bad Crowdstrike update caused FCP issues. Urgent: Final Cut Pro Suddenly Running Ex… - Apple Community Spinning wheel while using Final Cut afte… - Apple Community
• Rosetta has crashed many times so maybe something running in emulation isn't happy. Coremelt?
• App cleaners are typically frowned upon. I'm not familiar with AppCleaner but CleanMyMac has been known to break FCP, sometimes requiring a MacOS reinstall.
• Google Chrome updater. Their nasty keystone software is installed but doesn't appear to be active. These keystone daemons and agents running constantly in the background would break the video toolbox and even after completely removing all Google software, could sometimes require reinstalling FCP.

Others might see additional items.

BTW, with all the configuration profiles, that's definitely the longest etrecheck report I've seen.

You could post the entire crash log and perhaps the one user here who's adept at reading them might happen by and have a chance to investigate.

While you're checking for various problems, you should also Validate ALL of your fonts (with Font Book) just to make sure.

Fonts with the 'htmx' table usability error are tolerated and FCP actually ships with a couple of them (Coolvetica and Franklin Gothic Demibold). Otherwise, fonts with other errors should be disabled or removed (all of which can be done inside of Font Book.)

Terry: all good suggestions. Like you I'm suspicious of Rosetta crashing, also Crowdstrike and CoreMelt plugins. Yes if he could post several crash logs, I can examine them. It's important to grab those quickly because they will "age out" of the system. Having several different FCP crash logs enables comparison for common features.

Locations: in Finder, do Go>Go to Folder, and enter each of these:

~/Library/Logs/DiagnosticReports and here:

~/Library/Logs/DiagnosticReports/Retired

Send me any files containing "Final Cut" in the title. The below WeTransfer link is a secure write-only folder and only I can see the files there.

https://we.tl/r-xJ4sys3L98

@oldsoulsound, you're in the best possible situation with joema's offer to investigate the crash logs. I strongly recommend you take advantage of it. And please keep us updated on what the solution turns out to be for other users with similar issues.

Please run Etrecheck and post its full report here.

Use the “additional text” button and paste the report into the text box.

Does FCPro have Full Disc Access:

Al