Strange behaviour in modded install

[golkaidakhaana]

After re-installing KSP and most of the mods I was previously using, I have encountered some strange behaviour, like seemingly randomly-occurring large FPS drops, the Making History select launch site dropdown getting stuck or not dropping down altogether, and frequent game crashes happening mainly when I launch crafts, switch crafts or revert flights. This is incredibly frustrating for me as it takes around 10 minutes to launch the game.

Output log: https://www.dropbox.com/s/hkrxho31mbic793/output_log.txt?dl=0

Screenshot of my mods folder:

[golkaidakhaana]

I have provided the necessary info to help me solve this issue for the most part and I have waited quite patiently for 2 days, but there still hasn't been a reply. I feel no shame in bumping because it is a very serious issue that I cannot resolve and prevents me from enjoying KSP. Moderator, feel free to remove this, but please, please, PLEASE someone help me, I'm very unhappy!

[Serenity]

1 hour ago, sslaptnhablhat said:

I have provided the necessary info to help me solve this issue for the most part and I have waited quite patiently for 2 days, but there still hasn't been a reply. I feel no shame in bumping because it is a very serious issue that I cannot resolve and prevents me from enjoying KSP. Moderator, feel free to remove this, but please, please, PLEASE someone help me, I'm very unhappy!

First of all does this happen when you start a new save?

If yes and you can easily trigger the problem, start a new save, remove a small group of mods each time(start with the graphic mods, like remove 4-6 each time dont do it one by one)

until its not happening anymore.

Now if its not easily triggered and its not happening in a new save then thats a different level of difficulty to fix.

After ofcourse making a backup and a clean install/or verify files on steam, start your save

but since you cant replicate it easily, try to remove first the mods that dont stop you from playing or messing around with your career.

I cant read logs but maybe this will help to find out which mod is causing this(well maybe its multiple mods).

If you are on steam you can also revert to a previous version kerbal that might still work with the mods and doesnt have this problem.

Edited August 31, 2019 by Boyster

[golkaidakhaana]

1 hour ago, Boyster said:

If yes and you can easily trigger the problem, start a new save, remove a small group of mods each time(start with the graphic mods, like remove 4-6 each time dont do it one by one)

Thank you very much for taking the time to reply, but if I am honest I don't think this method of diagnosing issues / mod conflicts will be particularly helpful in my case. With the large amount of mods I have installed and the painfully slow startup time, it would be very time-consuming, to say the least.

 

[Serenity]

46 minutes ago, sslaptnhablhat said:

Thank you very much for taking the time to reply, but if I am honest I don't think this method of diagnosing issues / mod conflicts will be particularly helpful in my case. With the large amount of mods I have installed and the painfully slow startup time, it would be very time-consuming, to say the least.

 

Thats why i said to remove a large group of mods each time and not one by one.

Yes it will take some time but it will help you find the problem quicker.

Edited August 31, 2019 by Boyster

[VoidSquid]

Kopernicus is known to cause issues if you're using the surface features of BG, try removing that.

Edited August 31, 2019 by VoidSquid

[golkaidakhaana]

12 hours ago, Boyster said:

Thats why i said to remove a large group of mods each time and not one by one.

Yes it will take some time but it will help you find the problem quicker.

True, I'll try this later today.

 

12 hours ago, VoidSquid said:

Kopernicus is known to cause issues if you're using the surface features of BG, try removing that.

I don't have BG.

[VoidSquid]

You have the dump file available for debugging? 

Did you check the KSP.log?

One thing I found is that Citrix Receiver is sometimes involved in Unity crashes.

[golkaidakhaana]

5 hours ago, VoidSquid said:

You have the dump file available for debugging?

Where would I find that/those?

5 hours ago, VoidSquid said:

Did you check the KSP.log?

It's in the OP.

If you know someone who can read log files, could you please send them my way?

[VoidSquid]

12 minutes ago, sslaptnhablhat said:

It's in the OP.

In your OP there's the output log, not the KSP.log, which is to be found directly in your KSP directory.

As for the location of crash dump files, should be under %LocalAppData%\CrashDumps

Edited September 1, 2019 by VoidSquid

[golkaidakhaana]

15 hours ago, VoidSquid said:

In your OP there's the output log, not the KSP.log, which is to be found directly in your KSP directory.

How odd, there are two different things called logs?

OTHER log:

https://www.dropbox.com/s/mwm4bvogty7dma4/KSP.log?dl=0

15 hours ago, VoidSquid said:

As for the location of crash dump files, should be under %LocalAppData%\CrashDumps

Crash dumps:

https://www.dropbox.com/s/6vgcpu7oikd6iai/KSP_x64.exe.8648.dmp?dl=0

https://www.dropbox.com/s/xbzs935nit6gdky/KSP_x64.exe.13388.dmp?dl=0

[VoidSquid]

This is the WinDbg output from your second dump file:

Spoiler

*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Unable to verify timestamp for nvoglv64.dll
*** ERROR: Module load completed but symbols could not be loaded for nvoglv64.dll
*** WARNING: Unable to verify timestamp for mono.dll
*** ERROR: Module load completed but symbols could not be loaded for mono.dll
GetUrlPageData2 (WinHttp) failed: 12002.

DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT:  (.ecxr)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000233c69420
rdx=0000000271b30060 rsi=000000021fa55590 rdi=0000000000000000
rip=00000001400ff298 rsp=000000000031f110 rbp=0000000000003a71
 r8=000000000031f130  r9=0000000000000010 r10=0000000000000020
r11=000000000031ef20 r12=000000021fa55590 r13=0000000000000000
r14=0000000000000000 r15=0000000260ef0060
iopl=0         nv up ei pl nz na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
KSP_x64+0x72f298:
00000001`400ff298 4c396310        cmp     qword ptr [rbx+10h],r12 ds:00000000`00000010=????????????????
Resetting default scope

FAULTING_IP: 
KSP_x64+72f298
00000001`400ff298 4c396310        cmp     qword ptr [rbx+10h],r12

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00000001400ff298 (KSP_x64+0x000000000072f298)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000010
Attempt to read from address 0000000000000010

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_READ

PROCESS_NAME:  KSP_x64.exe

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:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000010

FOLLOWUP_IP: 
KSP_x64+72f298
00000001`400ff298 4c396310        cmp     qword ptr [rbx+10h],r12

READ_ADDRESS:  0000000000000010 

WATSON_BKT_PROCSTAMP:  4614489d

WATSON_BKT_PROCVER:  9.18.944.0

WATSON_BKT_MODULE:  KSP_x64.exe

WATSON_BKT_MODSTAMP:  5a7349f9

WATSON_BKT_MODOFFSET:  72f298

WATSON_BKT_MODVER:  2017.1.3.55103

BUILD_VERSION_STRING:  6.1.7601.24308 (win7sp1_ldr.181111-0600)

MODLIST_WITH_TSCHKSUM_HASH:  54a9f377f9929262c0eb06a5d87e5f365a14a9eb

MODLIST_SHA1_HASH:  f304b56c4de4583cc668f50906f8402443dc06bb

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

DUMP_FLAGS:  94

DUMP_TYPE:  1

ANALYSIS_SESSION_HOST:  

ANALYSIS_SESSION_TIME:  09-02-2019 13:07:53.0345

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

THREAD_ATTRIBUTES: 
OS_LOCALE:  ENG

PROBLEM_CLASSES: 

    ID:     [0n292]
    Type:   [@ACCESS_VIOLATION]
    Class:  Addendum
    Scope:  BUCKET_ID
    Name:   Omit
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x115c]
    Frame:  [0] : KSP_x64

    ID:     [0n264]
    Type:   [INVALID_POINTER_READ]
    Class:  Primary
    Scope:  BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x115c]
    Frame:  [0] : KSP_x64

    ID:     [0n289]
    Type:   [NULL_CLASS_PTR_READ]
    Class:  Primary
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [0x344c]
    TID:    [0x115c]
    Frame:  [0] : KSP_x64

BUGCHECK_STR:  APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POINTER_READ

PRIMARY_PROBLEM_CLASS:  APPLICATION_FAULT

IP_ON_HEAP:  0000000003a08fb0
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

FRAME_ONE_INVALID: 1

LAST_CONTROL_TRANSFER:  from 0000000003a08fb0 to 00000001400ff298

STACK_TEXT:  
00000000`0031f110 00000000`03a08fb0 : 00000002`1fa55590 00000002`1e35fef0 00000001`3fb7b909 00000000`02a80060 : KSP_x64+0x72f298
00000000`0031f118 00000002`1fa55590 : 00000002`1e35fef0 00000001`3fb7b909 00000000`02a80060 00000001`00000001 : 0x3a08fb0
00000000`0031f120 00000002`1e35fef0 : 00000001`3fb7b909 00000000`02a80060 00000001`00000001 00000000`00005977 : 0x00000002`1fa55590
00000000`0031f128 00000001`3fb7b909 : 00000000`02a80060 00000001`00000001 00000000`00005977 00000000`00008000 : 0x00000002`1e35fef0
00000000`0031f130 00000000`02a80060 : 00000001`00000001 00000000`00005977 00000000`00008000 00000000`0000048d : KSP_x64+0x1ab909
00000000`0031f138 00000001`00000001 : 00000000`00005977 00000000`00008000 00000000`0000048d 00000002`60ef3060 : 0x2a80060
00000000`0031f140 00000000`00005977 : 00000000`00008000 00000000`0000048d 00000002`60ef3060 00000000`00000021 : 0x00000001`00000001
00000000`0031f148 00000000`00008000 : 00000000`0000048d 00000002`60ef3060 00000000`00000021 00000001`3fbc5f68 : 0x5977
00000000`0031f150 00000000`0000048d : 00000002`60ef3060 00000000`00000021 00000001`3fbc5f68 00000000`03a08fb0 : 0x8000
00000000`0031f158 00000002`60ef3060 : 00000000`00000021 00000001`3fbc5f68 00000000`03a08fb0 00000000`03a08ea8 : 0x48d
00000000`0031f160 00000000`00000021 : 00000001`3fbc5f68 00000000`03a08fb0 00000000`03a08ea8 00000002`1fa55590 : 0x00000002`60ef3060
00000000`0031f168 00000001`3fbc5f68 : 00000000`03a08fb0 00000000`03a08ea8 00000002`1fa55590 00000000`00000000 : 0x21
00000000`0031f170 00000000`03a08fb0 : 00000000`03a08ea8 00000002`1fa55590 00000000`00000000 00000000`02587f80 : KSP_x64+0x1f5f68
00000000`0031f178 00000000`03a08ea8 : 00000002`1fa55590 00000000`00000000 00000000`02587f80 00000002`707655d0 : 0x3a08fb0
00000000`0031f180 00000002`1fa55590 : 00000000`00000000 00000000`02587f80 00000002`707655d0 00000002`71b30060 : 0x3a08ea8
00000000`0031f188 00000000`00000000 : 00000000`02587f80 00000002`707655d0 00000002`71b30060 ffffffff`ffffffff : 0x00000002`1fa55590

THREAD_SHA1_HASH_MOD_FUNC:  796796082370e4b047b265afc16e2fd5d905a7f8

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  da0e98e0a277bef03419b579d26eb42c4742f188

THREAD_SHA1_HASH_MOD:  f1daf1ee0be41b7a5a3db9a74ff157b4b02508e8

FAULT_INSTR_CODE:  1063394c

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  KSP_x64+72f298

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: KSP_x64

IMAGE_NAME:  KSP_x64.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5a7349f9

STACK_COMMAND:  .ecxr ; kb

FAILURE_BUCKET_ID:  NULL_CLASS_PTR_READ_c0000005_KSP_x64.exe!Unknown

BUCKET_ID:  X64_APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POINTER_READ_KSP_x64+72f298

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:  72f298

BUCKET_ID_MODTIMEDATESTAMP:  5a7349f9

BUCKET_ID_MODCHECKSUM:  166c47b

BUCKET_ID_MODVER_STR:  2017.1.3.55103

BUCKET_ID_PREFIX_STR:  X64_APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POINTER_READ_

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/KSP_x64.exe/2017.1.3.55103/5a7349f9/c0000005/0072f298.htm?Retriage=1

TARGET_TIME:  2019-08-27T09:00:54.000Z

OSBUILD:  7601

OSSERVICEPACK:  24308

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  256

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) SingleUserTS

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-11-11 18:01:05

BUILDDATESTAMP_STR:  181111-0600

BUILDLAB_STR:  win7sp1_ldr

BUILDOSVER_STR:  6.1.7601.24308

ANALYSIS_SESSION_ELAPSED_TIME:  651c

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:null_class_ptr_read_c0000005_ksp_x64.exe!unknown

FAILURE_ID_HASH:  {f13b8b30-379c-e420-b4c3-4a4eccb9fe8c}

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

A very common error, c0000005 means access violation. Here the application tried to read from memory with an invalid address: APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POINTER_READ

What is interesting: 
The fault address in not in any loaded module

And:
ERROR: Module load completed but symbols could not be loaded for nvoglv64.dll
ERROR: Module load completed but symbols could not be loaded for mono.dll

Per my understanding, the module causing the invalid call would then be in either mono.dll, or, and this is my candidate number one, in nvoglv64.dll

nvoglv64.dll belongs to your Nvidia graphics driver, I suggest you try updating it.

[golkaidakhaana]

4 hours ago, VoidSquid said:

nvoglv64.dll belongs to your Nvidia graphics driver, I suggest you try updating it.

I don't really have any clue about the other stuff you said, but this would appear to have fixed most of my issues (except for the lag experienced when using Snacks!, though I will bring this up with its' developer). Cheers!

[VoidSquid]

Problem solved then? Glad I could help, so my time spent wasn't wasted at all  

Edited September 2, 2019 by VoidSquid