Possible workaround to ksp _x64 exe crashing in win 1.1.2, Antivirus software culprit?

[Hrv123]

Had rather frequent ksp _x64 exe stop working in VAB, launch pad and first stage firing, atlast once per 2 hours of playing.

FPS is good no problem there, PC hardware is cooled higher over standard, no any software instability from installed programs. OS and KPS installed on SSD. 8gb of ram. 

After reading some mentions of possible windows related .dll files messing/been messed wih ksp making it to stop working, I turned off AVG and shut down CC I have always working in background.  

Playing ksp for ~+4h now no more any ksp exe stop working, I could swear there are now some white glitches and mouse shape turns back into windows one for sec or two when I would expect game crash to then load VAb or launch pad propperly.    Maybe Im to subjective but my bet is there is issue with AVG and KSP, it is difficult to say on couple hours of no exe crashing game in a row.   Try turning off CC and AVG while you play KSPO, maybe it will help.     

o7 and safe landing on Kerbin!

[Guest]

I don't run anti-virus on my pc. KSP still has the occasional random crash to desktop. I don't think this is the cause. Although, anti-virus's have been known to cause conflicts with KSP in the past. I'm pretty sure the problems are related to poor memory management in Unity 5, at least from what I've read. Not really anything we can do about it right now, except grin and bear it.

[Alshain]

There is still a crash issue in the VAB/SPH when moving parts around.  Though when I was playing it, the game seemed to crash a lot less in 1.1.2

[samstarman5]

I've only experienced crashes when staging.

It should be stated that .dll files are NOT causing those crashes, and most are essential to your OS operating. The error-checking is its own entity and not the greatest in the world, most likely to only go so far to find the culprit.  Think of it as a lazy and corrupt cop who is just as happy to arrest an innocent citizen just because they were in the neighborhood of a suspected drug dealer.

Making sure your drivers are up to date is a big help, as well as not running anything in the background that is not essential to your current gameplay.  CCleaner is a big help to getting useless junk out of the way that can also contribute to issues. However, run it manually and do not leave it running in the background, as it, too, can contribute to issues. It's not Norton Anti-virus bad but it is a bit of a memory hog. You can also use it to see if anything's getting loaded at startup that shouldn't be.  Never know when something you installed decided it needed to be run at start without your say-so. Or that something even installed without your say-so.  Browser toolbars, for one. Get rid of those.

That's pretty much the extent that I can think of to help prevent problems.  If these help, then at least it can help you enjoy your KSP experience until we get something more stable. Hate to say it, but stuff like this is to be expected with the upgrade to 64-bit. It's going to be like working with a wider brush that is likely to pick up more pests along the way.  Stay patient, friends.

[G'th]

My personal experience has been that I initially suffered from the same sort of crashes others have reported, VAB crashes, staging crashes, and other random CTD's near constantly.

 

Then suddenly the game just started working longer and longer and longer, and now I only crash with the moving parts in the VAB (as Alshain hinted at). Essentially, so long as I'm careful about how I work in the VAB I don't crash.

[ShadowZone]

I am not running any Antivirus Software, but I am getting regular crashes, especially when reverting to VAB/SPH.

Stability has to be fixed going forward with KSP 1.1

[BrutalRIP]

14 hours ago, Alshain said:

 

There is still a crash issue in the VAB/SPH when moving parts around

 

This is the only crash that ive had 

[Curveball Anders]

5 minutes ago, ShadowZone said:

I am not running any Antivirus Software, but I am getting regular crashes, especially when reverting to VAB/SPH.

I've noticed that sounds often lingers on a bit when reverting to VAB.

And since sound is handled by it's own thread I wonder if a de-synch there can be one source of the crashes some people suffer from.

But hard to pin down without a debug build :/

 

[LordFerret]

4 hours ago, Curveball Anders said:

I've noticed that sounds often lingers on a bit when reverting to VAB.

And since sound is handled by it's own thread I wonder if a de-synch there can be one source of the crashes some people suffer from.

But hard to pin down without a debug build :/

 

One of the things I noticed when my crashes occurred in the VAB (at least 3 or 4 I clearly recall), was that the mouse click noise (clicking on a part) was 'different' ... like, shortened. Dropping the part to discard it then resulted in a crash.