bernh

No sweat. Happy gaming

I don't know what Minimem does under the hood. If the info about the authors is correct, it was developed by some independent programmers, that do custom software and websites for people. Any tools they develop outside of a contract they put on their website for free download. There are a lot of testing, diagnostic, and fix it apps out there that have been developed because the functionality that is required is not in windows. Seriously guys, I am not employed by them, and gain nothing from mentioning them. If you don't want to try it, don't. I am 43 years old, a trained electronics and computer technician. I have had a computer since I was 9 years old. In all that time, I have only be been hit by 3 viruses. I always have virus scanners and malware scanners going. All I can say is that Minimem worked for me and allowed me to play my heavily modded game when included with the other steps I mentioned.

You are probably running out of RAM, based on the mods installed, but your error log in your dropbox is truncated, and the area that states a RAM problem is missing. I have around 50 mods, some very large ones, and was crashing bad. I could not even get past the loading screen. After a lot of trial and error I came up with this solution. - http://forum.kerbalspaceprogram.com/threads/115069-0-90-Possible-Windows-Memory-Wall-Crash-Workaround This is an alternative to ATM. No guarantee it will work for you, but it worked great for me.

Here's the solution I came up with - http://forum.kerbalspaceprogram.com/threads/115069-0-90-Possible-Windows-Memory-Wall-Crash-Workaround It is similar to what helaeon is suggesting, but I am adding in an extra step in the form of a RAM optimizer. I still couldn't get past the loading screen until I added the RAM optimizer into the mix.

Try this - http://forum.kerbalspaceprogram.com/threads/115069-0-90-Possible-Windows-Memory-Wall-Crash-Workaround I could not get past the loading screen due to the mods I had installed. Now I play with my RAM maxing at less than 50% of the limit, but still have all my mods and a few more added since I came up with this method.

install your game in 32bit and use the method I used here - http://forum.kerbalspaceprogram.com/threads/115069-0-90-Possible-Windows-Memory-Wall-Crash-Workaround I had enough mods installed that I could not get past the loading screen due to the 32bit RAM limit. I can now play the game with all my mods, and even a few more since I posted this workaround, and my RAM usage peaks at less that half of the 32bit limit.

Based on your logs, it looks like you are running out of RAM. Instead of using ATM to manage your textures, as your logs suggest, try using the method I posted here - http://forum.kerbalspaceprogram.com/threads/115069-0-90-Possible-Windows-Memory-Wall-Crash-Workaround I too was using ATM, but with all the mods I had installed, ATM was not able to manage all the textures and still keep them high enough quality to look good. After much trial and error, I came up with the workaround I posted in the link above.

I agree that Minimem is a bit old, but it works, and, as an Electronics Technician and Computer Technician for the last 20 plus years, I am a firm believer in the old saying, "If it's not broke, don't fix it." You don't need to install .NET 2.0, as long as you have a newer version. I personally have .NET 4.5. It has not raised and flags with AVG or Malwarebytes. I didn't jump to Minimem right away myself. After I did the other steps, and was still hitting the RAM wall, I looked for a RAM optimizer, actually trying several different ones, but Minimem is the one that worked, and unlike all the others I tried, it lets you target a specific process, instead of only working globally. Essentially, it was the last step I tried, after realizing that the other steps, while definitely helpful, were still letting the textures to keep a footprint in RAM, and while smaller than the non-DDS footprint, was still large enough to keep me from running the game. If you are happy without having to resort to the RAM optimization step, there is no need to do it.

Hey Everyone, I may have a workaround for the dreaded 3.6GB-3.7GB memory wall in Windows when running KSP 32bit First a little background in case it makes a difference. My system: i5-2320 running at 3GHz 8GB RAM Intel DZ77GA-70K nVidia GT610 2GB Graphics Card driving 2 monitors at 1280x1024 each Motherboard/CPU Intel graphics running a third monitor at 1024x768 Windows 7 Ultimate x64 SP1 KSP 0.90.0.705 49 mods installed, including some large ones like B9 Aerospace, KW Rocketry, Alchemy Labs, Karbonite, Regolith, KAS, KSO, KAX, MKS and OKS to name a few. I was at a point where the game would not load, crashing about 80%-90% through the loading progress bar. I now have the game running, with a RAM footprint of about 1.2GB sitting in the SPH or VAB. This is what I did: In the launcher settings -Terrain Detail default -SM3 Terrain Shaders Enabled -Terrain Scatters Disabled -Render Quality Good -Texture Quality Half Res -Fallback Part Shaders Disabled -Aerodynamic FX Quality Normal -Screen Resolution 1280x1024 (my monitor's native resolution) -Full Screen Disabled -Anti-Aliasing Off -VSync Every VBlank -Frame Limit 80FPS Installed ddsloader - http://forum.kerbalspaceprogram.com/threads/96729-0-90-DDSLoader-1-9-%28Mar-9%29-Loads-DDS-Texture-Boringly-fast-edition Installed KSP to DDS Texture Converter - http://forum.kerbalspaceprogram.com/threads/98672-WIN-KSP-to-DDS-texture-converter Ran the texture converter on the GameData folder picking 1/2 resolution for the conversion Created a shortcut to start KSP using the -force-opengl -popupwindow switches Installed a RAM optimizer called Minimem - http://main.kerkia.com/products/minimem/download.aspx With the Minimem GUI open, I set it to optimize every 30 seconds, and disabled the two options for Do not optimize the foreground process and Do not optimise if overall RAM available is above... I ran KSP using the created shortcut, then found the KSP process in the right hand side of the Minimem GUI and added it to the optimize list on the left side. Correct me if I'm wrong, but from what I have read, using ddsloader allows KSP to use the dds textures made by KSP to DDS. The force-opengl switch allows those textures to be loaded onto the RAM on the graphics card. The Minimem application then releases the RAM that those textures used while they were making their way to the GPU, but since they are now on the GPU they are no longer needed in RAM. I have been running this setup for 5 or 6 days now with great success. I have not played around with my settings much beyond what I have outlined, so feel free to experiment if you want to try this approach. One thing to note though, is that if you install any additional mods after the initial setup, you will need to re-run the KSP to DDS converter to convert the new textures. Happy Gaming!