1.17 Crash

[paulholt1983]

Hello everyone, I have problem with KSP crashing on me everytime i switch between buildings/flying or sometimes when loading parts during build. The crashes happen from anything to a few minutes to an hour.

 

Any help would be great

 

Fresh KSP 1.1.2.1260 install, launching from launcher, new save and no mods. Also pretty fresh (1 week or so) windows 7 32bit install

 

I have crash logs attached

 

Output_log:-

http://pastebin.com/gwPgk3nD

Error File:-

http://pastebin.com/ipiNq1F8

Edited June 10, 2016 by paulholt1983
added more detail

[FullMetalMachinist]

Hi @paulholt1983, sorry you're having troubles. 

I'm not sure about what version of KSP you're running, as there is no 1.17. The current version is 1.1.2, and that has some known crashing issues that will hopefully be solved when 1.1.3 comes out soon. There also is a 0.17.1, but that came out almost 4 years ago, so you're unlikely to get much support if that's what you're using . 

As for posting your log files, it's easiest to upload them to a file hosting site (like pastebin or dropbox) and then post the link to those files here. 

[Jas0n]

Have you tried the 64 bit version? Crashing during scene switches is usually caused by hitting the RAM limit in 32 bit.

[paulholt1983]

19 hours ago, FullMetalMachinist said:

Hi @paulholt1983, sorry you're having troubles. 

I'm not sure about what version of KSP you're running, as there is no 1.17. The current version is 1.1.2, and that has some known crashing issues that will hopefully be solved when 1.1.3 comes out soon. There also is a 0.17.1, but that came out almost 4 years ago, so you're unlikely to get much support if that's what you're using . 

As for posting your log files, it's easiest to upload them to a file hosting site (like pastebin or dropbox) and then post the link to those files here. 

Ah yes, you are correct my version is 1.1.2 - i have corrected above and also added the log files. Thanks for your help

17 hours ago, Jas0n said:

Have you tried the 64 bit version? Crashing during scene switches is usually caused by hitting the RAM limit in 32 bit.

Im currently on 32bit windows, however I'm not sure if RAM is the issue as keeping an eye on it it never goes crazy... also the time in which the crash happens changes between 10mins to a few hours. Thanks for your help

[paulholt1983]

Bump - if anyone could confirm/advise if this is caused by the program or something else that would be great - error logs attached. Cheers

[John FX]

There are known bugs that cause crashing in the VAB

You may wish to check this thread

There is a modlet in that thread which solves some of the problems for some people

Download from here

Modlet Installation:

1. Download the EditorCPUFix.dll from here.
2. Unzip the files.
3. Copy EditorCPUFix.dll into the KSP/GameData directory. (You can create a subdirectory if desired.)
4. Launch KSP

[paulholt1983]

7 hours ago, John FX said:

There are known bugs that cause crashing in the VAB

You may wish to check this thread

There is a modlet in that thread which solves some of the problems for some people

Download from here

Modlet Installation:

1. Download the EditorCPUFix.dll from here.
2. Unzip the files.
3. Copy EditorCPUFix.dll into the KSP/GameData directory. (You can create a subdirectory if desired.)
4. Launch KSP

Thanks John FX I'll give it a go

[Padishar]

On 6/10/2016 at 8:11 PM, paulholt1983 said:

Im currently on 32bit windows, however I'm not sure if RAM is the issue as keeping an eye on it it never goes crazy...

RAM is most definitely the issue.  On 32 bit windows the game (like any other process) can only use a maximum of about 1.7GB of RAM.  Once KSP tries to allocate more than this it will fail and usually crashes.  Sometimes, the initial failing allocation will not crash the game and this can result in strange rendering (e.g. the internal VAB textures being missing) or other weird effects but the game will usually crash pretty soon after.

Your only real solution is to reduce the memory usage of the game.  There are two main ways to do this, either reduce the texture resolution to the minimum setting or run the game with the -force-glcore or -force-d3d11 command line options.

[kiwi1960]

No offence, but had you looked before posting you would have seen this isn't a new problem.

[paulholt1983]

2 hours ago, kiwi1960 said:

No offence, but had you looked before posting you would have seen this isn't a new problem.

Hi Kiwi, as matter of fact I had looked, quite extensively actually. All of the things I could find indicated the game crashing after a certain period of time, however this crash happens after different periods 10min-1hr or even longer. 

You say it's a common problem but you don't actually know what the problem is, have you looked at the crash logs?

not everyone who uses forums is lazy you know...

2 hours ago, Padishar said:

RAM is most definitely the issue.  On 32 bit windows the game (like any other process) can only use a maximum of about 1.7GB of RAM.  Once KSP tries to allocate more than this it will fail and usually crashes.  Sometimes, the initial failing allocation will not crash the game and this can result in strange rendering (e.g. the internal VAB textures being missing) or other weird effects but the game will usually crash pretty soon after.

Your only real solution is to reduce the memory usage of the game.  There are two main ways to do this, either reduce the texture resolution to the minimum setting or run the game with the -force-glcore or -force-d3d11 command line options.

Thanks pandishar, the CPU texture mod posted above seems to have made no difference, I'll try messing with these options. I'm kind of thinking to just switch to 64bit win7 as I have a 6gig system. I was on windows 10 64bit before but it kept hitting bluescreens due to unsupported hardware drivers

Edited June 12, 2016 by paulholt1983

[Padishar]

2 hours ago, paulholt1983 said:

I'm kind of thinking to just switch to 64bit win7 as I have a 6gig system. I was on windows 10 64bit before but it kept hitting bluescreens due to unsupported hardware drivers

If your CPU supports 64 bit windows then that is easily the best course of action.  On 64 bit windows, even the 32 bit version of KSP is able to use 3.5GB of memory and the 64 bit one is basically unlimited.

[kiwi1960]

6 hours ago, paulholt1983 said:

Hi Kiwi, as matter of fact I had looked, quite extensively actually. All of the things I could find indicated the game crashing after a certain period of time, however this crash happens after different periods 10min-1hr or even longer. 

You say it's a common problem but you don't actually know what the problem is, have you looked at the crash logs?

not everyone who uses forums is lazy you know...

Yes, and I'm not lazy. Nearly 40 years of working 18 hour days and, now, at the age of nearly 56, I'm suffering the consequences. One heart attack, diabetes, insomnia, sleep apnoea, M.S. as well as two busted knees and a busted hip, I'm probably the least laziest person on these forums, child. Further to your comment, the bug in question has no set time limit, nor where it happens, it just DOES. To think you are special with a bug all your own is worthy of praise, but sadly, only an idiot would praise you. Its the same bug.

Thanks for reading.

[paulholt1983]

5 hours ago, Padishar said:

If your CPU supports 64 bit windows then that is easily the best course of action.  On 64 bit windows, even the 32 bit version of KSP is able to use 3.5GB of memory and the 64 bit one is basically unlimited.

Thanks for that, I've just updated my northbridge  driver and that seems to have worked, from my rudimentary understanding the chipset is the bridge between memory and CPU so that kinda makes sense, hopefully the issue is resolved. Going strong now after a couple hours games time... I think I'll update to x64 over the next few days as there's little point having the RAM and not using it. Thanks for your help.

 

1 hour ago, kiwi1960 said:

Yes, and I'm not lazy. Nearly 40 years of working 18 hour days and, now, at the age of nearly 56, I'm suffering the consequences. One heart attack, diabetes, insomnia, sleep apnoea, M.S. as well as two busted knees and a busted hip, I'm probably the least laziest person on these forums, child. Further to your comment, the bug in question has no set time limit, nor where it happens, it just DOES. To think you are special with a bug all your own is worthy of praise, but sadly, only an idiot would praise you. Its the same bug.

Thanks for reading.

I wasn't insinuating you were lazy. The standard approach when someone new asks a question is to assume that they have done zero research and are lazy - I was simply pointing that out.

I'm not getting drawn into some ridiculous slanging match on a forum as it won't achieve anything other than making your menagerie on conditions worse and wasting my time...  Point is this appears to be a driver related issue so maybe give people the benefit of the doubt next time and assume the best.

chees for your help - paul

Edited June 12, 2016 by paulholt1983

[Padishar]

1 hour ago, kiwi1960 said:

Yes, and I'm not lazy.  <snip>  

He didn't call you lazy, nor did he ask for your life story.  Also, your "child" remark is horribly condescending.  If I had to guess based on the very limited information available, I would say he's probably in his early thirties, e.g just like you used your birth year in your username, I suspect he did too...

1 hour ago, kiwi1960 said:

the bug in question

So, in your opinion, which particular "bug" is he experiencing?

1 hour ago, kiwi1960 said:

To think you are special with a bug all your own is worthy of praise, but sadly, only an idiot would praise you. Its the same bug.

I think you're being condescending again here but I can't actually work out what you are trying to say.  Again, what bug do you think it is?

His problem (it isn't really a bug because it's expected behaviour) is that his game is running out of virtual address space and failing to allocate memory because he is running on 32 bit windows where the game can only use ~1.7GB.  The only actual bugs he is having are probably the memory leaks (mostly on scene changes) that cause the memory usage to grow over time.

In any case, neither of your messages in this thread have been at all helpful and they certainly don't give a very good impression to a newcomer to the forums.  Are you deliberately trying to drive people away?

Edited June 12, 2016 by Padishar