Moleculor Moleculor

Severe Instability After Closing

Severe Instability After Closing

After quitting the game by any means (pushing the last button* in the main menu or the Download Updates button) does not actually seem to shut the game -down- on my system.

As in: It's still listed in my processes listing twelve hours later.

Worse, it seems that every time I quit (or possibly every time I End Process the Sins of a Solar Empire.exe process) my system starts to slowly grind to a halt.

Very very bad.

AMD X2 64 4400+
GeForce 7900 GT
2GB RAM
Sound Blaster X-Fi

*I don't remember the exact name of the button (Quit?) but I don't want to turn the game on again just to find out. I had a mild scare the last time I had to turn the machine off because it came crawling to a halt because of Sins with windows complaining about lost registry entries.

(PS While I don't use Steam's overlay in Sins (yet), I've seen some of the complaints about it and one of the responses about it from Stardock. It's a damn shame you guys won't even consider trying to work out whatever bug is causing problems, whether it's yours or theirs. PC gamers want options and compatibility, not forced restrictions. Besides, it's free advertising for your game, seeing someone on a friends list playing Sins.)
15,453 views 36 replies
Reply #26 Top

I also have the exit problem now, but (kudos to all you helpful people) I know that it's happening to alot of people, and not just me. Thanks guys (and sorry for "derailing the thread". I just thought since this was a technical problems thread,......well, it made sense at the time anyways. My apologies.)
Reply #27 Top
i experience the same problem: quit sins and the exe does not close properly and cpu usage jumps up to 100% - even after terminating the exe.

i'm not sure if this is connected to sins or not but i've noticed something I definitely did not see until after installing sins - Impulse.exe.

i've googled it but no "meaningful" results were returned.

Reply #28 Top
We at Stardock are not sure what is the cause of the shutting down and memory not being cleared. Unfortunately, as we are not the Dev's of this game there is not much we can do testing wise.
It is most likely some application, or system file that is not closing correctly.

Try e-mailing IronClad directly at [email protected], and perhaps they will have a solution, or at least be made aware of this issue.

Reply #29 Top

Hi all,

I suggest downloading Process Explorer and using it to track what processes are doing what. This is a freeware app that is very cool. You can save the data too - which will be helpful in finding out what's latching onto the game.

http://fileforum.betanews.com/detail/Process_Explorer/1063606657/1

Just extract it into an empty directory and away you go. :)

Reply #30 Top
I may have found the solution: An old version of FRAPS I had running. I upgraded that, and, at least for now, the problem is no longer there. I upgraded in the middle of a bunch of "lowering my settings to the lowest values" stuff, so that might have changed things too. I've bumped those all back to the top again ('cept my resolution, I really should go do that), and the problem hasn't resurfaced ever since upgrading FRAPS.
Reply #31 Top
I may have found the solution: An old version of FRAPS I had running. I upgraded that, and, at least for now, the problem is no longer there. I upgraded in the middle of a bunch of "lowering my settings to the lowest values" stuff, so that might have changed things too. I've bumped those all back to the top again ('cept my resolution, I really should go do that), and the problem hasn't resurfaced ever since upgrading FRAPS.
End of quote


"i concur."
shutting down fraps fixed this issue for me.
Reply #32 Top
FRAPS - I've just unloaded it (from running) and will see if this works. Did you say you were able to get a newer version of FRAPS to still work with SoaSE without this crash happening?
Reply #34 Top
I have this problem too and I don't use FRAPS. It's not the only problem.
Reply #35 Top
Makes sense, a driver/tool from my videocard provides an overlay display, but only to fullscreen applications, not windowed ones. I guess that's the reason playing in window mode fixed the problem for me. There is also the known issue with steam overlay... i guess anyone having problems should go check all the stuff running in the background for possible interference.
Reply #36 Top
Yeah installing the newest version of FRAPS also solved this issue for me. I haven't tried running the game with Steam running yet so I don't know if that causes problems for me.