Crashing after installing a mod

[Tukas]

Hello,

I've recently installed Interstellar extended mod for 1.0.5 and I get crashes when something loads, but not everytime. Sometimes I get a crash when going to building hangar, sometimes by going to space center etc.

Logs at the end shows this:

========== OUTPUTING STACK TRACE ==================


(0x1011940A) (mono): (filename not available): mono_gc_max_generation + 0x103e4
(0x10106F61) (mono): (filename not available): mono_set_defaults + 0x18cea
(0x10106FB5) (mono): (filename not available): mono_set_defaults + 0x18d3e
(0x101072A7) (mono): (filename not available): mono_unity_liveness_calculation_end + 0x9c
(0x1010742D) (mono): (filename not available): mono_unity_liveness_calculation_end + 0x222
(0x10107468) (mono): (filename not available): mono_unity_liveness_calculation_end + 0x25d
(0x10107649) (mono): (filename not available): mono_unity_liveness_calculation_end + 0x43e
(0x101078CB) (mono): (filename not available): mono_unity_liveness_calculation_from_root + 0x1e
(0x014ECD6A) (KSP): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0x912ea
(0x014ECE26) (KSP): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0x913a6
(0x01500317) (KSP): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0xa4897
(0x014F1579) (KSP): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0x95af9
(0x014F1A44) (KSP): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0x95fc4
(0x014F2BE8) (KSP): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0x97168
(0x014F2D94) (KSP): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0x97314
(0x0156BD1B) (KSP): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0x11029b
(0x0156D805) (KSP): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0x111d85
(0x017E0728) (KSP): (filename not available): AnimationEvent::Transfer<StreamedBinaryRead<1> > + 0x123458
(0x01815610) (KSP): (filename not available): AnimationEvent::Transfer<StreamedBinaryRead<1> > + 0x158340
(0x75C6337A) (kernel32): (filename not available): BaseThreadInitThunk + 0x12
(0x77B49882) (ntdll): (filename not available): RtlInitializeExceptionChain + 0x63
(0x77B49855) (ntdll): (filename not available): RtlInitializeExceptionChain + 0x36


========== END OF STACKTRACE ===========


**** Crash! **** Edited November 25, 2015 by Tukas

[maceemiller]

I would think your simply running out of memory. What RAM do you have in your machine?

[Tukas]

I have 4 x 1GB 1066Mhz, 4GB total . Well that may be the case. But why it doesn't use hdd space then if it lacks it for some textures which are not in use atm?
Anyway, since I have no fps drops and the game runs smoothly, how can I try to fix it without lowering texture quality? Also going to test it while viewing ram usage.

EDIT:

I just saw a sticky at this forum... Going to give it a try. Thank you for an idea. :) Edited November 24, 2015 by Tukas

[Tukas]

[COLOR=#333333]-force-d3d11 worked like a charm! Texts are a bit weird now but that's totally not a problem. :) Didn't crash for hours.[/COLOR]

[Hysterrics]

Try either the 64bit workaround or force the game to run in OpenGL.

[Speadge]

[quote name='Sequinox']Try either the 64bit workaround or force the game to run in OpenGL.[/QUOTE]

even if thread is "solved: for others having the problem:

64bit workaround wont reduce your memory footprint - it will increase it!
Only think is, that the process is not limited to 4GB only.

But on a 4GB machine that would make things worse

[sumghai]

KSP does not support dynamic asset loading/unloading, so there's no way to cache unused textures to the hard disk.

If your total system RAM is only 4GB, it is almost certain that KSP will not be able to make full use of it, since the Operating System itself will also use non-trivial amounts of RAM concurrently. Consider upgrading your computer's RAM in addition to the OpenGL/DX11 startup options previously mentioned.