Figure 6 The System Information window displays your system's CPU usage, commit, I/O bytes, and physical memory histories.
Process MonitorIf you've successfully used Filemon and/or Regmon in the past to troubleshoot errors, track down sources of malware, or monitor the registry, for example, you'll be happy to come across Process Monitor. This advanced tool offers real-time monitoring of the file system, process/thread activity, and registry.
Process Monitor combines the features of the legacy "mon" utilities and adds numerous enhancements, making it a must-have addition to your troubleshooting toolkit.
One of the jewels of Process Monitor is in troubleshooting generic error messages. Let's say an error occurs without enough information to know which direction to take.
Just start Process Monitor, reproduce the situation in which the error occurs, and then watch for the issue to appear in the interface.
You can avoid spending inordinate amounts of time noodling through the wrong log or report entries, instead zeroing in on the culprit within minutes.
(http://www.informit.com/content/images/art_tittel_sysinternals/elementLinks/20090602_tittel_fig07.jpg)
Figure 7 Process Monitor helps you quickly pinpoint system and registry problems.
A handful of the new or improved features in Process Monitor include the following:
•Ability to monitor DLL and kernel-mode device driver image loads
•Use of non-destructive filters, which enable you to configure filters without data loss
•Complete details of event properties, including user names, session IDs, and more
•Ability to capture thread stacks for each operation, which helps you to determine the root cause of an operation
Because of the breadth and depth of the feature set of Process Monitor, Microsoft recommends diving into the Help file and testing out menu items and options on a live system.
NOTEFor a tour-de-force illustration of how to use ProcMon for troubleshooting, see Mark Russinovich's blog "The Case of the Slooooow System."
It is here: > http://blogs.technet.com/markrussinovich/archive/2008/09/24/3126858.aspx (http://blogs.technet.com/markrussinovich/archive/2008/09/24/3126858.aspx)
PsTools/PsListFinally, we'll wrap up this article with a look at a non-GUI toolset for the command-line junkie. PsTools is a set of text-based utilities within the Sysinternals suite that enable you to view process information and manage local and remote systems.
NOTEThe "Ps" part of the toolset's name indicates its UNIX roots, referring to the process listing command ps.
One of the utilities in PsTools is PsList, which displays detailed information about processes. Similar to the Windows PerfMon monitoring tool, PsList draws its information from the Windows performance counters.
Running pslist at the command line with these parameters enables you to view the following:
•-d: Thread details
•-m: Memory details
•-x: Processes, memory information, and threads
•-t: A process tree
And much more. You can see a more comprehensive list on the Windows Sysinternals PsList web page, or type
pslist –help.(http://www.informit.com/content/images/art_tittel_sysinternals/elementLinks/20090602_tittel_fig08.jpg)
Figure 8 View all sorts of process information from the command line using PsList.
NOTEPsTools requires Windows XP or higher.
The Price Is Right, and the Power is Hard to BeatAs you get to know the Sysinternals utilities better, you'll find them invaluable for all kinds of Windows set-up, configuration, and troubleshooting situations. Though you can dive in and start anywhere, we think most Windows heads will find out top five worth investigating, and predict that all or most of them will be adopted for regular use shortly after learning about them.
Don't let this stop you from digging into the rest of the Sysinternals cornucopia: you won't be disappointed if you do.