Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Strange Final Cut system Problems

  • Strange Final Cut system Problems

    Posted by Rhendrickson on June 1, 2006 at 2:00 pm

    Occasionally one of our Final Cut systems decides to completely lock up. When it does, the only thing to correct it would be to do a hard shut down (hold the power button for 5 seconds) then reboot. When it reboots, we get the first second of the “chime” and then nothing.

    We’ve tried to clear the PRAM as we boot and that doesn’t work. We can restart the machine to our heart’s content and still have the same result.

    The only solution we have found is to completely turn off the computer and unplug the power cord…wait about 10 minutes, then it boots up as if nothing ever happened.

    Today’s problem started when we were using compressor to render a commercial to our XSAN. Compressor got to 99% and then completely locked up. No spinning pin-wheel of death either.

    SYSTEM SETUP:

    Dual Mac G5
    8GB Ram
    2 250GB Internal Drives
    Fiberchannel Network Card

    XSAN Systems:
    #1. 7TB RAID, Fiberchannel
    #2. 11TB RAID, Fiberchannel

    Tom Matthies replied 19 years, 11 months ago 3 Members · 2 Replies
  • 2 Replies
  • David Bogie

    June 1, 2006 at 3:29 pm

    Could be a power supply problem, RAM, your system disk failing, graphic card issues or any of about two hundred other things. You can open Activity Monitor (or is it Terminal?) and watch a progress log to see if there are any clues you can decipher. I’m 90% positive you’re looking at seriously odd hardware issues.

    Immediate advice: Backup your system and keep the backup current on a daily or half-daily basis, depending on this machine’s position in your workflow.

    And prepare to take this Macintosh in for extensive testing, diagnosis and service. You could be without the machine for about two weeks.

    bogiesan

    This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

  • Tom Matthies

    June 1, 2006 at 5:02 pm

    I had a similar problem with a G5 dual 2.3 machine. It turned out to a bad stick of RAM. Replaced it with a new one and it’s been stable ever since.
    Tom

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