Hello, I'm new to the forum and to Premiere. . .Having the same problem you guys are talking about.

What I'm experiencing: PR5.5 crashes when working with motion effects on jpg files, after resizing and/or repositioning on the 3rd or 4th edit. This is completely repeatable.

The background conditions:

• Just built up (2 days old) a new Dell T5500, dual xeon e5520, 250GB Intel 510 SSD primary, OCZ 60GB SSD scratch, 2x1TB Seagate striped (and always backed up) for storage, Pioneer BDXL, nVidia Quadro 2000 D.
• Fresh install of Windows 7 Ultimate, Premiere 5.5, Lightroom 3.4. All windows updates applied - SP1. Latest nVidia drivers - just installed 275.89 off nVidia's website, their web tool confirms I'm on that package. Device manager reports I'm on driver version 8.17.12.7589 for the video card? nVidia control panel reports video BIOS version 70.06.35.00.04. My card is running at about 60 deg C; don't know if that is normal or not.
• Had to edit the "cuda supported cards.txt" file entry from "quadro 2000D" to "quadro 2000 D" to get GPU assisted MPE to work.
• Much like some of you reporting this issue, I am working with high quality jpg and video clips, in my case this is from a Canon S95. The photos started as RAW in Lightroom, exported as high quality jpg, 72 ppi, 3000 on the long side to allow for "Ken Burns" motion effects. The stills are 1.5 mb to 5 mb in size.
• If I go to software only MPE, I can edit to my hearts content - no issues. I can actually deal with this workflow, it is relatively easy to go back and forth and I'm not seeing much difference in performance while I'm doing those edits (other than the crashes of course). But obviously would like to track this down and not have the workaround.

I hope this info helps the cause, I am willing to share any other info, or files if it will help.

I've worked with various forums for many years, this is one of the more helpful and professional that I have ever seen.

Thanks - Jeff

For me, I have found that keeping my files at 72 dpi (not sure if the
dpi makes a big difference in regards tot the crashing) and a maximum
size of 3600 pixels on the long edge of the image keeps PPRO from
crashing using my graphics card.

Thanks Michael, that makes me feel a little more comfortable. I had no frame of reference on Video Card temp.

Jeff

Harm

You are saying a pixel dimension of 1920 x 1080 ppi is all that is needed?  Regardless of ppi?

Please bear with me on this; lets take an image in Photoshop at 360 ppi with a pixel dimension of 6048 x 4032, at 72 ppi the pixel dimension is 1210 x 806 based on everything being relative.  Not withstanding that "constraining proportions" in Photoshop may have to be disabled, does your argument still apply, or are there additonal changes you would suggest?

Yes, I do appreciate Photoshop files are based on print or web usage, printing is what I'm most familiar with and dpi is something I leave to printer's RIPs.  However, until now I was under the impression that PPI is something that applies to video.  Perhaps wrongly based on several images given me to add to a video.  These images included large portions of blue sky and when displayed on HD video monitors there were clear steps of color changes from light to dark areas.

This has stuck with me ever since unfortunately those files are no longer available to check.  Of course it is possible these images were defective, but to the best of my recollection the files were of reasonable size around 4 or 5 MB in JPEG format.

BTW what does the acronym BRD stand for?

Cheers,

Michael

There is no "inch" in video. 

Well, I'm happy to have found this thread, and the work around - turn off my expensive GPU (GTX 570 in my case), but this doen't come near fixing this.

Has anyone, even Adobe or Nvidia found a solution to this. I'm one of those guys who switched from Mac & FCP7 to PC and Premiere 5.5. I did it for the real time, which I do love. However, in the last few weeks, I've reinstalled the system 4 times, removed and reinstalled CS5.5 5 times, spent a morning on on line chat with nvidia (who suggested the latest beta drivers. which did nothing, I'm running 280.xx.

Is there a final fix? Anyone?

DBK

I started to get this problem when I updated the Nvidia driver to 280, from 266.  But I was getting it with 100 Mb/s 1920x1080i.avi files captured via a Matrox MXO2.  There were no still images on the timeline.  It occurred only when I had several effects applied, e.g. colour correction, Mercalli stabilisation, scaling, unsharp mask.

My system is three years old, with a quad core 3GHz CPU, 8GB of RAM and a 1 GB GTX460 card, using 5 HDDs  - System, Project, Capture, Render files, Cache

With HDV files there are no problems at all.

Reverting to 266 largely removed the problem.  It still occurs very occasionally, and the system is somewhat unstable, with the very high data rate .avis.

My guess is that the system is over-stressed, probably more RAM, plus a Graphics card with more RAM would improve matters, but really my system is too slow overall for these large high data-rate files.

Roll on Sandy Bridge-E, or should I wait for Ivybridge????

.

Hello,

My system is: Intel Core i5-2300, 2,80Ghz, 8GB, GeForce GTX 470, win7pro-64bit, PrePro5.5.

I had the same problem but solved immediately installing version (roll back) 8.17.12.7533.

Thank you for helping.

Darren,

Have you been editing with any high resolution images? if so, how big are they?

Have Adobe/NVidia come up with a fix for this yet? Just build out a new system with a Quadro4000 and getting the same error just cutting some DVCPRO HD footage.  Long clips, but nothing exotic editing wise.  First project on the machine is making me nervous.  Deadline today.  Having to reboot every 1/2 hr is going to be an issue!  Help!

i7 950

Quadro 4000

24g ram

mxo2 mini

graid 4T

I've got the same frustrating problem:

CS5.5 Production Premium

X6 1100T - 6 CORES

Just upgraded to 16gb memory from 8gb

GTX 560 Ti 1056mb

SSD boot disk

2tb 7200rpm Scratch disks

266.54

Stock- no OC.

-Had tried selecting my graphics card GTX 560 ti instead of the 'auto select' option in Nvidia control panel, but still crashing.

I believe my system has sufficient muscle to handle a simple AE import of a Photoshop 3 liner text into premiere pro, and there should be no reason for the above extremely frustrating error message on my hardware being insufficient to handle the load...

Would appreciate any advice on how to remove this irritating message and constant hanging. Extremely frustrating to pay thousands to go through this pain.

Disabling the Mercury Playback Engine and setting it down to "Software only" will indeed fix the issue. The problem, obviously, is that this lessens performance drastically, especially when dealing with HD, and complex codecs that the GPU really excelled at. It is hard to place the blame on this one, for it appears that the GPU is getting overloaded, probably with multiple layers of large format images, and then locking up. But, on the other hand, perhaps PPro should be monitoring GPU load and adjusting accordingly. So, nVidia or Adobe--who's to blame? Probably both.

To get around this, in your PPro project, go to Project menu--->Project Settings---->General. Then, at the top drop down box change it from "Mercury Playback Engine GPU" to the option below it "Mercury Playback Engine Software Only" or something similar to that.

Also, if you right-click on your Program Monitor display, go to Playback Resolution and drop it down to 1/2 or 1/4 if your editing performance is severely sluggish, it will help--though you will lose visual quality (not real quality).

Adobe and nVidia--please go to lunch (I will pay for it!) and settle this problem. Standing offer.

I solved the problem when I switched to nvidia quadro 600.

Now is slower but the system does not stop as before.

Of course not. It's a cheap solution

I've had pretty much the same experience. I've assumed it was the limits of the GTX 480s cards memory.

If I have to edit huge images I'll do it in software mode, as we don't have $$$ for a super Nvidia card.

Not sure about CS6, but I am certainly having OpenGL errors on my rig with CS5.5 since updating CPU to i7-3930K and the motherboard to an ASUS P9X79. Predictably perhaps, PPro freezes when appllying Collorista II or MB Looks. The only way around this is to disable GPU rendering via the MB Looks standalone app and via 'Options' in the Collorista II tab in PPro. Extremely annoying. Sorry if I'm covering old ground, but this was working fine with my mobo/GPU/driver combo before changing boards. This isn't the large stills issue but just straight 1080p Canon 5DMKII video.

Also noticing the loss of my second monitor all of a sudden which is sporadic - investigating that now. The system completely freezes too, so no option for task manager here, just a hard reset. Not fun at all.

Red Giant have offered me nothing but the rather lame "update your graphics driver" excuse. I've run through just about every Nvidia driver since the 260 series and still no dice. Even tried the latest beta driver 301.24. No good either.

I have also encountered an issue with the Windows "Desktop Window Manager Session Manager" service that caused Premiere to freeze on project loading. Once I disabled this service Premiere works fine, except of course when I try to use Collorista II or Looks with GPU enabled. Crashes out Photoshop too BTW.

I'm on ASUS p9X79, i7-3930K, 16GB RAM, GTX480 (Hack applied), PPro 5.0.2, NVIDIA 296.10. Not sure but this may help someone or myself. RED GIANT have just gone very quite on the support line...

My bad Bill. It was a typo. Sorry, I meant to write 5.5.2.0, which is what I am running.

Well...just dowloaded the trial of CS6 and played around for a bit. Managed to get an Error Code 6 ("Your hardware configuration does not meet minimum specs") within half an hour. To be honest, I was stress testing it a bit by using a few large JPG images, accelerated effects etc, but still disappointing that it leads to a hard crash. Checked that I have the latest NVIDIA drivers etc.

I was really hoping that CS6 would have at least semi-fixed the issue (by not letting it crash at least), but so far...

I guess I will have to resort to re-sizing pictures etc. Still for things like a Ken Burns type effect it's much more preferred to start with a large image.

(GeForce GTX 460 SE via the CUDA "hack", 1GB)

Hi Todd - to be honest, I don't know b/c I don't own a supported one. I would be more than willing to buy a GeForce GTX 470 or other supported card if I would know this would fix the issue. Right now though, it seems that it's not just unsupported cards that suffer from this issue (judging from the replies in this thread)?

Other than this btw, I love the changes in CS6....and compared to CS5.5 the performance really improved too.