I am trying to export a wedding I filmed and edited a few years back. I can play the project fine in FCPX but when I try to export using any export method FCPX just crashes. Sometimes the entire MacBook restarts please help.
Process: Final Cut Pro 
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Version: 10.4.8 (358560)
Build Info: ProEditor-35856000076000000~7 (15B18c)
App Item ID: 424389933
App External ID: 833677189
Code Type: X86-64 (Native)
Parent Process: ??? 
Responsible: Final Cut Pro 
User ID: 501
Date/Time: 2020-07-06 02:02:29.527 +0100
OS Version: Mac OS X 10.15.5 (19F101)
Report Version: 12
Anonymous UUID: D65D1F4E-A908-9D90-C946-CDA639075483
External Modification Summary:
Calls made by other processes targeting this process:
Calls made by this process:
Calls made by all processes on this machine:
VM Region Summary:
ReadOnly portion of Libraries: Total=1.0G resident=0K(0%) swapped_out_or_unallocated=1.0G(100%)
Writable regions: Total=4.9G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=4.9G(100%)
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Accelerate framework 768K 6
Activity Tracing 256K 1
CG backing stores 44.7M 9
CG image 49.2M 1020
CG raster data 54.8M 218
CoreAnimation 95.8M 1149
CoreData Object IDs 4100K 2
CoreGraphics 8K 1
CoreImage 100K 8
CoreMedia memory pool 156.2M 425
CoreUI image data 5928K 58
Foundation 24K 2
IOKit 23.3M 3
Image IO 2560K 1
Kernel Alloc Once 8K 1
MALLOC 4.3G 2496
MALLOC guard page 48K 10
MALLOC_LARGE (reserved) 14.8M 46 reserved VM address space (unallocated)
MALLOC_NANO (reserved) 128.0M 1 reserved VM address space (unallocated)
Memory Tag 242 12K 1
Memory Tag 251 16K 1
OpenCL 5172K 61
SQLite page cache 16.3M 261
STACK GUARD 56.4M 99
Stack 60.3M 99
VM_ALLOCATE 104.6M 255
__DATA 99.8M 723
__DATA_CONST 1159K 47
__FONT_DATA 4K 1
__GLSLBUILTINS 5176K 1
__LINKEDIT 425.7M 144
__OBJC_RO 32.2M 1
__OBJC_RW 1892K 2
__TEXT 590.0M 676
__UNICODE 564K 1
libnetwork 128K 8
mapped file 1.0G 831
shared memory 648K 17
=========== ======= =======
TOTAL 7.2G 8686
TOTAL, minus reserved VM space 7.1G 8686
Model: MacBookPro11,3, BootROM 22.214.171.124.0, 4 processors, Quad-Core Intel Core i7, 2.8 GHz, 16 GB, SMC 2.19f12
Graphics: kHW_IntelIrisProItem, Intel Iris Pro, spdisplays_builtin
Graphics: kHW_NVidiaGeForceGTX750MItem, NVIDIA GeForce GT 750M, spdisplays_pcie_device, 2 GB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (126.96.36.199 AirPortDriverBrcmNIC-1610.1)
Bluetooth: Version 7.0.5f6, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
PCI Card: pci1b21,612, sppci_ahci, Thunderbolt@195,0,0
Serial ATA Device: APPLE SSD SM1024F, 1 TB
Serial ATA Device: ST3000DM001-9YN166, 3 TB
USB Device: USB 3.0 Bus
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1
Thunderbolt Device: d2, LaCie, 3, 7.4
I am trying to export a wedding I filmed and edited a few years back. I can play the project fine in FCPX but when I try to export using any export method FCPX just crashes. Sometimes the entire MacBook restarts please help...
From your crash log, it appears you are on a 2013 MacBook Pro with 16GB RAM and an nVidia GTX750 GPU.
If the entire machine hangs, crashes or spontaneously reboots, that is a system-level problem, not FCPX. It is possibly hardware and cannot be fixed at the FCPX level. I can also be caused by a buggy MacOS kernel extension. Such a system instability can also cause FCPX to unpredictably crash, even if MacOS does not.
Examine if any MacOS kernel extensions are in use. You can check if any are loaded by typing this command from a terminal window. This is safe to run, just do CMD-spacebar and type "terminal", then enter the below text exactly. If it returns anything, post those here. If it does not return anything you have no kernel extensions.
kextstat | grep -v com.apple
If you have any external audio or video hardware -- external monitors, external speakers, wireless bluetooth earphones, etc -- temporarily remove those as a troubleshooting measure. Sometimes that hardware or associated drivers can cause problems.
If any of your media and files are on NAS or cloud-based storage, as a troubleshooting measure reconfigure that so all storage is on locally-attached drives.
Make sure you have at least 20% free space on all drives.
If you have any HEVC media, transcode that to optimized media. There is a bug in FCPX 10.4.7 and later whereby certain HEVC codecs can cause FCPX (not MacOS) to crash. If it hangs during the transcode, report that here.
Do not run Chrome or any browser based on Chrome. It mis-uses the MacOS VideoToolBox framework and can cause FCPX to crash.
In FCPX preferences, disable background rendering. Then delete all render files with File>Delete Generated Library Files>Delete Render Files>All. After that select all timeline clips with CMD+A then do a one-time render with CTRL+R. Observe if that render completes OK, IOW no render dots left above the timeline. If it fully renders, then try to export using this preset: File>Share>Master File>Settings, Format:Computer, Video Codec: H.264 Faster Encode, Resolution: 1920x1080.
If the timeline render or export hangs or crashes, make a snapshot duplicate of your timeline, open that, select all clips with CMD+A, then remove all effects via Edit>Remove Effects. Then try to export that as above. If that works there may be an effect problem. In that case, make another snapshot duplicate of the original timeline, open that, then select 1/2 the clips and remove effects, render timeline with CTRL+R, then try to export. Based on that result repeat with 1/4, then 1/8 of the timeline until you narrow down what region and what effects are causing the problem.