KSP crashing and thinks I have 0 RAM

[TheBlazinLoony]

After updating to 0.25 (changed to 32 bit in order to use many mods which will not support x64) I am having seemingly random crashes within a few minutes of starting the game. Some textures are also playing up, with the directional nodes on the nav ball flashing between the correct symbol and what seems like 4 symbols in a square rapidly, and parts being translucent compared to the launch pad.

The error report seems to show that I have 0 RAM, although all other games/programs are running perfectly, and my PC specs are:

Intel Core i7-4770K @ 4.2GHz

16.0GB RAM (I am aware 32 bit only makes use of 3.5 )

64-bit Windows 7 Home Premium

NVIDIA GeForce GTX 760

Here is what the error report throws out:

Unity Player [version: Unity 4.5.2f1_9abb1b59b47c]

KSP.exe caused an Access Violation (0xc0000005)

in module KSP.exe at 0023:0038bf96.

Error occurred at 2014-10-23_175232.

C:\Users\Tom\Desktop\KSP_win\KSP.exe, run by Tom.

34% memory in use.

0 MB physical memory [0 MB free].

0 MB paging file [0 MB free].

0 MB user address space [114 MB free].

Read from location 00000004 caused an access violation.

Context:

EDI: 0x00000004 ESI: 0xfb63f144 EAX: 0x03310dc4

EBX: 0x00fcf3e8 ECX: 0xec8f0028 EDX: 0xeccf0028

EIP: 0x0038bf96 EBP: 0x00fcf3d0 SegCs: 0x00000023

EFlags: 0x00010202 ESP: 0x00fcf3ac SegSs: 0x0000002b

Bytes at CS:EIP:

8b 1f 89 77 fc 8b 46 08 81 e3 00 00 00 c0 c1 e8

Thanks to all you helpful people in advance, I'm off to Elite: Dangerous for now!

Edited October 23, 2014 by TheBlazinLoony

[NathanKell]

You have run out of memory (KSP is a 32bit process, and thus restricted to about 3.4GB memory usage, no matter your system RAM). Please remove some part mods, use Active Texture Management (or up the scale= line if you do), or run KSP in OpenGL mode (risky but seems to work for many people).

[TheBlazinLoony]

You have run out of memory (KSP is a 32bit process, and thus restricted to about 3.4GB memory usage, no matter your system RAM). Please remove some part mods, use Active Texture Management (or up the scale= line if you do), or run KSP in OpenGL mode (risky but seems to work for many people).

I have already tried running in OpenGL mode, if anything it crashed more (with the same error). I am also already using texture reducing mods as I was aware I would have issues regarding memory when reverting back to 32 bit.

What I am still confused about is the fact that my memory is displayed as "0 MB", which is not normal and would obviously cause problems like mine, I just have no idea what is causing this. I have tried removing large parts mods just in case, with no success.

[Padishar]

See this thread for a possible cause of this sort of crash, something to do with corrupted fonts making Unity get upset...

[NathanKell]

That's just how they write that error message; no idea why, but that's how it looks for everybody.

[TheBlazinLoony]

Thanks for the info, I shall take a look.

[reschke]

If you are running on full screen try running it at a lower resolution and see what happens. I did that a while back and it at least ran smoother for a while. I can run and load and launch one mission but when I go to return to VAB to launch a second mission the game gives me a CTD and I have to start over. I hate 32 bit for its low memory usage and 64 bit for its lack of support. This is one reason I am installing a Linux partition and going to try 64 bit Linux to see what happens with RAM usage in that version.