09.02.2014 Views

Windows sysinternals

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

112 Part II Usage Guide<br />

■ When the process started, and when it ended (if it has).<br />

■ Architecture (32-bit or 64-bit executable code).<br />

■ Whether UAC file and registry virtualization is enabled for this process (<strong>Windows</strong> Vista<br />

and newer only).<br />

■ The integrity level of the process (<strong>Windows</strong> Vista and newer only).<br />

■ The list of modules (executable images) loaded into the process’ address space at the<br />

time this event occurred. A newly launched process will have an empty list until after<br />

some Load Image events load the exe, Ntdll.dll, and other modules.<br />

Stack Tab<br />

The Stack tab of the Event Properties dialog box, shown in Figure 4-6, displays the thread<br />

call stack when the event was recorded. The stack can be useful for determining the reason<br />

an event took place and the component responsible for the event. See the “Call Stacks<br />

and Symbols” section in Chapter 2 to understand what a call stack is and how to configure<br />

Procmon to maximize the information you can get from one.<br />

Each row represents one stack frame, with five columns of data:<br />

■ Frame Displays the frame number, and a K for a kernel-mode frame or a U for a<br />

user-mode frame. (User-mode stack frames are not captured on x64 versions of<br />

<strong>Windows</strong> prior to <strong>Windows</strong> Vista SP1 and <strong>Windows</strong> Server 2008.)<br />

■ Module The name of the file containing the code being executed in this frame.<br />

■ Location The specific location within the module where the code is executing. If<br />

symbols are available, the location is expressed as a function name and an offset from<br />

the beginning of that function; if source file information is also available, the location<br />

will include the path to and the line number within the source file. If symbols are not<br />

available and the module has an export table, the location is given as the nearest preceding<br />

exported name and an offset from that location. If no symbols or exports are<br />

available, the location is expressed as an offset from the base address of the module in<br />

memory. See the “Call Stacks and Symbols” section in Chapter 2 for more information.<br />

■ Address The address of the code instruction in the virtual address space of the<br />

executing process.<br />

■ Path The full path of the file identified in the Module column. With the default size of<br />

the dialog box, you need to scroll or resize the dialog box to see this column. This can<br />

help you verify which version of a DLL is executing.<br />

www.it-ebooks.info

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!