GPF error message, game crashed

[Custmcom]

SE4 caused a general protection fault
in module 3DBT2W9X.DRV at 0001:0000af55.
Registers:
EAX=00000a20 CS=022f EIP=0000af55 EFLGS=00010202
EBX=00000000 SS=224f ESP=d26ec2a2 EBP=0000c2a2
ECX=0a20c400 DS=225f ESI=00029afc FS=0000
EDX=00000024 ES=201f EDI=001d6768 GS=2016
Bytes at CS:EIP:
8b 06 8b 4e 03 83 c6 06 c1 e8 03 c1 e9 03 c1 c8
Stack dump:
0000c6fa 0000701c 00000000 fffffde4 00000024 00000024 00006fbb 00000000 00000000 6fa54e26 00030000 00000000 e43400cc a3bc81e3 1e3fbff7 ffff0008

This message occurred when tactical combat ended and the game was supposed to go back to the regular screene. There were AI fighters still left in tactical combat as well as a carrier and one of my ships. If you want any further details please ask.

[Dracus]

what OS are you using? How much ram do you have? what type of pc are you runing this on?
Computer support is my job, so I may be able to help you when I get this information.

[raynor]

I did a search on '3DBT2W9X' and found a couple of links that suggest this is the driver for the Creative Labs 3DBLaster. So, I'm guessing the GPF was caused by a problem with the video driver. This URL documents the same exact problem encountered when running Microsoft Works:
http://support.microsoft.com/support.../Q246/0/62.ASP

The bottom of the article says:

CAUSE
This behavior can occur if the video adapter installed in your computer is based on the NVidia Riva TNT chip set.

RESOLUTION
To resolve this issue, download and install the latest video driver for your video adapter from the following NVidia Web site:
http://www.nvidia.com/Products.nsf/h...e_drivers.html

Hope this helps you.

[Custmcom]

Hey raynor, thanks alot for the tip. I didn't realize there were new drivers out for my card. It is such an old card (original TNT Version) that I didn't think they would be making new drivers too often. It turns out that new ones were posted just Last month. I got the Creative Labs Version instead of the generic Nvidia ones though. Anyway, thanks alot for the tip.

[Dracus]

Well,
guess I am not needed then.

[Arralen]

...have the Diamond V550 (Riva TNT) with the latest drivers from Diamond, and got this lately (reproducable) when I combat ended;
I started with "tactical" and switched to "resolve combat" after conquering the planet.
I reloaded the autosave and played the combat on "tactical" 'til turn 30, and everything was fine - than tried switching to "auto" again and got the crash after the "combat ended" message again.

SE4 verursachte eine allgemeine Schutzverletzung
in Modul NVDISP.DRV bei 0001:0000b5fa.
Register:
EAX=00001440 CS=02f7 EIP=0000b5fa EFLGS=00010202
EBX=00000000 SS=259f ESP=c108c386 EBP=0000c386
ECX=1440c400 DS=1337 ESI=0003cabc FS=0000
EDX=00000024 ES=1fcf EDI=003e86e8 GS=1fbe
Bytes bei CS:EIP:
8b 06 8b 4e 03 83 c6 06 26 89 07 26 89 4f 04 83
Stapelwerte:
0000c7de 0000774c 00000000 fffffde4 00000024 00000024 000076eb 00000000 00000000 00001356 00000003 00cc0020 058fbdd8 05bf7408 0000001a 00000012

[raynor]

I also have a Diamond Viper V550 in my computer. That makes three of us with really, old video cards. I guess TB gamer's don't need no stinkin' GeForce III, do we?

I've also seen an error message when I perform the actions you described. My workaround is to not do that anymore.

Hopefully, the GeForce II MX will drop to $50=$75 USD when the GeForce III starts showing up in stores, and all three of us can buy better video cards that don't run into these problems.

[Custmcom]

quote:

---

Originally posted by raynor:

Hopefully, the GeForce II MX will drop to $50=$75 USD when the GeForce III starts showing up in stores, and all three of us can buy better video cards that don't run into these problems.

---

Just to let you know, the GeForce2 MX is already under $75. Of course shipping will tack on about $10 though. As soon as I can talk the wife into it I'm going to get a new Motherboard, processor, and video card.

[Trancejeremy]

I get that same error (which I have fighters and use auto-resolve). It's new with the 2 latest patches

I have a TNT2 card.

So it's just a driver problem? It's been a few months since I updated drivers, so I guess I may as well.