Access Violation CTD in 1.2.1

[Mechastophiles]

Hello all, I wish my first post was not an error report, but that's how it goes.

Here's what I've got:

Running KSP 1.2.1 64-bit, Windows, through Steam.

The game crashes a few minutes into the flight scene. The error.log gives this:

KSP_x64.exe caused an Access Violation (0xc0000005)
  in module KSP_x64.exe at 0033:00000086.

(The address being accessed changes, but that's about it.)

Crash dump with output_log: https://www.dropbox.com/s/h5uehaz8xcjuh0q/2016-11-02_212130.zip?dl=0

Most recent crash dump (output_log did not generate): https://www.dropbox.com/s/g2dw1nyea7inhxy/2016-11-02_220508.zip?dl=0

DxDiag dump: https://www.dropbox.com/s/257omhvbnajskys/DxDiag.txt?dl=0

KSP.log, in case it helps: https://www.dropbox.com/s/1owmsbxmru4qpir/KSP.log?dl=0

System specs: Windows 10 64-bit, DirectX 12, AMD FX-4300 processor, Radeon R7 360 with 2 GB dedicated RAM, 8 GB system RAM

Crash happened with both long-running and clean installs, no mods.

[sal_vager]

Hi @Mechastophiles, please provide the output_log from an unmodded install, thank you.

[Mechastophiles]

Reproduced crash, this is what was output: https://www.dropbox.com/sh/w7dlhhn6cf99ech/AAAqWuHeY-Jj3ryGR8SjSxtDa?dl=0

Is there a way to force the game to create output_log?

Update: ran some more tests (still no output_log, sorry), and it seems the crash is related to using the in-flight aerodynamics overlay. So I guess my solution would be to not use the overlay?

Edited November 3, 2016 by Mechastophiles
New information added

[sal_vager]

It should make a log every time KSP starts, it's not dependent on KSP crashing, have you tried looking in C:\users ? It might be in a hidden application data folder which would happen if you didn't have write permissions for the folder where KSP is installed.

That can occur when using a desktop shortcut, or starting KSP via ckan.

[Mechastophiles]

Ah! Found it!

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

Edited November 3, 2016 by Mechastophiles
updated log in Dropbox with log from crash

[sal_vager]

3 hours ago, Mechastophiles said:

Ah! Found it!

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

Okay, RtlLookupFunctionEntry is a Unity engine error, but I can't see what might have caused it, does this crash happen frequently and can you recall what you did just prior?

[Mechastophiles]

The crash happens in-flight at some point after using the aerodynamic overlay. I'm going to guess it's within 5 minutes, but there may be other factors. I can run some more experiments to try and nail it down better.

[Mechastophiles]

All right, I did some more detailed testing, and the results are in, with log files:

Visible Mach effects, aero overlay; crashed https://www.dropbox.com/s/qbpjjbqdi99unup/output_log_1.txt?dl=0

Visible Mach effects, no aero overlay; no crash https://www.dropbox.com/s/h8mwdeyrsfqvy1j/output_log_2.txt?dl=0

No Mach effects, no aero overlay; no crash https://www.dropbox.com/s/lwiawlqrcu7iihx/output_log_3.txt?dl=0

No Mach effects, aero overlay; no crash https://www.dropbox.com/s/hx3hmrivfh13xxc/output_log_4.txt?dl=0

So it seems the crash comes from some interaction between the Mach effects from going fast and the aero overlay.

[electron2059]

Hi all. I just wanted to say, I have seen this error happen as well. @EJ_SA had the same kind of crash after using the aero overlay during his stream. He fixed it by unbinding the key for the overlay in case it was hit by accdent. No crashing when overlay was not used.

[Anth]

@sal_vager

This should clarify this problem

http://bugs.kerbalspaceprogram.com/issues/13188

[sal_vager]

1 hour ago, Anth12 said:

@sal_vager

This should clarify this problem

http://bugs.kerbalspaceprogram.com/issues/13188

Thanks Anth12, now I at least know what to ask others with crashes in flight :/