You can use windbg/cdb to create a memory dump. Download latest
de *** s from
then do this:
c:\de *** s>cdb -pv -p <process id>
0:000> .dump -mt c:\hang.dmp
You can then load the dump into windbg and examine call stacks,
memory, registers etc. Some of the most useful commands for troubleshooting
a 100% CPU problem are ~*k (list all call stacks) and !runaway (show
which threads consumed the most CPU time).
.dump -mt creates a relatively small dump that has just enough information
to get call stacks for all threads in the process. If you need full memory
contents, use .dump -ma (but the dump will be much larger).
This posting is provided "AS IS" with no warranties, and confers no