Congratulations. Thanks to useless bloat (exploding buildings) 4Gb isn't enuf.

[Fengist]

Complete fresh steam install...

ZERO mods...

DynamicHeapAllocator out of memory - Could not get memory for large allocationCould not allocate memory: System out of memory!

Trying to allocate: 2097152B with 4 alignment. MemoryLabel: STL

Allocation happend at: Line:74 in

Memory overview

[ ALLOC_DEFAULT ] used: 306579775B | peak: 0B | reserved: 336250610B

[ ALLOC_GFX ] used: 155542433B | peak: 0B | reserved: 204820916B

[ ALLOC_CACHEOBJECTS ] used: 66968B | peak: 0B | reserved: 12582912B

[ ALLOC_TYPETREE ] used: 7300B | peak: 0B | reserved: 4194304B

[ ALLOC_PROFILER ] used: 281124B | peak: 0B | reserved: 8388608B

Could not allocate memory: System out of memory!

Trying to allocate: 2097152B with 4 alignment. MemoryLabel: STL

Allocation happend at: Line:74 in

Memory overview

[ ALLOC_DEFAULT ] used: 306579775B | peak: 0B | reserved: 336250610B

[ ALLOC_GFX ] used: 155542433B | peak: 0B | reserved: 204820916B

[ ALLOC_CACHEOBJECTS ] used: 66968B | peak: 0B | reserved: 12582912B

[ ALLOC_TYPETREE ] used: 7300B | peak: 0B | reserved: 4194304B

[ ALLOC_PROFILER ] used: 281124B | peak: 0B | reserved: 8388608B

(Filename: Line: 909)

Crash!!!

[Supernovy]

Try setting texutre quality to half res.

If you can't get to the settings menu, I believe that's "TEXTURE_QUALITY = 1" in the settings.cfg file.

[Fengist]

Try setting texutre quality to half res.

If you can't get to the settings menu, I believe that's "TEXTURE_QUALITY = 1" in the settings.cfg file.

That IS half res.

[Claw]

You might want to try lowering the texture another notch (to 2 or 3) to get it to launch. Once it's launched, you can often get away with bumping the texture back up. I don't know if part of that has to do with how the .NET framework structures things during the first run cycles while it compiles. Also, KSP makes a huge memory grab when the main menu comes up. So if you can get past that, you might be able to safely bump the texture back up. I think part of that memory grab also depends on how high your resolution is set, but I'm not sure on that.

Also, even if you have 4GB of ram, KSP likely doesn't have access to it all because there needs to be a certain amount available for Windows. Check and make sure windows isn't keeping a bunch of other stuff loaded in the background to "help" you out.

In either case, it sounds like Squad is working on managing memory a bit better for the next version. So hopefully that will bring the requirements back down.

Cheers,

-Claw

[Slam_Jones]

I had to tune down a number of settings, but I can run KSP at a decent framerate (and 1920 x 1080) with only 4gB. Try some of Claw's suggestions.

[cantab]

What's your memory usage at before you run KSP? Considering this isn't a more widespread problem, I suspect the bloat isn't in KSP.

[Ruedii]

Are you using a 32bit Windows system, because if you are, KSP has to share it's memory space with all background programs and services. Close some of the background programs, and turn off some unnecessary services.

You could also try loading up in OpenGL mode, because it seems to have a smaller memory profile.

[Fengist]

What's your memory usage at before you run KSP? Considering this isn't a more widespread problem, I suspect the bloat isn't in KSP.

This is a fresh install of Windows 7 as well. No crap running in the background.

[One Wheeled Panda]

32 or 64bit?

32bit does not only limit you to 4GB, address space fragmentation also limits how much of these 4GB can be allocated in one chunk. With the very same preconditions a 64bit system may not produce this error.

Edited November 20, 2014 by One Wheeled Panda

[Sean Mirrsen]

I'm running KSP just fine with an assortment of mods (all Near Future Technologies packs plus Station Parts Expansion, and various supplementaries), on a windows 8 tablet with 4Gb RAM and an integrated GPU. Whatever the problem you're having is, it's not in KSP.

[ratchet freak]

This is a fresh install of Windows 7 as well. No crap running in the background.

even a fresh instal can have a lot of crap running in the background

[cantab]

^ Indeed. It depends on what sort of fresh install. Windows as provided by Microsoft isn't too bad, but the computer maker's "factory reset" will generally load on all the extras that were there originally because the computer maker thinks they're useful.

So as I said, I advise actually checking the baseline RAM usage, see that it's within normal range. For that matter double-check the available RAM. For some context, on my Windows 7 system I'm around 750 MB used with no programs open. (Full disclosure, this is not a system I run KSP on.) The desktop effects can add a little, but if your system is hogging more than a GB you need to look at what's running.

Next, if you've turned off the Windows paging file, turn it back on. This might have an impact, and on a 4 GB system you probably need it on nowadays.

In the wild mass guessing category, try running the game directly, not through Steam.

And on a final note, you can always tell Steam to download .24.2 for you. It's listed under "Betas" slightly confusingly.

[Fengist]

^ Indeed. It depends on what sort of fresh install. Windows as provided by Microsoft isn't too bad, but the computer maker's "factory reset" will generally load on all the extras that were there originally because the computer maker thinks they're useful.

So as I said, I advise actually checking the baseline RAM usage, see that it's within normal range. For that matter double-check the available RAM. For some context, on my Windows 7 system I'm around 750 MB used with no programs open. (Full disclosure, this is not a system I run KSP on.) The desktop effects can add a little, but if your system is hogging more than a GB you need to look at what's running.

Next, if you've turned off the Windows paging file, turn it back on. This might have an impact, and on a 4 GB system you probably need it on nowadays.

In the wild mass guessing category, try running the game directly, not through Steam.

And on a final note, you can always tell Steam to download .24.2 for you. It's listed under "Betas" slightly confusingly.

It's a MS copy of Win 7. Either way. I have no other issues with any other game crashing to desktop REPEATEDLY as a result of memory issues. This has GOT to get fixed on their end. Most people want to play a game, not fiddle with settings or memory usage trying to get it to work.

[Fizwalker]

As others have asked, are you running Win 7 64 bit or Win 7 32bit? (You can find out by going to Control Panel and then System. In the center of that panel is a section labeled System, and it will say what it is next to System Type.)

Since my desktop's power supply died, I've been running KSP .25 on a fresh install of Win 7 64 on an older laptop with integrated graphics and 4Gb (effectively 3Gb after the video card's usage...) of RAM with no issues.

If you are using a 32bit system, then the suggestions posted earlier might help, as well as this http://forum.kerbalspaceprogram.com/threads/92228-Known-Issues-Self-Help FAQ might give you other options to try.

Please keep in mind that this game is still in Alpha (by Squad's own admission it won't get to Beta until .90-- the next update) so fiddling with settings, and finding bugs and glitches are going to be part and parcel of playing this game. Keep trying things and while it might be frustrating as Hades, you'll eventually get it to work.

[Guest]

Congratulations. Thanks to useless bloat (exploding buildings) 4Gb isn't enuf.

The problem is on your end with your machine. Ksp will run on less than 2GB ram with a video card that has 1GB or more of dedicated video memory. If you want to be taken seriously, post your machine specs with screenshots of your applications and processes from the task manager as well as the full output_log and the ksp.log. Otherwise, this smells like a troll post.

[MisterFister]

It's a MS copy of Win 7. Either way. I have no other issues with any other game crashing to desktop REPEATEDLY as a result of memory issues. This has GOT to get fixed on their end. Most people want to play a game, not fiddle with settings or memory usage trying to get it to work.

We've asked repeatedly if you're running a 32-bit version of Windows, or a 64-bit version. Furthermore, are you running a laptop? Sometimes laptops share video and system memory (more likely on a 32-bit system by and large, but not unheard of on 64-bit.)

[ThirdHorseman]

There is something going on with KSP and 32-bit vs 64-bit Windows. Please refer to this post in my support thread.

Two laptops, both with almost exactly the same hardware, except one using Windows7 32-bit and the other Windows7 64-bit. On the 32-bit laptop KSP crashes constantly, just when reverting flights or attempting to launch craft or even loading the game. The 64-bit laptop runs KSP like a dream, even though the RAM used by KSP is MORE and the RAM available to the system is LESS on the 64-bit system.

Remember this is NOT using 64-bit KSP. It looks like you get the best performance when running 32-bit KSP on a 64-bit OS.

[Padishar]

On 32 bit versions of windows a process can only use a maximum of 2GB of memory (actually less than this due to also needing to load the exe and all the non-OS dlls). On 64 bit windows, the same 32 bit program can use 4GB of memory (less the same chunk for exe and dlls). This extra 2GB makes all the difference.

KSP 0.25 on default settings gets so close to the limit on 32 bit windows that it is often impossible to get further than the main menu and, even if you do, the game is highly likely to run out of memory on a subsequent scene switch and crash.

[MisterFister]

For those curious -- the OP on this thread is indeed running a 32-bit system, with 3GB of ram (4GB system memory minus 1GB shared video memory.)

[Talavar]

For those curious -- the OP on this thread is indeed running a 32-bit system, with 3GB of ram (4GB system memory minus 1GB shared video memory.)

Well then it's problem solved. Time for an upgrade!

[anarkhon]

Well then it's problem solved. Time for an upgrade!

Time for redesign the whole game,such as loading stuffs when need.

"Optimize,optimize,optimize"