Multiple Crashes

Seemingly Random events

I am having a problem with the beta... Im not really sure whats going on with it, I just know that its happened three times, each time crashing to the desktop between turns.

Heres the beginning of the .CRA file the crash generated:


OS version : Windows XP Service Pack 2 - (2600.xpsp_sp2_gdr.050301-1519)
Video card : MSI RADEON XPRESS 200 Series
Sound card : Realtek AC97 Audio
Date : 03/31/06
Application Exception code: C0000005 ACCESS_VIOLATION
Crash Addr: 0056A5A7 01:001695A7 C:\Games\GalCiv2\galciv2.exe

Processor Registers (x86):
EAX:0685F2F8
EBX:07870020
ECX:00000010
EDX:0685F2F8
ESI:0685F218
EDI:00703CFC
CS:EIP:001B:0056A5A7
SS:ESP:0023:0012FAE8 EBP:00000001
DS:0023 ES:0023 FS:003B GS:0000
Flags:00210202


Current Application Call Stack:

Addr Frame Logical addr Module Name
---------------------------------------------
0056A5A7 00000001 0001:001695A7 C:\Games\GalCiv2\galciv2.exe


Debug information for each stardock app follows ....

Debug.err info follows
Debug Message: Version v1.1 BETA-1 last updated on: Fri Mar 24 19:54:46 2006
Debug Message: Could not find a TGN Serial No.
Debug Message: *********DXDiag info follows.*********
System Info
Time: 3/31/2006, 21:07:19
DirectX Version: DirectX 9.0c (4.09.0000.0904)
Machine Name: JOESDESK
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519)
Languages: English (Regional Setting: English)
System Manufacturer: Gateway
System Model: T6522
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: AMD Athlon(tm) 64 Processor 3500+, MMX, 3DNow, ~2.2GHz
Physical Memory: 894MB RAM
Page File: 399MB used, 1766MB available
Windows Dir: C:\WINDOWS


Display Info
Display device 1:
Device Name: \\.\DISPLAY1
Card Name: MSI RADEON XPRESS 200 Series
Manufacturer: ATI Technologies Inc.
Chip Type: ATI RADEON XPRESS 200 Series (0x5954)
DAC Type: Internal DAC(400MHz)
Key Device: Enum\PCI\VEN_1002&DEV_5954&SUBSYS_71411462&REV_00
Display Memory: 128.0 MB
Current Display Mode: 1024 x 768 (32 bit) (60Hz)
Monitor Name: Samsung SyncMaster 700(M)b (CGM7607*)
Monitor Max Resolution: 1280,1024
Driver Name: ati2dvag.dll
Driver Version: 6.14.0010.6601
Driver Date: 2/21/2006 22:46:46
DirectX Acceleration Enabled: Yes



Sound info
Sound device 1:
Description: Realtek AC97 Audio
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1002&DEV_4370&SUBSYS_B0001462&REV_00
Manufacturer ID: 1
Product ID: 100
Driver Name: ALCXWDM.SYS
Provider: Realtek Semiconductor Corp.
Driver Version: 5.10.0000.5760
Driver Date: 12/1/2004 23:40:08
Type: WDM
Other Drivers:
Acceleration Level: 3
Cap Flags: 0
Min/Max Sample Rate: 0, 0



and heres the end of the file where the crash occured:
Debug Message: Destroying ship 9-Heavy Fighter M4-1X 4. Orbiting: 0
Debug Message: Random Event: Begin
Debug Message: Random Event: Checking for Rebels
Debug Message: Random Event: End
Debug Message: Destroying ship Escort M4-2 814. Orbiting: 1
Debug Message: Was Orbiting: Iversonia II
Debug Message: Destroying ship Heavy Fighter M4-1 781. Orbiting: 0
Debug Message: Destroying ship Iconian Fleet 58. Orbiting: 0
Debug Message: Destroying ship Iconian Fleet 59. Orbiting: 0
Debug Message: Destroying ship Defender M4-1 770. Orbiting: 1
Debug Message: Was Orbiting: Wisp
Debug Message: Random Event: Begin
Debug Message: Random Event: Checking for Rebels
Debug Message: Random Event: End
Debug Message: Altarian Republic (2): Researching: Alliances
Debug Message: Updating ZOC.
Debug Message: Destroying ship Troop Transport M3-12 817. Orbiting: 0
Debug Message: Destroying ship Drath Fleet 47. Orbiting: 0
Debug Message: Destroying ship Constructor M3-12 822. Orbiting: 0
Debug Message: A* Path too long to calculate (21.000000). Aborting

Don't know if this is all the information the folks over at stardock need.

If this bug has already been reported or something my apologies!
4,691 views 2 replies
Reply #1 Top
"Debug Message: A* Path too long to calculate (21.). Aborting"

I've seen numerous posts with people crashing and that as the last line of text from their debug. I think I saw Brad respond to one or two of them so I'm sure it's being addressed. If it is making the game unplayable you can always revert to 1.0X, or if you want to, patch in the Beta 2.


EDIT: Just found this on the v1.1 Beta 2 journal entry. Advise you to patch in the new beta

"+ Fixed crash when trade ship arrives at a planet and the trade routeaborts because it is too long"
Reply #2 Top
That's my personal crash bug that I introduced to Stardock a couple weeks ago.

I call it the 'Knightsaber Trade Bug'.

(lobbies to have that put in patch notes)