Yup. Boincapi, the 'library bits' compiled into all science applications under the Boinc framework, are wired to trigger an internal 'Boinc Runtime Debugger' when some crash occurs. Checking the stderr.txt output for such a crashed task originating from third party builds will most often look like gibberish because neither Berkeley, nor Microsoft have symbols for those for the debugger mechanism to locate (But it tries anyway).
Berkeley does, I assume, have symbol files in a symbol repository (A windows development thing) for stock applications & Boinc components, and Microsoft certainly has publicly available debug symbols for their windows components etc, so It can be a useful tool for deciphering what's going on in some specific cases .... But more often that not crashes originate in some not directly related driver & such, where symbols usually aren't available.
Either allowing or blocking those requests for debug information (symbol files) doesn't matter to anyone really, so it's a personal choice.
Jason
