Startup Crashes at same point every time.

[nin10dorox]

I hadn't played KSP in a few months, and suddenly really wanted to. I went to the website and saw that 0.90.0 BETA was out! I was excited, so I ran the patcher, then when it was done (it took forever) I ran the game. After about 5 minutes of loading the game, the progress bar was about one third of the way through, and it crashed. I tried a few more times, and it kept crashing. I tried restarting my computer, and even deleted the entire KSP folder and re-downloading it three times, but it keeps happening.

Every single time, it is on the exact same part of loading, which is Squad/Spaces/landerCabinInternals/model002.

I have searched for this problem, and nobody else has it. People have had similar problems, but I've tried everything suggested on their topics and nothing works. Please help.

Here is a screenshot:

BTW I am running Windows 7 Home Premium with 4GB ram. I don't know about the CPU and graphics cards, but I think those should be fine because the game worked perfectly before the update.

I've even tried deleting model002 and replacing it with model001 and renaming it, but the same thing happens.

[Claw]

Off hand, I don't know of something I can point at immediately. You can try skimming through this thread for some of the usual suspects like virus scanners. Another thing to check for, if the game took five minutes and only loaded that far. Ensure you don't have any unused network adapter, especially virtual ones (like Hamachi). There is a bug in Unity which can cause exceeding long load times. http://forum.kerbalspaceprogram.com/threads/92228-Known-Issues-Self-Help

If that's not helpful, then please check out this thread. It will outline some of the info that will potentially help us narrow down the problem. Specifically we will need your log files to see if there is anything unusual in there. Possibly also upload a dxdiag dump. http://forum.kerbalspaceprogram.com/threads/92230-%21%21%21-PLEASE-READ-BEFORE-POSTING-%21%21%21-Stock-Support-Bug-Reporting-Guide

Often when the game hangs up on loading a file like that, it's not the file itself but something else. It may take a bit of trial and error to narrow it down.

Welcome to the forums.

Cheers,

~Claw

[nin10dorox]

Thanks. I read the first topic and it turns out that I have a 32 bit duel core processor. I just made it only use one of the CPUs and it still didn't work. It did make it farther, though. This time it made it to mk1PodCockpit/model003.

Something strange happened, though. Rather than the game notifying me that it crashed, it just shut down without warning. It still left a log, though. I'll find a way to post the logs.

Could it be because both of my CPU cores are duel core?

[Claw]

Possibly, but it sounds unlikely. Generally through windows, identifying a single core to run on means it'll only run on that one core. Your post is slightly confusing to me. Do you have a dual processor, dual core machine? If it's just a usual Intel or AMD dual core, then specifying one core will keep it attached to just that one core. (Although I will also say that the need for single core affinity seems to have mostly gone away.)

It's kind of hard to guess what the problem might be without the logs. If you have the ability to, please upload them. You can use a place like dropbox, mediafire, google docs, or even paste it into pastebin.

Usually when something interferes with KSP loading, it is things like antivirus, or because people it is being run from somewhere like "Program Files" or the Desktop. Some of those usual problems are outlines within the general post I directed you to earlier.

Cheers,

~Claw

[sal_vager]

We need the game logs to really know what's happening here, please find the KSP.log or output_log.txt in the KSP folder and upload it somewhere for us

[oriramikad]

Often when the game hangs up on loading a file like that, it's not the file itself but something else.

It loads successively, so my money is on model003.mbm being the problem.

[nin10dorox]

I was finally able to get to my computer and post the logs.

Output log: http://pastebin.com/pBSqY9i1

Error: http://pastebin.com/V7hFWy0i

[Claw]

It looks like you are running out of memory. KSP is pretty memory hungry. You can try turning down the texture quality by editing the settings.cfg file with a plain text editor (such as notepad) and changing the "TEXTURE_QUALITY" line to say "TEXTURE QUALITY = 3" Also, make sure everything else is closed (as much as possible anyway). See if it starts after with that.

If you're able, you might want to consider upgrading your system RAM to 4gb or more.

Cheers,

~Claw

[nin10dorox]

Thanks! I'll turn the texture quality down and see if that works.

My computer already has 4GB RAM, but my dad is considering getting a new computer.

Hopefully the new one will be able to run things like KSP and Minecraft smoothly.

[nin10dorox]

Still "ran out of memory", only a bit farther. I'll have to wait for a not crappy computer

[Claw]

4GB ought to be enough to run it on lower resolutions. My old computer is about 7 or 8 years old, running Vista with a dual core Intel and 4GB...and it's capable of running KSP with the graphics turned down. Your logs seem to indicate that KSP is only able to get to about 2.6ish GB. You might have a lot of things running in the background.

You can try closing stuff in your task tray, and also starting up the process monitor and killing some unused or unknown processes. (If you kill the wrong ones, you might have to restart. But usually windows won't let you kill the wrong stuff.)

If you are comfortable with fiddling with the computer, you can try turning off some of the auto-start processes using MSCONFIG. Go to the run box and type "msconfig" (without the quotes of course). There's a "Services" and "Startup" tab. In there, you can look for old or unwanted programs that automatically load themselves to "help you out." You can uncheck items in here and restart your computer. This prevents them from loading upon startup, thereby booting the computer faster and gobbling up less memory. Generally speaking, leave all the Microsoft ones alone. Also, avoid anything for your graphics or sound drivers. You can keep turning things on and off, then restarting to get your computer to run a little smoother.

Cheers,

~Claw

[nin10dorox]

I just checked. My computer says "4GB (2.75 available)"

Do you know if there is a way to clear up space? (I wouldn't doubt if the RAM is being used by my dad's antivirus (Kaspersky). That stupid thing has caused more problems than a virus itself would)

[Claw]

Well, aside from what I suggested above, you can also find some descent programs that can help clear out old programs. Although you need to be very careful because many of them are mostly adware or malware. Really, my first recommendation is to read up on using MSCONFIG and try that. It doesn't require installing anything and is a microsoft built in utility. It helped me immensely in controlling the bloat on my old computer, without having to wipe it out. Also go through the Control Panel->Programs and uninstall old stuff. Sometimes that also helps remove bloat or stuff that is sitting around in the background. And make sure you have plenty of hard drive space. If your hard drive is full, it can cause problems for Window's swap file (not having enough space).

I don't know much about Kaspersky myself since I don't use it. It may be that you can disable some of it's protections while still maintaining firewall and virus support. But please make sure you know what you're turning off or take precautions to protect your computer if you disable while playing KSP.

Cheers,

~Claw

[Claw]

If you're still checking the forums...

As another thing to try, install KSP to a different location. Such as C:\Games\KSP, instead of in your user directories. Also, avoid places like the desktop, documents (which is where yours is installed), or "program files". Sometimes Windows has an issue installing to these locations.

Make sure you either install fresh from the .zip, or that you copy & paste the KSP directory over. Do not move the folder. Windows might try to help you out and will keep track of the protected directories.

Cheers,

~Claw