FMRS "Jump to Separation" causes crash (1.7.3, modded)

[BadModder54]

Pretty straightforward, whenever I go to land my Falcon 9 knockoff first stage via FMRS, it loads and then kicks me to my desktop with the line: KSP_x64.exe caused an Access Violation (0xc0000005) in module KSP_x64.exe at 0033:bfbd5650. I am lost at this point, and this issue is making stage recoveries almost pointless. Help would be very much appreciated!

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

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

[VoidSquid]

You have the dump file available?

[BadModder54]

Here is the .dmp file, I apologize if it is the wrong one. https://www.dropbox.com/s/ptdilf1ypzmd3kh/crash.dmp?dl=0   Also, thanks for actually looking into this! 

[VoidSquid]

WinDebug says:

Spoiler

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

*** WARNING: Unable to verify timestamp for K_FPS64.dll
*** WARNING: Unable to verify timestamp for mono.dll
*** WARNING: Unable to verify timestamp for atidxx64.dll
*** WARNING: Unable to verify timestamp for tasks_core.dll

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

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

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

Timeline: !analyze.Start
    Name: <blank>
    Time: 2019-09-02T16:33:09.778Z
    Diff: 51196778 mSec

Timeline: Dump.Current
    Name: <blank>
    Time: 2019-09-02T02:19:53.0Z
    Diff: 0 mSec

Timeline: Process.Start
    Name: <blank>
    Time: 2019-09-02T00:28:18.0Z
    Diff: 6695000 mSec

DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT:  (.ecxr)
rax=00000001f2a9f050 rbx=0000000000efda68 rcx=00000001f2e4fbb0
rdx=ffffffffffffffff rsi=00000001f2e4fbb0 rdi=00000001f2e4fbb0
rip=00007ff7bfbd5650 rsp=0000000000efd970 rbp=0000000000efd9e0
 r8=000000000000001e  r9=000000000000000a r10=00000004a408aff0
r11=00000004a408aa80 r12=000000015b884268 r13=000000000000123f
r14=0000000000000001 r15=000000015b87b070
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
KSP_x64+0x6e5650:
00007ff7`bfbd5650 ff5038          call    qword ptr [rax+38h] ds:00000001`f2a9f088=????????????????
Resetting default scope

FAULTING_IP: 
KSP_x64+6e5650
00007ff7`bfbd5650 ff5038          call    qword ptr [rax+38h]

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ff7bfbd5650 (KSP_x64+0x00000000006e5650)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

DEFAULT_BUCKET_ID:  INVALID_POINTER_READ

PROCESS_NAME:  KSP_x64.exe

FOLLOWUP_IP: 
KSP_x64+6e5650
00007ff7`bfbd5650 ff5038          call    qword ptr [rax+38h]

READ_ADDRESS:  ffffffffffffffff 

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

WATSON_BKT_PROCSTAMP:  4614489d

WATSON_BKT_PROCVER:  9.18.944.0

WATSON_BKT_MODULE:  KSP_x64.exe

WATSON_BKT_MODSTAMP:  5a7349f9

WATSON_BKT_MODOFFSET:  6e5650

WATSON_BKT_MODVER:  2017.1.3.55103

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

MODLIST_WITH_TSCHKSUM_HASH:  4c5f5e26daf293931a9c57d324856c70290b1a1e

MODLIST_SHA1_HASH:  40c93d606744568178bbe969068baf7fd6db5252

DUMP_FLAGS:  0

DUMP_TYPE:  2

ANALYSIS_SESSION_HOST:  

ANALYSIS_SESSION_TIME:  09-02-2019 18:33:09.0778

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

THREAD_ATTRIBUTES: 
BUGCHECK_STR:  APPLICATION_FAULT_INVALID_POINTER_READ_IN_CALL

PRIMARY_PROBLEM_CLASS:  APPLICATION_FAULT

PROBLEM_CLASSES: 

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

    ID:     [0n285]
    Type:   [INVALID_POINTER_READ]
    Class:  Primary
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x17b8]
    Frame:  [0] : KSP_x64

    ID:     [0n108]
    Type:   [IN_CALL]
    Class:  Addendum
    Scope:  BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [0x1250]
    TID:    [0x17b8]
    Frame:  [0] : KSP_x64

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 00007ff7bfbd5650

STACK_TEXT:  
00000000`00efd970 00000000`00000000 : 00000000`00efd9e0 00000004`0dbe17c0 00000000`00efd900 00000000`0001084f : KSP_x64+0x6e5650

THREAD_SHA1_HASH_MOD_FUNC:  237252ad4e326e3d0ee1b3684f2e7421d00a28cf

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  410ff4b7cb1e7f0a0d8b520343e91031d81522c9

THREAD_SHA1_HASH_MOD:  237252ad4e326e3d0ee1b3684f2e7421d00a28cf

FAULT_INSTR_CODE:  843850ff

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  KSP_x64+6e5650

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:  INVALID_POINTER_READ_c0000005_KSP_x64.exe!Unknown

BUCKET_ID:  APPLICATION_FAULT_INVALID_POINTER_READ_IN_CALL_KSP_x64+6e5650

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:  6e5650

BUCKET_ID_MODTIMEDATESTAMP:  5a7349f9

BUCKET_ID_MODCHECKSUM:  166c47b

BUCKET_ID_MODVER_STR:  2017.1.3.55103

BUCKET_ID_PREFIX_STR:  APPLICATION_FAULT_INVALID_POINTER_READ_IN_CALL_

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/006e5650.htm?Retriage=1

TARGET_TIME:  2019-09-02T02:19:53.000Z

OSBUILD:  18362

OSSERVICEPACK:  86

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

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  3eef

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:invalid_pointer_read_c0000005_ksp_x64.exe!unknown

FAILURE_ID_HASH:  {c31c3843-246f-f1f3-008a-593a914dede8}

Followup:     MachineOwner
 

Another of the typical and hard to analyze access violations (ExceptionCode: c0000005 (Access violation))

These 4 DLL's are mentioned in particular as WinDebug for obvious reasons can't .load the respective symbol files:

*** WARNING: Unable to verify timestamp for K_FPS64.dll
*** WARNING: Unable to verify timestamp for mono.dll
*** WARNING: Unable to verify timestamp for atidxx64.dll
*** WARNING: Unable to verify timestamp for tasks_core.dll

Looking for the best (worst) candidate to blame here:
k_fps64.dll is part of RazerCortex and developed by Razer Inc. 
mono.dll is part of KSP
atidxx64.dll belongs to the ATI/AMD graphics drivers
tasks_core.dll belongs to Microsoft Visual Studio

My take: the crash is either caused by the Razor driver (mouse, I'd assume), or, my personal candidate here, by the ATI/AMD graphics driver.

I suggest you update/revert graphic driver in the first place. If that doesn't help, update/revert your Razor driver/software.

Edited September 2, 2019 by VoidSquid

[BadModder54]

Ok. thanks so much! I'll check that out and see if it fixes the problem.

[BadModder54]

So far after updating the drivers, etc. it seems to be working. However, the map view is now unbearably laggy, it freezes while in the tracking station, and there's a ton of log spam with the line: FileNotFoundException: Could not load file or assembly 'BackgroundResources, Version=1.7.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. If this was solved, I would finally have a stable install. Thank you again, you did solve the original problem, after all

[VoidSquid]

Glad I could help  

Regarding the new errors, can you post the log files, in particular the KSP.log ?

 

Edited September 2, 2019 by VoidSquid

[BadModder54]

Sure thing, here: https://www.dropbox.com/s/7kghylxc4c43cim/KSP.log?dl=0

[VoidSquid]

Now that's heavily modded, I give you that  

My first preliminary impressions here:

Kopernicus: is known to have issues, if you have BG surface features enabled

TransferWindowPlanner: 1.7.x is also known to have issues, see the respective thread (1.6.3.0 works fine)

InterstellarFuelSwitch: seems to have a lot of issues, uninstall, clean directory, reinstall?

I'd start with these, then you can check the log again and see, if (hopefully) a lot of errors are gone.

 

Edited September 2, 2019 by VoidSquid