Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy fcp 7 crashing on launch! Tried everything!

  • fcp 7 crashing on launch! Tried everything!

    Posted by Jon Grimson on February 3, 2010 at 8:51 pm

    Help anyone! I’m at wits end now. Yesterday had FCP crash problems and did everything; repair permissions, trash prefs., re-installed FCP studio 3 and finally trashed some corrupted fonts. Yesterday it seemed as if the fonts were the problem and I was back up and running happily away. But FCP is crashing again amd I’m stumped. FCP maintenace utility is telling me it might be a memory issue. These are the crash log entries. Any help please, I’ve just officially gotten desperate!

    0 com.apple.CoreFoundation 0x903ef548 __exceptionFinalize + 152
    1 libSystem.B.dylib 0x94dc8013 _pthread_tsd_cleanup + 163
    2 libSystem.B.dylib 0x94dc7bb5 _pthread_exit + 98
    3 libSystem.B.dylib 0x94dc5012 thread_start + 34

    Hardware Overview:

    Model Name: MacBook Pro
    Model Identifier: MacBookPro5,1
    Processor Name: Intel Core 2 Duo
    Processor Speed: 2.8 GHz
    Number Of Processors: 1
    Total Number Of Cores: 2
    L2 Cache: 6 MB
    Memory: 4 GB
    Bus Speed: 1.07 GHz
    Boot ROM Version: MBP51.007E.B05
    SMC Version (system): 1.33f8
    Sudden Motion Sensor:
    State: Enabled

    System Version: Mac OS X 10.5.8 (9L30)
    Kernel Version: Darwin 9.8.0

    Graphics/Displays:

    NVIDIA GeForce 9600M GT:

    Chipset Model: NVIDIA GeForce 9600M GT
    Type: Display
    Bus: PCIe
    PCIe Lane Width: x16
    VRAM (Total): 512 MB
    Vendor: NVIDIA (0x10de)
    Device ID: 0x0647
    Revision ID: 0x00a1
    ROM Revision: 3437
    gMux Version: 1.7.3
    Displays:
    Color LCD:
    Resolution: 1440 x 900
    Depth: 32-Bit Color
    Core Image: Hardware Accelerated
    Main Display: Yes
    Mirror: Off
    Online: Yes
    Quartz Extreme: Supported
    Built-In: Yes
    Display Connector:
    Status: No Display Connected

    NVIDIA GeForce 9400M:

    Chipset Model: NVIDIA GeForce 9400M
    Type: Display
    Bus: PCI
    VRAM (Total): 256 MB
    Vendor: NVIDIA (0x10de)
    Device ID: 0x0863
    Revision ID: 0x00b1
    ROM Revision: 3437
    gMux Version: 1.7.3
    Displays:
    Display Connector:
    Status: No Display Connected
    Display Connector:
    Status: No Display Connected

    Memory:

    Memory Slots:

    ECC: Disabled

    BANK 0/DIMM0:

    Size: 2 GB
    Type: DDR3
    Speed: 1067 MHz
    Status: OK
    Manufacturer: 0x80CE
    Part Number: 0x4D34373142353637334448312D4346382020

    BANK 0/DIMM1:

    Size: 2 GB
    Type: DDR3
    Speed: 1067 MHz
    Status: OK
    Manufacturer: 0x80CE
    Part Number: 0x4D34373142353637334448312D4346382020

    Thanks very much!

    Phi Glazer replied 14 years, 11 months ago 9 Members · 18 Replies
  • 18 Replies
  • Ella Currer

    February 3, 2010 at 9:54 pm

    Are you getting error messages or does it just snap closed on you?

  • Jon Grimson

    February 3, 2010 at 10:08 pm

    It just quits without showing any fcp specific error message. Jsut the generic OSX crash box

  • David Roth weiss

    February 3, 2010 at 10:16 pm

    Have you tried fixing permissions with the Apple Disk Utility?

    David Roth Weiss
    Director/Editor/Colorist
    David Weiss Productions, Inc.
    Los Angeles

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, Indie Film & Documentary, and Film History & Appreciations forums.

  • Jon Grimson

    February 3, 2010 at 10:22 pm

    Yes. Tried with Apple Disk Utility and with Disk Warrior. Just tried setting up a new user account too per Larry Jordan’s suggestion; still no go.

  • Michael Sacci

    February 3, 2010 at 10:28 pm

    This would only give you a way to test if it is a memory issue.

    Install the OS on a new clean drive. Update. Install FCP/S if you do it without media it doesn’t take too long. Update. Test FCP. If it runs okay install and drivers for video card that you use with FCP.

    Realize this is a plan but it gives you a clean starting place that you can build from.

  • Jon Grimson

    February 3, 2010 at 10:32 pm

    I guess my assumption would be that if this is a memory issue, that I’d be having all sorts of problems with the computer and other software in general. As far as I can tell it seems to be FCP specific.

  • Ella Currer

    February 3, 2010 at 11:37 pm

    Try getting offline, disconnecting all superfluous connections (including ethernet) to your computer and then starting up. Could be you’re sharing a license with someone and FCP is shutting you out because it’s a single user license.

  • Jon Grimson

    February 3, 2010 at 11:47 pm

    That’s not it I have a new upgrade version of FCP Studio and I’m the only one with a license. But I tried disconnecting anyway and still no luck.

    FCP seems to crash while it’s attempting to RT profile. I’ve tried it on an attached project and media drive as well as setup a dummy test directly to my internal drive, so I think it is safe to say that it is not a drive issue.

    Really not liking how I can’t fix this but appreciate all the help from you folks. Please keep it coming…

  • Jon Grimson

    February 4, 2010 at 12:48 am

    Something strange is happening and it seems to be related to my second monitor display. When I edit from my office I have a 2nd display attached and FCP works just fine. When I take my laptop to a client and try and run FCP on just the laptop single display I have all these crashes. FCP ran perfectly fine before I had the 2nd display, but I believe something is happening that is causing it to crash when I take the laptop on the road and use in single display mode after having been used in dual display mode. Could this be the problem somehow? Has this ever happened to anyone else?

    All I can say is is it works with 2nd monitor setup and crashes when I go laptop only. Maybe it solves the problem but not the dilemma.

  • Michael Sacci

    February 4, 2010 at 5:10 am

    Trying to find a problem in the end is normally harder and more time consuming. My recommendation is to start with a clean HD and OS.

    If not, than a complete uninstall/reinstall of FCP, then a complete uninstall/reinstall of all of FCS apps. I use an app called FCS Remover for stuff like this. THere are a bunch of files all over the place so a program like this makes it a much easier job to uninstall completely.

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy