KSP Version 1.3.0 mono.dll Access Violation Crash (HELP PLEASE!)

[WaffleScience]

I need help with Fixing this crash... All mods should be compatible. I checked everything.

Error Log:

Unity Player [version: Unity 5.4.0p4_b15b5ae035b7]

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

Error occurred at 2017-12-29_220404.
C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_x64.exe, run by User.
47% memory in use.
8174 MB physical memory [4296 MB free].
16346 MB paging file [11265 MB free].
8388608 MB user address space [8386283 MB free].
Read from location 00000000 caused an access violation.

 

Game Data Folder:

000_AT_Utils

000_FilterExtensions

000_FilterExtensions Configs

000_USITools

ASET

B9PartSwitch

CommunityCategoryKit

CommunityResourcePack

ConfigurableContainers

Cormorant Aeronology 1.3.0b

CryoEngines

CryoTanks

CxAerospace

DeployableEngines

DynamicBatteryStorage

Endurance

ExtraplanetaryLaunchpads

Firespitte

FShangarExtender

GroundConstruction

InterstellarFuelSwitch

IXSWarpShipOS

JSI

KAS

KerbalAtomics

Kerbaltek

KerbetrotterLtd

KFC

KIS

KWRocketry

LonesomeRobots

MechJeb2

MiningExpansion

Mk2Expansion

Mk3Expansion

NearFutureConstruction

NearFutureElectrical

NearFutureLaunchVehicles

NearFutureProps

NearFuturePropulsion

NearFutureSolar

NearFutureSpacecraft

OPT_Legacy

PersistantRotation

PlanetaryBaseInc

PlanetaryDomes

RoverScience

ShadowWorks

SmokeScreen

Squad

StationPartsExpansion

SurfaceExperimentsPackage

Tantares

TantaresLV

TextureReplacer

TweakScale

UmbraSpaceIndustries

V.2.0Industries

WarpDrive

WildBlueIndustries

 

KSPModFileLocalizer.dll

ModuleManager.2.8.1.dll

ModuleManager.ConfigCache

ModuleManager.ConfigSHA

ModuleManager.Physics

ModuleManager.TechTree

 

 

 

 

 

 

I already tried this:

Forcing DX11 (-force-d3d11).

Verifying the integrity of game files.

I also deleted 2 big mods:

B9 Aerospace

Kopernicus with a bunch of Planet Mods

[Chel]

Quote

Game Data Folder:

000_AT_Utils

000_FilterExtensions

000_FilterExtensions Configs

000_USITools

ASET

B9PartSwitch

CommunityCategoryKit

CommunityResourcePack

ConfigurableContainers

Cormorant Aeronology 1.3.0b

CryoEngines

CryoTanks

CxAerospace

DeployableEngines

DynamicBatteryStorage

Endurance

ExtraplanetaryLaunchpads

Firespitte

FShangarExtender

GroundConstruction

InterstellarFuelSwitch

IXSWarpShipOS

JSI

KAS

KerbalAtomics

Kerbaltek

KerbetrotterLtd

KFC

KIS

KWRocketry

LonesomeRobots

MechJeb2

MiningExpansion

Mk2Expansion

Mk3Expansion

NearFutureConstruction

NearFutureElectrical

NearFutureLaunchVehicles

NearFutureProps

NearFuturePropulsion

NearFutureSolar

NearFutureSpacecraft

OPT_Legacy

PersistantRotation

PlanetaryBaseInc

PlanetaryDomes

RoverScience

ShadowWorks

SmokeScreen

Squad

StationPartsExpansion

SurfaceExperimentsPackage

Tantares

TantaresLV

TextureReplacer

TweakScale

UmbraSpaceIndustries

V.2.0Industries

WarpDrive

WildBlueIndustries

 

KSPModFileLocalizer.dll

ModuleManager.2.8.1.dll

ModuleManager.ConfigCache

ModuleManager.ConfigSHA

ModuleManager.Physics

ModuleManager.TechTree

 

 

 

 

 

 

I already tried this:

Forcing DX11 (-force-d3d11).

Verifying the integrity of game files.

I also deleted 2 big mods:

B9 Aerospace

Kopernicus with a bunch of Planet Mods

 

I think I know why the mono.dll is crashing. Mono.dll is the Unity engine file, and KSP is built on Unity. So, put simply, the game can't handle all your mods, so try deleting some. If that doesn't work, and you still have the issue, make sure all your mods are up to date. 

By the way, do you have one 'ModuleManager' file, or many of them? Most mods come with ModuleManager, a file that makes the mod work with other mods or the game. Because of this, if you have a lot of mods, you may have a lot of ModuleManagers. You should only have one ModuleManager file, that should be the newest one. If you have a lot of them, then delete all but the newest version one. Otherwise it interferes with the game and also causes crashes.

Edited January 29, 2018 by The_Cat_In_Space

[Jas0n]

Normally a mono.dll Access Violation means some of your mods are out-dated or incompatible. 

5 minutes ago, The_Cat_In_Space said:

So, put simply, the game can't handle all your mods, so try deleting some

I've seen modlists much much longer than this, so I don't think that's the issue here.

Also, MM is smart enough to only run the newest version.

 

A way to test which one of your mods is incompatible is by removing half of them and trying to start the game. If the issue occurs, then you know the culprit is the half you didn't remove. If it doesn't, then you know the culprit is in the half you removed. Repeat this until you have it narrowed down to one mod.

Edited January 29, 2018 by Jas0n

[Chel]

Just now, Jas0n said:

Normally a mono.dll Access Violation means some of your mods are out-dated or incompatible. 

I've seen modlists much much longer than this, so I don't think that's the issue here.

Also MM is smart enough to only run the newest version.

Really? I kept getting MM out of memory issues on loading KSP, deleted all but the newest version, and it loaded fine afterwards.

[Jas0n]

Just now, The_Cat_In_Space said:

Really? I kept getting MM out of memory issues on loading KSP, deleted all but the newest version, and it loaded fine afterwards.

Well, I'm repeating things I've heard from other people in this sub-forum. I'm pretty it should work that way though....