Which mod crashes my game?

[Mołot]

Error occurred at 2015-01-05_230016.
C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP.exe, run by Mołot.
68% memory in use.
0 MB physical memory [2224 MB free].
0 MB paging file [787 MB free].
0 MB user address space [394 MB free].
Read from location 00000000 caused an access violation.

Full dump at http://molot.pl/KSP-modded-errors.zip

How can I know which mod did it? 68% of memory in use does not seem like much. Two-thirds of what I have, sounds like nice safety margin. And crashes all the same with and without ActiveTextureManagement, only without it percentage used is higher.

It happens at random points, not necessarily in graphic-heavy situations.

I would suspect out of 32bit address space, but Read from location 00000000 looks more like pointer error than anything. Or is it?

Edited January 8, 2015 by Mołot

[smjjames]

Might help if you actually listed the mods. Also, have you tried Active Texture Management mod? The snippet above sort of looks like the crash I was having, but I didn't get the huge stacktrace.

[Mołot]

Might help if you actually listed the mods.

My GameData folder:

• ActiveTextureManagement
  
• BoulderCo
  
• Chatterer
  
• EnvironmentalVisualEnhancements
  
• FerramAerospaceResearch
  
• Firespitter
  
• KAS
  
• MechJeb2
  
• ModuleManager.2.5.6.dll
  
• ModuleManager.ConfigCache
  
• ModuleManager.ConfigSHA
  
• NASAmission
  
• PartCatalog
  
• ProceduralFairings
  
• RealChute
  
• SCANsat
  
• SmartStage
  
• Squad
  
• StageRecovery
  

Don't have any fast method to tell where exactly they came from, but afair the ones that are not self-explanatory are PartCatalog - seems to come with FireSpitter; BoulderCo - textures for city lights and clouds; EnvironmentalVisualEnhancements - well, city lights and clouds, basically.

Also, have you tried Active Texture Management mod?

As I've already said: "And crashes all the same with and without ActiveTextureManagement, only without it percentage used is higher." I should say "seems" instead of "is", to be honest, but anyway.

Edited January 5, 2015 by Mołot

[smjjames]

Have you made sure all of the mods are updated (and compatible for 0.90) and are the latest?

[Mołot]

Why yes, of course. All was downloaded when they were marked 0.90 compatible, pretty much all of them merely last week, and they are updated, to the best of my knowledge.

Edited January 5, 2015 by Mołot

[smjjames]

Looks like the crash happens pretty often, so, the only thing that I can think of atm is to try and take out half of the mods and see whether it crashes or not?

[Master Tao]

The first four logs show out-of-memory errors. If you're not already using the aggressive version of ATM, switch to that. Otherwise, you'll have to either change the scale setting in its config file or reduce the number of modded parts.

The fifth log? No idea. Could be related to an incompatible mod, but we can't tell unless you provide the versions for each. It could also be an out-of-memory error since sometimes those don't show themselves clearly.

[smjjames]

The first four logs show out-of-memory errors. If you're not already using the aggressive version of ATM, switch to that.

This, very much this. I used the basic one, which helped, but I still had a crash after a long while, so I used the aggressive version. The only crash that I had since was one that didn't even leave a crashlog, which I suspect may have been due to the loads of struts that I had on the ship.

[Mołot]

I removed Firespitter parts I didn't need (I only installed it for propellers anyway) and the errors are gone. Thanks, seems it was it.