New
#41
I think the WPT - and the Xperf installation MSIs - are buried somewhere in that SDK, but if you haven't been able to find it then I don't know. I suspect there'll be an uproar and the WPT will be made available as a separate download again, but you probably don't want to wait that long.
Xperf is excellent for two main reasons:
a) It "sees" deep into the action. In other words, it collects a massive amount of detailed data.
b) It is a relatively lightweight logging mechanism. You could configure it to run all day without greatly impacting your machine's performance or resulting in a 4TB logfile!
Still, no point crying over spilt milk.
There's an in-built mechanism which can also produce a useful log, though I fear it may not be enough in your case. Only one way to find out...
1) Create a counters.txt file somewhere on your machine with the following contents:
Code:\process(*)\* \processor(*)\* \memory\* \PhysicalDisk(*)\* \system\*
2) On an elevated (run as admin) CMD prompt (change <path> to location of counters.txt): logman create counter hangLog -cf c:\<path>\counters.txt -si 1 -max 10 -cnf 10:00
3) Then this (on the same CMD prompt): logman start hangLog
4) Wait for the hang to happen again.... then wait say 2 minutes more.
5) On an elevated CMD prompt again: logman stop hangLog
In the \Perflogs\Admin folder there should be a whole bunch of BLG files by then. They're Binary LoG files containing some info about what your machine was doing at the time, broken up into smaller chunks for easier handling.
If you zip up and upload say the last 5 somewhere, it may be possible to tell you what the box is doing during the "freeze". Or not :)