New ram crashes fcp

I just purchased new ram for the second day in a row. I bought four 1 gig ram sticks for my g5 power pc mac. I have a total of 6 gigs. I had previously had two gigs, 4 512 ram sticks.
Under about this mac, my new ram is reongized and other programs recongized the new ram (after effects).
I opened up FCP (5.0.4) project and fcp crashes everytime. I looked up my ram, and it is compatiable with my system. Crucial. i have the ram stickes in the proper slots.
http://www.crucial.com/store/mpartspecs.aspx?mtbpoid=1D1DFB01A5CA7304
The project I opened in fcp was done befrore the new ram (2 gigs) was installed. Can that be the issue, or is the ram I purchased not compatiable with FCP. At first FCP would crash after opening it, now it takes a few minutes before crashing. Would Resetting your Mac's PRAM and NVRAM help? Any tips and insight on installing and ram (ram suggestion) would also help.
Thankyou for taking your time and any suggestions will be helpfull and appericated.

I get our memory from Data Memory Systems in NH.
www.datamem.com not sure what the brand name is...
My machine has 4 slots.
DIMM0/J11 512Mb (Pre-installed)
DIMM1/J12 512Mb (Pre-installed)
DIMM2/J13 Empty
DIMM3/J14 Empty
I put a 512Mb chip in J13 & J14... The computer recognizes it, feels fresh and snappy, but without fail, it will crash after a short period of time forcing a 'hard' shutdown with the power button.
Steve

Similar Messages

  • Re: New ram crashing in GT70 2OC

    I would choose option 1 but I would try to install one of these three dimms into the 4th dimm slot to make sure the slot is ok.

    The F3 method they told you is the way to restore system back to default. Just press F3 during post when you see MSI logo and then follow on screen message to proceed the process. But Most of the time this is just a malfunction ODD causes the problem.

  • Mac crashes regularly after installing new RAM

    My laptop crashes at least once a day ever since installing new RAM. It seems to be triggered by quitting programs, usually Firefox, Logic or Spotify. There was nothing else connected to the Mac that brought about the latest crash but I do use an Mbox 2 on a regular basis.
    Below is the last crash report and also the RAM profile. It's Kingston brand if that means anything.
    *_Crash Report:_*
    Interval Since Last Panic Report: 55868 sec
    Panics Since Last Report: 1
    Anonymous UUID: AEEF5666-4C4E-4FC1-AC7A-5A500F952BF9
    Sat Jan 22 00:00:25 2011
    panic(cpu 1 caller 0x2aab55): Kernel trap at 0x8b042474, type 14=page fault, registers:
    CR0: 0x8001003b, CR2: 0x8b042474, CR3: 0x00100000, CR4: 0x00000660
    EAX: 0x09947100, EBX: 0x09ad4a00, ECX: 0xe15f0000, EDX: 0x0a133800
    CR2: 0x8b042474, EBP: 0x5294bb68, ESI: 0x08bd7f40, EDI: 0x0085f838
    EFL: 0x00010246, EIP: 0x8b042474, CS: 0x00000008, DS: 0x03450010
    Error code: 0x00000010
    Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
    0x5294b968 : 0x21b50c (0x5d42fc 0x5294b99c 0x223974 0x0)
    0x5294b9b8 : 0x2aab55 (0x59616c 0x8b042474 0xe 0x596336)
    0x5294ba98 : 0x2a09a8 (0x5294bab0 0x246 0x5294bb68 0x8b042474)
    0x5294baa8 : 0x8b042474 (0xe 0x48 0x52940010 0x230010)
    0x5294bb68 : 0x1854f8f (0x9ad4a00 0x0 0x5294bbf8 0x60)
    0x5294bb88 : 0x4ff5ae (0x9ad4b00 0x85f838 0x1 0x0)
    0x5294bba8 : 0x50f6e0 (0x9ad4b00 0x85f838 0x5294bbd8 0x4ff931)
    0x5294bbd8 : 0x50f854 (0x8bd7f40 0x0 0x1 0x0)
    0x5294bbf8 : 0x4ff5ae (0x8bd7f40 0x0 0x1 0x1)
    0x5294bc18 : 0x4ff5c9 (0x8bd7f40 0x0 0x5294bc48 0x4ff5ae)
    0x5294bc38 : 0x531e12 (0x8bd7f40 0xffff 0x8bd4f84 0x4ff5c9)
    0x5294bc58 : 0x531e45 (0x8bd4f80 0x246 0x5294bc98 0xb18e540)
    0x5294bc78 : 0x4ff5ae (0x8bd4f80 0x0 0x1 0x1e)
    0x5294bc98 : 0x4ff5c9 (0x8bd4f80 0x0 0x5294bce8 0x0)
    0x5294bcb8 : 0x2844eb (0x8bd4f80 0xb18e540 0x1e 0x5294bce8)
    0x5294bd08 : 0x21d8d1 (0xa088398 0xb2555a0 0x997aa24 0x1)
    0x5294bd48 : 0x210a3a (0xa088300 0x12 0x5294bda8 0x20f45c)
    0x5294bda8 : 0x21dda0 (0xa088300 0x10000 0x0 0x2107c2)
    0x5294bdd8 : 0x23f567 (0x5294bdfc 0x24 0xa4289e4 0x0)
    0x5294be28 : 0x214f6f (0xb18e540 0x1 0x1 0x221bb4)
    0x5294be78 : 0x215581 (0x7fc7420 0x33303 0x43dfe330 0x8f1e1f4)
    0x5294beb8 : 0x22c521 (0x7fc7420 0xc971640 0x5294bf08 0x47a0f3)
    0x5294bf08 : 0x47ab28 (0x8f1e1f4 0x0 0x0 0x2ea2)
    0x5294bf58 : 0x47ab56 (0x8f20000 0x0 0xc971684 0x0)
    0x5294bf78 : 0x4f0f7d (0x8f20000 0xc971640 0xc971684 0x0)
    0x5294bfc8 : 0x2a0ef8 (0xa1916c0 0x1 0x10 0xa194964)
    Kernel Extensions in backtrace (with dependencies):
    com.digidesign.mbox2.driver(8.0.0f1)@0x184e000->0x1871fff
    dependency: com.apple.iokit.IOAudioFamily(1.7.9fc4)@0x90c000
    dependency: com.apple.iokit.IOUSBFamily(4.1.7)@0x1232000
    dependency: com.apple.driver.AppleUSBMergeNub(4.1.5)@0x1292000
    dependency: com.apple.kext.OSvKernDSPLib(1.3)@0x908000
    dependency: com.apple.iokit.IOPCIFamily(2.6)@0x948000
    dependency: com.apple.driver.AppleUSBComposite(3.9.0)@0x1266000
    BSD process name corresponding to current thread: Spotify
    Mac OS version:
    10H574
    Kernel version:
    Darwin Kernel Version 10.5.0: Fri Nov 5 23:20:39 PDT 2010; root:xnu-1504.9.17~1/RELEASE_I386
    System model name: MacBook7,1 (Mac-F22C89C8)
    System uptime in nanoseconds: 10016535514139
    unloaded kexts:
    com.apple.driver.AppleMCP89RootPortPM 1.11 (addr 0x11cd000, size 0x20480) - last unloaded 250987080117
    loaded kexts:
    com.digidesign.mbox2.driver 8.0.0f1 - last loaded 49888220612
    com.rogueamoeba.hermes 2.0.2
    com.paceap.kext.pacesupport.snowleopard 5.7.2
    com.Cycling74.driver.Soundflower 1.5.1
    tc.tctechnologies.driver.PaeFireStudio 8028
    com.digidesign.iokit.DigiIO 8.0.0f1
    com.digidesign.iokit.DigiDal 8.0.0f1
    com.apple.driver.AppleHWSensor 1.9.3d0
    com.apple.filesystems.autofs 2.1.0
    com.apple.driver.AGPM 100.12.19
    com.apple.driver.AppleMikeyHIDDriver 1.2.0
    com.apple.driver.AppleMikeyDriver 1.9.9f12
    com.apple.driver.AudioAUUC 1.13
    com.apple.driver.AppleUpstreamUserClient 3.4.5
    com.apple.driver.AppleMCCSControl 1.0.17
    com.apple.driver.SMCMotionSensor 3.0.0d4
    com.apple.driver.AppleHDA 1.9.9f12
    com.apple.DontSteal_Mac_OSX 7.0.0
    com.apple.driver.AudioIPCDriver 1.1.6
    com.apple.driver.AppleIntelPenrynProfile 17
    com.apple.driver.ACPISMCPlatformPlugin 4.5.0d5
    com.apple.driver.AppleLPC 1.4.12
    com.apple.driver.AppleBacklight 170.0.34
    com.apple.GeForce 6.2.4
    com.apple.driver.AppleUSBTCButtons 200.3.2
    com.apple.driver.AppleUSBTCKeyboard 200.3.2
    com.apple.iokit.SCSITaskUserClient 2.6.5
    com.apple.BootCache 31
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
    com.apple.iokit.IOAHCIBlockStorage 1.6.3
    com.apple.driver.AppleHPET 1.5
    com.apple.driver.AirPortBrcm43224 426.36.1
    com.apple.driver.AppleAHCIPort 2.1.5
    com.apple.driver.AppleUSBHub 4.1.7
    com.apple.nvenet 2.0.15
    com.apple.driver.AppleUSBEHCI 4.1.7
    com.apple.driver.AppleUSBOHCI 4.1.5
    com.apple.driver.AppleSmartBatteryManager 160.0.0
    com.apple.driver.AppleEFINVRAM 1.4.0
    com.apple.driver.AppleRTC 1.3.1
    com.apple.driver.AppleACPIButtons 1.3.5
    com.apple.driver.AppleSMBIOS 1.6
    com.apple.driver.AppleACPIEC 1.3.5
    com.apple.driver.AppleAPIC 1.4
    com.apple.driver.AppleIntelCPUPowerManagementClient 105.13.0
    com.apple.security.sandbox 1
    com.apple.security.quarantine 0
    com.apple.nke.applicationfirewall 2.1.11
    com.apple.driver.AppleIntelCPUPowerManagement 105.13.0
    com.apple.driver.AppleProfileReadCounterAction 17
    com.apple.driver.AppleProfileTimestampAction 10
    com.apple.driver.AppleProfileThreadInfoAction 14
    com.apple.driver.AppleProfileRegisterStateAction 10
    com.apple.driver.AppleProfileKEventAction 10
    com.apple.driver.AppleProfileCallstackAction 20
    com.apple.driver.AppleSMBusController 1.0.8d0
    com.apple.driver.DspFuncLib 1.9.9f12
    com.apple.iokit.IOFireWireFamily 4.2.6
    com.apple.iokit.IOSurface 74.2
    com.apple.iokit.IOBluetoothSerialManager 2.3.8f7
    com.apple.iokit.IOSerialFamily 10.0.3
    com.apple.iokit.IOAudioFamily 1.7.9fc4
    com.apple.kext.OSvKernDSPLib 1.3
    com.apple.driver.AppleHDAController 1.9.9f12
    com.apple.iokit.IOHDAFamily 1.9.9f12
    com.apple.driver.AppleSMBusPCI 1.0.8d0
    com.apple.iokit.AppleProfileFamily 41
    com.apple.driver.AppleSMC 3.1.0d3
    com.apple.driver.IOPlatformPluginFamily 4.5.0d5
    com.apple.nvidia.nv50hal 6.2.4
    com.apple.NVDAResman 6.2.4
    com.apple.iokit.IONDRVSupport 2.2
    com.apple.iokit.IOGraphicsFamily 2.2
    com.apple.driver.BroadcomUSBBluetoothHCIController 2.3.8f7
    com.apple.driver.AppleUSBBluetoothHCIController 2.3.8f7
    com.apple.iokit.IOBluetoothFamily 2.3.8f7
    com.apple.driver.AppleUSBMultitouch 206.6
    com.apple.iokit.IOUSBHIDDriver 4.1.5
    com.apple.driver.AppleUSBMergeNub 4.1.5
    com.apple.driver.AppleUSBComposite 3.9.0
    com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.5
    com.apple.iokit.IOBDStorageFamily 1.6
    com.apple.iokit.IODVDStorageFamily 1.6
    com.apple.iokit.IOCDStorageFamily 1.6
    com.apple.driver.XsanFilter 402.1
    com.apple.iokit.IOAHCISerialATAPI 1.2.5
    com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.5
    com.apple.iokit.IO80211Family 312
    com.apple.iokit.IOAHCIFamily 2.0.4
    com.apple.iokit.IOUSBUserClient 4.1.5
    com.apple.iokit.IONetworkingFamily 1.10
    com.apple.driver.NVSMU 2.2.7
    com.apple.iokit.IOUSBFamily 4.1.7
    com.apple.driver.AppleEFIRuntime 1.4.0
    com.apple.iokit.IOHIDFamily 1.6.5
    com.apple.iokit.IOSMBusFamily 1.1
    com.apple.kext.AppleMatch 1.0.0d1
    com.apple.security.TMSafetyNet 6
    com.apple.driver.DiskImages 289
    com.apple.iokit.IOStorageFamily 1.6.2
    com.apple.driver.AppleACPIPlatform 1.3.5
    com.apple.iokit.IOPCIFamily 2.6
    com.apple.iokit.IOACPIFamily 1.3.0
    Model: MacBook7,1, BootROM MB71.0039.B0B, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB, SMC 1.60f5
    Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
    Memory Module: global_name
    AirPort: spairportwireless_card_type_airportextreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.10.131.36.1)
    Bluetooth: Version 2.3.8f7, 2 service, 12 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: TOSHIBA MK2555GSXF, 232.89 GB
    Serial ATA Device: MATSHITADVD-R UJ-898
    USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06600000
    USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8218, 0x06630000
    USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0237, 0x06300000
    USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0x24600000
    *_Memory Profile_*
    Memory Slots:
    ECC: Disabled
    BANK 0/DIMM0:
    Size: 2 GB
    Type: DDR3
    Speed: 1067 MHz
    Status: OK
    Manufacturer: 0x0000
    Part Number: 0x000000000000000000000000000000000000
    Serial Number: 0x00000000
    BANK 1/DIMM0:
    Size: 2 GB
    Type: DDR3
    Speed: 1067 MHz
    Status: OK
    Manufacturer: 0x0000
    Part Number: 0x000000000000000000000000000000000000
    Serial Number: 0x00000000

    It's almost impossible to trace back the panic report to a specific cause, but it's highly suspicious that you started experiencing problems after installing new RAM.
    It's also strange that your RAM has no stated VendorID, Part Number or Serial Number.
    I would return this memory poste haste.
    Alternatively, if the DIMMs are from Kingston's ValueRAM range, just dump them in the garbage because that's where they belong. While you're there, look for any other RAM that someone else has thrown away - chances are its ValueRAM, too (hint: I have never seen a single ValueRAM DIMM work in any of my systems, so I avoid them like the plague - shame, since Kingston used to have such a good reputation).

  • New RAM causes crash problems

    Hello Everybody,
    have some problems with new RAM for my G5. With the original 4 x 256 RAM everything's going fine, but as soon as I correctly stick in the new 2 x 1 GB (Mac Dealer bought), my mac's going crazy (crashes or not being able to install and so on...) Changed the new RAM allready at my Mac Dealer, things remain the same. Does anybody have an idea?

    Have you made sure the RAM is properly seated?
    If it is, contact the Mac dealer and inform them they have a bad batch of RAM.

  • HUGE JPEGs crashing FCP

    Ok, I'll start off by admitting I made a nubie mistake scanning photos in at exorbitant PPIs resulting in TIFFs that were hovering around 1GB, yes that GIG, and the largest file being 1.58GB. I've since gone through, and exported them to JPEGs resulting in file sizes about 10% the originals. However, that largest file is still giving FCP problems. Most other jpegs, from 2.7MB to 65.7MB results in a green render bar under Unlimited RT on my 2.16 Core Duo MBP with 2GB of RAM. Now when I go over that, with the 3 files that are 77.3, 86.6, and 115.8MB, the images get an orange render bar and result in crashing FCP. I read in a previous thread that it was a memory issue, and that was confirmed when I went to play one of the images in the Viewer and I get Error:Out of Memory. So I jacked the memory, all of it. Application was always listed as 100%, but now I have Still Cache also set to 100% and Disk set to 10,000K and RAM at 1,000K, but this still hasn't fixed my issue. I've tried every way I know of to render this image, and they all quit FCP. Before I raised the memory, just placing the file in the timeline would cause a crash, so at least now it gets past that. If I let it auto render, crash. If I do it manually, crash. If I make a new sequence like David suggest in a previous thread, you better believe it crashes. The interesting thing is despite raising FCP's memory usage, Activity Monitor still shows 1.04GB of free RAM, so if FCP is Out of Memory, why doesn't it just use up that 1+GB? Does anyone know why FCP can't play with such large files?
    I guess I'll just need to recompress the few images again, but it's VERY annoying. At least I'm not trying to work with the 1.5GB image.
    -Brian
    By the way, I am on Final Cut 5.1.4.

    You can reduce the cache levels and history states in Photoshop's memory preferences. This will buy back some memory. You should quit and restart Photoshop after each major image resize. This will also keep the app from building up too much cache.
    I'll assume these are PSB format, rather than PSD. PSB's don't work the same as PSD's with scratch disk. You may need a separate scratch disk if you keep getting errors. Designate your fastest largest drive to do this.
    You really need to get them down to around 1000x1000 pixels to be truly fast in FCP.
    Don't forget that Photoshop has a new tool called Image Processor under File/Scripts/ that can size documents without really having to rasterize them. It works much faster than opening the file then running a resize. But be careful to just run 1 or 2 at a time, since I've found that it doesn't do a great job at purging the memory after each image. You will run out of memory quickly if you have too many files at once.
    Remember to quit and restart Photoshop, or even you machine if it really slows to a crawl. These are signs your hard drive is full and relaunch and reboot will clear all the temp files from Photoshop's scratch disk.

  • Calligraphy Crash FCP 4.5

    Hi, each time I tried to go in the style palette in either Title 3D or Title Crawl, it crashed FCP. Does anyone got this problem before, if yes how did you fixed it?
    Thanks
    G4 500   Mac OS X (10.3.9)   384 of RAM

    I think I found the problem. I edited one of the stills, adding a transition, and the 3 second change took 32 minutes to render. Then I made a similar change to another still and it rendered in less than a minute. I then checked the size of the files, which were provided to me as TIFFs. The slow rendering photo is 33 Megs, while the quick one is only 1 meg. I'm going to go back and reduce the size of these in Photoshop. Hopefully that is all it takes. The 33 meg photo must be some poster-sized giant. Thanks to all of you. Great to have a community like this. I learned some new things, and I love FCP Rescue --gonna keep that puppy handy. The more I learn, the more I hope I can become a resource like all of you.
    PowerMac G4 MDD Dual 1Ghz   Mac OS X (10.4.5)  

  • Capturing AVCHD Crashes FCP

    I've been using the new Panasonic camera hmc 151 AVCHD. I've been using it fine at work without problem except I've found a problem with some footage settings and the Perian plugin.
    I've taken some stuff home to work on but when I click on the 'add to queue' button in the L&T window, FCP just pooofs off the screen.
    Does it everytime without fail.
    I want to post the log file but it's massive, before I do, any ideas?
    OSX 10.5.6
    iMac 2.8 Ghz intel duo core
    FCP 6.0.3
    4 GB RAM
    QT 7.6.2

    hmmmm,
    1920 by 1080 comes in fine but 1280 by 720 crashes FCP.
    The clips play fine in the L&T window but won't transfer.

  • MBP 2010 8gb ram Crashing on boot

    I have tried to upgrade my 2010 13" MBP with the 8gb 1333 DDR3 corsair. I did this once already with my 2009 15" MBP and worked just fine without any problems. I have read many success stories for upgrading a 2010 13" with the exact same ram and it's begining to frustrate me because i can't figure out if it's hardware or software with the computer. I did try the new ram in 15" just to make sure the ram wasn't bad and it booted just fine. Back to the 13" it will either simply crash on boot and have a error messae wich i can try to add a link to later but i did get this crash report (see below) after i put in the old 2gb sticks running at 1033. But it will either simply crash or i will get the grey apple logo and the spinner will start spinning for about 10 seconds than freeze. I let it sit for about 10-20 minutes multiple times to see if it just needed to think but it didn't progress pass that. i've also tried just using one of the single sticks instead of having both in and that didn't help either. tried reseting pram and enter safe mode but both attempts ended in it crashing the same way. I also tried using a different harddrive from another 13 macbook that had Snow lion on it thinking that something rooted on the 13" MBP operating system was causing it not to boot properly with the ram, that also didn't work. I am up for any suggestions. Thank you - D
    Interval Since Last Panic Report:  152 sec
    Panics Since Last Report:          1
    Anonymous UUID:                    A57408DC-841D-406F-8FF9-380E4C3B6437
    Sun Apr  8 17:18:12 2012
    panic(cpu 0 caller 0x2a0663): "Spinlock acquisition timed out: lock=0x45d85e0, lock owner thread=0x2000, current_thread: 0xd2873d4, lock owner active on CPU 0xffffffff"@/SourceCache/xnu/xnu-1504.15.3/osfmk/i386/locks_i386.c:374
    Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
    0x7bafb7c8 : 0x21b837 (0x5dd7fc 0x7bafb7fc 0x223ce1 0x0)
    0x7bafb818 : 0x2a0663 (0x59ccb0 0x45d85e0 0x2000 0xd2873d4)
    0x7bafb858 : 0x279ec7 (0x45d85e0 0x1 0x849088 0x7b946c1c)
    0x7bafb898 : 0x272ba8 (0xd8ab280 0xe60000 0x0 0xa50)
    0x7bafbab8 : 0x274fbb (0xd8ab280 0xe60000 0x0 0x8000)
    0x7bafbb98 : 0x5601ff (0x2fdb520 0x11e60000 0x1 0x7bafbc34)
    0x7bafbc58 : 0x56052a (0xd74bf00 0x0 0x2ed05005 0x1)
    0x7bafbc78 : 0x7b9898e2 (0xd74bf00 0x0 0x200 0x0)
    0x7bafbd28 : 0x7b989b1d (0x5f8ee4 0xe000002 0x7bafbec4 0x0)
    0x7bafbd48 : 0x30d6a4 (0xe000002 0x7bafbec4 0x0 0x2ed05)
    0x7bafbdd8 : 0x2ff592 (0x7bafbdfc 0x3 0x7bafbe28 0x58a167)
    0x7bafbe28 : 0x2f45e1 (0xd8a8784 0x7bafbec4 0x0 0x7bafbf54)
    0x7bafbe78 : 0x49f5f9 (0xd67ef60 0x7bafbec4 0x0 0x7bafbf54)
    0x7bafbf18 : 0x49fd75 (0x7bafbf54 0xd67ef60 0x11e60000 0x1)
    0x7bafbf78 : 0x4f82fb (0xd649540 0xce82e28 0xce7d134 0x1)
    0x7bafbfc8 : 0x2a251d (0xce82e24 0x0 0x2a17ab 0xce82e24)
          Kernel Extensions in backtrace (with dependencies):
             com.apple.iokit.IOStorageFamily(1.6.3)@0x7b97b000->0x7b993fff
    BSD process name corresponding to current thread: fsck_hfs
    Mac OS version:
    10K549
    Kernel version:
    Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
    System model name: MacBookPro7,1 (Mac-F222BEC8)
    System uptime in nanoseconds: 30863821997
    unloaded kexts:
    (none)
    loaded kexts:
    com.apple.driver.AppleUSBTCButtons          201.6 - last loaded 1982567428
    com.apple.driver.AppleIRController          303.8
    com.apple.driver.AppleUSBTCKeyEventDriver          201.6
    com.apple.driver.AppleUSBTCKeyboard          201.6
    com.apple.driver.AppleUSBCardReader          2.6.1
    com.apple.iokit.SCSITaskUserClient          2.6.8
    com.apple.iokit.IOAHCIBlockStorage          1.6.4
    com.apple.BootCache          31.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.driver.AppleEFINVRAM          1.4.0
    com.apple.driver.AppleAHCIPort          2.1.7
    com.apple.driver.AirPortBrcm43xx          423.91.27
    com.apple.driver.AirPortBrcm43224          428.42.4
    com.apple.driver.AppleFWOHCI          4.7.3
    com.apple.iokit.AppleBCM5701Ethernet          3.0.5b8
    com.apple.driver.AppleUSBHub          4.2.4
    com.apple.driver.AppleUSBEHCI          4.2.4
    com.apple.driver.AppleUSBOHCI          4.2.0
    com.apple.driver.AppleHPET          1.5
    com.apple.driver.AppleRTC          1.3.1
    com.apple.driver.AppleSmartBatteryManager          160.0.0
    com.apple.driver.AppleACPIButtons          1.3.6
    com.apple.driver.AppleSMBIOS          1.7
    com.apple.driver.AppleACPIEC          1.3.6
    com.apple.driver.AppleAPIC          1.4
    com.apple.driver.AppleIntelCPUPowerManagementClient          142.6.0
    com.apple.security.sandbox          1
    com.apple.security.quarantine          0
    com.apple.nke.applicationfirewall          2.1.14
    com.apple.driver.AppleIntelCPUPowerManagement          142.6.0
    com.apple.driver.BroadcomUSBBluetoothHCIController          2.4.5f3
    com.apple.driver.AppleUSBBluetoothHCIController          2.4.5f3
    com.apple.iokit.IOBluetoothFamily          2.4.5f3
    com.apple.driver.AppleUSBMultitouch          207.7
    com.apple.iokit.IOUSBHIDDriver          4.2.0
    com.apple.iokit.IOUSBMassStorageClass          2.6.7
    com.apple.iokit.IOSCSIBlockCommandsDevice          2.6.8
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          2.6.8
    com.apple.iokit.IOBDStorageFamily          1.6
    com.apple.iokit.IODVDStorageFamily          1.6
    com.apple.iokit.IOCDStorageFamily          1.6.1
    com.apple.driver.XsanFilter          402.1
    com.apple.driver.AppleUSBMergeNub          4.2.4
    com.apple.driver.AppleUSBComposite          3.9.0
    com.apple.iokit.IOAHCISerialATAPI          1.2.6
    com.apple.iokit.IOSCSIArchitectureModelFamily          2.6.8
    com.apple.driver.AppleFileSystemDriver          2.0
    com.apple.iokit.IOAHCIFamily          2.0.6
    com.apple.iokit.IO80211Family          320.1
    com.apple.iokit.IOFireWireFamily          4.2.6
    com.apple.iokit.IONetworkingFamily          1.10
    com.apple.iokit.IOUSBUserClient          4.2.4
    com.apple.driver.AppleMCP89RootPortPM          1.11
    com.apple.iokit.IOUSBFamily          4.2.4
    com.apple.driver.NVSMU          2.2.7
    com.apple.driver.AppleEFIRuntime          1.4.0
    com.apple.iokit.IOHIDFamily          1.6.6
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.TMSafetyNet          6
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.driver.DiskImages          289
    com.apple.iokit.IOStorageFamily          1.6.3
    com.apple.driver.AppleACPIPlatform          1.3.6
    com.apple.iokit.IOPCIFamily          2.6.5
    com.apple.iokit.IOACPIFamily          1.3.0
    Model: MacBookPro7,1, BootROM MBP71.0039.B0B, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB, SMC 1.62f6
    Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
    Memory Module: global_name
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.10.131.42.4)
    Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
    Serial ATA Device: FUJITSU MHY2080BH, 74.53 GB
    Serial ATA Device: MATSHITADVD-R   UJ-898, 7.8 GB
    USB Device: Built-in iSight, 0x05ac  (Apple Inc.), 0x8507, 0x24600000 / 2
    USB Device: Internal Memory Card Reader, 0x05ac  (Apple Inc.), 0x8403, 0x26100000 / 2
    USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x06600000 / 4
    USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.), 0x8213, 0x06610000 / 5
    USB Device: IR Receiver, 0x05ac  (Apple Inc.), 0x8242, 0x06500000 / 3
    USB Device: Apple Internal Keyboard / Trackpad, 0x05ac  (Apple Inc.), 0x0236, 0x06300000 / 2

    I know that it says that it likes 1033 but..... when i had read around to upgrad my 15" people said it would work and would just clock the ram speed down from 1333 to 1033. I installed it and to a shocking suprise it didn't even clock it down to 1033. My frustration is that this 13" MBP is a year newer and isn't even wanting to boot with the ram. I would assume, and be glad with it booting and just clocking the RAM down. i wouldn't see why that wouldn't be a problem. Thank you though for youru suggestion.  Thanks - DJ

  • New RAM problems with my Dual G4 1.25 MDD

    Howdy I've had my Dual G4 1.25 MDD for 2 years and love it. I got it with 1GB RAM, thinking I was set. For Christmas I wanted to Upgrade the RAM to 2GB. from My PowerMac G4 Manual I knew I needed 2x 512MB PC2700 DDR333 CL2.5 SDRAM DIMM's.
    I went to DealRam (part of DealMac) and found 18004memory.com The price seemed great $39 per stick. I ordered it and within a week got 2x 512MB DIMM's. Problem was it was the Wrong RAM spec. I tried that RAM in my Mac 30 different ways and Everytime the computer either wouldn't boot, or it would suffer Kernel Protection Faults. One time it did boot up but the RAM only recognized as 2x 256MB DIMM's. I called the company, got an RMA and returned the RAM, this time they sent me 2 replacement DIMM's.... for a POWERBOOK, SO-DIMM's. I returned it again and finally Got from them the
    2x 512MB PC2700 DDR333 CL2.5 SDRAM DIMM's. They call it Hyperspeed RAM. Anywho, I powered down let the system cool over night and in the morning, popped it open, put the RAM in the 2 open slots DIMM2/J23 & DIMM3/J20. closed it back up and powered up. Everything was snappier, the boot was quicker and I checked About this Mac, it says 2GB. Apple System Profiler showed all 4 DIMM's and I thought everything was fine.
    Computer ran great for hours, no issues. Everything seemed quicker. Computer went to sleep overnight, next day woke from sleep and Tried to use iTunes and during an extensive sort for Songs, the system Locked up. Nothing would work. Had to force restart. this time I tried to Run my favorite online Game, WoW and after it loaded and I started to play, within 5 mins the whole game locked up. The audio sound went into a sort of Loop, I couldnt force quit and had to force reboot. This happened several times. I finally decided to Run the Apple Hardware Test. The Quick test locked up after running 2mins. I let it sit for 1hr just in case it was still doing something and the progress bar and time never progressed. So i forced reboot, ran Test again this time as Extended test. at 8 min & 31 sec the test stopped and I got an Error Code, this time I wrote it down "2MEM/2/4: DIMM3/J20."
    I guess that DIMM failed. I shutdown, popped open case, and removed DIMM3/J20 leaving the Original 1GB RAM and One of the 512MB Upgrades. I rstarted the Test again and Ran the Extended Test once more. It ran for 27mins & 24 secs and everything passed. So. 1.5GB is better than just 1GB. I powered down and powered back up to try and play WoW. Within 5 mins of loading game to play, everything locked up again.
    So I took both of the new RAM out and left the Original 1GB RAM and ran Test everything was great no Errors. Rebooted, and went onto WoW again and was able to play for several hours. I quit game and shut down for night.
    I have since Tried the 2x 512MB DIMM's in over 10 different variations in the computer with and without the original RAM and everytime I run a high end program or game (WoW, iTunes, and Photoshop), I get lock ups, crashes, and other screen weirdness.
    I dont want to have to Return the Memory again. I am already out over $15 from s/h with RMA's.
    PLEASE Any ideas what to do?
    1 thing I noticed the RAM gets very very hot, when I've powered down tand removed the new RAM. I wonder if there is a cooling issue?
    Anytime I put the Original 1GB RAM in, I dont have problems!

    Hi lz3broc,
    Sounds very much like faulty RAM to me, I'm afraid. I'm not sure about the temperature it's running at, but if the surrounding DIMMs aren't having a problem then I would definitely point the finger at those new memory sticks not being up to scratch.
    If you were convinced it was temperature related then you could always try putting heat spreaders on the memory to help with cooling, but as these stick (semi-permanently) to the RAM then you would never be able to return them.
    My personal opinion is that you should send the RAM back and buy two new DIMMs from Crucial Technology. I only ever buy RAM made by them and I've never had a problem with it - it's the same stuff Apple themselves generally use and works a charm every time. Probably not the news you wanted to hear, but that's probably the only way you're going to get a stable machine with 2GB RAM.
    Hope that helps,
    Andy.
    PowerMac G4 Dual 1.50GHz   Mac OS X (10.4.4)   Liquid Cooled

  • Kernel Panic Message...Caused by new RAM???

    Hey guys, just purchased 2x1gb ram from otherworldcomputing.com for my powerbook G4, im currently running the latest version I can possibly run which is 10.5.8  Everything seemed great when I put the RAM in, seemed like my computer was running pretty fast campared to the 512gb that came with the computer.  All of a sudden, while im searching the web, it throws that kernel panic message up at me.  I restarted and a few minutes later while im still on the web, bam, the same message. 
    I am currently in safe mode while Im writing this and nothing has happened yet(update:a few mintues after I finished typing this thread I received the same message, I have turned the computer off and jumped on my wiftes computer to type this I am thinking about putting the original 512mg ram back in to see if I get the message again) 
    Wierd, the first few days witht the new RAM everything seemed fine and then all of a sudden I got those messages.  I have never had the problem ever before so it makes sense that its gotta be the new RAM right?  Here are my specs
    Model Name:          PowerBook G4 15"
      Model Identifier:          PowerBook5,6
      Processor Name:          PowerPC G4  (1.2)
      Processor Speed:          1.67 GHz
      Number Of CPUs:          1
      L2 Cache (per CPU):          512 KB
      Memory:          2 GB
      Bus Speed:          167 MHz
      Boot ROM Version:          4.9.1f1
      Hardware UUID:          00000000-0000-1000-8000-0011243630A2
      Sudden Motion Sensor:
      State:          Enabled
      Version:          1.0
    This is the log from the 2nd kernel panic message that i copied and pasted for you guys
    Process:         SystemUIServer [404]
    Path:            /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer
    Identifier:      com.apple.systemuiserver
    Version:         1.5.5 (248.9)
    Build Info:      SystemUIServer-2480900~26
    Code Type:       PPC (Native)
    Parent Process:  launchd [63]
    Date/Time:       2012-04-08 11:31:41.326 -0500
    OS Version:      Mac OS X 10.5.8 (9L31a)
    Report Version:  6
    Anonymous UUID:  C89C038C-A8C3-4C08-B445-D420315A507C
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000002f61400
    Crashed Thread:  0

    To eliminate RAM being the problem, Look at this link: Testing RAM @ http://guides.macrumors.com/Testing_RAM Then download & use Memtest & Ramber.
    Do you have an Apple Hardware Test disc (the AHT is on the Install/Restore DVD that came with your Mac)? Running the Apple Hardware Test in Loop Mode is an excellent troubleshooting step for finding intermittent hardware problems. It is especially useful when troubleshooting intermittent kernel panics. If Loop Mode is supported by the version of the Apple Hardware Test you are using, you run the Extended Test in Loop Mode by pressing Control-L before starting the test. Looping On should appear in the right window. Then click the Extended Test button.The test will run continuously until a problem is found. If a problem is found, the test will cease to loop, indicating the problem it found. If the test fails, be sure to write down the exact message associated with the failure.In some cases, RAM problems did not show up until nearly 40 loops, so give it a good run.
     Cheers, Tom

  • Random restarts and freezes. Just upgraded my RAM trying to diagnose new RAM as the problem but they pass Rember test.

    Hey so I have been dealing with random reboots and computer freezes since upgrading my RAM. I also reinstalled my 10.8.2 at the same time I upgraded my RAM. I have a Mac Mini Mid 2011 with the OWC Data Doubler Kit and a Crucial M4 128GB Boot drive. My computer reboots every 30 minutes or so and sometimes completely freezes up. I am trying to figure out if the new RAM is the issue as I can send them back. I have ran several Rember RAM tests but the computer freezes mid test so I can not see the issue. All other times it completeles the RAM test with no issues.
    Any help is greatly appreciated!
    Here is my last crash report:
    Thu Mar  7 15:34:36 2013
    panic(cpu 0 caller 0xffffff8009ab7b95): Kernel trap at 0xffffff8009a76c4e, type 14=page fault, registers:
    CR0: 0x000000008001003b, CR2: 0xffffffa00cffad88, CR3: 0x000000000582b00c, CR4: 0x00000000000606e0
    RAX: 0x0000000000000000, RBX: 0xffffff800d17f488, RCX: 0x0000000000000000, RDX: 0xffffff800a0bd430
    RSP: 0xffffff80fa013d10, RBP: 0xffffff80fa013d60, RSI: 0x0000000000000000, RDI: 0xffffff800d17f488
    R8:  0xfffffffffffff000, R9:  0xffffff801b50b5d0, R10: 0x000000010ccc3000, R11: 0x0000000000000200
    R12: 0xffffffa00cffad78, R13: 0x000000000000007d, R14: 0x0000000000000000, R15: 0x0000000000000000
    RFL: 0x0000000000010293, RIP: 0xffffff8009a76c4e, CS:  0x0000000000000008, SS:  0x0000000000000010
    Fault CR2: 0xffffffa00cffad88, Error code: 0x0000000000000000, Fault CPU: 0x0
    Backtrace (CPU 0), Frame : Return Address
    0xffffff80fa0139b0 : 0xffffff8009a1d5f6
    0xffffff80fa013a20 : 0xffffff8009ab7b95
    0xffffff80fa013bf0 : 0xffffff8009ace4ad
    0xffffff80fa013c10 : 0xffffff8009a76c4e
    0xffffff80fa013d60 : 0xffffff8009a7be07
    0xffffff80fa013d90 : 0xffffff8009a75cf4
    0xffffff80fa013dc0 : 0xffffff8009a75150
    0xffffff80fa013e00 : 0xffffff8009a66b2c
    0xffffff80fa013ef0 : 0xffffff8009a6a890
    0xffffff80fa013f20 : 0xffffff8009db8d66
    0xffffff80fa013f50 : 0xffffff8009de17da
    0xffffff80fa013fb0 : 0xffffff8009acecf3
    BSD process name corresponding to current thread: syslogd
    Mac OS version:
    12A269
    Kernel version:
    Darwin Kernel Version 12.0.0: Sun Jun 24 23:00:16 PDT 2012; root:xnu-2050.7.9~1/RELEASE_X86_64
    Kernel UUID: 8D5F8EF3-9D12-384B-8070-EF2A49C45D24
    Kernel slide:     0x0000000009800000
    Kernel text base: 0xffffff8009a00000
    System model name: Macmini5,1 (Mac-8ED6AF5B48C039E1)
    System uptime in nanoseconds: 151583130298
    last loaded kext at 11211562865: com.apple.driver.AppleHWSensor          1.9.5d0 (addr 0xffffff7f8b414000, size 28672)
    loaded kexts:
    com.apple.driver.AppleHWSensor          1.9.5d0
    com.apple.driver.AudioAUUC          1.60
    com.apple.iokit.IOBluetoothSerialManager          4.0.9f8
    com.apple.filesystems.autofs          3.0
    com.apple.driver.AppleUpstreamUserClient          3.5.10
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.driver.AppleMikeyHIDDriver          122
    com.apple.driver.AppleMCCSControl          1.0.33
    com.apple.driver.AppleHDAHardwareConfigDriver          2.3.0f2
    com.apple.driver.AppleTyMCEDriver          1.0.2d2
    com.apple.driver.ApplePlatformEnabler          2.0.5d4
    com.apple.driver.AGPM          100.12.69
    com.apple.driver.AppleMikeyDriver          2.3.0f2
    com.apple.driver.AppleIntelHD3000Graphics          8.0.0
    com.apple.iokit.IOBluetoothUSBDFU          4.0.9f8
    com.apple.driver.AppleHDA          2.3.0f2
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.0.9f8
    com.apple.driver.AppleSMCPDRC          1.0.0
    com.apple.iokit.AppleBCM5701Ethernet          3.2.5b3
    com.apple.driver.AppleMuxControl          3.2.6
    com.apple.driver.ApplePolicyControl          3.2.6
    com.apple.driver.AirPort.Brcm4331          600.15.20
    com.apple.driver.AppleLPC          1.6.0
    com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
    com.apple.driver.AppleIntelSNBGraphicsFB          8.0.0
    com.apple.iokit.SCSITaskUserClient          3.5.1
    com.apple.driver.AppleIRController          320.15
    com.apple.driver.AppleFileSystemDriver          3.0.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.BootCache          34
    com.apple.driver.XsanFilter          404
    com.apple.iokit.IOAHCIBlockStorage          2.2.0
    com.apple.driver.AppleUSBHub          5.1.6
    com.apple.driver.AppleFWOHCI          4.9.5
    com.apple.driver.AppleSDXC          1.2.2
    com.apple.driver.AppleAHCIPort          2.4.0
    com.apple.driver.AppleUSBEHCI          5.1.5
    com.apple.driver.AppleUSBUHCI          5.1.5
    com.apple.driver.AppleEFINVRAM          1.6.1
    com.apple.driver.AppleHPET          1.7
    com.apple.driver.AppleACPIButtons          1.6
    com.apple.driver.AppleRTC          1.5
    com.apple.driver.AppleSMBIOS          1.9
    com.apple.driver.AppleACPIEC          1.6
    com.apple.driver.AppleAPIC          1.6
    com.apple.driver.AppleIntelCPUPowerManagementClient          196.0.0
    com.apple.nke.applicationfirewall          4.0.39
    com.apple.security.quarantine          2
    com.apple.driver.AppleIntelCPUPowerManagement          196.0.0
    com.apple.iokit.IOSerialFamily          10.0.6
    com.apple.kext.triggers          1.0
    com.apple.iokit.IOSurface          86.0.2
    com.apple.driver.DspFuncLib          2.3.0f2
    com.apple.iokit.IOAudioFamily          1.8.9fc9
    com.apple.kext.OSvKernDSPLib          1.6
    com.apple.iokit.IOBluetoothFamily          4.0.9f8
    com.apple.driver.AppleSMBusController          1.0.10d0
    com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.0.9f8
    com.apple.iokit.IOEthernetAVBController          1.0.2b1
    com.apple.iokit.IOFireWireIP          2.2.5
    com.apple.driver.AppleHDAController          2.3.0f2
    com.apple.iokit.IOHDAFamily          2.3.0f2
    com.apple.driver.AppleBacklightExpert          1.0.4
    com.apple.driver.AppleGraphicsControl          3.2.6
    com.apple.iokit.IONDRVSupport          2.3.4
    com.apple.iokit.IO80211Family          500.15
    com.apple.iokit.IONetworkingFamily          3.0
    com.apple.driver.AppleSMC          3.1.3d11
    com.apple.driver.IOPlatformPluginLegacy          1.0.0
    com.apple.driver.IOPlatformPluginFamily          5.2.0d16
    com.apple.driver.AppleSMBusPCI          1.0.10d0
    com.apple.driver.AppleThunderboltEDMSink          1.1.8
    com.apple.driver.AppleThunderboltEDMSource          1.1.8
    com.apple.iokit.IOGraphicsFamily          2.3.4
    com.apple.driver.AppleThunderboltDPOutAdapter          1.8.5
    com.apple.driver.AppleThunderboltDPInAdapter          1.8.5
    com.apple.driver.AppleThunderboltDPAdapterFamily          1.8.5
    com.apple.driver.AppleThunderboltPCIDownAdapter          1.2.5
    com.apple.iokit.IOSCSIBlockCommandsDevice          3.5.1
    com.apple.iokit.IOUSBMassStorageClass          3.5.0
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.1
    com.apple.iokit.IOUSBHIDDriver          5.0.0
    com.apple.driver.AppleUSBComposite          5.0.0
    com.apple.iokit.IOUSBUserClient          5.0.0
    com.apple.driver.AppleThunderboltNHI          1.6.0
    com.apple.iokit.IOThunderboltFamily          2.0.3
    com.apple.iokit.IOFireWireFamily          4.5.5
    com.apple.iokit.IOAHCIFamily          2.2.0
    com.apple.iokit.IOUSBFamily          5.1.6
    com.apple.iokit.IOHIDFamily          1.8.0
    com.apple.driver.AppleEFIRuntime          1.6.1
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.sandbox          220
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          7
    com.apple.driver.DiskImages          344
    com.apple.iokit.IOStorageFamily          1.8
    com.apple.driver.AppleKeyStore          28.18
    com.apple.driver.AppleACPIPlatform          1.6
    com.apple.iokit.IOPCIFamily          2.7
    com.apple.iokit.IOACPIFamily          1.4
    com.apple.kec.corecrypto          1.0

    Reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts on the memory modules when handling them. If necessary, clean them with a mild solvent such as rubbing alcohol.
    The Apple Hardware Test, though generally unreliable, will sometimes detect a fault. A negative test can't be depended on. Run the extended version of the test.

  • Thumbnail view crashing FCP -- Kona3 the problem?

    For larger projects, running bins in thumbnail view crashes FCP.
    Most of the time, I'm editing 6 to 8 min. stories for a news magazine format show. We shoot on Sony XDCAM, so usually 2 or 3 disks per project (roughly 44 mins of HD viddy per disk, with anywhere from 20 to 120 individual clips on the disk).
    However, for our documentaries (either 26 mins or 56mins) we shoot between 30 to 45 disks full of content. When importing the disks into FCP7, we use a bin per disc, translating into an average of 80 clips per bin. Whenever a project is this big, I can only open 3 or so bins in thumbnail view. After that, the system crashes. Even if I only keep one bin open at a time, by that fourth bin, the system crashes.
    We are using a KONA3 card configuration.
    Anyone else seen this?

    PROBLEM IDENTIFIED (NOT SOLVED):
    I've had this problem with thumbnail images crashing FCP after opening bins for over a year now and when going back using footage from old projects it happens more frequently. I can open 2-4 bins before it will crash FCP completely.
    TROUBLESHOOTING IN THE PAST:
    - Dumped Prefs
    - Re-installed FCP
    - Formatted & Re-installed EVERYTHING (OSX included)
    - Increased thumbnail cache size
    - Created new projects & bins, etc.
    CONCLUSION:
    None of the above troubleshooting strategies worked. Increasing the thumbnail cache size may appear to work a little but problem persists with little improvement.
    HOW I IDENTIFIED THE PROBLEM:
    Only recently have I been working with other formats aside from XDCAM. I've recently incorporated more ProRes files into my most recent project of T2i footage from the Canon DSLR camera. If I open a bin and display thumbnails of the ProRes video clips everything works without a problem. Loading thumbnail bins with the raw .mp4 files also works fine. Only loading XDCAM files will cause FCP to crash. The problem has nothing to do with the Kona card. If you read the posts carefully here and elsewhere you will see the common denominator is the XDCAM encoded video files being displayed as thumbnail icons.
    I am using XDCAM EX files at 1080p 30fps. To further isolate this problem as something having to do with the XDCAM files, another user posted on another thread:
    *"I am having similar issues with two separate projects. The only commonality between them is XDCam.*
    *To possibly isolate it I reinstalled FCP on one system, and installed latest Blackmagic driver on the the same. Both systems are up to date visa vi OS, FCP, and QT.*
    *Both still crash with the same regularity as described here."*
    Apple, this problem has persisted for more than two years and is a major problem. Just search the forums including this one. Any further upgrades of Final Cut Studio or OS X are worthless until this problem is fixed. A brand new body and interior won't fix a car with a broken engine. Please help!! Please solve this issue with the XDCAM footage in FCP!
    If anyone has any solutions or work arounds please notify me. I need it!
    [email protected]
    /\/\ichael
    Message was edited by: MichaelRev1412
    Message was edited by: MichaelRev1412

  • When i install the new os my fcp,motion and many adobe software not working so please help me out.

    when i install the new os my fcp,motion and many adobe software not working so please help me out.
    there are so many videos on youtube but i want know any solution from apple side plz my so many works are pending becuze i am working as Video Editor.

    You need to be more specific about which software applications you're using, the versions and what happens when you try to open them.
    It would also be nice if you could include which model MacBook Air you're using.
    Clinton
    MacBook Pro (15” Late 2011), OS X Yosemite 10.10, 16GB Crucial RAM, 960GB M500 Crucial SSD, 27” Apple Thunderbolt Display

  • AVCCam Crashing FCP

    Hi,
    Just back from Cannes where my latest short film was picked up by a distributor...aside from that great news, back to reality:
    I'm just trying to load in some footage from the new HMC151 panasonic AVCCam.
    However, everytime I try log and transfer it crashes FCP saying there's a problem with Perian. I've tried different Macs, card readers, using the camera as the reader etc, but the clips won't load in.
    I tried shooting in 720/25p and the clips came in fine, but that doesn't help the fact I have a card full of 720/50p clips I need to get in and edit.
    Any ideas? How do I remove Perian to get that out of the equation?
    Help as always appreciated.
    Kenny.

    It has an uninstaller.
    Look in the system preferences.

  • Sequences crash fcp

    so we're transitioning from fcp 5.0.4. on a g5, 10.3.9 to fcp 6.0.4 on an intel, 10.4.11. i've got all my old fcp sequences transfered over along with all the necessary files. however, there are some projects that have troublesome sequences that crash fcp whenever i try and open them. the projects are updated and open fine. but when i try and open up certain sequences, they'll open up in the timeline and immediately crash fcp.
    i tried copying all the files in the project to a new project. i deleted the old project file and resaved it under a new name. i saved and restarted fcp. still have the exact same problem. what's going on? am i never going to be able to open these sequences again? cause they're kinda important.

    so your guess is that it's an operating system issue? and you don't think it could be anything else? i suppose that does make sense since the issue makes no sense at all, but just wanna confirm before thinking about spending more money.

Maybe you are looking for

  • Bring Back the HTML Web Photo Galleries to CS4

    These were useful, easy to customize templates with more creative freedom. Much more so than what the flash templates provide. Using the web photo gallery control panel through Bridge was more efficient than through Photoshop since you could select f

  • Photo and iphoto create albums?!??

    I downloaded iphoto with the misunderstanding that it would let me organize my photos, something i have been waiting for since i have started using the ipad2.  I went through support and found that you must go through just plain Photo to do so.  Okay

  • Accessing one mail database across multiple macs

    I am not too familiar with the mac yet, I'm getting there, but I have an issue I can't figure out... I convinced my parents a long time ago to get macs, imac and macbook pro, and both have windows on them, and that's what they're using. I have impose

  • Wht is the differance betwen urn and url?

    wht is the differance betwen urn and url?  why we neet to give sender communication channel and sender service that not done in file to file plz clarify my basic and fundamental doubt..thanq

  • MWI on analog phone using stutter dial on VG248

    Someone is telling me that you can use stutter dial or some other method to light up an anolog phone Message waiting indicator using on a VG248. This is with an analog phone that has an Message light on it. Is this possible and if so is it possible u