CTD issue

[udidwht]

https://www.dropbox.com/s/9v5lydvrg912226/crash.dmp?dl=0

https://www.dropbox.com/s/psjst9mud15jnuq/error.log?dl=0

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

 

System specs:

Windows 10 Pro (Clean install UAC off)

Core i5 2500K Unclocked

G-Skill 16GB Trident X CAS 7-8-8-24

Gigabyte GA-Z68XP-UD3 (BIOS F-10)

XFX HD Radeon 7870DD 256bit 2GB Crimson drivers 16.10.1

Sound Blaster X-Fi Xtreme Gamer (Drivers are current)

Hitachi 1TB SATA-3 64mb cache (OS drive)

WD Black (x2) 1TB HDD's SATA-3 64mb cache

Rosewill mid Challenger tower

Antec PSU 650w

Edited November 8, 2016 by udidwht
add sys specs

[sal_vager]

Hi @udidwht, did you use the aero overlay before the crash occurred?

[Padishar]

Welcome to the forums.  Well done for providing the logs etc.  Somewhat ironic, given your name, but could you describe what you were doing just before the crash...?

From the log it appears that you crashed a vessel called Thunderbird and then the game unloaded a couple of debris vessels, updated the record altitude and speed and then started spamming:

CheckEncounter: failed to find any intercepts at all

...a considerable number of times before dying.  It certainly looks like a pretty serious stock bug but it may be difficult to reproduce, especially without details of what you did actually do (the logs can be misleading, especially in regards to the timing of what happens).

[sal_vager]

@udidwht, can you provide your save where this occurred, the issue of the orbit targeting may not be related, so far it has only been consistently caused by a modded install.

What is also interesting is that you apparently ran out of memory, on a 64bit OS your applications can use around 3.5 gigs of ram, not easy to do with a stock game.

G:\Steam\steamapps\common\Kerbal Space Program\KSP.exe, run by udidwht.
33% memory in use.
0 MB physical memory [0 MB free].
0 MB paging file [0 MB free].
0 MB user address space [1324 MB free].
Write to location 000000e0 caused an access violation.

And a DLL could not be found

ERROR: SymGetSymFromAddr64, GetLastError: 'The specified module could not be found.' (Address: 000000E0)
  ERROR: SymGetModuleInfo64, GetLastError: 'A dynamic link library (DLL) initialization routine failed.' (Address: 000000E0)

 

[Padishar]

I'm pretty sure those memory figures are bogus. None of them should have 0 MB at the start (well, unless you've disabled the paging file).  33% memory in use and 0 MB free physical memory aren't consistent so something has got confused.

The DLL that can't be found is, also, not an error.  That's just the stack trace dumping code trying to work out what DLL corresponds to the address 0x000000e0 but there isn't a DLL loaded at that address.  The code in AnimationCurveTpl<float>::GetKeyCount has called a bad function pointer (e.g. because some underlying object in Unity has already been deleted or it failed to allocate something leaving a null pointer) and ended up trying to run code from address 0x000000e0 but there is no real code there so the program crashed.

My current best guess is that there's a problem when the active vessel is destroyed and the other nearby vessels get unloaded which can result in the encounter code still trying to use some object that it shouldn't and getting stuck in a loop and then the large amount of log spam is causing the actual crash (there have recently been some mod issues where extreme spamming to the log makes KSP crash).  Possibly switching to map mode (or actually being in map mode) at the moment the vessel crashes could do it?

@udidwht, is there any particular reason you're running the 32 bit version of the game?

[sal_vager]

Steam opens the 32bit version of KSP when you click Play or when you use the shortcut, unless you right click on KSP in the Steam client and choose to open the 64bit version, or if you manually modify the launch options.

[udidwht]

7 hours ago, sal_vager said:

Hi @udidwht, did you use the aero overlay before the crash occurred?

Not sure. My son was playing the game when the crashes occurred. This is not a modded version. As for running 32bit vs 64bit...I was unaware one needed to do anything other than just clicking on the shortcut to enable 64bit.

[sal_vager]

52 minutes ago, udidwht said:

Not sure. My son was playing the game when the crashes occurred. This is not a modded version. As for running 32bit vs 64bit...I was unaware one needed to do anything other than just clicking on the shortcut to enable 64bit.

He may have used it, especially if he was flying a plane, unfortunately there is a bug with the aero overlay and the part highlighter, after using the overlay (it's F12) if a part is highlighted in flight the game will crash.

This doesn't explain the CheckEncounter issue though, but that might be a red herring and not the cause (though it could cause a drop in performance, many mods that have their own bugs will quite happily spam the logs and generate logs many hundreds of megabytes in size) and the crash may have occurred when your son moused over the debris.

The highlighter crash can be avoided by disabling the part highlighter in flight from the settings screen, it would be interesting to know if your son (or yourself) should experience this crash again with the highlighter disabled.

[udidwht]

3 hours ago, sal_vager said:

He may have used it, especially if he was flying a plane, unfortunately there is a bug with the aero overlay and the part highlighter, after using the overlay (it's F12) if a part is highlighted in flight the game will crash.

This doesn't explain the CheckEncounter issue though, but that might be a red herring and not the cause (though it could cause a drop in performance, many mods that have their own bugs will quite happily spam the logs and generate logs many hundreds of megabytes in size) and the crash may have occurred when your son moused over the debris.

The highlighter crash can be avoided by disabling the part highlighter in flight from the settings screen, it would be interesting to know if your son (or yourself) should experience this crash again with the highlighter disabled.

Will do. I've disabled it and will post back if it crashes again.

[Motokid600]

I was about to report the same until I heard the F12 issue. Thank you @sal_vager