[Landy Folsom]

You’re right, it was a kernal panic; I just didn’t get the code looking screen stating it.

10.0.06 worked fine on this machine and I had it on for a long time; 10.0.07 worked great for a long while, too. That sucks if it’s the cards all the sudden because they have been working with FCP all along. Totally o/o/the blue? Argh.

Isn’t this something Apple could rectify software-wise if that’s the case. I still hope it’s not the case.

Any idea what else I could look into?

[Landy Folsom]

Sorry, I just recalled this other bit. I thought the kernel panics were because of the system being ridiculously bogged down. But I recall that I was thinking, I’ve got to pull stuff off this machine, and so I thought I would pull the iPhoto media out. I searched the for the largest iPhoto files, thinking that I could just xfer “that” file over and it was like 250GB but the xfer time stated something like 24hrs.

I stopped it of course but the kernel panics came soon after that.

Did messing with that iPhoto file do some underlying damage to the system itself?

[Landy Folsom]

I didn’t get a kernal panic warning. I did have those a month ago. I wound up reinstalling OS and everything else then. All hardware was tested then and deemed sound.

Cards are definitely on the approved list: AMD Radeon HD 6770M 1024MB; Intel HD Graphics 3000 (VRAM 512)

Machine is late 2011 MBP 17″, INtel Core i7, 2.5GHz, 16GB RAM

The only peripheral I’m connected to right now is the Promise Pegasus R4. I’ve run tests on it, have the latest firmware update, had Promise double-check the subsystem info file, all that jazz.

I had Apple check the machine out weeks ago, after all the kernel panics. Note: I did swap out the 8GB RAM that came with my machine when it shipped for OWC 16GB and the kernel panic occurred with both. At the time, I had let the system drive get bogged down with a ton of iPhoto media, pics and videos of my kid (a year’s worth) and it was down to about 10% of it’s then capacity. Backed up all that and wiped the system drive clean. But now it’s back, this colossal, repeatable death.

What. Could. It. Be?

Thanks,

LF

[Landy Folsom]

I cut docs for years on earlier iterations of FCP to 7 and there I backed up all the time, worked fast, primarily hot keyed my way through the day, saving all the time like a fundamentalist, and of course my auto saves were set to every 15 mins, so I never lost much in those days. Major FUBAR and I could recover with the backups, yes.

This project proper is sitting on an FCP7 TL. My problem is that I’ve been experimenting with FCPX and like a lot about it but it’s worrisome when I think about migrating my show here. As it is I’m stuck with this piece that I must deliver ASAP and I’m continually flopping on the shore.

Event= project. I meant project.

[Landy Folsom]

Okay, I just noticed that the 3 clips I tried to move are 4.3MB apiece. The culprit(s)? Massive file sizes?

[Landy Folsom]

OMG. It’s not over.

I tried to move three clips made of stills (with some motion/compositing moves on them, color correction) down the timeline and the entire screen melted to that dreaded gray with the warning to “restart your computer.”

Any ideas?

[Landy Folsom]

Thanks, Craig

Sys dr is 750GB and only 20% of that is taken. I did run verify/repair permissions. The RAM tested okay. Hardware okay.

I took the edit and pasted it into a new timeline and renamed it and it’s been working fine so far. Could it have been simply Event corruption? Geez, how to avoid that? Because I’m taking this tiny piece from my 2.5hr show. I had considered migrating the show to FCPX from 7 but now it looks like a fool’s errand not knowing what caused this chaos.