My game crashes when I play q3dm16
+ uWillBeHere
server side error message. All I see on the server is the client connecting
and later timing out. My client either locks up completely or crashes with
this error message:
QUAKE3 caused an invalid page fault in
module QUAKE3.EXE at 0187:00456d69.
Registers:
EAX=00000000 CS=0187 EIP=00456d69 EFLGS=00010246
EBX=00000800 SS=018f ESP=0150d0e4 EBP=00003f00
ECX=00000000 DS=018f ESI=00000000 FS=1c77
EDX=00000000 ES=018f EDI=00001b00 GS=1186
Bytes at CS:EIP:
8a 14 3e 33 c9 8a 0c 28 03 ca 33 d2 8a 14 38 03
Stack dump:
00000000 0150f284 0150f254 02b8cb00 05b1f0d6 00000000 00000200 00000000
05b1f0d4 00000000 00000000 05b1f0d4 00000000 00000000 00000000 00000004
I've done a complete reinstall with no improvement. I'm at a loss to suggest
a fix, anyone have any idea?
noise
+ uWillBeHere wrote:
>
<snip>
> I've done a complete reinstall with no improvement. I'm at a loss to suggest
> a fix, anyone have any idea?
Well when just one map crashes a game, particularly this one as it's
OpenGL-only, I could only suggest that there's a particular shader,
texture or something that is unique to that map which is causing the
problem. I had something like this with a Matrox G400 card with the
early drivers - certain rooms made my framerate crawl and occasionally
even crash. That was because those rooms used particular graphic FX
that called special GL functions called extensions.
So my guess is that on that map a particular graphic element calls
a GL extension which isn't working, if this problem is anything like
what happened to me (I don't have that card anymore either). There
were issues with the G400 because they released an ICD (OpenGL driver)
that didn't support all the GL extensions used by Q3, so it used
software emulation to make them work. Later driver revisions fixed
it.
What I suggest you do is go to Q3's system (graphics) options page
and set Extensions Off. If that fixes it, you'll know that's the
answer. No matter what, if it's a graphics problem you have one real
course of action - update your video drivers, or try some alternative.
Other things to do are to make sure you have the latest DirectX (it
could be something to do with DirectDraw), all the operating system
updates you can get, and ensure that Q3 is actually using the driver
you thought it was... you can put the driver into the Q3 dir (or was
it \baseq3\ ?? Not sure... try both). I find that my Voodoo3's newest
drivers don't work with certain software, so I have the newest installed
as normal for windows, but games and SW that don't work with it, I
put an older version that works in that program's directory. This
is the only way I can run 3dStudio Max 2.5 and get GL, more impor-
tantly I need to do this with Q3Radiant as the newer drivers don't
work right. So you might need new (or older!) drivers.
If you have a Voodoo card you could try wickedGL... if you already
are, try the 3dfx drivers. For other cards, try reference drivers;
if you're using those already, try card-specific driver releases.
It might be worth using GLsetup if you're not sure if you are using
up-to-date video drivers. See if your card's website lists any known
bugs, and check the Q3 doc's and readme's for card-specific bugs.
As always, check that ALL your drivers are up to date. And of course,
sometimes newer isn't always better. If you have a VIA chipset, DO
get the latest 4-in-1 driver (but install each of the 4 parts ONE AT
A TIME!!! and then TEST TEST TEST with all your games and stuff before
you add the next part, and remove it if it causes problems.) That,
and probably sound card drivers.
You didn't mention what your system is: what is your operating system,
CPU, motherboard, m/b chipset, graphics card, sound card, any other
stuff? Go into BIOS - is everything set correctly there? You haven't
overclocked anything? If so try reversing that. Long shot but worth
a try. Look at cache and RAM timings (not too aggressive), AGP arpeture,
(I *think* this is supposed to be about 1/2 your total RAM), and try
to only change one thing at a time then test, or you might screw some-
thing else up and not know what it was. Or, you might fix it but not
know how, which is slightly better than not fixing it but doesn't
tell you what in your system causes such problems next time. And
there will be a next time!
The main hint is that it only happens on that map... it sounds like
it must be something that only happens on Q3DM16, so I'd guess a
shader or something that requires a GL extension like I said, and
that GL ext. has a problem, so hopefully new GFX drivers will fix
it. Let us know how you go!
--
To email, replace spamblock with net in the address on this post.