Galciv Lockup

May 1, 2003 4:53 PM from

This issue happend to me weeks ago with a different Galciv version,
now it has shown up again with version 1.03A:

When I start Galciv the screen goes blank and instead of showing the introduction
movie nothing happens. I can switch to other apps using Alt-Tab and some of them
can be closed by Alt-F4 but the screen stays blank so I cannot really see what I'm
doing. I can do Ctrl-Alt-Del but selecting the Taskmanager in order to kill Galciv
does not help me either. It probably comes up but I can't see it because the screen stays
all black.
This is really bad because I have no other just but to press the reset button. Not good!
(I am using Windows 2000 SP3)

The debug file reads like this:
Debug Message: ******* Starting Game Shell *******
Debug Message: Going Fullscreen
Debug Message: Preparing to change display settings.
Debug Message: Set cooperative level failed.
Debug Message: Canvas Initialization failed.
Debug Message: Now Fullscreen
Debug Message: Shell initialization complete
Debug Message: Main Shell terminating normally
Debug Message: Unallocated Mem: 1024 bytes of memory from line 188 of G:\PROJECTS\pear\SOURCE\PALETTE.CPP
Debug Message: Not all memory has been freed from memory system Palette.
Debug Message: 1024 bytes of memory still allocated.
Debug Message: Unallocated Mem: 299 bytes of memory from line 149 of G:\PROJECTS\pear\SOURCE\LIBRARY.CPP
Debug Message: Unallocated Mem: 299 bytes of memory from line 149 of G:\PROJECTS\pear\SOURCE\LIBRARY.CPP
Debug Message: Not all memory has been freed from memory system Library.
Debug Message: 598 bytes of memory still allocated.
Debug Message: Unallocated Mem: 206 bytes of memory from line 561 of G:\PROJECTS\pear\SOURCE\SPRMAN.CPP
Debug Message: Unallocated Mem: 200 bytes of memory from line 548 of G:\PROJECTS\pear\SOURCE\SPRMAN.CPP
Debug Message: Unallocated Mem: 512 bytes of memory from line 320 of G:\PROJECTS\pear\SOURCE\SPRMAN.CPP
Debug Message: Unallocated Mem: 2048 bytes of memory from line 319 of G:\PROJECTS\pear\SOURCE\SPRMAN.CPP
Debug Message: Unallocated Mem: 1024 bytes of memory from line 318 of G:\PROJECTS\pear\SOURCE\SPRMAN.CPP
Debug Message: Unallocated Mem: 1024 bytes of memory from line 317 of G:\PROJECTS\pear\SOURCE\SPRMAN.CPP
Debug Message: Unallocated Mem: 1024 bytes of memory from line 316 of G:\PROJECTS\pear\SOURCE\SPRMAN.CPP
Debug Message: Unallocated Mem: 1024 bytes of memory from line 315 of G:\PROJECTS\pear\SOURCE\SPRMAN.CPP
Debug Message: Unallocated Mem: 1024 bytes of memory from line 314 of G:\PROJECTS\pear\SOURCE\SPRMAN.CPP
Debug Message: Unallocated Mem: 1024 bytes of memory from line 313 of G:\PROJECTS\pear\SOURCE\SPRMAN.CPP
Debug Message: Unallocated Mem: 5120 bytes of memory from line 188 of G:\PROJECTS\pear\SOURCE\DATAMAN.CPP
Debug Message: Unallocated Mem: 1024 bytes of memory from line 187 of G:\PROJECTS\pear\SOURCE\DATAMAN.CPP
Debug Message: Unallocated Mem: 1024 bytes of memory from line 186 of G:\PROJECTS\pear\SOURCE\DATAMAN.CPP
Debug Message: Unallocated Mem: 1024 bytes of memory from line 185 of G:\PROJECTS\pear\SOURCE\DATAMAN.CPP
Debug Message: Unallocated Mem: 256 bytes of memory from line 184 of G:\PROJECTS\pear\SOURCE\DATAMAN.CPP
Debug Message: Unallocated Mem: 512 bytes of memory from line 183 of G:\PROJECTS\pear\SOURCE\DATAMAN.CPP
Debug Message: Unallocated Mem: 256 bytes of memory from line 182 of G:\PROJECTS\pear\SOURCE\DATAMAN.CPP
Debug Message: Unallocated Mem: 5120 bytes of memory from line 181 of G:\PROJECTS\pear\SOURCE\DATAMAN.CPP
Debug Message: Not all memory has been freed from memory system DataMan.
Debug Message: 23446 bytes of memory still allocated.
Debug Message: MemMan: Unable to find pointer in GetBlockInfo. Memory system: Palette
ASSERT ERROR in file G:\PROJECTS\pear\SOURCE\MEMMAN.CPP at line 579.
Debug Message: MemMan: Trying to free memory that has not been allocated. Memory System Palette
ASSERT ERROR in file G:\PROJECTS\pear\SOURCE\MEMMAN.CPP at line 361.
Debug Message: MemMan: Unable to find pointer in GetBlockInfo. Memory system: Palette
ASSERT ERROR in file G:\PROJECTS\pear\SOURCE\MEMMAN.CPP at line 579.
Debug Message: MemMan: Trying to free memory that has not been allocated. Memory System Palette
ASSERT ERROR in file G:\PROJECTS\pear\SOURCE\MEMMAN.CPP at line 361.

I have Smartexception installed but that does not help with this issue because the
game does not crash. I would prefer if it would though...
Please consider to quit the process if the game fails like this during startup.

Markus
(about to start the game again and risk thrashing my system)

~SDC~

242 views 7 replies

Reply #1 May 1, 2003 6:23 PM from

Stardock Forums Top

I've had the same problem recently. I found that hitting ctrl-alt-del will repeatedly will bring up the task manager (eventually) and you can then alt-tab to get mouse access. Then you can shut down galciv. Only thing is then it does the same thing after that. A reboot is needed and it works again. I'm using XP Pro.

Have you been using your PC a lot before attempting to run GalCiv (like internet browsing for a few hours beforehand)? Looking at the file it looks like something else is hogging all the system resources, possibly another program that hasn't shut down properly? I had the problem the other night, and thinking about it, had used the PC for an hour before hand.

~SDC~

Reply #2 May 1, 2003 8:42 PM from

Stardock Forums Top

Hi Starvald,

the PC was up for quite some time. I used it to surf the internet and for several sessions of Galciv before it locked up.

~SDC~

Reply #3 May 1, 2003 9:52 PM from

Stardock Forums Top

You're definitely having video problems there. If you start immediately after rebooting your computer, can you run Gal Civ?

Did you recently upgrade your drivers? What version DX do you have?

Reply #4 May 2, 2003 2:19 AM from

Stardock Forums Top

I have DirectX 8.1a. My hardware does not even support most of DirectX 8 features
so I thought it wouldn't help much to upgrade.

Of course I can run GalCiv after rebooting, I just prefer not having to reboot
before I play.

I upgraded the graphics card drivers (Detonator v41.09 on a GeForce 2MX) but
that was before I first installed GalCiv.
I had this happend twice since the release of the game so it does not
occurs very often. As Starvald suggest it might be related to long uptimes.

~SDC~

Reply #5 May 2, 2003 11:07 AM from

Stardock Forums Top

Current detonator drivors are 42.35 or something like that. Anyways, there's a newer set after 41.09, which I'm running along with DX9.

The long uptime's what I've attributed my problems to. I wonder if you only log off and log back in (rather than a complete reboot) would satisfy it?

Actually, I've been having random lockups on bootup recently too, which might be a CursorXP problem. Or what's attempting to load just after it. Got to play about a bit before I know for certain though.

Glad I could be of (some) service!

Reply #6 May 2, 2003 11:53 AM from

Stardock Forums Top

Since you have the same problem with DX9 and newer drivers
I don't see any reason to upgrade.
I'm thinking about getting a new Radeon card (not for Galciv but to be able to play other current games). I guess that will lead to other problems. The GeForce is slow nowadays but I never had stability issues with it...

Reply #7 May 2, 2003 7:43 PM from

Stardock Forums Top

Well, upgrading to DX 9.0a probably wouldn't hurt. But at least you don't have just 9, which appears to have had problems...

Welcome Guest! Please take the time to register with us.

Richer content, access to many features that are disabled for guests like commenting and posting on the forums.
Access to a great community, with a massive database of many, many areas of interest.
Access to contests & subscription offers like exclusive emails.
It's simple, and FREE!