i told you so windbg

Processor 0: Ready Threads at priority 1. The visual studio remote debugging capabilities are somewhat more sophisticated than windbgs, so I tend to us VS for application debugging and windbg strictly for kernel debugging. If not, then you have the same problem but not as much of an impact as in kernel mode. There are already plenty of posts and tutorials out there regarding that. Here are a couple of commands that will get you the information that you need.

62305 62306 62307 62308 62309