Apologies for the slow response - I was hoping that Process Explorer would show which thread(s) were stopping when the Dashboard hung - given that it's a low CPU hang, and likely some form of deadlock. Stack traces can be collected - details here:http://blogs.msdn.com/b/dotnet/archive/ ... lorer.aspx
I'll give this a go myself when I'm back on a Windows system (Linux desktop at home), see if the GUI threads are identifiable from the native audio ones..
Thanks for your patience.
Edited as I have just noticed you are running 64-bit Win 7, and the Dashboard is built for a 32-bit target, so you may not have any luck getting stack traces out according to the linked page.. :(