Hi,

The best that can happen is that you can use the debugger in "Trace" mode and add a few breakpoints at various points in the code to report expression/variable values but not to halt the processing by breaking. This allows you to slowly find the problem by trial and error, moving breakpoints close to the crash.

Often an Arduino crash means the memory limit is exceeded. If using Arduino 1.5 formats the compiler should show you how much memory has been used. If the value exceeds 90% there is high chance of crash as the code uses more memory during processing.

If the memory usage is very high the Visual Micro debugger will make things worse because it has to use some memory so be aware of that.

Strings in your code can consume the special 2k or 4+k of memory provided by these chips for that type of storage. If you have a lot of serial.print("my string") or "long quoted string" in your code this would consume some important memory and cause a crash more easily.

If debug strings in code are the problem then the Visual Micro debugger can help if you transfer the strings from your code to break point messages. Visual mciro does not store the breakpoint messages on the Arduino. 

notes: You probably know that VS stores breakpoints in the .sln file so it must be saved to be sure that breakpoints messages are saved. Breakpoints can also be exported for safe keeping but can fall out of sync with the code so another thing to be aware of