Crashing upon loading Squad/RCS

tkalm · September 16, 2019

I've stepped away from KSP for a little while, and recently came back to it. Added some of my favorite old mods, and a couple others.
My mods are DockingPortAlignment 6.8.3 , FilterExtension 1.7.2-3.2.3.2 KAS_v1.4 KittopiaTech-1.7.3-1 KSPIE+1.23.2 MechJeb2 NearFutureElectric, NearFutureLaunchVehicles, Near Future Propulsion, OPT, PhotonSailor, TacLifeSupport, TransferWindow Planner, USITools

It always gets to RCS tank 25 before crashing.
crash.dmp

Output log

Error log

VoidSquid · September 17, 2019

Windbg says:

Spoiler

Loading Dump File [E:\Downloads\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 (8 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Debug session time: Mon Sep 16 19:10:50.000 2019 (UTC + 2:00)
System Uptime: not available
Process Uptime: 0 days 0:14:46.000
................................................................
....................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(2c04.4abc): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtGetContextThread+0x14:
00007ffd`587614d4 c3 ret
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

*** WARNING: Unable to verify timestamp for nvd3dumx.dll
*** WARNING: Unable to verify timestamp for nvspcap64.dll
*** WARNING: Unable to verify timestamp for DiscordHook64.dll

KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullPtr

Key : AV.Fault
Value: Read

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

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

Timeline: !analyze.Start
Name: <blank>
Time: 2019-09-17T07:47:36.230Z
Diff: 52606230 mSec

Timeline: Dump.Current
Name: <blank>
Time: 2019-09-16T17:10:50.0Z
Diff: 0 mSec

Timeline: Process.Start
Name: <blank>
Time: 2019-09-16T16:56:04.0Z
Diff: 886000 mSec

DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT: (.ecxr)
rax=0000000000000000 rbx=0000000000000007 rcx=0000000000000003
rdx=0000000000000072 rsi=0000000017cfff40 rdi=00000000ea9bf7d0
rip=00007ffce4b51504 rsp=00000000005ddaf0 rbp=00000000005ddbf0
r8=0000000019a9303c r9=00000000005ddc68 r10=00000000ea9bf020
r11=00000000005dda80 r12=00000000ea9bf630 r13=0000000000000053
r14=0000000070ac70c0 r15=0000000000000001
iopl=0 nv up ei pl nz na pe nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202
mono!mono_reflection_type_from_name+0xa04:
00007ffc`e4b51504 488b10 mov rdx,qword ptr [rax] ds:00000000`00000000=????????????????
Resetting default scope

FAULTING_IP:
mono!mono_reflection_type_from_name+a04
00007ffc`e4b51504 488b10 mov rdx,qword ptr [rax]

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffce4b51504 (mono!mono_reflection_type_from_name+0x0000000000000a04)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

DEFAULT_BUCKET_ID: NULL_POINTER_READ

PROCESS_NAME: KSP_x64.exe

FOLLOWUP_IP:
mono!mono_reflection_type_from_name+a04
00007ffc`e4b51504 488b10 mov rdx,qword ptr [rax]

READ_ADDRESS: 0000000000000000

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

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

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

WATSON_BKT_PROCSTAMP: 5a7349f9

WATSON_BKT_PROCVER: 2017.1.3.55103

WATSON_BKT_MODULE: mono.dll

WATSON_BKT_MODSTAMP: 5a2fe579

WATSON_BKT_MODOFFSET: 91504

WATSON_BKT_MODVER: 1.0.0.1

MODULE_VER_PRODUCT: libmono

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

MODLIST_WITH_TSCHKSUM_HASH: 1042fc9d9c4382682d8088081e3a2d6b9c61463f

MODLIST_SHA1_HASH: 983ff8dd2a60a481b8d9d603986a472dc202dcbd

DUMP_FLAGS: 0

DUMP_TYPE: 2

ANALYSIS_SESSION_HOST:

ANALYSIS_SESSION_TIME: 09-17-2019 09:47:36.0230

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

THREAD_ATTRIBUTES:
BUGCHECK_STR: APPLICATION_FAULT_NULL_POINTER_READ_INVALID_POINTER_READ

PRIMARY_PROBLEM_CLASS: APPLICATION_FAULT

PROBLEM_CLASSES:

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

ID: [0n285]
Type: [INVALID_POINTER_READ]
Class: Primary
Scope: BUCKET_ID
Name: Add
Data: Omit
PID: [Unspecified]
TID: [0x4abc]
Frame: [0] : mono!mono_reflection_type_from_name

ID: [0n300]
Type: [NULL_POINTER_READ]
Class: Primary
Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
BUCKET_ID
Name: Add
Data: Omit
PID: [0x2c04]
TID: [0x4abc]
Frame: [0] : mono!mono_reflection_type_from_name

LAST_CONTROL_TRANSFER: from 00007ffce4b51e0f to 00007ffce4b51504

STACK_TEXT:
00000000`005ddaf0 00007ffc`e4b51e0f : 00000000`17cfff40 00000000`19a9303c 00000000`19a93010 00000000`0644d290 : mono!mono_reflection_type_from_name+0xa04
00000000`005ddc60 00007ffc`e4b55a76 : 00000000`eaa82770 00000000`005ddda0 00000000`00000000 00000000`17d409b0 : mono!mono_custom_attrs_construct+0x183
00000000`005ddca0 00007ffc`e4b04282 : 00000000`4b05fcf8 00000000`005deb78 00000000`05ad7100 00000000`00000000 : mono!mono_reflection_get_custom_attrs_by_type+0x2a
00000000`005ddcd0 00000000`0605a341 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`4b05fcf8 : mono!mono_domain_finalize+0xba92
00000000`005ddd10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`4b05fcf8 00000000`00000000 : 0x605a341

THREAD_SHA1_HASH_MOD_FUNC: 2791366ad53634e079175c1ab31c70b7d40b19da

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 571275588a913bc77d2bec5c08241b18cc04450b

THREAD_SHA1_HASH_MOD: d1bee20528081916798930b96d8f3c0316bdb327

FAULT_INSTR_CODE: 48108b48

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: mono!mono_reflection_type_from_name+a04

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: mono

IMAGE_NAME: mono.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 5a2fe579

STACK_COMMAND: ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID: NULL_POINTER_READ_c0000005_mono.dll!mono_reflection_type_from_name

BUCKET_ID: APPLICATION_FAULT_NULL_POINTER_READ_INVALID_POINTER_READ_mono!mono_reflection_type_from_name+a04

FAILURE_EXCEPTION_CODE: c0000005

FAILURE_IMAGE_NAME: mono.dll

BUCKET_ID_IMAGE_STR: mono.dll

FAILURE_MODULE_NAME: mono

BUCKET_ID_MODULE_STR: mono

FAILURE_FUNCTION_NAME: mono_reflection_type_from_name

BUCKET_ID_FUNCTION_STR: mono_reflection_type_from_name

BUCKET_ID_OFFSET: a04

BUCKET_ID_MODTIMEDATESTAMP: 5a2fe579

BUCKET_ID_MODCHECKSUM: 2829ed

BUCKET_ID_MODVER_STR: 1.0.0.1

BUCKET_ID_PREFIX_STR: APPLICATION_FAULT_NULL_POINTER_READ_INVALID_POINTER_READ_

FAILURE_PROBLEM_CLASS: APPLICATION_FAULT

FAILURE_SYMBOL_NAME: mono.dll!mono_reflection_type_from_name

WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/KSP_x64.exe/2017.1.3.55103/5a7349f9/mono.dll/1.0.0.1/5a2fe579/c0000005/00091504.htm?Retriage=1

TARGET_TIME: 2019-09-16T17:10:50.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: 2e1a2

ANALYSIS_SOURCE: UM

FAILURE_ID_HASH_STRING: um:null_pointer_read_c0000005_mono.dll!mono_reflection_type_from_name

FAILURE_ID_HASH: {a58085e7-a444-e512-fd9c-500391cb3967}

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

Couple of things to mention here:

Your Windows is not up-to-date, latest general release build is 18362, while you're using 17763, updating might help (I don't know what issues were addressed, ask Microsoft for that )

Next, these non-Windows files are mentioned in particular in the dump file:

*** WARNING: Unable to verify timestamp for nvd3dumx.dll
*** WARNING: Unable to verify timestamp for nvspcap64.dll
*** WARNING: Unable to verify timestamp for DiscordHook64.dll

nvd3dumx.dll is part of the NVidia graphics driver, nvspcap64.dll belongs to NVidia Experience, DiscordHook64.dll belongs to Discord.

The Access Violation Bucket ID reads:
FAILURE_BUCKET_ID: NULL_POINTER_READ_c0000005_mono.dll!mono_reflection_type_from_name

Conclusions:
Quite possible that your KSP installation is corrupt, mono.dll trying to read something which fails. Do a file verification via Steam, also verify the mods are good (correct versions, files, configs).

Also update your graphics driver, and try running KSP w/o NVidia Experience and Discord.

And update your Windows, see above.

~~EDIT: I also checked your output.log:~~

Spoiler


TypeLoadException: Could not load type 'Firespitter.customization.FSfuelSwitch' from assembly 'Firespitter, Version=7.0.5613.30088, Culture=neutral, PublicKeyToken=null'.
  at (wrapper managed-to-native) System.MonoCustomAttrs:GetCustomAttributesInternal (System.Reflection.ICustomAttributeProvider,System.Type,bool)
  at System.MonoCustomAttrs.GetCustomAttributesBase (ICustomAttributeProvider obj, System.Type attributeType) [0x00000] in <filename unknown>:0 
  at System.MonoCustomAttrs.GetCustomAttributes (ICustomAttributeProvider obj, System.Type attributeType, Boolean inherit) [0x00000] in <filename unknown>:0 
  at System.MonoType.GetCustomAttributes (System.Type attributeType, Boolean inherit) [0x00000] in <filename unknown>:0 
  at UnityEngine.AttributeHelperEngine.GetParentTypeDisallowingMultipleInclusion (System.Type type) [0x00000] in <filename unknown>:0 
UnityEngine.GameObject:Internal_AddComponentWithType(Type)
UnityEngine.GameObject:AddComponent(Type)
Part:AddModule(String, Boolean)
Part:AddModule(ConfigNode, Boolean)
PartLoader:ParsePart(UrlConfig, ConfigNode)
<CompileParts>c__Iterator66:MoveNext()
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)
UnityEngine.MonoBehaviour:StartCoroutine_Auto(IEnumerator)
UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
<CompileAll>c__Iterator65:MoveNext()
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)
UnityEngine.MonoBehaviour:StartCoroutine_Auto(IEnumerator)
UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
PartLoader:StartLoad()
<LoadSystems>c__Iterator61:MoveNext()
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)

~~TypeLoadException: Could not load type 'Firespitter.customization.FSfuelSwitch' from assembly 'Firespitter~~

~~Fits the dump file analysis, it seems your installation of the firespitter mod causes the problem for mono.dll~~

EDIT2: as @4x4cheesecake mentioned, the output.log is from an older installation of KSP 1.3.1, hence my conclusions from that file are nul and void.

Edited September 17, 2019 by VoidSquid

Harry Rhodan · September 17, 2019

15 hours ago, tkalm said:

My mods are DockingPortAlignment 6.8.3 , FilterExtension 1.7.2-3.2.3.2 KAS_v1.4 KittopiaTech-1.7.3-1 KSPIE+1.23.2 MechJeb2 NearFutureElectric, NearFutureLaunchVehicles, Near Future Propulsion, OPT, PhotonSailor, TacLifeSupport, TransferWindow Planner, USITools

Did you remove your old mods before installing new ones? Because your output log lists several other and much older mods. And your error.log says mono.dll crashes while accessing the very beginning of the adress space, which usually means one of your mods is incompatible.

Always remember that even if you uninstall the game through Steam all your mods will still remain.

4x4cheesecake · September 17, 2019

Usually, a crash caused by "mono.dll" indicates an outdated mod but unfortunately, you posted the wrong output_log so I cannot tell you which mod may cause the issue.
The location for the log changed since KSP 1.4. and it can be found here now:

%USERPROFILE%\AppData\LocalLow\Squad\Kerbal Space Program\output_log.txt

The log you've posted is from KSP 1.3 or even older and I guess, you found it somewhere in your KSP files. If I'm right, you've updated a fairly old version to the latest one or at least, you had some gamefiles remaining before reinstalling the game. There are some rare issues which can appear during big version jumps, like missing localization strings or duplicated parts, so I would suggest to go for a clean reinstall of the game (uninstall the game, (create a backup of your savegame, if you have any), manually delete the remaining game files, reinstall the game.)

Then, try to launch the stock game at least once before reinstalling the mods, just to be sure it is not any other issue. If the game crashes again after reinstalling the mods, please post a fresh output_log from the location I've mentioned before

VoidSquid · September 17, 2019

17 minutes ago, 4x4cheesecake said:

The log you've posted is from KSP 1.3 or even older

Doh... didn't check that, my bad, didn't expect OP would upload an old log file from KSP 1.3.1

Thanks, @4x4cheesecake

At least the crash dump is current:
Debug session time: Mon Sep 16 19:10:50.000 2019 (UTC + 2:00)

Edited September 17, 2019 by VoidSquid

4x4cheesecake · September 17, 2019

6 minutes ago, VoidSquid said:

Doh... didn't check that, my bad, didn't expect OP would upload an old log file from KSP 1.3.1

This happens quite often so it became one of the first things I'll check when someone posts a log file

9 minutes ago, VoidSquid said:

At least the crash dump is current:
Debug session time: Mon Sep 16 19:10:50.000 2019 (UTC + 2:00)

Yep, they are and you are definitely more skilled in reviewing these dumps than me, so I stick to the logs

*Sends a like in your direction which may or may not appear some day* xD

VoidSquid · September 17, 2019

4 minutes ago, 4x4cheesecake said:

This happens quite often so it became one of the first things I'll check when someone posts a log file

Good tip, thanks, will try to keep that in mind

*And a like for you too, ofc *

tkalm · September 17, 2019

1 hour ago, 4x4cheesecake said:
Usually, a crash caused by "mono.dll" indicates an outdated mod but unfortunately, you posted the wrong output_log so I cannot tell you which mod may cause the issue.
The location for the log changed since KSP 1.4. and it can be found here now:
%USERPROFILE%\AppData\LocalLow\Squad\Kerbal Space Program\output_log.txt 
The log you've posted is from KSP 1.3 or even older and I guess, you found it somewhere in your KSP files. If I'm right, you've updated a fairly old version to the latest one or at least, you had some gamefiles remaining before reinstalling the game. There are some rare issues which can appear during big version jumps, like missing localization strings or duplicated parts, so I would suggest to go for a clean reinstall of the game (uninstall the game, (create a backup of your savegame, if you have any), manually delete the remaining game files, reinstall the game.)

Then, try to launch the stock game at least once before reinstalling the mods, just to be sure it is not any other issue. If the game crashes again after reinstalling the mods, please post a fresh output_log from the location I've mentioned before

Okay, so this is startingto deepen the question for me. Cause, my game is 1.7.3 and the crash log was updated from yesterday.

But the responses have been good... other than the one telling me to update windows. I'll try with a clean install, I deleted data from the GameData, but there are a couple Steam mods I have, I'll probably try that once I get home from work.

4x4cheesecake · September 17, 2019

7 minutes ago, tkalm said:

Okay, so this is startingto deepen the question for me. Cause, my game is 1.7.3 and the crash log was updated from yesterday.

Ok, I'll try to explain it to you:

There is a difference between the "crash log" (named "error.log") and the "output_log".

The crash log is only created on a game crash and a popup window will ask you, if you want to open the directory which contains this log together with the crash.dmp. This log contains some basic information about your system like ram usage at the moment the game crashed:

Quote


90% memory in use.
8054 MB physical memory [756 MB free].
21878 MB paging file [7085 MB free].
134217728 MB user address space [134209497 MB free].

the crash reason:

Quote


mono.dll caused an Access Violation (0xc0000005)
  in module mono.dll at 0033:e4b51504.

and right at the top, the unity version (that's the game engine KSP is build on)

Quote


Kerbal Space Program [version: Unity 2017.1.3p1 (02d73f71d3bd)]

Since KSP 1.4, the version is "2017.1.3p1".

The output_log on the other hand, is created every time you launch the game and it contains a lot of information about stuff which happens in the background, like details about the game loading progress, installed mods and issues which happen at runtime but don't crash the game.
It also contains the unity version:

Quote


Initialize engine version: 5.4.0p4 (b15b5ae035b7)

and the actual game version:

Quote


[KSP Version]: 1.3.1.1891 (WindowsPlayer x64) (x64) en-us ==============================

Since the unity version in your output_log doesn't match the unity version of your error.log, it tells me that you picked an old output_log Like I said before, this happens quite often because every KSP version up to 1.3.1 stored the output_log in the game files but unity changed this behavior and when KSP was updated to 1.4, SQUAD also updated to a newer unity version, so KSP started to save the output_log in a new location as well but the old output_log was never deleted or moved.
When you uninstall the game through steam, it will only remove the files which were also installed by steam but logs, mods, savegames and some configs are created during the game launch and steam doesn't know anything about these files, so they are not affected by the uninstalling progress until they are removed manually.

VoidSquid · September 17, 2019

@4x4cheesecake Interesting that we came both independently to the same result, you analyzing the log files, me debugging the crash dump. I like it

jfischerhubert · September 18, 2019

I had the same issue. I dont know what was conflicting with that RCS tank, but dont listen to anyone about mono.dll its a red herring. Just go into the squad folder, delete the 2.5 m rcs tank, and voila, you can get past that part of the boot up screen. I had to remove a few more parts to boot up at this point, ( i had like 130 mods installed). Ok yea you cant use 1 of squads rcs tanks, but if you have enough mods I promise you wont notice.

VoidSquid · September 18, 2019

3 hours ago, jfischerhubert said:

dont listen to anyone about mono.dll its a red herring

When KSP crashes because mono.dll can't load a missing/corrupt part due to an outdated mod, that's a red herring then?

Crashing upon loading Squad/RCS

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation