2.02 broke my game. update and updated again with debug.err after installing amd fix.

from Stardock Forums

Update: adding debug.err 3 post down to ease the reading ( this post has dxdiag ) yes it crashed again.

 

 

I was finaly crash free on the release of 2.0 But I am now cashing as often as I did pre 2.0 days with 2.02. My version is the impulse version so I do not think I have the option to reinstall and just play 2.0 untill 2.03 is/if made. I can reinstall ofcoarse, maybe a clean install is all it needs. But I wanted to verify that this isn't just a common 2.02 issue ( the return of crashes as though you where still playing v1.96 ) The reason to check is because impulse takes forever to dl and install, I would really rather avoid that if the problem is something that needs another patch rather than a reinstall. Thank you.

 

ps:  I can not be more specific on the nature of the crashes, they are totaly random.. just like 1.96. And my system has not changed since I was playing flawlessly on 2.0

 

 Well some of the problem seems ot have been the information in mydocuments. I deleted the twilight folder and let the game make  new one. This helped. But I noticed something when I saved a ship an dthe templates. When you delete a user made ship template, it does not get completely delted and the shipyard gets really unstable after naming a new template the same as the one you just deleted. To resolve this all template deletions has to be done manualy. I did however still get another crash that lead to me uninstalling Twilight and reinstalling it. The last crash may have had something to do with govenors, I will know after a fresh install.

 I hope 2.03 will address this issue. I doubt there is anything wrong with my dxdiag but just for kicks here goes. lol at the smilies that showed up :P

 

[dxdiag clipped by moderator]

6,828 views 6 replies
Reply #1 from Stardock Forums Top

This issue may be the AMD Dual Core processor. There are quite a few people with them that have similar issues.

The AMD update is found here;
 http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_13118,00.html

Go to bottom of page and use the link that reads 'AMD Athlon™ 64 X2 Dual Core Processor Driver for Windows XP and Windows Server 2003 Version (x86 and x64 exe) 1.3.2.0053'

 

Reply #2 from Stardock Forums Top

Quoting highlander, reply 1
This issue may be the AMD Dual Core processor. There are quite a few people with them that have similar issues.

The AMD update is found here;
 http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_13118,00.html

Go to bottom of page and use the link that reads 'AMD Athlon™ 64 X2 Dual Core Processor Driver for Windows XP and Windows Server 2003 Version (x86 and x64 exe) 1.3.2.0053'

 
End of highlander's quote

 

 Interesting. I guess there is more than one AMD fix then. So this is different than the pn132 driver? I installed it no problems. Later on I will be able to test it.

DeskScapes - Bring your desktop background to life.
Reply #4 from Stardock Forums Top

Not sure where the debug.er is listing what caused the crash.  But somethitgn I definantly noticed was the failurs to open regkeys ( saw that a lot ) Should I shut down regmechanic while this is being played?

 Also a lot of failures to open files is listed in the bug report, as well as failures to place planets.  seems a little borked :(

 

 I do have windvd but I shut it down before playing. Do I need to disable it completely while playing this game?

Reply #5 from GalCiv2 Forums Top

[Moved debug off to pastebin for thread readability.]

 

The registry and file finding messages at the beginning are normal. As the different retail region versions of the game use different registry locations, the game has to check all of them.

Do you recall what the random event was that you got right at the end before it ended? There was an issue in the past with the Dread Lords spawn event causing crashes.

Reply #6 from Stardock Forums Top

If it was an event the game crashed before it could display the info. The crash was at the beginning of a turn, just before it was going to release me to start moving ships around.