Yes, StackTrace Deobfuscate tool can help you to find the place of exception.
You can parse with this tool rather standard Exception.StackTrace message and provided for free our SmartStackTrace message.
Parsing of standard StackTrace some time doesn't work correctly because Exception.StackTrace doesn't contain return types of methods in the call stack and in situation with names of methods having same names names and same parameter types(but with different return types) StackTrace just sin't able to find right method.
If you're using SmartStackTrace (you can find source code in the \SDK folder and use in your projects for free) you'll get all detailed information about methods in the call stack, position in il or source code(if debug info is available), method token, assembly of method information, so be able to precisely find the place of exception.
In next reply I'll explain how to use Deobfuscate Stack Trace with SmartStackTrace.