i have no idea

[Oxygentlemen]

so i have a problem. ksp crashes when: launching from VAB/SPH, or reverting to VAB/SPH. i have 1.2.2, steam version, and i think it's caused by outdated mods, but no matter how many i update, it keeps happening. this is just a sample of a few bazillion crash reports. do you need the stack or any other reports? i just hope that this can be fixed.

Unity Player [version: Unity 5.4.0p4_b15b5ae035b7]

KSP.exe caused an Access Violation (0xc0000005)
  in module KSP.exe at 0023:0189a1a3.

Error occurred at 2017-01-16_180314.
C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP.exe, run by Catherine.
85% memory in use.
0 MB physical memory [919 MB free].
0 MB paging file [0 MB free].
0 MB user address space [104 MB free].
Write to location 000000fe caused an access violation.

Context:
EDI:    0x05099460  ESI: 0x00000000  EAX:   0x00000000
EBX:    0x00000000  ECX: 0xecfb0000  EDX:   0xecfb0040
EIP:    0x0189a1a3  EBP: 0x0acff898  SegCs: 0x00000023
EFlags: 0x00010206  ESP: 0x0acff840  SegSs: 0x0000002b

Bytes at CS:EIP:
88 88 fe 00 00 00 33 ff 3b b2 c0 01 00 00 7d 05 

[Snark]

So, the general procedure in cases like that is to figure out which mod is causing the problem.  I recommend this technique:

1. Try running with no mods installed.  Does it still crash?  If so, then this isn't a mod problem, and you can post your question over in the tech support forum for unmodded installs.  Otherwise, keep reading.
2. Assuming that it stops crashing when you uninstall all the mods, it means some mod is causing your problem, and you need to figure out which one.  You do this by a process of elimination.  That's tedious, yes, but it's not as tedious as you probably think-- use the technique below.
3. Install just half of your mods.  (Doesn't matter which ones.)  Now run.  Do you still have the problem, or not?  This will tell you which half the culprit lies within.
4. So, toss out the half of your mods that have been proven to be innocent.  Now take the remaining mods, and go back to step 3 above, installing just half of them.
5. Repeat steps 3 and 4 until you've narrowed it down to one mod that's causing the problem.  Since you cut the list in half each time, it converges pretty quickly-- for example, even if you have 1000 mods installed, you'd need to do 10 iterations at most.
6. Once you've identified which mod is causing the problem, go find its mod thread in Add-on Releases, and post your question there.  That's where all the experts are for that particular mod.

Good luck!

 

[Jas0n]

Also, make sure you don't have any mods that are for 1.3.0, not 1.2.2.

[Oxygentlemen]

thanks! i'll try that now. also, i'll probably just throw some mods into the trashbin if i don't use them anymore. that should make it easier.

[Harry Rhodan]

8 hours ago, Oxygentlemen said:

so i have a problem. ksp crashes when: launching from VAB/SPH, or reverting to VAB/SPH. i have 1.2.2, steam version, and i think it's caused by outdated mods,

C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP.exe,

No. There are basically two paterns of these crash reports: If the game crashes while launching the game after an update usually your mods are outdated, if the game crashes on any scene transition while running the game you usually run out of memory because you either have too many mods for your system to handle or are not using the 64bit executable. And that second line in the quote clearly says that you are still using the 32bit ecexutable.

[Oxygentlemen]

what is the 64bit executable?

[Harry Rhodan]

KSP_x64.exe in your installation folder.

[Oxygentlemen]

how do i use it instead of x32?

 

[Oxygentlemen]

alrighty, did some tests, and now it crashes on startup. i could not complete the tests due to it now missing more then half the mods and dying immediately. here's a log:

 

Unity Player [version: Unity 5.4.0p4_b15b5ae035b7]

mono.dll caused an Access Violation (0xc0000005)
  in module mono.dll at 0023:100704db.

Error occurred at 2017-06-23_160054.
C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP.exe, run by Catherine.
63% memory in use.
0 MB physical memory [2237 MB free].
0 MB paging file [0 MB free].
0 MB user address space [2700 MB free].
Read from location 00000000 caused an access violation.

Context:
EDI:    0x370bdf08  ESI: 0x00000000  EAX:   0x0043e768
EBX:    0x355b9d48  ECX: 0x370bdf08  EDX:   0x00000067
EIP:    0x100704db  EBP: 0x0043e76c  SegCs: 0x00000023
EFlags: 0x00210216  ESP: 0x0043e6b8  SegSs: 0x0000002b

Bytes at CS:EIP:
ff 36 ff 75 08 e8 0f f9 ff ff 50 56 53 89 45 0c 
 

from what i see, it's something in the mono file, but i am a novice and have no idea what the mono file does or if it's even the right file.

[Harry Rhodan]

On 23.6.2017 at 9:19 PM, Oxygentlemen said:

how do i use it instead of x32?

 

You double-click it.

[Oxygentlemen]

just... nevermind. i know how to open a simple application. i meant steam defaults. but i fixed it anyway. i found the problem was in my BDamory file. so no more posts on this thread