How do I use the logfiles to tell which mod is killing KSP?

[Tassyr]

So I recently installed a large amount of mods; listing them all would take a while but they include

Mechjeb

RPM

Scansat

KAS

Universal Storage

Tweakable Parts

and more. Now for no apparent reason it's crashing to desktop if I try to start it. I have a whole mess of logfiles but I can't translate computer to English. Help? What am I LOOKING for?

https://www.dropbox.com/sh/1cak1g8h6jh0txo/AADWs5sGxStwN4DzYn6vbIr9a?dl=0 here's a link to four of the logs if it helps anyone.

[tobjv]

Well to put it bluntly, in the error.log is "mono.dll caused an Access Violation (0xc0000005)." Seeing this and the mods listed in the output.log pretty much guarantees to me that your running out of RAM. Try reducing your the amount of mods your using and look into mods that can help reduce textures and stuff like this one. http://forum.kerbalspaceprogram.com/threads/59005-0-24-Release-3-4-Active-Texture-Management-Save-RAM-without-reduction-packs! Note that ATM isn't updated yet.

I cant read anymore than that from those things.

[Master Tao]

I gave a real example of how I read logs here. When I have a bit more time, I'll try to write it up as a tutorial.