Help me understand Crash logs

[ConstantinP234]

Hey everyone,

my game keeps crashing quite often when I switch from the space center to the "real world" or back (e.g. Launching, recovering...).

This started happening after I installed some new mods, and I know the logical steps I should take (reinstalling and stuff), but because its occurence increased with time, I would like to know what is causing it (specific mod, memory shortage...). What happens is that the game freezes while being in the black loading screen, my computer fan is getting slower and I manually have to kill the task. The error.log reads the following:

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

Error occurred at 2014-05-23_235052.
C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP.exe, run by Constantin.
63% memory in use.
0 MB physical memory [2936 MB free].
0 MB paging file [2437 MB free].
0 MB user address space [127 MB free].
Write to location 00400000 caused an access violation.

Can anyone help me understand what this means? Thanks

[blizzy78]

Take a look at output_log.txt, it usually has more information.

[Taki117]

What you have posted means that KSP is running out of memory. I suggest you get the Aggressive Version of the Active Texture Management mod.

[ConstantinP234]

What you have posted means that KSP is running out of memory. I suggest you get the Aggressive Version of the Active Texture Management mod.

Is that a problem with unity? Because both the error log and my PC tell me I'm only using 63% of my RAM.

Btw, the output_log reads the following:

[HighLogic]: =========================== Scene Change : From EDITOR to FLIGHT =====================

(Filename: C:/BuildAgent/work/d3d49558e4d408f4/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 53)

UnloadTime: 40.994789 ms
Crash!!!

And later:

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

(0x10118D2A) (mono): (filename not available): unity_mono_install_memory_callbacks + 0x1178c
(0x101069FA) (mono): (filename not available): mono_gc_wbarrier_value_copy + 0x10fa8
(0x10106A4E) (mono): (filename not available): mono_gc_wbarrier_value_copy + 0x10ffc
(0x10106CE3) (mono): (filename not available): mono_unity_liveness_calculation_end + 0xc2

And it continues with a couple dozen lines of mono_unity_liveness_calculation_end

[Blu_C]

Is that a problem with unity?

Sort of. Currently KSP only uses the the 32-bit version of Unity, which puts a restriction on how much memory it can access (4GB max). Even if your computer has more than 4gb of RAM available the program cannot 'see' it since it is only 32-bit. Eventually KSP will presumably switch over to 64-bit unity, but as I recall currently does not use it because of bugs with the 64-bit version.

In short, if you use a lot of mods (especially ones that add a lot of textures or are otherwise memory intensive) then getting the Active Texture Replacer mod is a good idea, otherwise you are likely to run into insufficent RAM crashes.