New Participant

Question

OpenGL Error Code 7

Forum|Forum|15 years ago
January 24, 2011
23 replies
52600 views

I just bought a EVGA GTX 470 so I could use the GPU Acceleration in Adobe. Soon after starting to edit some video, I get this error:

Your hardware configuration does not meet minimum specifications needed to run the application. The application must close. Please visit http://www.nvidia.com/page/support.html for help. Error code: 7

Premiere then freezes and I have to end the task.

When I set the render settings to Software Only, I have no issues.

I have googeled the error and have found no solution, but others are having similar problems.

All my drivers are up to date as of right now.

My hardware consists of:

Intel Core 2 Quad Q8300 @ 2.50GHz

6GB DDR2 RAM

EVGA GTX 470

600 Watt Power Supply

Any help would be much appreciated.

This topic has been closed for replies.

Show previous replies

A

Anonymous

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

S

Sonama268

New Participant

The news is very bad my Friends,

After roll back the program worked for a few hours, and last night gave me back the open GL error 7.

I work on a documentary with more than 2,000 takes and over 500 images, with the greatest more of 7000X12000, 96dpi.

The technician 10 min ago (it's morning in Greece) told me that we should put the Quadro 600 to solve problems.

What do you think? It's a good idea?

S

Sonama268

New Participant

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.

J

JustAnotherPhotog

Participating Frequently

I don't have this problem, but I have significantly changed my computer.

1. I upgraded my MB to the latest and greatest AMD 990x chipset

2. I upgraded my system drive from a 5400 to a 7200

3. Did a complete new windows install, and CS5.5.2 install.

4. All the latest drivers.

Things are rock solid now for about a week. I've been cutting everyday for 8 hours or so.

Good Luck

{KMS}

Known Participant

Darren,

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

J

JustAnotherPhotog

Participating Frequently

I have some news to report.

First my system

AMD Phenom III - 1090

16GB of RAM

Nvidia GTX570 - 1.28gb (drivers are the most recent, October 24 drivers)

MPE is turned ON

I read this thread, and a ton of others, and tried changing all my still images. I resized them to 72dpi and always under the 1920X1080.

I opened a new project, and rebuilt a short 10 second project that always causes the crash. This included changing the size of each jpeg, and the position of each jpeg. All the things that usually cause an Open GL 7 crash.

I worked the project for 30 minutes, no crash.

The key here is the size of the images, using the latest driver. Make sure they are under 1920X1080 for size, and at 72 DPI.

I hope this helps. Please try it and let me know what you think.

Cheers

DBK

D

DavidNDobson

Participating Frequently

I just ran into the exact same error.

on CS5.5 with a nVIdia GTX 285 and driver version 280.26.

The project is all stills and they are large and they are all scaled to frame with dissolves in between (yes a simple slideshow.)

Program crashed as I was scrolling through the timeline - happened multiple times at different points. I'd get to a frame that wouldn't resolve and then a crash.

I turned off MPE and I can work with the project and am rendering out the final now - but wow is it slow without MPE!

J

JustAnotherPhotog

Participating Frequently

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

2

2 Pros Media

New Participant

I just updated to the 10/24/11 driver update and got the same error. Never had a problem until the 24th. Had to pull the card and put in an old GTS 8800 as I had a project due with a deadline. Adobe, Nvidia.... either of you have an answer or fix? Everythingn my PC is up to date. This is VERY frustrating.

S

sirira2000

New Participant

I'm getting the same problem. Whenever I add a picture to the timeling

or work on resizing it in the

timeling it says the the exact same thing you have. I have to shutdown premiere pro via control panel. What the heck!

I hope Nvidia comes up with a new driver to fix this or adobe adresses this as and update. I'm getting frustrated with my projects..

Eric

S

stevesheridan

New Participant

I went back to Ver. 259.81 drivers and it seems to have taken care of the problem. I'm working on a project now that has over a hundred and fifty 12 megapixel stills in it.

S

stevesheridan

New Participant

I'm using 270.61 with an FX 3800

Colin Brougham

Participating Frequently

Steve,

The Nvidia 270.61/270.71 drivers have a problem with CS5/CS5.5 right now; a new version is supposed to be released soon. Use the previous WHQL version in the meantime.

mikeklar

Inspiring

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

Jeff

Regarding the Video card temperature, this appears to be normal. In my case (Nvidia GTX 580) if left at the default settings the idle temperature will run at 60 degrees C. Using EVGA's software I manage to keep this at 50 degrees C, however the cost is slightly more fan noise.

As to your issue with PP5.5 crashing, If I understand your explanation correctly it seems to be similar to what caused one of my video clips to do the same. This is an issue Adobe needs to address, or at least make a recommendation on the limits of the resolution acceptable. Naively I started with images that were 100MB in size, eventually reduced them to 140ppi (from 360ppi) with a file size from 2MB to 15MB. These were stacked six to seven layers deep.

At that point PP stopped crashing except for one image which had been severely edited in photoshop and merging some of the layers solved this problem.

Hoping you will solve your problem soon.

Cheers

Michael

B

bandgeek8910Author

New Participant

Well it turns out the issue must of been due to the fact I was working with large pictures. I just did a project with just video from a T2i and it worked just fine.

However I have discovered a issue where if I am watching a video (you tube, Vimeo, Windows Media Player, VLC) and I switch into full screen mode, the display turns black for ab out 5 seconds. Same thing happens when i swtich from full screen to normal windowd. And in cases where I am watching via online, when I switch from full screen to normal, the video does not scale back down, so I only see whatever fits in the normal size of the frame. Flash player is updated to the latest version.

Here is an example.

http://www.youtube.com/watch?v=uEJfYzC7gI4

I am not really expecting an answer to this as I know the main issue of the thread has been 'solved' I thought I would post this anyway.

B

bandgeek8910Author

New Participant

Still no fix, I will also note that my Photoshop Printing process is quite laggy as well.

Colin Brougham

Participating Frequently

Hopefully Steve won't mind me mentioning, but I sent him a project file and some images that were triggering the crash, and it seems that he had cornered the issue. Without going into specifics--mainly because I don't know any specifics--this appears to be related to large images that, when displayed using hardware MPE and CUDA acceleration, fill up the memory of the GPU and eventually crash the software. The workaround, beyond not using hardware MPE, is to resize your images.

Can you pinpoint the part of your project that causes the problem? If it's with an image file, you might try resizing it in Photoshop or similar; lowering the DPI and changing the frame size will help this. If it's with a video clip, that might be a different issue altogether and you should probably report the issue with as much detail as possible.