Nvidia opengl driver error code 7 как решить проблему

In Response To Todd_Kopriva

CS5 5.0.3.

The update manager says everything is up to date.

In Response To bandgeek8910

In the mean time while they sort this problem out why don’t you roll back to 258.96 (or any other earlier version than that last one where they made immense changes). That is what I have on my editing computer and it is working perfect on my GTX 480 and my GTX 580.

I just encountered this error message and subsequent crash, myself. I’m running the latest nVidia drivers—which seem to be causing other issues as well.

This error/crash seems is reminiscent of the earlier crash that would occur with large images and hardware MPE. I wonder if the new drivers introduced a regression to this behavior.

I can easily reproduce this. I’ll post up a project file and image later; hopefully Steve Hoeg will pop in here. He seems to be the guy on-task with these issues

For people running into this problem, what version of the NVIDIA driver are you using?

In Response To Steve_Hoeg

I’m using GeForce 266.58, released 01.18.11, on a GTX480 and 5.0.3. I’m going to rollback to 260.99 in a little while, to see if I can replicate it. I’ve had all kinds of issues since going to these drivers; the «jumpy stills» thread is another issue I hadn’t witnessed before.

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

In Response To bandgeek8910

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.

In Response To Colin_Brougham

Colin,

Perhaps a case of doing things, as they needed to be done in earlier versions — Scaling overly large stills in PS, prior to Import?

Just thinking here,

Hunt

In Response To the_wine_snob

Maybe… but this was a bug, not a matter of practice or performance.

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.

I’m using 270.61 with an FX 3800

In Response To stevesheridan

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.

In Response To Colin_Brougham

In Response To Todd_Kopriva

FYI

The same issue has just arisen on my system after installing the latest upgrade of GeForce GTX 580 driver to version: 275.33, and Premiere Pro CS 5.5

This problem did not occur prior to the latest video driver installation.

My basic system parameters:

CPU i7 950

24 GB DDR3 RAM

14TB available in a RAID configuration (8 HDs) via dedicated RAID card

250GB SSD system drive

Video card GTX 580

Granted, I do have a number of large still images stacked three layers deep above the video.  Per suggestions in this thread I will resize them smaller and hopefully this will remmedy the problem for now.

Glad to see others are also having this problem and hopefully between Adobe and NVidia something will be done to remedy it soon.

Cheers,

Michael

In Response To Todd_Kopriva

I thought by downscaling my images I had resolved (or at least worked around) the issue, but I still get the dreaded error 7 OpenGL error when I work with still images (scrubbing the timeline, scaling, positioning etc). Not directly, but generally within 10 minutes or so (only when working with still images). I’ve got a 460GTX SE with the latest NVIDIA drivers (275.33) for WIndows 7 64bit. Picture size is 2448 * 3696, standard JPG. I also tried an older NVIDIA driver (263.09) but that didn’t help.

Is Adobe still working with NVIDIA to resolve the issue? (sorry had erroneously posted a similar message in another topic, but that topic was about a different OpenGL error)

In Response To 3dmus

Also — would it help at all if I would open a ticket/report a bug? If so, what would be the most appropriate place? Or is there already an open ticket for this?

In Response To 3dmus

What is the DPI of your images? Yes, I know that DPI does not matter as far as video is concerned—only pixel dimensions do—but when it comes to CUDA acceleration, it can make a difference.

If they’re digital camera photos at something like 180DPI, I’ve found that decreasing to 72DPI while maintaining the raw pixel dimensions helped.

In Response To Colin_Brougham

Ah — that’s an interesting one, Thanks for the suggestion Colin. The dpi for my resized images is 240 and for my original ones 300. I will definitely try your suggestion.

In Response To 3dmus

Yeah, 240DPI is probably the issue; as long as you maintain the pixel dimensions when you drop to 72DPI, you’ll get no quality difference in Premiere Pro. DPI is for printing.

In Response To Colin_Brougham

Just going through some batch conversion in Photoshop to get to new DPI (and I realise this is not the right forum to bring this up!); recorded my resize + change DPI  action for a landscape photo and then batch processed all….only to find out that all landscape ones are fine, but portrait ones aren’t (for some reason PS treats them differently wrt my action)….grrrrr…anyways, will check the PS forum.

In Response To 3dmus

3dmus,

Has lowering the DPI worked out for you?  Just courious.  Thanks.

Kevin

In Response To {KMS}

Forgive my butting here.

In my case (per a previous entry in this thread) changing the ppi to 120 did the trick on three layers of still images above the video clips.

Cheers,

Michael

In Response To Todd_Kopriva

CS5 5.0.3.

The update manager says everything is up to date.

In Response To bandgeek8910

In the mean time while they sort this problem out why don’t you roll back to 258.96 (or any other earlier version than that last one where they made immense changes). That is what I have on my editing computer and it is working perfect on my GTX 480 and my GTX 580.

I just encountered this error message and subsequent crash, myself. I’m running the latest nVidia drivers—which seem to be causing other issues as well.

This error/crash seems is reminiscent of the earlier crash that would occur with large images and hardware MPE. I wonder if the new drivers introduced a regression to this behavior.

I can easily reproduce this. I’ll post up a project file and image later; hopefully Steve Hoeg will pop in here. He seems to be the guy on-task with these issues

For people running into this problem, what version of the NVIDIA driver are you using?

In Response To Steve_Hoeg

I’m using GeForce 266.58, released 01.18.11, on a GTX480 and 5.0.3. I’m going to rollback to 260.99 in a little while, to see if I can replicate it. I’ve had all kinds of issues since going to these drivers; the «jumpy stills» thread is another issue I hadn’t witnessed before.

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

In Response To bandgeek8910

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.

In Response To Colin_Brougham

Colin,

Perhaps a case of doing things, as they needed to be done in earlier versions — Scaling overly large stills in PS, prior to Import?

Just thinking here,

Hunt

In Response To the_wine_snob

Maybe… but this was a bug, not a matter of practice or performance.

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.

I’m using 270.61 with an FX 3800

In Response To stevesheridan

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.

In Response To Colin_Brougham

In Response To Todd_Kopriva

FYI

The same issue has just arisen on my system after installing the latest upgrade of GeForce GTX 580 driver to version: 275.33, and Premiere Pro CS 5.5

This problem did not occur prior to the latest video driver installation.

My basic system parameters:

CPU i7 950

24 GB DDR3 RAM

14TB available in a RAID configuration (8 HDs) via dedicated RAID card

250GB SSD system drive

Video card GTX 580

Granted, I do have a number of large still images stacked three layers deep above the video.  Per suggestions in this thread I will resize them smaller and hopefully this will remmedy the problem for now.

Glad to see others are also having this problem and hopefully between Adobe and NVidia something will be done to remedy it soon.

Cheers,

Michael

In Response To Todd_Kopriva

I thought by downscaling my images I had resolved (or at least worked around) the issue, but I still get the dreaded error 7 OpenGL error when I work with still images (scrubbing the timeline, scaling, positioning etc). Not directly, but generally within 10 minutes or so (only when working with still images). I’ve got a 460GTX SE with the latest NVIDIA drivers (275.33) for WIndows 7 64bit. Picture size is 2448 * 3696, standard JPG. I also tried an older NVIDIA driver (263.09) but that didn’t help.

Is Adobe still working with NVIDIA to resolve the issue? (sorry had erroneously posted a similar message in another topic, but that topic was about a different OpenGL error)

In Response To 3dmus

Also — would it help at all if I would open a ticket/report a bug? If so, what would be the most appropriate place? Or is there already an open ticket for this?

In Response To 3dmus

What is the DPI of your images? Yes, I know that DPI does not matter as far as video is concerned—only pixel dimensions do—but when it comes to CUDA acceleration, it can make a difference.

If they’re digital camera photos at something like 180DPI, I’ve found that decreasing to 72DPI while maintaining the raw pixel dimensions helped.

In Response To Colin_Brougham

Ah — that’s an interesting one, Thanks for the suggestion Colin. The dpi for my resized images is 240 and for my original ones 300. I will definitely try your suggestion.

In Response To 3dmus

Yeah, 240DPI is probably the issue; as long as you maintain the pixel dimensions when you drop to 72DPI, you’ll get no quality difference in Premiere Pro. DPI is for printing.

In Response To Colin_Brougham

Just going through some batch conversion in Photoshop to get to new DPI (and I realise this is not the right forum to bring this up!); recorded my resize + change DPI  action for a landscape photo and then batch processed all….only to find out that all landscape ones are fine, but portrait ones aren’t (for some reason PS treats them differently wrt my action)….grrrrr…anyways, will check the PS forum.

In Response To 3dmus

3dmus,

Has lowering the DPI worked out for you?  Just courious.  Thanks.

Kevin

In Response To {KMS}

Forgive my butting here.

In my case (per a previous entry in this thread) changing the ppi to 120 did the trick on three layers of still images above the video clips.

Cheers,

Michael

PLS HELP ME
when i using houdini software(shatter,particles,fluids) my system showing the following msg -(The Nvidia OpenGL driver lost connection with the display driver and is unable to continue. The application must close. Please visit http//www.nvidia.com/page/support.html for help. Error code 8.).how to fix this problem.any one help me pls..

my system configuration is

-software-windows 7 home premium,houdini12.5,
hardware-intel core i5,8gb RAM,2gb NVIDIA geforce GT-540M with cuda,750GB HARD DISK.

Usually this message is cause of the your VGA driver !
Update your VGA driver and if it’s not solve , temporally change Houdini Scene Renderer to other options like H11 until you find solution !

I have same problem but when I change Rendere Option to H11 it’s solved and finally I install another driver to fix it (GTX 570)

To change renderer option :

Edit -> Preferences -> 3D Viewports -> Scene Renderer

This means that either a single compute or graphics task is taking long enough to prevent the driver from communicating back to Windows, so Windows thinks it has crashed and attempts to restart it. The graphics card may be still be running a valid task.

The default timeout is 2 seconds, which is relatively short. You can adjust the timeout by editing the registry (minimally using regedit shipped along with Windows, but other tools exist for this). The full Windows article on the subject is here:

http://msdn.microsoft.com/en-us/windows/hardware/gg487368.aspx [msdn.microsoft.com]

And the relevant section:

The TDR-related registry keys are located under HKLMSystemCurrentControlSetControlGraphicsDrivers.

TdrLevel: REG_DWORD. The initial level of recovery. The possible values are:
— TdrLevelOff (0). – Detection disabled.
— TdrLevelBugcheck (1) – Bug check on detected timeout, for example, no recovery.
— TdrLevelRecoverVGA (2) – Recover to VGA (not implemented).
— TdrLevelRecover(3) – Recover on timeout. This is the default value.

TdrDelay: REG_DWORD. The number of seconds that the GPU is allowed to delay the preempt request from the scheduler. This is effectively the timeout threshold. The default value is 2.

TdrDdiDelay: REG_DWORD. The number of seconds that the operating system allows threads to leave the driver. After a specified time, the operating system bug checks the system with the code VIDEO_TDR_FAILURE (0x116). The default value is 5.

You could try setting TdrDelay to 5 and TdrDdiDelay to 15 and see if that helps things. I wouldn’t recommend turning off detection altogether; that would prevent legitimate driver hangs from being detected.