KSP keeps crashing

[DasKatzenbrot]

I bought ksp 1 a few weeks ago. it kept crashing every 5 minutes, even without mods. I dont know what to do, and everything i found online wasnt working.

These are the last few lines of the log

https://drive.google.com/drive/folders/1kxK-9aowAVB3wWf5uzrbi1xf3G4AkmSM?hl=de
This is the google docs link for the crash log

Edited June 19, 2024 by DasKatzenbrot
I wanted to add a docs link, because the copy paste of the document was too big and removed

[Lisias]

Please publish the ENTIRE ksp.log. please use Dropbox or Google Drive or similar services, then post the link here!

Also, avoid pasting long pieced of the log on the  Forum, it makes Forum slower- and are useless anyway, because we need the whole log in order to diagnose the problem.

Right now I can only guess. Remove BDA.Armory and see what's happens.

Edited June 18, 2024 by Lisias
Hit "Save" too soon.

[Vanamonde]

6 hours ago, DasKatzenbrot said:

I bought ksp 1 a few weeks ago. it kept crashing every 5 minutes, even without mods. I dont know what to do, and everything i found online wasnt working.

These are the last few lines of the log

[snip]

I'm sorry to tell you that files that large are too big to post directly on the forum so we've had to remove that. Please upload it to a sharing service and link to it here. 

That being said, welcome.

[DasKatzenbrot]

13 hours ago, Vanamonde said:

I'm sorry to tell you that files that large are too big to post directly on the forum so we've had to remove that. Please upload it to a sharing service and link to it here. 

That being said, welcome.

https://drive.google.com/drive/folders/1kxK-9aowAVB3wWf5uzrbi1xf3G4AkmSM?hl=de This is the link for my crash log, should i set everyone as commentator? so you can write something next to the error or smth

[Lisias]

23 hours ago, DasKatzenbrot said:

https://drive.google.com/drive/folders/1kxK-9aowAVB3wWf5uzrbi1xf3G4AkmSM?hl=de This is the link for my crash log, should i set everyone as commentator? so you can write something next to the error or smth

This is unusual.

On the modded log, you managed to reach flight mode after loading the savegame and then suddenly the log stops.

On the unmodded log, you managed to load the savegame and the thing crashed on you while Editing a craft.

I wondering if there's something related to lighting, I remember a old bug on a GPU driver that was triggered on KSP in the editor by looking into one of the spotlights of the VAB. But I'm blind guessing.

Please publish your unity's Player.log - read this post if you don't know where to find it (it's a bit convoluted). This crash happened on the C++ land, and it instakilled the C# land before if could log something. The Player.log will 99% surely have a stackdump of the crash that may help to pinpoint the cause.

 

Edited June 20, 2024 by Lisias
Yeah, tyops...

[DasKatzenbrot]

On 6/20/2024 at 11:16 AM, Lisias said:

This is unusual.

On the modded log, you managed to reach flight mode after loading the savegame and then suddenly the log stops.

On the unmodded log, you managed to load the savegame and the thing crashed on you while Editing a craft.

I wondering if there's something related to lighting, I remember a old bug on a GPU driver that was triggered on KSP in the editor by looking into one of the spotlights of the VAB. But I'm blind guessing.

Please publish your unity's Player.log - read this post if you don't know where to find it (it's a bit convoluted). This crash happened on the C++ land, and it instakilled the C# land before if could log something. The Player.log will 99% surely have a stackdump of the crash that may help to pinpoint the cause.

 

i updated it

 

[Lisias]

On 6/27/2024 at 11:09 AM, DasKatzenbrot said:

i updated it

Got it. Thanks for the comprehensive material, I could compare the different crashes looking for patterns - this made my life easier!

Well, somehow, your Kerbals got their collective arses bitten by the resurrection of a pretty old mishap from the times KSP transitioned from 32 to 64 bits! The infamous xinput1_3.dll induced crash! This one was tackled down by @JoE Smash a long time ago, by the way!

What happens is, now that we know about, simple: (yours) xinput1_3 is a 32 bits DLL, and so is can read only a pretty small window of memory compared to a 64 bits application. However, KSP nowadays is a 64 bits application, and merrily ears memory are they were candies and hyperglycemia was only a fairy tail.

Initially, these crashes happened randomly because at that times, KSP didn't used so much memory initially, and so the xinput1_3 triggers the problem only after KSP growing its memory footprint beyonud that it can address, but nowadays KSP became, well, somewhat memory hungry at startup and the xinput1_3 gets screwed pretty fast now.

You probably installed a 32 bits game in your rig, and it shoved this xinput1_3 thing in your SYSTEM32 as it was a pretty usual way to do ways at that time. But since Microsoft, in their infinite "wisdom" (coff, coff ) decided to keep SYSTEM32 for 64 bits applications and created a place called SysWOW64 to keep legacy 32 bits support, and then older installers kept shoving 32 bits DLLS on the "wrong place", and this royally screwed you now.

edit: previous answer "spoilled" because I remembered a better way!

Spoiler

Move this file

• C:\WINDOWS\SYSTEM32\xinput1_3.dll

To a directory in your Documents folder for safekeeping (you may need it later).

And this will fix your KSP. This probably will break the game that installed it there, but once you realize a older game is not working correctly, you can copy that file to the same place where the EXE file for that game is, and then it will find it and used it.

edit: BETTER WAY

1. Check if is more than 80K in size (the 80K variant is a 32 bits DLL)
   1. If it's 32 bits, use the hint on the spoiler above
2. If it's a 64 bits DLL, then the one in your <KerbalSpaceProgram>/KSP_x64_Data/Plugins is screwed.
   1. Delete <KerbalSpaceProgram>/KSP_x64_Data/Plugins/xinput1_3.dll and COPY (be absolutely sure not to move it) the file C:\WINDOWS\SYSTEM32\xinput1_3.dll into <KerbalSpaceProgram>/KSP_x64_Data/Plugins/.

And, yeah. This is a mess. Thanks, Microsoft!

Cheers!

Edited June 30, 2024 by Lisias
better way

[DasKatzenbrot]

13 minutes ago, Lisias said:

Got it. Thanks for the comprehensive material, I could compare the different crashes looking for patterns - this made my life easier!

Well, somehow, your Kerbals got their collective arses bitten by the resurrection of a pretty old mishap from the times KSP transitioned from 32 to 64 bits! The infamous xinput1_3.dll induced crash! This one was tackled down by @JoE Smash a long time ago, by the way!

What happens is, now that we know about, simple: xinput1_3 is a 32 bits DLLs, and so is can read only a pretty small window of memory compared to a 64 bits application. However, KSP nowadays is a 64 bits application, and merrily ears memory are they were candies and hyperglycemia was only a fairy tail.

Initially, these crashes happened randomly because at that times, KSP didn't used so much memory initially, and so the xinput1_3 triggers the problem only after KSP growing its memory footprint beyonud that it can address, but nowadays KSP became, well, somewhat memory hungry at startup and the xinput1_3 gets screwed pretty fast now.

You probably installed a 32 bits game in your rig, and it shoved this xinput1_3 thing in your SYSTEM32 as it was a pretty usual way to do ways at that time. But since Microsoft, in their infinite "wisdom" (coff, coff ) decided to keep SYSTEM32 for 64 bits applications and created a place called SysWOW64 to keep legacy 32 bits support, and then older installers kept shoving 32 bits DLLS on the "wrong place", and this royally screwed you now.

edit: previous answer "spoilled" because I remembered a better way!

  Reveal hidden contents

Move this file

• C:\WINDOWS\SYSTEM32\xinput1_3.dll

To a directory in your Documents folder for safekeeping (you may need it later).

And this will fix your KSP. This probably will break the game that installed it there, but once you realize a older game is not working correctly, you can copy that file to the same place where the EXE file for that game is, and then it will find it and used it.

Cheers!

Thank you very much, il try this out rn, but isnt it kinda dangerous to do stuff in the System 32 folder?

Edited June 27, 2024 by DasKatzenbrot

[DasKatzenbrot]

16 minutes ago, Lisias said:

Got it. Thanks for the comprehensive material, I could compare the different crashes looking for patterns - this made my life easier!

Well, somehow, your Kerbals got their collective arses bitten by the resurrection of a pretty old mishap from the times KSP transitioned from 32 to 64 bits! The infamous xinput1_3.dll induced crash! This one was tackled down by @JoE Smash a long time ago, by the way!

What happens is, now that we know about, simple: xinput1_3 is a 32 bits DLLs, and so is can read only a pretty small window of memory compared to a 64 bits application. However, KSP nowadays is a 64 bits application, and merrily ears memory are they were candies and hyperglycemia was only a fairy tail.

Initially, these crashes happened randomly because at that times, KSP didn't used so much memory initially, and so the xinput1_3 triggers the problem only after KSP growing its memory footprint beyonud that it can address, but nowadays KSP became, well, somewhat memory hungry at startup and the xinput1_3 gets screwed pretty fast now.

You probably installed a 32 bits game in your rig, and it shoved this xinput1_3 thing in your SYSTEM32 as it was a pretty usual way to do ways at that time. But since Microsoft, in their infinite "wisdom" (coff, coff ) decided to keep SYSTEM32 for 64 bits applications and created a place called SysWOW64 to keep legacy 32 bits support, and then older installers kept shoving 32 bits DLLS on the "wrong place", and this royally screwed you now.

edit: previous answer "spoilled" because I remembered a better way!

  Reveal hidden contents

Move this file

• C:\WINDOWS\SYSTEM32\xinput1_3.dll

To a directory in your Documents folder for safekeeping (you may need it later).

And this will fix your KSP. This probably will break the game that installed it there, but once you realize a older game is not working correctly, you can copy that file to the same place where the EXE file for that game is, and then it will find it and used it.

edit: BETTER WAY

1. Check if is more than 80K in size (the 80K variant is a 32 bits DLL)
   1. If it's 32 bits, use the hint on the spoiler above
2. If it's a 64 bits DLL, then the one in your <KerbalSpaceProgram>/KSP_x64_Data/Plugins is screwed.
   1. Delete <KerbalSpaceProgram>/KSP_x64_Data/Plugins/xinput1_3.dll and COPY (be absolutely sure not to move it) the file C:\WINDOWS\SYSTEM32\xinput1_3.dll into <KerbalSpaceProgram>/KSP_x64_Data/Plugins/.

And, yeah. This is a mess. Thanks, Microsoft!

Cheers!

That may be the reasons for other games to crash too. I always wondered why older games crash, and newer games run perfectly fine. But it was just until that i had ksp that i actually wanted to fix this, again, thank you so much, you saved Ksp and many more games from never being played

[DasKatzenbrot]

23 hours ago, Lisias said:

Got it. Thanks for the comprehensive material, I could compare the different crashes looking for patterns - this made my life easier!

Well, somehow, your Kerbals got their collective arses bitten by the resurrection of a pretty old mishap from the times KSP transitioned from 32 to 64 bits! The infamous xinput1_3.dll induced crash! This one was tackled down by @JoE Smash a long time ago, by the way!

What happens is, now that we know about, simple: xinput1_3 is a 32 bits DLLs, and so is can read only a pretty small window of memory compared to a 64 bits application. However, KSP nowadays is a 64 bits application, and merrily ears memory are they were candies and hyperglycemia was only a fairy tail.

Initially, these crashes happened randomly because at that times, KSP didn't used so much memory initially, and so the xinput1_3 triggers the problem only after KSP growing its memory footprint beyonud that it can address, but nowadays KSP became, well, somewhat memory hungry at startup and the xinput1_3 gets screwed pretty fast now.

You probably installed a 32 bits game in your rig, and it shoved this xinput1_3 thing in your SYSTEM32 as it was a pretty usual way to do ways at that time. But since Microsoft, in their infinite "wisdom" (coff, coff ) decided to keep SYSTEM32 for 64 bits applications and created a place called SysWOW64 to keep legacy 32 bits support, and then older installers kept shoving 32 bits DLLS on the "wrong place", and this royally screwed you now.

edit: previous answer "spoilled" because I remembered a better way!

  Reveal hidden contents

Move this file

• C:\WINDOWS\SYSTEM32\xinput1_3.dll

To a directory in your Documents folder for safekeeping (you may need it later).

And this will fix your KSP. This probably will break the game that installed it there, but once you realize a older game is not working correctly, you can copy that file to the same place where the EXE file for that game is, and then it will find it and used it.

edit: BETTER WAY

1. Check if is more than 80K in size (the 80K variant is a 32 bits DLL)
   1. If it's 32 bits, use the hint on the spoiler above
2. If it's a 64 bits DLL, then the one in your <KerbalSpaceProgram>/KSP_x64_Data/Plugins is screwed.
   1. Delete <KerbalSpaceProgram>/KSP_x64_Data/Plugins/xinput1_3.dll and COPY (be absolutely sure not to move it) the file C:\WINDOWS\SYSTEM32\xinput1_3.dll into <KerbalSpaceProgram>/KSP_x64_Data/Plugins/.

And, yeah. This is a mess. Thanks, Microsoft!

Cheers!

Uhhhh, i dont know if i did anything wrong but it didnt work

[Lisias]

On 6/28/2024 at 12:59 PM, DasKatzenbrot said:

Uhhhh, i dont know if i did anything wrong but it didnt work

Send us a new logs as you did initially. Let's see what's going on now - your logs are remarkably similar to that issues I pinpointed, it's too much of an coincidence to be completely unrelated.

On 6/27/2024 at 1:21 PM, DasKatzenbrot said:

Thank you very much, il try this out rn, but isnt it kinda dangerous to do stuff in the System 32 folder?

Yes, and it's the reason whoever did what they did on yours shouldn't had done that.