random but always crash on 0.90

[jnops]

Hello,

Since 0.90 I cannot play without having crash to desktop.

I am not sure it is only for 0.90, I have not played since 1 month, but have been playing since Aug. 2013

I have tried clean installs, clean unzip, x32, x64 and always have a crash.

crash to desktop always during flying.

Sometimes it takes 1 minute of flight to crash, sometimes more. but always a crash.

I have only tried sandbox.

Here are the files for a crash, after clean unzip, flying stock Stearwing D45 and also dxdiag output :

https://drive.google.com/folderview?id=0B2hvhZvnVoTYU0FTM3dtVkJISW8&usp=sharing

thank you

Edited December 21, 2014 by jnops
tentative resolve?

[vexx32]

Well, this is an odd one. I'm not seeing much in the way of probable causes here, except a lot of event listeners being setup for individual keys that I don't recall seeing in other 0.90 logs... That, combined with this entry in the error.log...

Module 2
C:\Program Files (x86)\ASUS\AI Suite II\TurboV EVO\HookKey32.dll
Image Base: 0x10000000  Image Size: 0x0000e000
File Size:  43520       File Time:  2012-05-17_115710
Version:
   Company:    
   Product:    HookKey Dynamic Link Library
   FileDesc:   ASUS HookKey for HotKey Service
   FileVer:    1.0.2.0
   ProdVer:    1.0.2.0

It seems to indicate that there's some kind of hotkey service running which is hooked into the KSP process. It's unusual for that kind of thing to crash KSP, but it's a possibility -- it might be worth poking through the running processes with Task Manager and seeing if there's a hotkey application or service running in the background. It might be worth shutting that down and seeing if it can help.

[jnops]

Thank you for looking into the logs.

I tried killing all processes linked to the Asus tool, not disabling any services yet:

I was able to goof around in sandbox mode for what seemed to be a longer time than before. Until it crashed when going from flight to the space center.

I will now try looking into disabling some services.

Question : by "event listeners being setup for individual keys" , could this be that I remap the keyboard inside KSP to be able to use my french keyboard?

Thank You.

P.S. I have uploaded to the same location a new crash directory with current processes killed.

[vexx32]

Hmm, interesting.

I don't think that should result in what the log showed, unless you did the remapping in a non-standard way (i.e., not using the key binding settings screen). That's corroborated by the fact that the log file no longer shows the event listeners for the keys it did in the first occurrence.

There are a few odd errors in the file, although nothing on its own seems to really explain the crash. Was the save file you're playing created in 0.90? There seem to be a few errors regarding some parts of the save file, though I'm not sure whether they're just warning messages or something more serious as yet. There were a couple exceptions thrown, which is some progress, at least, though I can't see what actually caused them -- they were thrown from within the Unity engine itself, not even in KSP-managed code, which is fairly rare, to my memory.

Not sure exactly what's going on here, but this exception is... unusual, to say the least:

NullReferenceException  at (wrapper managed-to-native) UnityEngine.Transform:INTERNAL_get_position (UnityEngine.Vector3&)


  at UnityEngine.Transform.get_position () [0x00000] in <filename unknown>:0 


  at CompoundParts.CModuleLinkedMesh.TrackAnchor (Boolean setTgtAnchor, Vector3 rDir, Vector3 rPos, Quaternion rRot) [0x00000] in <filename unknown>:0 


  at CompoundParts.CModuleLinkedMesh.OnTargetUpdate () [0x00000] in <filename unknown>:0 


  at CompoundPart.LateUpdate () [0x00000] in <filename unknown>:0 

(Filename:  Line: -1)

Edited December 20, 2014 by vexx32

[jnops]

Hello again,

Yes, I am sure it was a save from beta, but it was a "continue" from a crashed game before killing a bunch of processes.

For the sake of wuickness in installation I only changed the keymappings and resolution: this time I didn't set the graphics to full.

I have tried a clean install again today, and playing a new game I have had no crahses for ~1 hour.

So I'm guessing my issue comes from some kind of incompatiability with the software that comes from my motherboard manufacturer or between graphic settings and my hardware.

I will keep tryin to identify more precisely which application is interfering.

But I guess that for now the problem is resolved.

Thank you for your help.

[jnops]

well...

I just got a BSOD.

jnops.

Happy holidays!

[sal_vager]

Windows does not show the cause of BSOD by default any more, you'll need to see here for info on how to get it.