Does Paging File CTD mean "too much memory use" ?

[Cassin]

Hello,

 

I have a heavyly modded KSP (70+ mods), but with OpenGL, ATM and Dynamic Texture Load, the game works "fine" (OpenGL make it slow, even with small part count ships) ; but every few hours (or sometime only minutes), I've got a CTD, mostly when changing scene (KSC screen to VAB, VAB to KSC, landed ship to KSC after recover, etc...). Each time the cause in the error log is the same : out of Paging File Memory :

 

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

Error occurred at 2016-02-12_153012.
D:\Jeux\steam\steamapps\common\Kerbal Space Program\KSP.exe, run by Cassin.
66% memory in use.
0 MB physical memory [2715 MB free].
0 MB paging file [0 MB free].
0 MB user address space [116 MB free].
Write to location 00800000 caused an access violation.

 

It's always the same, for ALL the CTD. But in the same time, the Task Manager opened on my second screen show a memory usage for KSP.exe barely above 1.5 Gb, sometime even below 1 Gb. (I'm running on Windows 10)

 

So I wonder, does this mean that the game hasn't enough memory in his 32 bits limitation, or is this something completly different ? Is there any way to monitor this Paging File thing, or to make it use another memory page (as there is still place in physical memory) ?

 

 

 

Thanks

[Benoit Hage]

Paging file or Swap (if in Linux) is an extension of your RAM on your hard disk drive. From the figures shown above, you are clearly reaching the limit of memory KSP.exe can use. Indeed, 70 mods is quite a big number. Try to get rid of some parts and/or mods you don't need. Or wait a bit until 1.1 is out.

[Cassin]

I tought indeed this was a sort of buffer. I suppose there's no way to set it to a bigger size, some people should have already found how ^^

 

I have the game paused the last 6 months in waiting for 1.1 but I cannot wait anymore

I even tried the workaround for 64 bits on Windows, the game is gorgeous with HD uncompressed texture, and I have no more CTD but freezes instead ^^ (mostly when touching ground) So I reverted back to 32 bits  So yeah I suppose I'll need to cut in the mods. Some are just here for testing purpose, anyway.

 

Thanks

[ve7oko]

256 GB RAM sticks are the answer. Need at least two...

[Cassin]

Won't be a great help as the game will still stick to is 3.5 Gb limit

[Tex_NL]

11 minutes ago, ve7oko said:

256 GB RAM sticks are the answer. Need at least two...

Not true.

Damn. this is the FOURTH time in less than 15 minutes I spot you spewing this crap. You really have no idea what you're saying, right?

[rudi1291]

Since i installed Windows 10 (64bit), it behaves a bit weird: when a 32bit process (like KSP) gets close to 3.5GB, windows shifts about 2GB over to a system process. The process itsself shows 1-1.5GB ram usage... No idea why windows does that, KSP crashes anyways.

[Cassin]

Same for me. Win10 has a weird way to determine RAM usage than Win7 had.

But at the end, I always get crashing with this paging file thing, never with the physical memory. And it always happen on a change of scene. If I have to test a new rocket and going back and forth between VAB and flight, it's almost certain that I will crash within 15 minutes. When I was testing my Remote Tech layout on sandbox, teleporting satellites with HyperEdit (means a lot of changes between flight to KSC to VAB), it was within 5 minutes. But if I run a long mission, I can play for hours without crash.

 

It makes me wonder if there can be a sort of memory leak on the loadings.

[rudi1291]

Looked a bit around, its Windows´ ´memory compression' feature. http://www.tenforums.com/windows-10-news/17993-windows-10-memory-compression.html