Random crashes modded or not modded

[Chocolat Oreos]

I play the game and it randomly crashes during fun missions and i have to do the whole mission all over again...

 

output.log: https://www.dropbox.com/s/bl0sa5bc205rib5/output_log.txt?dl=0

Edited July 28, 2016 by Chocolat Oreos

[sebi.zzr]

2 hours ago, Chocolat Oreos said:

I play the game and it randomly crashes during fun missions and i have to do the whole mission all over again...

 

output.log: https://www.dropbox.com/s/bl0sa5bc205rib5/output_log.txt?dl=0

You're playing 32 bit version,so you probably running out of ram.
As a side note,you also use mods(some of them are quite ram hungry),so next time you need to post this in modded support.

[Chocolat Oreos]

but my -force-opengl glitches out completely, where i can't see the ground when launching a rocket ( ͡° ͜ʖ ͡°)

and the same happens on 64 bit ksp, idk anymore...

[sebi.zzr]

15 hours ago, Chocolat Oreos said:

but my -force-opengl glitches out completely, where i can't see the ground when launching a rocket ( ͡° ͜ʖ ͡°)

and the same happens on 64 bit ksp, idk anymore...

Well,the main question remains,how much of physical memory(RAM)you have?
My 64bit SRSS instal starts with 4,6GB,and i can play for hours without crashing,actually the game didn't crash at all since 1.1.X,but i have 8GB of physical memory.The 32bit version can only use around 3,5GB RAM before crashing.
It is known issue with Unity(garbage collection),and it gets worse with every scene change.With forcing openGL or DX11,some of the physical memory get allocated to graphic cards VRAM,but the result depends mostly on hardware capabilities and its drivers.The older AMD cards dont handle openGL well.
I remember reading on the forums,that AMD owners used "-force-glcore "(Make the editor use OpenGL 3/4 core profile for rendering. The editor tries to use the best OpenGL version available and all OpenGL extensions exposed by the OpenGL drivers. If the platform isn’t supported, Direct3D is used.)

You can also check the forum,the question about crashing is quite common if not the most.But like i said at the end it's mostly dependent from hardware itself.

[Chocolat Oreos]

2 hours ago, sebi.zzr said:

Well,the main question remains,how much of physical memory(RAM)you have?
My 64bit SRSS instal starts with 4,6GB,and i can play for hours without crashing,actually the game didn't crash at all since 1.1.X,but i have 8GB of physical memory.The 32bit version can only use around 3,5GB RAM before crashing.
It is known issue with Unity(garbage collection),and it gets worse with every scene change.With forcing openGL or DX11,some of the physical memory get allocated to graphic cards VRAM,but the result depends mostly on hardware capabilities and its drivers.The older AMD cards dont handle openGL well.
I remember reading on the forums,that AMD owners used "-force-glcore "(Make the editor use OpenGL 3/4 core profile for rendering. The editor tries to use the best OpenGL version available and all OpenGL extensions exposed by the OpenGL drivers. If the platform isn’t supported, Direct3D is used.)

You can also check the forum,the question about crashing is quite common if not the most.But like i said at the end it's mostly dependent from hardware itself.

I might aswell give al my specs: 

AMD A6-5400K APU clocked at 4.3 MHZ with Radeon(tm) HD 5450 Graphics, GPU clocked to 700 MHZ, memory clocked to 900 MHZ with the fan at 100%

1 gigabyte of VRAM and 8 gigabytes of DDR3 ram.

[radonek]

I have enough memory (64bit binary on 8G) yet ksp crashes on me all the time since 1.1. I actually managed to get KSP pacified by OOM killer yesterday for the first time ever (by running memory hungry chrome build in background) and believe me, it behaves very different from usual segfault. But its nice to know we have another Universal Answer To Every Problem.
 

[Chocolat Oreos]

13 minutes ago, radonek said:

I have enough memory (64bit binary on 8G) yet ksp crashes on me all the time since 1.1. I actually managed to get KSP pacified by OOM killer yesterday for the first time ever (by running memory hungry chrome build in background) and believe me, it behaves very different from usual segfault. But its nice to know we have another Universal Answer To Every Problem.
 

It's not my ram, ITS NOIT MY RAM, MY RAM IS FINE; it doesn't even turn yellow in the task manager and it doesn't crash when reaching a cap; i was doing the burn i do to test this (2000 deltaV on my spaceplane to jool) it crashed but the cpu was fine, the Ram was all cool so it has nothing todo with that; IT JUST get CRASHES AT RANDOM TIMES and it's so frustating

 

oh, and chrome only uses 50 mb out my 8G 64bit binary...

Edited July 29, 2016 by Chocolat Oreos

[JPLRepo]

Yeah, looking at your log, you should probably try running 64 bit KSP instead instead of 32 bit. Then KSP can use all of your RAM and stop running out at the 32 bit limit.

[Chocolat Oreos]

meh, you know what i did, still crashed... oh, and ksp used 1.3 gigabytes at the max, so it's not because of running ksp in a 32bit system.... because in a 32bit system apps can only use 1 gb of ram and when a ram crash happens; it should say: game crash, out of memory...

Edited July 29, 2016 by Chocolat Oreos

[Chocolat Oreos]

I also have an output.log for the random 64x crashes...

https://www.dropbox.com/s/bl0sa5bc205rib5/output_log.txt?dl=0

 

task manager also not giving any weird out of memory crashes http://prntscr.com/bz2phq (this is on an unmodded install with the crashspaceplane called: ( ͠° ͟ʖ ͡°))

Edited July 29, 2016 by Chocolat Oreos

[sebi.zzr]

Can you post KSP.log from ...KSP_win when crash happens,and maybe "crash report"?

[Chocolat Oreos]

https://www.dropbox.com/sh/bk9qwsl56xunh3s/AADoHh9LmcecpkfoopE5-2pXa?dl=0 crash report from earlier

But i just played without any crashes and closed the game and looking at the KSP.log everything seems normal and maybe you can see the ragequit in there too ( ͡° ͜ʖ ͡°)

https://www.dropbox.com/s/38q1hwd6hz96xlw/KSP.log?dl=0 KSP.log

 

[JPLRepo]

Well if you are so insistent on saying you are running 64 bit KSP why are you supplying logs that are from 32 bit KSP?
Your log:
[KSP Version]: 1.1.3.1289 (WindowsPlayer) ====================================

If you were running 64 bit it would say:
[KSP Version]: 1.1.3.1289 (WindowsPlayer) (x64) ==============================

Sorry but either you are NOT running 64 bit, or you are supplying the logs from the WRONG folder.

Here is how it works:

KSP.exe - if you run that - it's 32 bit.
KSP_X64.exe - if you run that - it's 64 bit.
32 bit logs are in \GameData\KSP_Data
64 bit logs are in \GameData\KSP_X64_Data
 

...and the crash in your log confirms you are running 32 bit KSP.exe:
Crash!!!
SymInit: Symbol-SearchPath: '.;C:\Users\hugob\Desktop\KSP_win;C:\Users\hugob\Desktop\KSP_win;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'hugob'
OS-Version: 10.0.10586 () 0x300-0x1
C:\Users\hugob\Desktop\KSP_win\KSP.exe:KSP.exe (00DC0000)
 

and 32 bit RAM limit is NOT 1GB as you claim. Do the maths. It is 2^32=4GB
 Under 32 BIT you will usually run out of RAM anywhere between 3-4GB running KSP.

If you are going to continue raging and not listen to advice, I'm done.

Edited July 29, 2016 by JPLRepo