Archived

This topic is now archived and is closed to further replies.

Ratheous

Error in NVDISP.DRV

Recommended Posts

Ratheous    122
I've been having a problem with the demos I've been getting from NEHE's site. I have a GeForce 2 MX and the latest Detanator drivers, AMD Athlon, WinME (though a friend with a GeForce 256, Det 3 drivers, PIII 600 and Win98 is having the same problems). I compile everything in MSVC++ 6 pro. After running once or twice without problems, I try to run again and before the video mode is even changed I get this, causing me to have to restart the system almost every time: < insert name of program > has caused an illegal operation in NVDISP.DRV Not an exact quote of course but that's basically it. (not at my compter right now so I can't duplicate it). The error is intermittent, so sometimes I can run a dozen times in a row and other times I'll run it once, and it will crash on the next attempt. I haven't tested this extensively with other programs using OpenGL, but every one of the tutorials I compile gives me this error. I've also gotten the error from demos not compiled by me, but other things seem to work. I run UT in OpenGL without problems, Deus EX is OpenGL, no? but if this is a new error that's just started coming up since I've been working in OpenGL I don' know, it's been awhile since I played them. I've tried using drivers downloaded from Hercules (the maker of my card) but that didn't seem to make any diference. Has anyone else had this error and fixed it? Is it something I'm doing wrong in the program? This is driving me insane! Thanks in advance for any help you can give.

____________________________________________________
"Two wrongs do not make a right; it usually takes 3 or more."

Edited by - Ratheous on 11/1/00 12:13:42 PM

Share this post


Link to post
Share on other sites
Ratheous    122
Um... Hm.

If so few are having this problem, it's not very likely it's an error in the code.

1: The drivers we are using are screwed - Not likely I think
2: Windows itself is set up in some way that causes this - Also unlikely
3: Other hardware installed is conflicting or some such - not that I've found
4: Another program running in the system is messing with things

But why are we not experiencing this with other programs?
If it's not an error in the code, then perhaps it's technically correct, and works on most systems, but on those few it has trouble with perhaps there's some way to code around it, preventing the error from occurring. Anyone else have any ideas?

____________________________________________________

"Two wrongs do not make a right; it usually takes 3 or more."



Edited by - Ratheous on November 2, 2000 2:42:51 PM

Share this post


Link to post
Share on other sites
zedzeek    529
it looks very much like you''re doing something that the display driver doen''t like.
try compiling some of the progs from the nvidia site and if they work see what they''re doing different to what u are doing

http://members.xoom.com/myBollux

Share this post


Link to post
Share on other sites
alistair b    122
i got this a lot when i was using my TNT with the 5.x drivers... and it cleared up when i got 6.x... i now have an asus geforce ddr running 6.31 and haven''t had any problems
(i was also running seti v2.7beta at the time of the crashes which may or may not have contributed)

the crashes also stopped me running display settings as i got an error in rundll32 - one that looked like an old style win3.1 error message - big white box, big black writing with only a disappointing ''OK'' for me to press... these always resulted in reboots......

so, i don''t think i can help other than to say try out other versions of the drivers, and see if you can get errors when only the openGL app is running

alistair

Share this post


Link to post
Share on other sites
Guest Anonymous Poster   
Guest Anonymous Poster
I use GLUT for my stuff... and I still experience this problem.
I''m pretty sure it is not a code problem but a driver problem.
Most likely since its NVDISP.DRV ... everyone with this error has a NVidia card, right??
I *THINK* I''m still using the 5.x drivers so they may be the cause of the problem.
It hasn''t bothered me too much yet (seems to be reset after a few minutes?) but it would be nice to get it solved.
I am using an AMD K6-2 300, 128 mb ram, TNT2 M64, Windows Millenium and I think the 5.x drivers.

Share this post


Link to post
Share on other sites
Guest Anonymous Poster   
Guest Anonymous Poster
I use GLUT for my stuff... and I still experience this problem.
I''m pretty sure it is not a code problem but a driver problem.
Most likely since its NVDISP.DRV ... everyone with this error has a NVidia card, right??
I *THINK* I''m still using the 5.x drivers so they may be the cause of the problem.
It hasn''t bothered me too much yet (seems to be reset after a few minutes?) but it would be nice to get it solved.
I am using an AMD K6-2 300, 128 mb ram, TNT2 M64, Windows Millenium and I think the 5.x drivers.

Share this post


Link to post
Share on other sites
Ratheous    122
Well I looked at NVIDIA''s site last night and found they had upgraded the Detanator drivers from v.0618 (which I had) to v.0631. I have yet to get the error again, but I didn''t have enough time to test it fully last night. I will do so tonight. *crosses fingers*

____________________________________________________

"Two wrongs do not make a right; it usually takes 3 or more."

Share this post


Link to post
Share on other sites
zedzeek    529
i had a look at lesson1
u might wanna change under window style
WS_CLIPSIBLINGS | WS_CLIPCHILDREN

to WS_POPUP | WS_CLIPSIBLINGS (i think u need that popup in there for fullscreen)

http://members.xoom.com/myBollux

Share this post


Link to post
Share on other sites
Ratheous    122
Well it''s offcial. The new drivers fixed the problem. I haven''t gotten the error in 2 days! Thanks all for the help, and casparov - try the new drivers, bet they fix your problem as well.

____________________________________________________

"Two wrongs do not make a right; it usually takes 3 or more."

Share this post


Link to post
Share on other sites