Frequent Game Crashing in the VAB

[MrOnyx]

So I have been experiencing numerous crashes over the past few days (I even had two today). These crashes have only occurred while building in the VAB and when I am able to finally finish building and launch it, the game doesn't crash anymore. Has anyone else been having crashes similar to mine and any idea on how to fix them?

[GunsForBucks]

Verify your game files in the library.
right click on game - properties - local files - verify integrity

Running any mods?

[MrOnyx]

Originally posted by GunsForBucks:

Running any mods?

The major mods are HyperEdit, Kerbal engineer, and SCANsat. The rest of the mods are just parts packs.

[SkiRich]

Originally posted by REFAdenak:

Originally posted by GunsForBucks:

Running any mods?

The major mods are HyperEdit, Kerbal engineer, and SCANsat. The rest of the mods are just parts packs.

Those mods are pretty lightweight in the VAB. I would bet you are crashing due to lack of memory. Parts mods all load into the games core memory. The more parts or the more intricate the textures of the parts the more memory you need. Check that and then report back.

I also had some really good experience with upping the Garbage Collection memory. I would get weird stalling in the VAB before. I have 110 mods loaded, lots of parts, lots of heavy game changing mods as well.

This helped me, YMMV ... https://forum.kerbalspaceprogram.com/index.php?/topic/186521-19x-heappadder-pads-the-heap-to-minimize-the-garbage-collection/

[MrOnyx]

Originally posted by SkiRich:

Those mods are pretty lightweight in the VAB. I would bet you are crashing due to lack of memory. Parts mods all load into the games core memory. The more parts or the more intricate the textures of the parts the more memory you need. Check that and then report back.

I also had some really good experience with upping the Garbage Collection memory. I would get weird stalling in the VAB before. I have 110 mods loaded, lots of parts, lots of heavy game changing mods as well.

This helped me, YMMV ... https://forum.kerbalspaceprogram.com/index.php?/topic/186521-19x-heappadder-pads-the-heap-to-minimize-the-garbage-collection/

I don't think memory is the problem for me (I have 16 GB of RAM). Also, I did verify my game files like GunsForBucks suggested, and it did find 3 files that failed. I am going to boot up the game and build something.

[GunsForBucks]

Good luck!

[MrOnyx]

So, crashes are still happening. I have verified the game files several times and one file still appears to be failing. I also thought that the crashing might be a result of outdated nividia drivers. I installed the most recent update, and even with that, the game still crashes.

this is my mod list:
https://imgur.com/a/X0hqT5s

could there be a conflict that is causing the crashes?

[SkiRich]

Originally posted by REFAdenak:

I don't think memory is the problem for me (I have 16 GB of RAM). Also, I did verify my game files like GunsForBucks suggested, and it did find 3 files that failed. I am going to boot up the game and build something.

16 Gb of Ram is lightweight.
By the time the O/S and all other programs load, you'll be left with 8Gb or less.
My copy of KSP loads from cold start and uses 18 Gb of ram before I even load a game.
Granted I have 110 mods loaded, but no crashes and memory issues, I have 64Gb.
Having two files fail on verify is normal. It seems like there are some sort of config files that change from stock install during gameplay that are not excluded from the verify list which causes them to always come up as needing re-download.

As I said before, I would bet its ram related, you sound like you are paging to file and the game gets out of sync and crashes.

You can verify all of this, scan the ksp.log for errors, there is also a crash log. Scan your application log in windows, and also watch the Task Manager memory allocations.

Good luck.

[MrOnyx]

Originally posted by SkiRich:

16 Gb of Ram is lightweight.
By the time the O/S and all other programs load, you'll be left with 8Gb or less.
My copy of KSP loads from cold start and uses 18 Gb of ram before I even load a game.
Granted I have 110 mods loaded, but no crashes and memory issues, I have 64Gb.
Having two files fail on verify is normal. It seems like there are some sort of config files that change from stock install during gameplay that are not excluded from the verify list which causes them to always come up as needing re-download.

As I said before, I would bet its ram related, you sound like you are paging to file and the game gets out of sync and crashes.

You can verify all of this, scan the ksp.log for errors, there is also a crash log. Scan your application log in windows, and also watch the Task Manager memory allocations.

Good luck.

I am still hesitant to agree that its a memory related issue, but I could be wrong. On startup, my computer was using 30% of memory, and with KSP running, its at 66%. When it crashes, its at ~70 to 71%. I have run KSP flawlessly in past, and no other game has been crashing like KSP has recently, probably even when other games use more memory than it. Plus, these crashes started happening out of the blue and only while in the VAB; no other place. Its also as if entering and exiting the VAB delays it temporarily I think, but not by much.

Speaking of player logs, I did actually go digging into my drive to find them and two errors keep coming up.

This:

MiniAVC -> System.NullReferenceException: Object reference not set to an instance of an object
  at MiniAVC.AddonInfo.get_IsKspExcludedVersion () [0x00000] in <946c68c810554a77bc35cab54adcb678>:0 
  at MiniAVC.IssueGui.DrawNotCompatible () [0x00030] in <946c68c810554a77bc35cab54adcb678>:0 
  at MiniAVC.IssueGui.Window (System.Int32 id) [0x00006] in <946c68c810554a77bc35cab54adcb678>:0

(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.binding.h Line:35)

And this

Resource ID out of range in GetResource: 1048577 (max is 1048575)
 
(Filename: c:\buildslave\unity\build\runtime\gfxdevice\GfxResourceIDMap.h Line: 109)

The 1048577 goes to 1048673.

Both of there were found in the Player.txt file in username\AppData\LocalLow\Squad\KerbalSpaceProgram and I have no idea if these are worth mentioning.

[SkiRich]

The big clue in all this is you experiencing the crash in the VAB. The physics engine is out of play there, the background threads are just that in the background. You are left with parts related issues and textures. Memory is the issue, even if you have enough.

Just try this, it cant hurt.
https://forum.kerbalspaceprogram.com/index.php?/topic/186521-19x-heappadder-pads-the-heap-to-minimize-the-garbage-collection/

It will extend the allocated memory of your garbage collection process. For me, even with all my memory I would experience stutter in the VAB and that was due to the GC running too often due to low allocation of a resource I had plenty of.
Installed this and its all gone.

[MrOnyx]

Originally posted by SkiRich:

The big clue in all this is you experiencing the crash in the VAB. The physics engine is out of play there, the background threads are just that in the background. You are left with parts related issues and textures. Memory is the issue, even if you have enough.

Just try this, it cant hurt.
https://forum.kerbalspaceprogram.com/index.php?/topic/186521-19x-heappadder-pads-the-heap-to-minimize-the-garbage-collection/

It will extend the allocated memory of your garbage collection process. For me, even with all my memory I would experience stutter in the VAB and that was due to the GC running too often due to low allocation of a resource I had plenty of.
Installed this and its all gone.

So, last night I installed HeapPadder and it appeared to work, unfortuantely, that was short lived. When I booted up the game today and started to build, I eventually encountered another damn crash. However, I think you were correct in your hypothesis that the problem is memory related. I came across this, which describes a very similar problem I am having: https://forum.kerbalspaceprogram.com/index.php?/topic/139124-very-frequent-vab-crashes/
although this is from 2016 and I have no idea if its even useful considering how old it is.

I am really bummed out this is happening. KSP is pretty much unplayable right now.

[SkiRich]

Originally posted by REFAdenak:

Originally posted by SkiRich:

The big clue in all this is you experiencing the crash in the VAB. The physics engine is out of play there, the background threads are just that in the background. You are left with parts related issues and textures. Memory is the issue, even if you have enough.

Just try this, it cant hurt.
https://forum.kerbalspaceprogram.com/index.php?/topic/186521-19x-heappadder-pads-the-heap-to-minimize-the-garbage-collection/

It will extend the allocated memory of your garbage collection process. For me, even with all my memory I would experience stutter in the VAB and that was due to the GC running too often due to low allocation of a resource I had plenty of.
Installed this and its all gone.

So, last night I installed HeapPadder and it appeared to work, unfortuantely, that was short lived. When I booted up the game today and started to build, I eventually encountered another damn crash. However, I think you were correct in your hypothesis that the problem is memory related. I came across this, which describes a very similar problem I am having: https://forum.kerbalspaceprogram.com/index.php?/topic/139124-very-frequent-vab-crashes/
although this is from 2016 and I have no idea if its even useful considering how old it is.

I am really bummed out this is happening. KSP is pretty much unplayable right now.

Read the instructions in heappadder and tweak the settings.
I have 64Gb of ram 46 is available after game load so I upped HeapPadder to 10000.

If that doesnt work, go to your GameData directory and see which parts mod is the largest.
Go in and start deleting some of the really big parts and cfgs or move them away and reload the game, so if its one or two parts with massive textures that your system is just chocking on you may be able to live without a few parts.
An internet product that is free called WINDIRSTAT visualizes the directory sizes so you can see exactly which files are massive.