Crash switching to space center

[Mapoko]

Hello.

After finishing my vanilla goals I decided to mod.

For some reason it crashes when I switch to space center/recover vessel.

I thought it may be the temp gauges, but I had them disabled last 2 times.

My mod list :

The latest crash report :

http://s000.tinyupload.com/download.php?file_id=25244454867384638371&t=2524445486738463837138420

http://s000.tinyupload.com/download.php?file_id=18437481174263693090&t=1843748117426369309069444

Every mod is fresh, unless they added new version in the past 8 hours.

Edited June 10, 2015 by Mapoko

[Mapoko]

Crashes continue. Please help.

http://s000.tinyupload.com/download.php?file_id=39481800633824537925&t=3948180063382453792558439

[sal_vager]

Hmm, looks like it might be transfer window planner.

6/10/2015 7:30:35 AM,TransferWindowPlanner,Destroying the TransferWindowPlanner (TWP)

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

[FlightEngineer]: Destroying Floating Window for HUD 1

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

[FlightEngineer]: Destroying Floating Window for HUD 2

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

UnloadTime: 35.945335 ms

Crash!!!

Also there's this.

mono.dll caused an Access Violation (0xc0000005)

in module mono.dll at 0023:10107259.

Error occurred at 2015-06-11_155030.

C:\Program Files (x86)\Kerbal space program\KSP.exe, run by Mapoko.

45% memory in use.

0 MB physical memory [0 MB free].

0 MB paging file [0 MB free].

0 MB user address space [106 MB free].

Write to location 00000000 caused an access violation.

It should never be writing to 00000000.

Can you try removing the plugin for transfer window planner and see if it helps?

[Mapoko]

Thanks, I will try, but TWP will be vital for my program in few days when I start moving in the system. Even more later.

It happens in change of scenery. Does not matter from where to where.

Happens on recovery of a vessel,

changing from KSC to VAB

VAB > KSC

Never Tracking station > active vessel or VAB > Vessel or Vessel > Vessel.

So I am guessing it crashes when switching to the stationary scenes.

[Lumaan]

mono.dll caused an Access Violation (0xc0000005)

in module mono.dll at 0023:10107259.

Error occurred at 2015-06-11_155030.

C:\Program Files (x86)\Kerbal space program\KSP.exe, run by Mapoko.

45% memory in use.

0 MB physical memory [0 MB free].

0 MB paging file [0 MB free].

0 MB user address space [106 MB free].

Write to location 00000000 caused an access violation.

You are running in to KSP going over MAX RAM it can handle.

Either run with "-force-opengl" or run 64bit http://forum.kerbalspaceprogram.com/threads/117224-Windows-64-bit-community-workaround

[Mapoko]

As far as I know x64 have been cut from 1.0 on ? I do not see the option.

My rig have 16GB of ram, so it is not a problem from hardware point.

I will check the topic, but will my mods work if I run it that way?

EDIT : After reading it it seems that if I go that way I am trading 3-5 crashes in 5 hours (give or take) for way more frequent crashes and not working mods and even more buggy situations.

I am playing hard career, so for me there is no F5. I can not afford a version that is that unstable.

Edited June 12, 2015 by Mapoko

[Lumaan]

Did you even read the whole thread? If you did then you''d know that you'll crash less then what you do now.

Only time I have had a few crashes is when I push KSP 64bit pass 10Gb of RAM. I run with 80+ mods installed now and RAM is about 7-8Gb.

I have played 40+ hours with the 64bit unofficial KSP, and only crashed 3-4 times, and that mostly ind the beginning I ran the 64bit on KSP 1.0.2 where I had to see how far I was able to puss it.

The only thing bugging for me is when I sometime (80% of the times) go back to KSC I get KSC looking like it's upgraded,

but that I get fixed by either going in SPH or VAB, few times I have to save then game and to out to the menu and restart the save.

And from you list of mods I don't see any of the ones I know is not working on 64bit.

[Mapoko]

I admit I did only read the first post. I may give it a go tomorrow, but now I removed TWP and wll monitor the situation today.

P.S. I removed TWP but it crashed twice since then.

Not sure where this is from.

Serialization depth limit exceeded at 'OcclusionData'. There may be an object composition cycle in one or more of your serialized classes.

(Filename: Line: 67)

Serialization depth limit exceeded at 'ThermalLink'. There may be an object composition cycle in one or more of your serialized classes.

(Filename: Line: 67)

Edited June 13, 2015 by Mapoko

[Mapoko]

I tried everything so far, but crashes continue. I can not tell if it is specific mod or simply overload of the game.

Started to remove the mods 1 by 1 until it stops crashing. Hope to find it, but not hopeful.