Random Crashes in Vista

Hola,

Anyone else have random crashes in Dark Avatar about every 20 minutes or so? I'm running Vista on a laptop with T7400 Dual Core processors and a GeForce 7400 Go video card. 2 gigs of ram and the latest drivers for all.

thanx
3,886 views 8 replies
Reply #1 Top
Please go to C:\Program Files\Stardock\Totalgaming\GalCiv2 (or wherever you installed the game at), open the debug.err file you find there in notepad, and copy/paste the contents into a post here. If this is a DA report, you'll find the debug in C:\Program Files\Stardock\Totalgaming\GalCiv2\DarkAvatar instead. This will give us some technical information that can help troubleshoot your problem.

Be sure to copy the debug immediately after the error occurs; if you start the game again, the debug will be erased and recreated for the new session.
Reply #2 Top
Hmmm, I've tried to find a debug.err in the galciv2/darkavatar directory but no luck. Is it saved somewhere special in the DarkAvatar directory???
Reply #3 Top
I havent had a crash in Vista yet. Just tons of lag.
Reply #4 Top
Hmmm, I've tried to find a debug.err in the galciv2/darkavatar directory but no luck. Is it saved somewhere special in the DarkAvatar directory???


It should be right there. If you run the game under a limited account it may not be able to write it, though. If that's the case, try running the game under an admin account.
Reply #5 Top
I am running an admin account and whenever the game crashes to the desktop (which is everytime I try and play) I check to see if a debug.err message was generated and sure enough it hasn't. Don't know what to tell you guys but I wish I could troubleshoot this problem since it seems like a lot of folks are experiencing the same thing. The same problem happens in both Dark Avatar and Dread Lords, it just randomly crashes to the desktop. I have the latest drivers and am running Vista 32-bit. I'm using a midsize map with common planets. Is there some sort of beta coming out to fix this problem or do I need to talk with the customer service folks and get my money back???

Sorry to be salty but i've just about had it.
Reply #6 Top
Last resort, to at least see exactly what drivers you have, try running dxdiag via the search field at the bottom of the start menu. Dxdiag should be able to tell you the exact version number and date of your current video drivers, which you can then report here.
Reply #7 Top
Here it is:

Windows Vistaâ„¢ Home Premium (6.0, Build 6000) (6000.vista_rtm.061101-2205)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: MXC062
BIOS: Phoenix ROM BIOS PLUS Version 1.10 A07
Processor: Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz (2 CPUs), ~2.2GHz
Memory: 2046MB RAM
Page File: 1365MB used, 2945MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 10
DX Setup Parameters: Not found
DxDiag Version: 6.00.6000.16386 32bit Unicode
Card name: NVIDIA GeForce Go 7400
Manufacturer: NVIDIA
Chip type: GeForce Go 7400
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_01D8&SUBSYS_01D71028&REV_A1
Display Memory: 330 MB
Dedicated Memory: 58 MB
Shared Memory: 271 MB
Current Mode: 1280 x 800 (32 bit) (60Hz)
Monitor: Generic PnP Monitor
Driver Name: nvd3dum.dll
Driver Version: 7.15.0010.9746 (English)
DDI Version: 9Ex
Driver Attributes: Final Retail
Driver Date/Size: 12/13/2006 19:16:38, 3055616 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71E3E-4298-11CF-8A55-DD2101C2CA35}
Vendor ID: 0x10DE
Device ID: 0x01D8
SubSys ID: 0x01D71028
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_B ModeVC1_A ModeWMV9_B ModeWMV9_A


I hope this helps. I tried running dread lords and the same problem of dumping to windows or freezing up happened in both versions
Reply #8 Top
Yep, you're still running with nVidia's Vista release drivers.

Since nVidia has not released proper Vista drivers on their own for Go chipsets, you can get modfied versions of the standard drivers from laptopvideo2go.com that should fix you right up. The 158.18 driver on this page should do the trick.