So many crashed i dont know where to start


#1

My game crashed when i take challenges, in the middle of fights, when i load fleets, when i edit. Not all the time, but enough so that i never use the quit button, i just wait till an inevitable crash.

What do i need to post?I know there is a patch out soon, but it doesnt seem to adress some of the other bugs.

Also, got an awesome all white map today. Hurt my eyes. I took some screenshots, couldnt get the loadout screen (The game crashed)

I havent met a game this crashtastic since boiling point or medevial total war.

Its on the strength of the game that i continue to play, though its getting more and more frustrating.


#2

Hi, this sounds more like system instability than the game, otherwise I’d be getting lots of reports of this. Have you checked the games errors.txt file in \program files\gratuitous space battles\debugdata?

There is a patch coming tomorrow for one known crash, but it sounds like you have more general issues. Is your video card maybe overclocked or not seated correctly? Have you checked your PC for viruses and spyware? and defragged it (yes really). Also make sure you have the newest video card drivers for your machine.


#3

My card is overclocked, but it has been so for years, with minimal problems. I scan regularly for spyware and virii. I atempt to defrag one a month (Computer doesnt need to). It may be a driver issue, but i am unable to get newer drivers for my alienware made nvidia card. Its a real pain. Here is a little snippit from the end of my error file:

14/12/2009 - 16::18 - D3DEngine Restore Failed
14/12/2009 - 16::18 - D3DERR_INVALIDCALL
14/12/2009 - 16::18 - D3DEngine Restore Failed
14/12/2009 - 16::18 - D3DERR_INVALIDCALL
14/12/2009 - 16::18 - D3DEngine Restore Failed
14/12/2009 - 16::18 - D3DERR_INVALIDCALL
14/12/2009 - 16::18 - Begin Scene
14/12/2009 - 16::18 - D3DERR_NOTAVAILABLE
14/12/2009 - 16::18 - Error creating texture:[$s]
14/12/2009 - 16::18 - D3DERR_NOTAVAILABLE
14/12/2009 - 16::18 - Error creating texture:[$s]
14/12/2009 - 16::18 - D3DERR_NOTAVAILABLE
14/12/2009 - 16::18 - Error creating texture:[$s]
14/12/2009 - 16::18 - D3DERR_NOTAVAILABLE
14/12/2009 - 16::18 - Error creating texture:[$s]
16/12/2009 - 18::9 - Assertion failure:filename:…\src\GUI_TitleBar.cpp,linenum:25,build:Full 1.27
16/12/2009 - 19::52 - Assertion failure:filename:…\src\GUI_TitleBar.cpp,linenum:25,build:Full 1.27
17/12/2009 - 13::24 - Assertion failure:filename:…\src\GUI_TitleBar.cpp,linenum:25,build:Full 1.27
17/12/2009 - 13::30 - Assertion failure:filename:…\src\GUI_TitleBar.cpp,linenum:25,build:Full 1.27
17/12/2009 - 15::2 - Untranslated HRESULT
17/12/2009 - 15::2 - Error creating texture:[$s]
17/12/2009 - 15::3 - Untranslated HRESULT
17/12/2009 - 15::3 - D3DXCreateEffectFromFile failed
17/12/2009 - 15::3 - Untranslated HRESULT
17/12/2009 - 15::3 - D3DXCreateEffectFromFile failed
17/12/2009 - 15::3 - Untranslated HRESULT
17/12/2009 - 15::3 - Error saving screenshot
17/12/2009 - 15::3 - Untranslated HRESULT
17/12/2009 - 15::3 - Error saving screenshot


#4

Overclocked cards mean all bets are off.
WHY overclock a video card? You are possibly damaging it permanently, and the chances of running all games at a stable level just nosedive. You are the only user experincing mass random crashes, and the only user with an overclocked card, so I’m pretty much assuming this is hardware. None of those errors are showing up in anyone else’s logs.
Seriously, don’t overclock a video card. It’s not worth it.


#5

Cause it came with the laptop and i dont have the know how to revert it. Thanks for the info though.


#6

A sample of the current errors I’m getting.

19/12/2009 - 4::24 - D3DEngine Restore Failed
19/12/2009 - 4::24 - D3DERR_INVALIDCALL
19/12/2009 - 4::24 - D3DEngine Restore Failed
19/12/2009 - 4::24 - D3DERR_INVALIDCALL
19/12/2009 - 4::24 - D3DEngine Restore Failed
19/12/2009 - 4::24 - D3DERR_INVALIDCALL
19/12/2009 - 4::24 - D3DEngine Restore Failed
19/12/2009 - 4::24 - D3DERR_INVALIDCALL
19/12/2009 - 4::24 - D3DEngine Restore Failed
19/12/2009 - 4::24 - D3DERR_INVALIDCALL
19/12/2009 - 4::24 - D3DEngine Restore Failed
19/12/2009 - 4::24 - D3DERR_INVALIDCALL
19/12/2009 - 4::24 - D3DEngine Restore Failed
19/12/2009 - 4::24 - D3DERR_INVALIDCALL
19/12/2009 - 4::24 - D3DEngine Restore Failed
19/12/2009 - 4::26 - Assertion failure:filename:…\src\GUI_TitleBar.cpp,linenum:25,build:Full 1.28
19/12/2009 - 4::29 - Assertion failure:filename:…\src\GUI_TitleBar.cpp,linenum:25,build:Full 1.28
19/12/2009 - 4::54 - Assertion failure:filename:…\src\GUI_TitleBar.cpp,linenum:25,build:Full 1.28

So far though 1.28 seems more stable then 1.27


#7

Thunder, when does the game crash for you? I thought I’d fixed that titlebar stuff in 1.28.


#8

When switching races most often.