KSP crashes when taking screen shot

[Kurld]

build id = 00830 2015.04.26 at 19:45:40 CEST Branch: master

Obviously, I can't include a screen-shot of this problem... It's not specific to any save file or craft. Happens any/every time I press F1. Windows reports KSP has stopped working.

Link to output_log.txt on Dropbox.

DxDiag.txt on Dropbox.

Thanks for your time and attention!

[sal_vager]

Hi Kurld, please reinstall KSP to C:\Games, running KSP from the desktop causes issues.

[Kurld]

OK, sure. Let me try that.

- - - Updated - - -

Nope, no joy.

[Claw]

Make sure that you Copy & Past (not move), or do a fresh install to somewhere outside of windows protected areas. If you move it, Windows sees what you are doing and continues to "help" you out.

Beyond that, I'm not sure I've seen this problem before......

[Kurld]

Ok... let me make sure I'm following you. I think yesterday I just moved the ksp_win folder from my desktop to the root of my c drive. Instead I should have copy-pasted. (I don't "install" the game, just unzip the file I get from Squad's site).

I'll give it another shot.

This actually appeared in the beta, but I figured I'd ignore it until the full release came out. I used to play back in .23 (on a different machine) and never had any issues. I will also reinstall it on that box and see what happens on it.

A new gaming rig is on the way soon, so it may be moot. This machine I'm on now is about six years old (hardware-wise) There's no telling about how compatible to drivers are.

[sal_vager]

I better explain the reason for the advice above.

Unless you use Steam or the Squad installer, KSP won't have a Windows registry entry telling Windows what folders KSP is allowed to write to, this is not only true of KSP but of any software that is just extracted manually from an archive file.

If such software is extracted to a folder that Windows protects from malicious code, Data Execution Prevention can stop it from writing files or even from working at all.

DEP exists on Linux and OS X as well, but is particularly annoying on Windows.

The KSP.exe would be flagged as potentially malicious and the files ID logged, so even if it's moved elsewhere DEP won't let it run properly.

Copying the game, or re-extracting afresh, gives you new files that are not logged, and as long as these are run from a non-protected Windows folder Windows couldn't care less if your software hosed your system or turned it into a botnet zombie.

So the copied KSP should run just fine

[Kurld]

OK, I extracted the game files to my c drive from the zip file. Still crashes.

I took a screenshot in windows (PrtScn key).

Here is the text that is in the dialog:

Problem signature:

Problem Event Name: APPCRASH

Application Name: KSP.exe

Application Version: 4.6.4.63619

Application Timestamp: 55115266

Fault Module Name: ntdll.dll

Fault Module Version: 6.1.7601.18798

Fault Module Timestamp: 5507b3e0

Exception Code: c0000005

Exception Offset: 000222d2

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: b7be

Additional Information 2: b7beb4baeb9b8a37e91008d4eb17e0e0

Additional Information 3: 2f84

Additional Information 4: 2f8460e7dab64ba52d6cabb526323d4a

- - - Updated - - -

So, just to be sure, I re-extracted to C:\KSP. Would that be a good location?

[sal_vager]

Okay this is really really strange, it should be working, can you please post another output_log after this occurs.

[Kurld]

Sure, give me a few minutes. Meanwhile, I installed the game on another computer (the one I was using before) and it was happy to take screenshots.

[sal_vager]

That suggests something you have installed is causing this, can you also post pics of your task manager showing your running processes to imgur.com ?

[Kurld]

Here is the output_log file from the install to C:\KSP.

- - - Updated - - -

And here is a screenshot of running processes. I ticked "show processes from all users" but I run under the username Geek.

[sal_vager]

There's no hit at all that I can see that might explain this, can you try remapping the screenshot key, you can find it in the settings.cfg

TAKE_SCREENSHOT

{

primary = F1

secondary = None

group = 0

modeMask = -1

modeMaskSec = -1

}

[Kurld]

TAKE_SCREENSHOT

{

primary = RightShift

secondary = None

group = 0

modeMask = -1

modeMaskSec = -1

}

still blows up.

On a lark, I went into services.msc and turned off anything that wasn't from MS and rebooted. That didn't help either.

I'll work on this as long as you want, but like I say, it works fine on another PC and I'm building a new gaming rig very soon, so it's essentially moot for me at this point (assuming screenshots work on new system, lol)

If you want me to keep trying different stuff to get to the bottom of things, though, I am willing to help out however I can.

[sal_vager]

Nah it's okay, but if you do figure it out it could help others with the same issue

[Kurld]

On another lark, I tried reducing the resolution to 1600x1200 (instead of 2560x1440) and running the game in a window (instead of full-screen). This actually allowed me to take a screenshot.

- - - Updated - - -

More info: running in a 2560x1440 window (not full screen) causes it to blow up on screenshot.

- - - Updated - - -

Running it 1920x1080 in full screen also allows a screenshot (sure looks ugly though). So something about 2560x1440 is causing it to blow.

Edited May 3, 2015 by Kurld
removed erroneous logic

[sal_vager]

Maybe 2560x1440 is just more than it can handle.

[Kurld]

What would be the limitation there? Video memory?

[TheMoonRover]

I would say probably, particularly since you're using an older computer.

There is an option in the settings.cfg which increases the resolution of screenshots, "SCREENSHOT_SUPERSIZE = 0" but you can't change it in game. If that is turned up too high, it can cause the game to crash because of the limited video memory, but you would have to have manually edited the file to get that. But the same thing would happen if the screen resolution itself is too high, which looks to be the case.