General Protection Fault after large combat

[Valleymite]

I am receiving a GPF error after large tactical combats.

It reads like this:
SE4 cause a general protection fault error in module NVDisp.drv.

Is anyone else getting this bug?

[Mephisto]

Yep, I encounter it after my carrier battles or when recovering fighters from space.
But I'm still able to save the game, quit it and start where I saved it without further errors.

Philipp

[Taqwus]

NV => nVidia, perchance? Hrm. System specs?

FWIW, I've seen no such issue, in either tactical and strategic combat with more than 30 ships and 200+ fighters involved (the fighter launching is slow in strategic, but that's about it. Oh, and minelayers fleeing while dropping mines, even when this makes absolutely no sense such as when the enemy ships will clearly all be destroyed before any of 'em fires a shot...).

Possibly relevant system specs -

SE4: full, patched
OS: Windows 2K Pro, SP1, misc hotfixes
Video: STB nVidia Riva TNT 16MB (OEM specifically for Dell, methinks)
Detonator 3 drivers (6.18. 6.34, 6.47 break Shogun:TW, unfortunately.)
DX: DirectX 7
Mem: 128MB, plus *plenty* of space for swap, etc
Mobo: SE440BX, so standard AGP etc.
CPU: Pentium II, 450, never OC'd.


------------------
-- The thing that goes bump in the night

[Malfador Machinations]

Can you guys getting the GPF's send us your savegames? It may be specific to your system, but then again, it may just be the right combination of things. Regardless, there may be protections in the code we can put in to solve the problem.

Aaron

[Valleymite]

Here's the savegame file where the error occurs after tactical combat.

I'm running SE4 v. 1.11 on a P3/450 with 128Mb RAM, Windows 98 SE, Hercules 3D Prophet II MX w/ 32 Mb Vid. Memory (yes, this is an NVidia chipset) with the latest driver from Hercules (just downloaded today). The error occurs after tactical combat is completed and you click ok. Oh, the error occurred even before I installed the latest drivers. I thought I might correct the error by installing updated drivers, but no luck.




[This message has been edited by Valleymite (edited 01 December 2000).]