KSP sometimes Crashing when opening Map screen

[dochockin]

As the title says my game is crashing at times when I try to open the Map screen, especially while climbing to orbit.  I am using numerous mods.  I'm playing on KSP 1.73.  My graphics card driver is up to date.  Where should I start troubleshooting this problem?  I have tried searching for answers online, but I've found nothing helpful.

Thanks for helping a noob!

[Gargamel]

1 minute ago, dochockin said:

Where should I start troubleshooting this problem?

This would be the place:

 

 

[VoidSquid]

Yes, a mod list, log files and the crash.dmp are needed for finding out what's going on.

[dochockin]

Ok,

I've gotten a window to track down all the log and crash files and am adding them now:

 

KSP: 1.7.3 Windwos 64

Problem: Game crashes when transitioning to and from Map Screen

Mods installed:

https://www.dropbox.com/s/h8vil9jw7s4wdfr/ckan mods.txt?dl=0

 

Reproduction steps:

Switch to Map screen from flight screen or vice versa

Log:

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

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

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

 

Thanks in advance!

[VoidSquid]

Eeeek... another one of those ugly memory access denied errors, WinDbg says:

Spoiler

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\Temp\crash (1).dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*c:\symbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Debug session time: Sun Nov  3 01:38:54.000 2019 (UTC + 1:00)
System Uptime: not available
Process Uptime: 0 days 0:55:28.000
................................................................
.......................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(3838.508): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtGetContextThread+0x14:
00007ffc`85d214d4 c3              ret
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Unable to verify timestamp for KSP_x64.exe
*** WARNING: Unable to verify timestamp for mono.dll
*** WARNING: Unable to verify timestamp for nvd3dumx.dll
*** WARNING: Unable to verify timestamp for nvwgf2umx.dll
*** WARNING: Unable to verify timestamp for poco.dll
*** WARNING: Unable to verify timestamp for MessageBus.dll

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Execute

    Key  : Timeline.Process.Start.DeltaSec
    Value: 3328

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

Timeline: !analyze.Start
    Name: <blank>
    Time: 2019-11-03T01:39:58.451Z
    Diff: 3664451 mSec

Timeline: Dump.Current
    Name: <blank>
    Time: 2019-11-03T00:38:54.0Z
    Diff: 0 mSec

Timeline: Process.Start
    Name: <blank>
    Time: 2019-11-02T23:43:26.0Z
    Diff: 3328000 mSec

DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT:  (.ecxr)
rax=0000000274299ff8 rbx=0000000000cfdda8 rcx=00000002742b1110
rdx=ffffffffffffffff rsi=00000002742b1110 rdi=00000002742b1110
rip=0000000000000000 rsp=0000000000cfdca8 rbp=0000000000cfdd20
 r8=000000000000001e  r9=0000000000000003 r10=0000000c289dfff0
r11=0000000c289dffd8 r12=000000006fbf8dd0 r13=0000000000000bac
r14=0000000000000001 r15=000000006fbf3070
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
00000000`00000000 ??              ???
Resetting default scope

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 0000000000000000
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000

DEFAULT_BUCKET_ID:  SOFTWARE_NX_FAULT

PROCESS_NAME:  KSP_x64.exe

FOLLOWUP_IP: 
KSP_x64+6e5653
00007ff7`a3dc5653 ??              ???

EXECUTE_ADDRESS: 0

FAILED_INSTRUCTION_ADDRESS: 
+0
00000000`00000000 ??              ???

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  0000000000000000

WATSON_BKT_PROCSTAMP:  4614489d

WATSON_BKT_PROCVER:  9.18.944.0

WATSON_BKT_MODULE:  unknown

WATSON_BKT_MODVER:  0.0.0.0

WATSON_BKT_MODOFFSET:  0

WATSON_BKT_MODSTAMP:  bbbbbbb4

BUILD_VERSION_STRING:  17763.1.amd64fre.rs5_release.180914-1434

MODLIST_WITH_TSCHKSUM_HASH:  d8057ee48c604e1b436ac4dd813f0cda31b15e78

MODLIST_SHA1_HASH:  07dc5bfb68a07ce7a1f18ae383d60884b53fbde2

DUMP_FLAGS:  0

DUMP_TYPE:  2

ANALYSIS_SESSION_HOST: 

ANALYSIS_SESSION_TIME:  11-03-2019 02:39:58.0451

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

THREAD_ATTRIBUTES: 
BUGCHECK_STR:  APPLICATION_FAULT_SOFTWARE_NX_FAULT_NULL_INVALID_POINTER_EXECUTE

PRIMARY_PROBLEM_CLASS:  APPLICATION_FAULT

PROBLEM_CLASSES: 

    ID:     [0n313]
    Type:   [@ACCESS_VIOLATION]
    Class:  Addendum
    Scope:  BUCKET_ID
    Name:   Omit
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x508]
    Frame:  [0] : unknown!unknown

    ID:     [0n287]
    Type:   [INVALID_POINTER_EXECUTE]
    Class:  Primary
    Scope:  BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x508]
    Frame:  [0] : unknown!unknown

    ID:     [0n295]
    Type:   [SOFTWARE_NX_FAULT]
    Class:  Primary
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [0x3838]
    TID:    [0x508]
    Frame:  [0] : unknown!unknown

    ID:     [0n294]
    Type:   [NULL]
    Class:  Primary
    Scope:  BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [0x3838]
    TID:    [0x508]
    Frame:  [0] : unknown!unknown

LAST_CONTROL_TRANSFER:  from 00007ff7a3dc5653 to 0000000000000000

STACK_TEXT:  
00000000`00cfdca8 00007ff7`a3dc5653 : 00000000`00000000 00000000`00cfdd20 00000000`6192fee0 00000000`00cfdd00 : 0x0
00000000`00cfdcb0 00000000`00000000 : 00000000`00cfdd20 00000000`6192fee0 00000000`00cfdd00 00000000`00032c75 : KSP_x64+0x6e5653

THREAD_SHA1_HASH_MOD_FUNC:  237252ad4e326e3d0ee1b3684f2e7421d00a28cf

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  410ff4b7cb1e7f0a0d8b520343e91031d81522c9

THREAD_SHA1_HASH_MOD:  237252ad4e326e3d0ee1b3684f2e7421d00a28cf

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ksp_x64+6e5653

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: KSP_x64

IMAGE_NAME:  KSP_x64.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5a7349f9

STACK_COMMAND:  ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID:  SOFTWARE_NX_FAULT_c0000005_KSP_x64.exe!Unknown

BUCKET_ID:  APPLICATION_FAULT_SOFTWARE_NX_FAULT_NULL_INVALID_POINTER_EXECUTE_NULL_IP_ksp_x64+6e5653

FAILURE_EXCEPTION_CODE:  c0000005

FAILURE_IMAGE_NAME:  KSP_x64.exe

BUCKET_ID_IMAGE_STR:  KSP_x64.exe

FAILURE_MODULE_NAME:  KSP_x64

BUCKET_ID_MODULE_STR:  KSP_x64

FAILURE_FUNCTION_NAME:  Unknown

BUCKET_ID_FUNCTION_STR:  Unknown

BUCKET_ID_OFFSET:  6e5653

BUCKET_ID_MODTIMEDATESTAMP:  5a7349f9

BUCKET_ID_MODCHECKSUM:  166c47b

BUCKET_ID_MODVER_STR:  2017.1.3.55103

BUCKET_ID_PREFIX_STR:  APPLICATION_FAULT_SOFTWARE_NX_FAULT_NULL_INVALID_POINTER_EXECUTE_NULL_IP_

FAILURE_PROBLEM_CLASS:  APPLICATION_FAULT

FAILURE_SYMBOL_NAME:  KSP_x64.exe!Unknown

WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/KSP_x64.exe/9.18.944.0/4614489d/unknown/0.0.0.0/bbbbbbb4/c0000005/00000000.htm?Retriage=1

TARGET_TIME:  2019-11-03T00:38:54.000Z

OSBUILD:  17763

OSSERVICEPACK:  475

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  768

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  1989-09-10 08:58:46

BUILDDATESTAMP_STR:  180914-1434

BUILDLAB_STR:  rs5_release

BUILDOSVER_STR:  10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME:  a2af

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:software_nx_fault_c0000005_ksp_x64.exe!unknown

FAILURE_ID_HASH:  {29aa2c52-72c3-9485-30ec-1bc0758812e0}

Followup:     MachineOwner
---------

Most common reason: driver issue. But you say your graphics driver is up to date.

The error itself: SOFTWARE_NX_FAULT

"NX" means "no execute" and  indicates that a memory address that should not be executed has in fact tried to execute.

I'm wondering though, these dlls (besides Windows itself and KSP) are mentioned in particular the crash, chances are that one of these has caused the crash:

*** WARNING: Unable to verify timestamp for nvd3dumx.dll
*** WARNING: Unable to verify timestamp for nvwgf2umx.dll
*** WARNING: Unable to verify timestamp for poco.dll
*** WARNING: Unable to verify timestamp for MessageBus.dll

Are you running any additional graphics related utilities, like overlays, FPS display, anything like that? E.g. Riva Tuner, MSI Dragon Eye, Afterburner, NVIDIA 3D Vision Driver, ...?

 

Edited November 3, 2019 by VoidSquid

[dochockin]

Thanks for the reply.  I'm not running any of those programs you mentioned, nor anything similar that I know of.  I've just updated my GUI driver again since your reply (an update came out a couple of days ago). 

Stuff running in the background while I play KSP are: CCleaner, Malwarebytes, Unchecky, Dropbox, Razer Synapse and usually Firefox on my second monitor.

[VoidSquid]

21 minutes ago, dochockin said:

Razer Synapse

I've read more than once in the KSP forum that this sometimes is the cause of such access violations. Try running KSP without it.

Edited November 3, 2019 by VoidSquid

[dochockin]

I've turned off Razor Synapse and everything seemed to be good.  I played for well over an hour, back and forth between Screens (map, tracking station, flight, space center) no problems and then CRASH!  So I'm adding the new .dmp, log and error files for your viewing pleasure. This crash happened as I was in Space Center screen and clicked on the tracking station to enter that screen. Thanks!

 

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

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

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

 

 

[VoidSquid]

Looks very similar to the last one. 

But if you can play for an hour with multiple times switching between different screens before having a crash, the issue was that Razer Synapse. A crash every few hours is kind of normal, happens here too.

Edited November 3, 2019 by VoidSquid