Jump to content

Access Violation CTD in 1.2.1

Recommended Posts

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.

Link to comment
Share on other sites

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 by Mechastophiles
New information added
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...