NVidia driver 260.89 issues

Started by MikOfClassX, October 21, 2010, 09:42:39

Previous topic - Next topic

MikOfClassX

Hello,

I'm experiencing crashes with the New NVidia drivers 260.89 (win7 64). Again the PBuffers initialization is the problem. This happens systematically in my apps (but not in the LWJGL samples) both with 32bit and 64bit jvm.

Everything works with the previous version 258.96 and on ATI cards with the latest drivers.

I'm quite sure I'm facing a driver issue.

The error (sorry, Italian dump):
--
Nome dell'applicazione che ha generato l'errore: javaw.exe, versione: 6.0.220.4, timestamp: 0x4c908d15
Nome del modulo che ha generato l'errore: nvoglv32.DLL, versione: 8.17.12.6089, timestamp: 0x4caebc9a
Codice eccezione: 0xc0000005
Offset errore 0x00673ad0
ID processo che ha generato l'errore: 0xdac
Ora di avvio dell'applicazione che ha generato l'errore: 0x01cb70ff4c4ba034
Percorso dell'applicazione che ha generato l'errore: C:\Program Files (x86)\Java\jdk1.6.0_22\bin\javaw.exe
Percorso del modulo che ha generato l'errore: C:\Windows\system32\nvoglv32.DLL
ID segnalazione: aac3f15c-dcf2-11df-82a6-90e6ba448da0
--



Anyone with the same problem ?


Estraven

Hi, i've a similar issue

Since i upgraded to 260.89 drivers, the JVM crashes with no error message, except for the Windows 7 crash message box (32)

It crashes on OpenGL context initialisation.

I can't find any more information...

Estraven

kappa

this is a known bug in the nvidia drivers, hopefully they'll fix it soon.

The only known workaround atm is
QuoteFound a workaround that does not crash the app. Just need to turn Threaded optimization in nVidia panel to on or off. Do not set it to auto. Strangely the auto setting is causing the crash.

Estraven

Ho, ok, thanks. I'll try that.

Just to correct my previous message, I checked my code, i'm actually not sure where it crashes.
The OpenGL context is initialized correctly. A simple quad with a texture renders ok,
but some of my more "advanced" code make it crash.

Anyway, if there's a word around... that's fine for me. Thanks again Kappa.

Estraven,

MikOfClassX

Many thanks Kappa for the comments. I'll live with the previous driver version  :-\ until they fix it..

@Estraven, yes same issues here. Looks like "advanced" GL code kills the app and the jvm.


MikOfClassX

Update: 260.99 still suffer of the same problem. JVM crash.

Kappa Workaround: switch the Threaded optimization to ON or OFF in the NVidia 3D settings control panel. Confirmed that this works.

Let's hope NVidia fixes the problem asap.

pjohnsen

I ran into this too using 260.99.

I did however find another workaround: make sure you do all initialization and rendering on the same thread.

I'm using AWTGLCanvas in an applet, so for me this meant using SwingUtilities.invokeAndWait in the applets init() method to make sure construction of the canvas was done in the same event dispatch thread which does the rendering.

MikOfClassX

At last: 266.58 fixes the problems. No need to switch off the Threaded Optimization into the Nvidia cpl.

Cheers!