totm jan 2022 Cant play kerbal right now! GPU crashing

[Lisias]

20 minutes ago, Noobi said:

I have gpu on maximum performance already

Check the "Event ID 14 nvlddmkm"  stunt. It's the only option left at this moment.

[Noobi]

41 minutes ago, Scarecrow71 said:

@Noobi

I also would like to ask if you have tried a different video card/GPU on your machine?  Do you have the capability of taking this GPU and trying it on a different machine?  I know, I'm still focused on a hardware issue here; I'm just trying to (hopefully) eliminate all the problems I can!

I have an old Msi nvidia N1996 Gpu but it's so old that i can't use it, so no i haven't

Unfortunately i don't have any other PC:s to test gpu on

[Noobi]

 

30 minutes ago, Lisias said:

Check the "Event ID 14 nvlddmkm"  stunt. It's the only option left at this moment.

On event ID 14 there are events named "Wininit" what is system event apparently 

[Noobi]

On 11/10/2021 at 9:43 PM, Noobi said:

When i start up kerbal it works perfecly, but when i am in editor gpu is at 40% usage and cpu 30% which is normal

When i hit launch and go to simulation/playing mode my gpu rises to 60% usage and cpu is still 30%, but then when i start to fly (plane or rocket) my gpu goes to 96-99% usage and cpu to 35% and then my gpu just straight up crashes

Before there were no problems but randomly this started happening idk what to do (before gpu was at max 55% when flying at hight speeds near ground)

what i know

- My gpu is 63 celcius when playing so its not overheating and cpu is 55c and ram is at 50%

- I restored to older Nvidia driver and it still crashes

- I tried to lower graphics, it decreased gpu usage but  still it crashed

- All other games working perfectly, just ksp

- When gpu crashes i still hear sound of the game but all my pc fans ramp up to max idk why, then i have to restart my pc

- Done fresh install and tried multiple graphical settings, no difference

Specks

- Ksp graphics are at nearly lowest and no mods

- Asus rog strix RTX 2060 super

- Amd ryzen 5 3600 (3.6ghz)

- 16GB ram (3200mhz)

- Asus rog strix B450-F GAMING motherboard

- Game installed on samsung SSD

- Windows 10 (21H1) newest updates installed

Thank you for helping

From Freezing cold Finland

 

player. log (google drive)

https://drive.google.com/file/d/1i0Wdfdyj3hk61Dsa6bBT6U4J0OClAi73/view?usp=sharing

!!!

So i disabled highlight FX and lowered my anti aliasing settings from 8x to 4x

I tested a different plane and NO problems WHAT! I played for 2 hours and nothing

When i fly my VTOL aircraft my gpu is still at 80% but its probably because of  the 12 juno engines that are lifting it and their surface effects

But no crashes at all

I deleted that one plane that was crashing my gpu 

why is it now working ?

- lowered settings

- windows or steam fixed something

- that one plane was "corrupted" ? (it has just 50 pieces and 6 engines, so its not even big)

I will send new messages if it crashes again

 

Thanks for people who helped (Kapitalizing Every Word, Proxbi Kerman, Staticalliam7, Scarecrow71, Lisias, ColdJ, AtomicTech

 

 

Edited December 8, 2021 by Noobi
i forgot something

[Noobi]

On 12/8/2021 at 11:17 PM, Noobi said:

!!!

So now i know what it is, its effect count

My gpu's vram just can't handle too many engines

i have 8gb vram but its not enought for ksp

So to fix

- lower settings

- don't use too many engines, lights or decouplers

 

Thanks for people who helped (Kapitalizing Every Word, Proxbi Kerman, Staticalliam7, Scarecrow71, Lisias, ColdJ, AtomicTech

 

 

 

[Noobi]

19 hours ago, Noobi said:

 

but its still weird

because, before i could make huge planes without crashes

so my ksp is till broken, but now i know how to bypass it

[Lisias]

19 hours ago, Noobi said:

so my ksp is till broken, but now i know how to bypass it

Interesting! How do you bypass the problem? This can help to understand what's happening….

[Noobi]

On 12/12/2021 at 2:09 PM, Lisias said:

Interesting! How do you bypass the problem? This can help to understand what's happening….

It just randomly got fixed idk, sorry