Jump to content

Mono.dll caused an Access Violation... AGAIN.


Recommended Posts

So I've been getting this error for a while and I'm getting tired of it. Help!

Here's the error log:

  Reveal hidden contents

I honestly have no idea what's going on. I don't know if it's a single mod or if it just doesn't like me anymore.

Link to comment
Share on other sites

  On 9/22/2018 at 5:32 PM, steve_v said:

You are absolutely sure this is not the cause of the problem?

If so, we're going to need logs 'n stuff.

Expand  

I have no idea what it could be. I was using 1.2.2, though. That may be it. Launched KSP in 1.3.1 and ModuleManager found 9 errors. Removed the files it had problems with, testing it now.

Link to comment
Share on other sites

  On 9/22/2018 at 5:34 PM, Kebab Kerman said:

I have no idea what it could be.

Expand  

I was trying to suggest that you do something about your free memory situation before digging any further, to eliminate the obvious.

 

  On 9/22/2018 at 5:34 PM, Kebab Kerman said:

ModuleManager found 9 errors

Expand  

This is almost certainly not causing crashes. MM rejected some patches is all.

Is this crash occurring on startup, scene change, or randomly? Where's output.log.txt?

Link to comment
Share on other sites

  On 9/22/2018 at 5:39 PM, steve_v said:

I was trying to suggest that you do something about your free memory situation before digging any further, to eliminate the obvious.

 

This is almost certainly not causing crashes. MM rejected some patches is all.

Is this crash occurring on startup, scene change, or randomly? Where's output.log.txt?

Expand  

Well, the moment ModuleManager finishes, it crashes.

Anyway, output log is here:

  Reveal hidden contents

 

Link to comment
Share on other sites

  On 9/22/2018 at 5:45 PM, Kebab Kerman said:

moment ModuleManager finishes, it crashes.

Expand  

Right, crashing on loading then.
Are all your mods compatible with the game version you're running? Mods compiled against the wrong game version can and often do crash mono.

Link to comment
Share on other sites

well just a minor piece of info for you !

 on windows 7 system(not the same for windows10)

96% memory in use.
16084 MB physical memory [505 MB free].
32166 MB paging file [14745 MB free].

your pagefile is not what I would recommend and will give the user a slower responsive system(making believe the hd is memory space.)

it is recommended the setting be manually set to 1.5 x ram size so you should set the pagefile size to be 24gigs not 32 this will cause memory issues and slowness.

even wioth that,I have found if you get past 95% you will, within a short time crash.. your system seems to be at its max when its starting up. maybe verify what needs to be started at sign-in and reduce the load.

any mods you load need working space. does this happen in the default install of KSP without mods?

hope this helps

Jammer

 

 

Link to comment
Share on other sites

@Jammer-TD I have same problem than the OP.

KSP loads fine with vanilla and so far as many mods as I want.
When I try to load additional parts is where it crashes.  Most are old parts that where compatible in 1.2.2.

So 2 questions if you or anyone can answer:
#1- Did anything change Part-wise since 1.2.2 ? (ie: some new syntax making them crash?  This is my bet right now, but can't find what so far)
#2- what is a pagefile, how does one modify it?  I have 64 gigs of ram in my beast of a PC, so I doubt I am running out of space (ie: "31% memory in use.") from my error log).

Maybe I should've started my own thread, but it's the exact thing, Mono.dll cause access violation, also "Read from location 00000000 caused an access violation."
Fixing my install is a bit beyond me this time, unless I can get over the crashing.
Any help welcomed.

Ok, in my case it seemed to be a mod overload.  KSP 1.4.5 seems to be creating entries for every part the first time it's loading them.
And as there was MANY parts it tried to add at once (I had a lot) it kept crashing with the Mono.dll error.
Adding one or 2 mods at a time seems to have fixed it.  It's very weird, but that's the only logical explanation.

 

So OP, if you are starting the game with a lot of older parts, or parts never added to your current install before, add one or 2, then fire game, test, alt-f4, go back and add some more.
I hope this fixes your issue.

Edited by Francois424
Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...