Q312505- didn't work, OpenGL gives me an access violation

  • Thread starter Thread starter WaterWolf
  • Start date Start date
W

WaterWolf

I know the problem is a memory problem (trying to access
non-existent memory), and the article Q312505 on the
microsoft support page said my opengl32.dll file would be
updated to version 5.1.2600.21, but after installation of
the service pack, my opengl32.dll is still version
5.1.2600.1106 Basically, any games I try to run with
OpenGL lock up after 5 minutes or so. My current video
card is a Geforce2 MX 400, and I've dl'ed the latest
drivers from Nvidia, but nothing has changed. A random
website suggested muting a DVA=1 line in the win.ini
file, but that entry does not exist. My machine is a 3.2
P4 on an Albatron 865PE/PE Pro motherboard. I have a
stick of Kreton 512MB RAM, and am using a Western Digital
120MB hard drive. I'm hoping to geta new vid card soon,
but this one needs to last me a while longer. Any
suggestions? Reply or e-mail me at
(e-mail address removed). Thank you in advance for your
help.
 
The best way to change the graphics driver is to boot into Safe Mode, so
you're only using the generic VGA driver and than do the install. Make sure
your anti-virus software isn't running, too.
 
Have done. No change. Does anyone happen to have the
5.1.2600.21 version of opengl32.dll that they send me a
copy via e-mail maybe? I have a feeling it's the problem.
 
The article you referenced appears to be out of date, or at least the file
is. Opengl32.dll ver. 5.1.2600.1106 is the correct version for XP SP1.
The MS DLL database does not even list a version 5.1.2600.21. If you look
at the article again you will see that the date on it is 2001. The file you
currently have is dated 2002.

Search the computer for duplicate opengl32.dll files that may be in any of
the game folders. For instance I have version 1.4.9.0 of this file in my
Quake folder. Rename the extensions if you find any. The first file found
when you start a game will be the one that is used and if it happens to be
too old or incompatible with XP................
 
Try going to Start/Run and type in "sfc /scannow" without the quotes. This
invokes the System File Checker (SFC) which will verify the validity of your
system files. Further information on SFC is in Help and Support. If there
is something corrupt or the wrong version of the file, this should correct
it.
 
If you are running a GeForce2 MX card then if you install the Nvidia drivers
from www.nvidia.com you will get their OpenGL implementation and
opengl32.dll won't ever be used by your system again. opengl32.dll only
supports software render mode. Once there is an ICD on the system that will
be used instead since they support hardware calls. The 5.1.2600.1106 is the
correct version for Windows XP SP1 though.


Joshua Smith
DirectInput and OpenGL Test Labs
Microsoft
 
WaterWolf said:
I know the problem is a memory problem (trying to access
non-existent memory), and the article Q312505 on the
microsoft support page said my opengl32.dll file would be
updated to version 5.1.2600.21, but after installation of
the service pack, my opengl32.dll is still version
5.1.2600.1106 Basically, any games I try to run with
OpenGL lock up after 5 minutes or so. My current video
card is a Geforce2 MX 400, and I've dl'ed the latest
drivers from Nvidia, but nothing has changed. A random
website suggested muting a DVA=1 line in the win.ini
file, but that entry does not exist. My machine is a 3.2
P4 on an Albatron 865PE/PE Pro motherboard. I have a
stick of Kreton 512MB RAM, and am using a Western Digital
120MB hard drive. I'm hoping to geta new vid card soon,
but this one needs to last me a while longer. Any
suggestions? Reply or e-mail me at
(e-mail address removed). Thank you in advance for your
help.
Click to expand...

I had the same problem and ended up doing an in-place reinstall of WinXP
which I assume you are using. I tried a number of things like the win.ini
thing, replacing the dilly etc., all to know avail.

Ron
 
The solution was actually in my BIOS. BIOS was outdated,
and after updating it, the problem disappeared. Thanks
for your help!
--WaterWolf
 
Back
Top