Premiere CS5 crash in new Mac Pro 2010

I've had Premiere Pro CS5 5.0.2 installed since maybe July 2010 on this macbook pro 10.6.4   i7 w/8 Gigs of ram.

My problem just started last week.

I'm playing P2 Footage (but it does it with all kinds of footage) and lets say I drop about 15 minutes of clips on the timeline.

Then I start playback, and about 4 minutes into the video, the video and the Current Time Indicator freeze and the audio keeps playing.

When I hit stop or do anything, the beachball spins. I have to forcequit Premiere and the same thing keeps happening after I reboot and reopen Premiere.

So pretty much I'm stuck like chuck and not able to edit anything :-(

Please help,

~Lou~

Was the 5.0.4 update supposed to fix this problem? Because I am STILL getting it on my 2010 Mac Pro and 5.0.4 whenever I zoom into the timeline. Clicking Continue crashes Premiere.

In fact, I remember getting this error in 5.5 as well before I rolled back to cs5, except clicking continue did not crash the program.

I would also like to point out that with OSX 10.6.7 iMac 27" i7 with the ATI Radeon HD 5750 1G graphics, going back to Premiere Pro 5.0.0, like Adobe suggests, I now had a 100% reproducible bug of when I make in/out points on files in source player, then tried to drag to timeline, Premiere crashes. This makes working with Premiere impossible for me.

So now here are my choices:

1. work in 5.0.0 without being able to drag source clips that I mark in/out points on.

2. work in 5.0.3 with:

    a. not being able to have windows resizing while playing a clips without critically FREEZING my entire system (gray screen) - !00% all the time

    b. not being able to click on or drag a file that is in my project window to open in source player without crashing Premiere (doesn't freeze system) - 100%

          i. Workaround to this bug is to first play a clip in that tiny preview window (don't know what it's called) in the project window, then I can get any clip to    not crash the source player

3. Work in Final Cut pro. No crashes.

Please don't tell me my only solution to get Premiere Pro working is to wipe my system and then reload 5.0.0 because I won't do that when I also have Final Cut Pro on my system with no issues. I prefer Premiere and was telling people this was a game changer especially in the emerging indie DSLR film industry (where many many people are moving to iMacs 27" i7 form older Mac Pros because of how great and inexpensive these systems are to new emerging production studios, this is going to be a HUGE market for you Adobe because the already established production studios are still suck on FCP).

Yes I get it, the Mac Pro's with NVIDIA chips are your primary focus, but this doesn't mean you can just ignore a critical bug like this with ATI chips and with people who don't have the choice to get an NVIDIA card to fix this issue. It just proves the point to all those hardcore FCP people out there that Premiere is unreliable and I hate that because Premiere right now, I feel, is the best editor out there for DSLR editing and I can't use it without remember certain CAN'S AND CAN NOT'S while working with the software.

Thanks for your feedback, I tried your idea and it didn't seem to make much difference so you are probably right. My error is the same as the original post  by pericu_parrac in September. My system is the fastest and most efficient recommended by Adobe for Mac with the Matrox recommendation. Every configuration can present a problem and when three manufacturers product are being used together each one blames the other if there's an issue, mainly because they do not fully cooperate with one another, and systems are tending to be fragmented. i have used both Apple and PC edit systems since the mid 90's and there are still not 100% stable. What I object to is that customers are being used more and more to test products before they are ready to be released, thanks to forums, companies can correct errors through the forum feedback - this is cart before horse. There is nothing more frustrating than spending 000's of dollars/pounds and ending up with something you constantly have to repair yourself through patch downloads etc

The error message I have is exactly the same as the one here already posted except that mine reads [/Skinner64 instead of [/Scully64 as seen below...

thanks for any advice...but please let's not get into a PC versus Mac discussion!!

I too have experienced exactly the same issue with my new MacPro with the following set up:

Here are my specs:

a) MacPro 6-core Intel Xeon running OSX Snow Leopard 10.6.4
b) MX02 Max (& accelerator) with latest drivers 2.1,
c) Graphics card: Invidia Quadra 4800,
d) Premiere CS5.02.
e) Capture drive is G-TECH (GTECH-GR4-4000-EMEA) with ESata.

Capture preset: Matrox MX02 - Pal YUV 8bit
Capture Format: Matrox MPEG I-Frame limiting data to 5000KBytes/sec

The crash happens with no warning or apparent specific operation. The last time it happened for instance I was scrolling through Audio, but before that it happened for another reason. It is absolutely imperative that Apple and Adobe sort this out - as you can see from the spec it is nothing to do with the Apple ADI-Radeon card, and the Invidia one is a CUDA based one recommended by Aobe and Apple specifically for use with the Matrox MX02 set up. I don't know how to cure this issue so please Apple & Adobe help us by providing a patch

Thank you

Also seeing intermittment system freezes in PPro CS5 on my Mac Pro and I have updated to 5.0.3 (lates OS X as well 10.6.5). I  think have narrowed it down to only happening when using a second monitor for External device playback (playback options menu). Sometime the video will just freeze and the audio will continue but the mouse and keyboard have frozen and only a hard reboot will do. Unfortuantely this kind of crash does not engage the crash reporter for Apple or Adobe. ATI 5870 card in use as well. It may just be a conincidence but sticking to one monitor has not produced a crash yet (I would prefer to use that second monitor however).

I've had the same problem.  I even had my Mac Pro replaced since there was no real clear cause to the issue other than a Kernal Panic tied to the graphics card.  I did however find a a posting claiming that using the "FIT" setting for the clips viewers caused this issue.  I changed both of my viewers to specific percentages and CS5 PP has been stable.  Every now and then the graphics card will become glitchy causing me to restart PP.  Give it a try and see if it helps.

Sean

Ok this is going to sound crazy. I've recently had the same problem. I'm using the new iMac 27" with the ATI Radeon HD 5750, one month old. I would 100% crash hard lock up or even computer instantly shutting off the moment I tried to resize my sequence preview window while I was playing the timeline. I trashed my prefs, uninstalled PP CS5, nothing fixed it. This was happening with OSX 10.6.4, updated to 10.6.5, didn't fix it. Then I changed my preview from "fit" (which is what I always have it set to) to 20%. For some odd reason, now it's totally fine when runing the timeline and resizing. Changed it to other percentage options, no problem. Went back to "fit" and no issues now. STRANGE. But there is something definately funky going on with this ATI card because when I do have the window set to "fit" even if I have no clips in the timeline, when I go to resize the preview window I get white blocks of corruption in the black movie window on the borders. I'm not a programmer but I believe this is a redraw issue? Maybe that's a problem causing the crash because the one time I was able to get an Apple report dump there was a kore panic