Ok - seriously ... is the problem and how do I fix it (or can I even)?

[Iam aspaceman]

Wall of text trying to understand - I am a bit noobish, so please bear with me...

First off - I have read the support instructions and have asked individually for much/all of this, but so far I haven't seen or gotten straight answers. I am going to highlight my main questions to try to understand this and see if there is a workaround.

I have a modded install and running win 7 64 bit, it crashes straight to windows with no messages or anything. It started when I was trying to land on Eve and it would crash within 20km of the surface every time. I only had the mods Kerbal engineer and mechjeb. So I came here posted the logs, etc....and nada, nothing. Just a whole bunch of views no replies (I even tried to reply to add more information and it wouldn't post it...hmmm). So I went through the posts and saw that 60%-70% of the posts were about the same thing just happening in different points or actions in the game. The common reply was "we can't help because you didn't post the correct information". they would post the correct information and the next reply was either nothing or "you ran out of memory"...then at that point everything gets a bit disorganized in that out of the different posts, people were given slightly different advice depending upon who was answering. As far as I can tell, nobody from Squad has ever answered or given solutions to try. If I am wrong - please link the information.

The point of this isn't to whine or cry but to try again to get a solid answer as to what is going on and what to do about it, because KSP is getting unplayable and that makes me sad.

Milestones and Steps taken:

1. Game has been pretty buggy from day one with no mods installed.

2. I installed KE & MechJeb because, hey, it was already buggy so why not try these?

3. Computer Crash upon trying to land on Eve

4. Posted on Forums - no love...so went looking and searching for help.

5. Discovered CKAN

6. Uninstalled the mods and reinstalled using CKAN, installed Active Texture Management in aggressive mode made modules turn black.

7. Was able to land

8. Still random crashes and the further I go or more complex the more it crashes...

9. Why hasn't Unity 5 been implemented yet? Isn't that going to help?

So, system info:

OS Name Microsoft Windows 7 Professional

Version 6.1.7601 Service Pack 1 Build 7601

OS Manufacturer Microsoft Corporation

System Type x64-based PC

Processor Intel® Core i7-4790K CPU @ 4.00GHz, 4001 Mhz, 4 Core(s), 8 Logical Processor(s)

Installed Physical Memory (RAM) 16.0 GB

Total Physical Memory 15.9 GB

Available Physical Memory 12.6 GB

Total Virtual Memory 31.7 GB

Available Virtual Memory 27.3 GB

Page File Space 15.9 GB

First Major Question: Are my problems (running out of memory) mostly due to having windows 7 64bit OS?

If so, seriously? Doesn't that affect a large portion of the KSP community?

Second: By switching to a 32 bit OS would that help even with modded installs?

I have an Nvidia GeForce GTX 980 4 GB VRam card

3rd: Is my Graphics Card part of the Problem?

I ask this because I am seeing some of the postings refer to problems caused by these cards.

Some of the Postings recommend placing the " -force-d3d11" in the command line

Some of the posts refer to placing other things in the command line.

When the game starts up GCmonitor shows me using 2.4gb memory - and that is at the startup screen...it get worse from there...

People - please help me to understand what is going on - if I can make this game playable...great, if not, then I will walk away wondering how this manages to get a 98% approval on steam when it doesn't run well (I have had issues from day one w/ vanilla install...so keep those comments to yourself - not helpful)

I can and will post error logs but they all say:

Unity Player [version: Unity 4.6.4f1_99f88340878d]

mono.dll caused an Access Violation (0xc0000005)

in module mono.dll at 0023:1011940a.

Error occurred at 2015-06-13_175810.

C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP.exe, run by Scott's.

41% memory in use.

0 MB physical memory [0 MB free].

0 MB paging file [0 MB free].

0 MB user address space [121 MB free].

Write to location 00800000 caused an access violation.

Context:

EDI: 0x00400000 ESI: 0xabbcf190 EAX: 0x00010000

EBX: 0xb695b4a0 ECX: 0x00800000 EDX: 0x00000000

EIP: 0x1011940a EBP: 0x0017dc00 SegCs: 0x00000023

EFlags: 0x00010206 ESP: 0x0017dbdc SegSs: 0x0000002b

Mods Currently installed:

.

[11of10]

"0 MB physical memory [0 MB free].

0 MB paging file [0 MB free].

0 MB user address space [121 MB free].

Write to location 00800000 caused an access violation."

There you have it. Out of available RAM for the game. Maybe a heating/PP-something-something bug? Try looking for a mod that disables stock temperature gauges that appear when a part is overheating, or just remember to always press F10 when you start your mission.

Also, we can't see the mods you use since you linked to a location on your computer, you have to host it someplace (some web site for hosting images) and then link from there.

Damn... I can't remember how the option in settings is called. I believe it dissapears when you disable antialiasing in game tho.

Edit: PPFX

Edited June 14, 2015 by 11of10

[smjjames]

"0 MB physical memory [0 MB free].

0 MB paging file [0 MB free].

0 MB user address space [121 MB free].

Write to location 00800000 caused an access violation."

There you have it. Out of available RAM for the game. Maybe a heating/PP-something-something bug? Try looking for a mod that disables stock temperature gauges that appear when a part is overheating, or just remember to always press F10 when you start your mission.

Also, we can't see the mods you use since you linked to a location on your computer, you have to host it someplace (some web site for hosting images) and then link from there.

Damn... I can't remember how the option in settings is called. I believe it dissapears when you disable antialiasing in game tho.

Was there a point in making your text light grey?

[11of10]

I don't know how it happened, fixed it now. Weird. I use custom page colours, so I didn't even notice it until now.

[Iam aspaceman]

http://imgur.com/l9Dqgqv

GCmonitor starts at 2.4 Gb and I won't touch a thing and it will slowly increase to 2.9 Gb...then crash or freeze.

[11of10]

Did you try to completely reinstall the game from Steam? Does any other software on your computer make any problems?

Do you use, and if so which, antivirus software?

A bit of a poke in the dark: Are you using your administrator account or just a regular user account to play?

Overall, No, x64 Windows shouldn't be a problem not even remotely. (Don't think of installing x32 Windows on a computer with 16GB of RAM, you'd be wasting about 13GBs of it then.) Your computer is to all my knowledge very good. No GPU issues that I can think of, KSP isn't really too heavy on GPU anyway.

Forcing DX11 or OpenGL wouldn't really help much.

Have you tried the antialiasing thing I mentioned before, or disabling PPwhatever and thermal gauges?

[Lumaan]

There are 2 mods that help with the temperature memory leak when in flight by auto disable it, so you don't have to remember to press F10 or F12 every time:

Temperature Gauge Killer http://forum.kerbalspaceprogram.com/threads/120731

DisableTempGauges http://forum.kerbalspaceprogram.com/threads/116034

And you only need one of them.

[Iam aspaceman]

I just uninstalled, cleaned out the directory and reinstalled the game, reloaded the mods, and dropped my save game folder into it. I opened the game and GC monitor started at 2.1gb and when I quit it was up to 2.7 Gb. However, I quit before it crashed or anything. The common denominator were the mods and the existing save game.

No AV software on this build - this is my gaming computer so decided to go commando.

Admin account I assume - how can I verify that?

Next step is the anti-aliasing thing...do I do all of that from the settings menu?

[11of10]

Well, just hit the ppwhateveritiscalled to disable it. I tossed in AA for good measure only, it seems disabling AA also disables PPFX (had to check up the name!).

Have you tried without mods after reinstall? Backup your save game, in case any of your craft is unloaded for lack of parts, and try that maybe. Or maybe try a completely new save as well?

[Iam aspaceman]

I disabled PPFX and the anti-aliasing - no change

I tried a clean install with no mods - same thing happens, just starts off at a lower memory so would take a lot longer.

Here is what I have noticed - the memory used increases 75-100 Mb every time I change scenes. So for instance:

brand new game, career mode, normal difficulty, AA and PPFX off, starts off using 2.1 Gb memory

I switch to the admin building (keep in mind I am not doing anything except changing scenes) - 2.175 Gb

Switch to Space Center scene - 2.25 Gb

Switch to VAB - 2.3 Gb

Back to SC - 2.4 Gb

SPH - 2.45 Gb

...and so on.

If I stay in one scene and there is no (or very little) change in memory used. So I can build a rocket, unbuild it, redesign and rebuild it, no change in used memory...as soon as I go to launch it, +100 Mb memory used, I recover it, +75 Mb, I head back to VAB, +75Mb...

Edit - when I switch menus for the various modules in the VAB it also adds to the memory used count - just not as much

Edited June 15, 2015 by Iam aspaceman

[11of10]

Well, either you've uncovered a new bug, and a very nasty one, or something is wrong with your particular system.

However, with this I'm going out of my depth.

Can you at least scan for viruses, and maybe check your drivers, directX and similar?

Oh, a long shot I guess, but maybe try to disable AA in the nVidia control panel?

BTW, that thing with kicking you out with changing scenes is happening to me at the moment as well. Takes a while, and it's a heavily modded game with some big craft being constantly reverted for some fine tunings, but it's a third time since 18 hours ago.

I guess it's contagious! xD

[Iam aspaceman]

So I went to the NVidia GeForce Experience Panel - KSP is listed and I optimized my settings - just to see what would happen...

2.4 Gb on startup and slow increase in memory used (like before) but no crashes up to 3.35 Gb or so at which point I am exiting. It hasn't crashed since I optimized settings but I haven't been doing anything complicated and it is a new game (trying not to ruin my old one if I can help it). But - the memory used increases with each screen change as before. Is this normal?

I will probably sit and play till it crashes (or not) to see the limits, but my understanding is that point is 3.5 Gb, correct?

BTW - no viruses or malware. I have VP software loaded but it isn't on 24/7 - I have to start it, upload latest profiles and scan.

But back to my original post - this memory crash isn't isolated to just me. So what is the fix? A lot of people are having this happen and I suspect it is similar to my experience.

[ExEvolution]

Well, either you've uncovered a new bug, and a very nasty one, or something is wrong with your particular system.

However, with this I'm going out of my depth.

Can you at least scan for viruses, and maybe check your drivers, directX and similar?

Oh, a long shot I guess, but maybe try to disable AA in the nVidia control panel?

BTW, that thing with kicking you out with changing scenes is happening to me at the moment as well. Takes a while, and it's a heavily modded game with some big craft being constantly reverted for some fine tunings, but it's a third time since 18 hours ago.

I guess it's contagious! xD

Not a new issue, this has existed for ages

Every time you load or unload the VAB or SPH, memory usage increases. In heavily modded installs, this eventually causes a crash due to memory usage on Windows. This also occurs on other OS builds, but because they are lucky enough to have 64 bit builds, their memory usage is allowed to grow and does not cause crashes.

This bug has existed since at least version 0.21, I became very fond of it on my stream with KSPI, B9, and KW rocketry, Remote Tech, FAR, and Deadly Reentry with other various mods strewn about. A high memory base install that could only load the VAB 2 or 3 times before crashing.

[11of10]

Well, a fix, sort of, might be to switch to community hack for x64, but that comes with it's own set of issues. It's much better than before, but still has bugs of it's own. At least it'd take longer to get too big a RAM footprint

PS thx ExEvolution, had no clue about that bug.

[eightiesboi]

Some suggestions:

Remove ATM. Yes, it once was a godsend, but now it doesn't help as much as you might think and there are other things you can try to get your system stable. Once it is stable, if you want to try re-enabling ATM, try the basic version first.

Use the following launch options in Steam for KSP: -popupwindow -force-opengl

Remove Texture Replacer and any mods that utilizing it. CKAN will help you here.

The behavior you mention with memory usage going up for each screen change is well-documented. At the present time, the best work-around is monitor your usage and restart the game before you are going to crash. I am hopeful that Squad will address this issue eventually.

Good luck!