Tracking down which mod is logging exceptions

[Fwiffo]

My KSP.log and output.log are getting spammed with exceptions like this:

TypeLoadException: Could not load type 'Vector3d' from assembly 'Assembly-CSharp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'.

Any suggestions on how to track which mod is generating them?

I could have sworn I saw a log from someone at some point (maybe running KSP on a different OS than mine, or running with switches hitherto unknown to me?) which seemed to have slightly more detailed exception traces.

I'm hoping there's a more direct approach than "remove half your mods and proceed in a binary search pattern until you identify the culprit".

EDIT: It turned out to be an old version of WaterSounds, but I'd still really like to know if there's a way better way to troubleshoot this sort of thing.

Edited September 17, 2016 by Fwiffo

[ExplorerKlatt]

Try this next time