What does the Module collection function do?
A performance data Object called Module is created internally, when you include the Module Object in your Data Collection set data definition. Each instance of the Module Object shows a load module name, usually a DLL (dynamically linked library module) that is loaded within the specific process. The Module Object also has a parent instance, which is the name of the process that has loaded the module. The Module data is for identification purposes. The only Counters available for each Module are the process ID, which is used to identify the parent process uniquely, and the Load Address of the Module within the parent process virtual address space. The Module data is intended to assist in identifying the application being executed within a container process, which is something we notice occurring more and more frequently in Windows 2000 and XP. There are three specific container processes that you are likely to collect Module Object information about: mtx.exe in Windows NT 4.0, dllhost.
