KSP randomly closing without message

[jaguarac1]

List of my mods:

Output log: https://www.dropbox.com/s/l9agyvueyf0djvo/output_log.txt?dl=0

KSP Version:1.0.5 64-bit

Randomly closing when building ship, launching ship, etc. ksp closes without a message. I'd really like help please

[Tex_NL]

You say you use KSP 1.0.5 64bit? Sorry but there is no 64bit KSP in under windows. (Except for the unstable, unsupported hacked version.)

Let me guess, KSP crashed on a scene change. I quickly went over your output log and confirmed my first suspicion: You're out of memory.

Loose some mods, wait for the 64bits unity5 KSP 1.1 or bare with it. Not much else you can do about it.

 

Edited February 17, 2016 by Tex_NL

[jaguarac1]

Oh I thought it is a 64-bit game. Thanks for the advice

[Padishar]

The addresses in the call stack at the end of your log are only 32 bit and, as Tex_NL said, KSP is running out of virtual address space and failing to allocate memory.  There are various things that you can do to reduce the memory usage, use OpenGL mode, reduce the texture resolution setting, remove or trim down some of the heavier mods (large part packs and beautification mods mainly) etc.

However, there are also various other errors in your log that would appear to imply that some of your mods are either not compatible with KSP 1.0.5 or are clashing with other mods, and these should probably be investigated further.  First, EVE is causing a nasty exception quite early on which appears to stop it initialising correctly as it goes on to cause lots of other exceptions later.  Second, something is causing a "MissingMethodException: Method not found: 'FlightGlobals.getAtmDensity'." a number of times in the log which probably indicates a plugin mod compiled for a previous version of KSP.  During the entry into the flight scene the game fails to allocate memory for a 1920x1080 texture but this isn't immediately fatal.  RasterPropMonitor then gives a few odd looking errors and then starts spamming a couple of exceptions on every frame.  These may be caused by the lack of free memory or may be something else.  It appears that you then launched (I would have expected your frame rate to be terrible with the amount of log spam happening) and activated a further stage before something in the bowels of Unity tried to allocate an approx. 4 meg chunk of memory and when this failed it didn't handle it gracefully and caused an access violation that killed the program.

As a first step I would suggest removing EVE (EnvironmentalVisualEnhancements) as it doesn't appear to be working correctly and this should also reduce your memory usage considerably.  Then look at whether RPM starts working correctly and remove it (and/or check for an update) if not.  Then check all of your other mods that include .dll files to make sure you are using a version built for KSP 1.0.5.  Once you get it running stable without unexpected errors in the log then you can see about reinstalling EVE though you will probably have to do something else to reduce the memory usage.