KSP Shuts off Mid-load while loading files from 'Squad' folder

[ncore]

Hello, I haven't played KSP in forever. I installed it nice and new and decided to add some mods included but not limited to Mechjeb, KSI, Interstellar, Infernal Robotics, B9 rocketry, KAS, shuttle orbiter, etc..

There were a couple downloads that required 'Firespitter' to be replaced 3 or so times due to it being in a lot of the mods/plugins/parts I downloaded. All of my downloads were moved to the Gamedata folder, which I would assume they would go because the download files would have everything in a Gamedata folder.

Anyway, I started KSP up for the first time after installing all these nice things and the game randomly closed halfway through the loading screen with no error messages. Upon inspection and squinting eyes it appeared as though the game crashed while loading files from "landerCabinInternals" from gamedata\squad. I simply removed the folder and put it onto my desktop for safekeeping.

I started KSP once again and this time it seems like it stopped while loading something from "GenericSpace1" from gamedata\squad.

This is getting disappointing real fast. Can somebody help me solve this issue? Thanks!

[Berlioz]

I think it's because there's too many mods causing a memory problem. You will most likely have to remove some of your mods to get it to work.

and also, it seems like it's required that you post in this format otherwise people may refuse to help you. Not saying I wouldn't, but it makes it easier for others.

example format from sticky:

KSP: 0.23 Windows 32bit

Problem: Deadly Reentry destroys my RAPIER in closed-cycle mode

Mods installed:

Deadly Reentry Continued v4.1

Module Manager 1.5.0

Reproduction steps:

Build a simple craft with a Mk1 pod, a long tank, two radial intakes, and a RAPIER. Take off, switch to closed-cycle mode. Watch engine overheat and explode.

Log:

<link>Output_log.txt

[Master Tao]

It's been well documented on the forums that RAM usage past the usual 32-bit limit also crashes Windows 64-bit KSP. While technically it's not the number of mods, the underlying message is sound and may be the problem for ncore. It's a common problem because everyone expected that 64-bit KSP would resolve the RAM usage issues, but it clearly did not.

You don't need to follow the exact format in the How to Get Support (READ FIRST) sticky, but it does help. It is nearly impossible to resolve issues without all the information requested.

[MisterFister]

Not only that, crash-on-load issues with "no error message" often generates a new folder in the KSP directory, a folder named by a time/date stamp. I suggest deleting those, re-attempting KSP, and then checking after it crashes. If a new one appears, this lends strength to a RAM-issue theory.

You mention KSPI and B9, both part-heavy mods. Part textures are the single greatest RAM-burden during load. During runtime, part textures continue to weigh the system down, but plugins can have somewhat erratic memory consumption.

It should be noted that the B9 release page itself describes ATM (Active Texture Management) as "practically required," just by itself. There are two preconfigured versions, a basic and an aggressive. Download the aggressive, install it with preconfigured settings, and see how that works. If you do manage to get to the title screen, alt-tab out to Task Manager and see how much memory the ksp.exe process is using. If it's anywhere above 3GB (which is likely, depending on the exact extent of your mod list) then know that no matter what you do, you'll always be crash-prone. Consider removing mods, or at least pruning duplicate parts from certain mods.