Crashing modded KSP

[party214]

My game is crashing every half-hour or so. I haven't figured out anything in particular that is causing the crashes. A dropbox folder with some of the crash folders is linked below. I would suspect the crashes are caused by running out of RAM but I'm not sure so I figured I would upload the logs just in case

https://www.dropbox.com/sh/ksb52o4q33josmd/AAA_wgjvZjFUexRr-mQokXDLa?dl=0

[NathanKell]

Welcome to the forums!

It is indeed out-of-memory crashing. You're going to need to remove some mods with lots of parts, and/or use Active Texture Management (once it's solidly working on .25).

[Romuless]

Nathan is this probably causing most crashes since .25? I actually don't even have B9 installed and before I was never crashing and now I CTD in the VAB literally every 10 minutes. I don't really know all about posting crash logs but they are all as you guys say the code for a memory crash and I have Never had this particular ctd before. This one being the one where it literally goes to desktop instantly with no messages at all. However a crash file is created each time. Sorry I know you need more info I don't really expect a perfect answer just wondering if it's a known issue generally since the update because ATM isn't working at it's best or something, which still seems strange since I'm talking about 10-15 parts in the VAB with settings extremely low (the same I always use).. And I have some pretty part intensive things going up in the.... let's just say stupid amounts.

[party214]

Thank you Nathan!

[NathanKell]

party214: you're most welcome!

Romuless: Sorry, totally missed your post. As the amount of stock assets increased in .25, it's very possible you were much further under the limit in .24, but are now very close so it's easy to spike above the limit. ATM is indeed working agani, though you should download the latest version. That said, logs are really, really not hard to find and to upload; the sticky tells you exactly where to find it. If you can't upload the log, just start reading from the bottom up, and see if you come across anything regarding memory (if it's an out-of-memory crash, you will).