KSP not launching

[Serivitus]

Error.log : http://pastebin.com/0tvn7Hwf
Output_log : http://pastebin.com/GCrKJH2i

PC's just an Intel Core2Duo E5500 @2.8GHz on a G41-M Combo motherboard. No external GPU, about 4 GBs of RAM on a 32 bit OS.
It worked fine and then this started happening. Program launches, I see the resources loading in and when the bar's entirely filled up, the program exits. No dialogue

Edited June 7, 2016 by Serivitus

[sal_vager]

Quote

d3d: failed to create 2D texture id=2777 w=1024 h=1024 mips=11 d3dfmt=21 [out of memory]

UnloadTime: 19.509535 ms

Crash!!!

This is in the logs, it suggests your graphics chip is the cause, if KSP ran before this then it's possible a driver update has caused it and it can be rolled back.

[Serivitus]

I updates my driver, didn't work. Dont know how to rollback. It's a G41 Express chipset

[sal_vager]

You could try another driver from here.

And try deleting your settings.cfg file to reset the graphics in KSP, as your screen is set to an unusual resolution of 1024 by 1024

If KSP worked before it should be working now, which suggests an issue with your computer not KSP.

[Padishar]

18 hours ago, sal_vager said:

This is in the logs, it suggests your graphics chip is the cause, if KSP ran before this then it's possible a driver update has caused it and it can be rolled back.

It doesn't suggest that at all.  It simply says that the video driver failed to allocate memory for a texture and the game crashed shortly after...

51 minutes ago, sal_vager said:

And try deleting your settings.cfg file to reset the graphics in KSP, as your screen is set to an unusual resolution of 1024 by 1024

Again, no it isn't.  That is just the size of the texture that the video driver was trying to allocate, it has absolutely nothing to do with the screen resolution which the log file clearly shows is set to 1366x768.

 

On 6/7/2016 at 6:41 AM, Serivitus said:

PC's just an Intel Core2Duo E5500 @2.8GHz on a G41-M Combo motherboard. No external GPU, about 4 GBs of RAM on a 32 bit OS.

This is the important bit.  The game can only use a maximum of approx 1.7 GB of memory on 32 bit windows and it is simply exceeding this amount and crashing.  You will need to do something to reduce the memory usage.  The first thing you should try is to find the TEXTURE_QUALITY = line in the settings.cfg and change the number at the end to 3 which will change to using 1/8th resolution textures.  If the game starts then you may be able to increase this in the settings screen in KSP.

The most likely cause of your game working and then stopping working is that the settings file became corrupted at some point and this has caused KSP to use default values, including a texture quality setting that is too high for your system.

This line in your logs is also somewhat concerning:

[KSP Version]: 1.0.5.1024 (WindowsPlayer) ====================================

This was the original version of the 1.0.5 release before it was quietly patched.  The "correct" version for 1.0.5 should be 1.0.5.1028.  However, this would also be out-of-date as version 1.1 (and 1.1.1 and 1.1.2) has been released since then.  Whether you want to use 1.0.5 or 1.1.2, you should download a new version from GOG...

[sal_vager]

9 minutes ago, Padishar said:

This is the important bit.  The game can only use a maximum of approx 1.7 GB of memory on 32 bit windows

 

I really, really do not think this is the case, at all, considering that KSP has used more memory than that for other players before now, even on 32bit systems.

Serivitus says he had KSP working, so this is not likely to be as simple as you believe.

Now, until we hear back from Servitus and can find out if he had any luck we're not going to know, as unless you didn't notice he's using a 10 year old gpu.

@Serivitus, can you please run dxdiag and save the hardware report and post the report to pastebin.

[Padishar]

4 minutes ago, sal_vager said:

I really, really do not think this is the case, at all, considering that KSP has used more memory than that for other players before now, even on 32bit systems.

The log clearly shows that this is an out-of-memory problem (just like it clearly shows his screen resolution and what GPU he has).  KSP can sometimes use very slightly more than 1.7GB on Win32 (e.g 1.8GB of "commit size") but any more is totally impossible (without tweaking the Windows boot-time option that increases the address space available to user mode processes and this is likely to cause other issues and is not a good solution).

8 minutes ago, sal_vager said:

Serivitus says he had KSP working, so this is not likely to be as simple as you believe.

Yes, I know that, my reading comprehension skills are really quite good.  This is why I wrote:

17 minutes ago, Padishar said:

The most likely cause of your game working and then stopping working is that the settings file became corrupted at some point and this has caused KSP to use default values, including a texture quality setting that is too high for your system.

 

[sal_vager]

Or it could have been a Windows driver update, which are not always reliable, also...

[Padishar]

20 minutes ago, sal_vager said:

also...

Why have you posted this?  In what way is that page at all relevant to either the OPs problem or anything I wrote?  If you think the bit that says "can directly access at most 4 GiB of byte-addressable memory" supports your argument then you are mistaken.  It clearly states "(though in practice the limit may be lower)", which in the case of 32bit Windows operating systems, it is.  User mode processes can only address 2GB of memory.  The exe and all the (non-system) DLLs it uses are included in this 2GB so the amount of memory that can be allocated is significantly less than 2GB.

I have been a professional computer programmer for over 23 years and was a highly talented and knowledgeable amateur for the ten years before that.

 

[sal_vager]

Well I learn something new every day, as a Linux user I've not run into a 2 gig memory limit for a long time, and little things like this can be missed

It's a wonder any Windows player has managed to play KSP on a 32bit version of Windows at all...

Still, Serivitus says it worked, so if nothing else changed I'd expect it to still work, so we still need more info here than just saying it's out of memory, it's out of memory why?

[Serivitus]

Thank you all for your quick (and detailed) response. I deleted the settings.cfg file and restarted KSP. It's working now
Set all my graphic settings to the lowest, so it shouldn't bother me anymore. Turns out, I was playing around with the graphic settings a bit before KSP stopped working
Again, thanks a lot, guys!