KSP crashing after taking a few screenshots

[Fastfishy2]

So on my new laptop, I've encountered an issue lately with KSP. When I press F12 to take game screenshots through steam, it usually works a couple times but it may work once and then crash a minute after, or crash after I take about 2-3 screenshots in flight. I've tried repeatedly taking screenshots in my other steam games such as Rust and Fallout 4, no crashes no matter how many I take.

Error.txt:

Unity Player [version: Unity 5.4.0p4_b15b5ae035b7]

KSP.exe caused an Access Violation (0xc0000005)
  in module KSP.exe at 0023:000001c4.

Error occurred at 2016-11-13_100148.
D:\Steam\steamapps\common\Kerbal Space Program\KSP.exe, run by Harrison.
25% memory in use.
0 MB physical memory [0 MB free].
0 MB paging file [0 MB free].
0 MB user address space [1520 MB free].
Write to location 000001c4 caused an access violation.

Context:
EDI:    0x2f6fc1ac  ESI: 0x00000000  EAX:   0x000001c4
EBX:    0x0219f268  ECX: 0x00000001  EDX:   0x2f6fc040
EIP:    0x000001c4  EBP: 0x0219f258  SegCs: 0x00000023
EFlags: 0x00010202  ESP: 0x0219f230  SegSs: 0x0000002b

Bytes at CS:EIP:
?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? 

And then it goes on and on

 

Output_log.txt:

Initialize engine version: 5.4.0p4 (b15b5ae035b7)
GfxDevice: creating device client; threaded=1
Direct3D:
    Version:  Direct3D 9.0c [nvd3dum.dll 21.21.13.7570]
    Renderer: NVIDIA GeForce GTX 960M
    Vendor:   NVIDIA
    VRAM:     2018 MB (via DXGI)
    Caps:     Shader=30 DepthRT=1 NativeDepth=1 NativeShadow=1 DF16=0 INTZ=1 NULL=1 RESZ=0 SlowINTZ=0 ATOC=1

 

and then a million lines of... stuff

 

Any help appreciated.

 

[TheDestroyer111]

1 hour ago, Fastfishy2 said:

Error.txt:

Error occurred at 2016-11-13_100148.
D:\Steam\steamapps\common\Kerbal Space Program\KSP.exe, run by Harrison.
25% memory in use.
0 MB physical memory [0 MB free].
0 MB paging file [0 MB free].
0 MB user address space [1520 MB free].
Write to location 000001c4 caused an access violation.

What the freak? 0 MB memory? Does this mean that the game suddenly started thinking that the computer has no memory at all? That is certainly no good!

@sal_vager sal vager heeeeeeeeeeeeellpppp!

Oh and what access violation? I have no crazy idea what is "000001c4" (although it seems like it is 452 written in hexadecimal), but it looks like some other application or security measure is trying to prevent KSP from running by blocking access to its files. Double check if your antivirus program didn't put some KSP or Steam file in quarantine, or if any other application which could do that does attempt to block KSP, although if it's not antivirus (not very likely), then it's not likely that i could easily find out.

[Fastfishy2]

19 minutes ago, TheDestroyer111 said:

What the freak? 0 MB memory? Does this mean that the game suddenly started thinking that the computer has no memory at all? That is certainly no good!

@sal_vager sal vager heeeeeeeeeeeeellpppp!

Oh and what access violation? I have no crazy idea what is "000001c4" (although it seems like it is 452 written in hexadecimal), but it looks like some other application or security measure is trying to prevent KSP from running by blocking access to its files. Double check if your antivirus program didn't put some KSP or Steam file in quarantine, or if any other application which could do that does attempt to block KSP, although if it's not antivirus (not very likely), then it's not likely that i could easily find out.

I think what it means by 0MB memory is that it has 0mb ALLOCATED memory left to it. Because it then shows later down that there is about 15.2GB of memory left. I'll check my antivirus and also check what mode KSP is running in.

 

[Fastfishy2]

Tried it in x64 mode, no difference. Funny thing is, I have games that use over 4x more RAM and are much more intensive, doesn't happen with them

[sal_vager]

@Fastfishy2, F12 toggles the aero overlay, and there is a known bug where if you highlight a part after the overlay is disabled the game will crash.

You can avoid this by disabling the highlighter in flight, or by removing the key mapping to the aero overlay so it can't be toggled.

[Fastfishy2]

5 hours ago, sal_vager said:

@Fastfishy2, F12 toggles the aero overlay, and there is a known bug where if you highlight a part after the overlay is disabled the game will crash.

You can avoid this by disabling the highlighter in flight, or by removing the key mapping to the aero overlay so it can't be toggled.

Alright, I'll try that today.

[Fastfishy2]

10 hours ago, sal_vager said:

@Fastfishy2, F12 toggles the aero overlay, and there is a known bug where if you highlight a part after the overlay is disabled the game will crash.

You can avoid this by disabling the highlighter in flight, or by removing the key mapping to the aero overlay so it can't be toggled.

Problem solved. Thank you!