This article was previously published under Q330138
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
This article describes how to gather information about your Microsoft Windows 2000-based computer to troubleshoot performance issues when you work with a Microsoft Product Support Services support professional. When you contact a Microsoft support professional for help, you may be asked to provide information that is collected from several tools.
You can use the System Monitor tool and the Performance Logs and Alerts tool that are included in Windows 2000 to monitor resource usage on the local computer or the remote computer. With Performance Logs and Alerts, you can collect the performance data from a local or remote computer, and use this data to help you to troubleshoot and identify the cause of a performance issue.
The following procedure describes how to create a counter log to collect performance data for the computer that is experiencing the issue from a remote computer. You must have administrative credentials to the computer that you are collecting data from, and you must run the Performance Logs and Alerts tool by using an account that has sufficient permissions to access the computer.
To create a counter log to monitor performance, follow these steps:
On the remote computer, click Start, point to Programs, point to Administrative Tools, and then click Performance.
Expand Performance Logs and Alerts, right-click Counter Logs, and then click New Log Settings.
In the New Log Settings box, type a name for the log, and then click OK.
Click the General tab, and then click Add.
In the Select Counters dialog box, click Select counters from computer, and then click the computer whose performance you want to monitor.
Add counters for each of the following performance objects to the performance log:
Cache Logical Disk Memory NBT Connection Network Interface Objects Paging File PhysicalDisk Process Processor Redirector Server Server Work Queues System Thread
To do this, in the Performance object box, click the first performance object in this list (that is, click Cache), click All counters, click All instances, and then click Add. Perform this step for each performance object in this list.
Under Sample data every, type 160 in the Interval box, click seconds in the Units box, and then click OK.
Note Collecting approximately 500 to 1000 data samples is a good starting point for troubleshooting a performance issue. Use the following formula to determine the sample interval for the performance log:
sampling rate = total time between occurrences of the issue / 750
Note The number 750 is an arbitrary number. It is the midpoint between 500 to 1000 data samples.
The following are calculations that you can use for the sampling rate for days (in seconds) and the sampling rate for hours (in seconds):
Sampling rate for days (in seconds) = (number of days x 24 hours x 60 minutes x 60 seconds / 750) = number of days x 115
Sampling rate for hours (in seconds) = (number of hours x 60 minutes x 60 seconds / 750) = number of hours x 5
For example, if the issue occurs every six to eight days, generate a performance log with a sampling rate of 805 seconds (7 days x 115). Determine whether you want to sample data more or less frequently. If you want smaller performance logs, increase the time interval in the performance log. If you want more data logged, decrease the time interval in the performance log.
Click the Log Files tab.
In the Log file type box, click Binary Circular File. Under Log file size, click Limit of, and then type 256000.
Note Set the size of the log file so that sufficient data can be collected to view changes in performance that may occur.
The log is listed in the right pane of the Performance window. A green icon next to the name of the log indicates that the log is running.
Repeat steps 2 through 11 to create another performance log. Configure this log to sample data every five seconds.
Note Performance logs that use short sample periods, such as five-second intervals, are used to troubleshoot and investigate event-related issues. An event-related issue is an issue that is caused by a particular action.
Run the logs until the problem occurs, or run the logs for the period of time that the Microsoft support professional who is helping you to troubleshoot this issue instructs you to use.
Do not log off the computer where you are running Performance Logs and Alerts. You can minimize the Performance window while the log is running. To stop the log, right-click the log that is in the right pane of the Performance window, and then click Stop.
Prepare the computer to generate a memory dump file
You may also have to generate a memory dump file (Memory.dmp) to help you to troubleshoot and to identify the cause of a performance issue. To prepare the computer for a memory dump file, follow these steps.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Configure the computer to generate a complete memory dump file. To do this, follow these steps:
Click Start, point to Settings, and then click Control Panel.
Double-click System, and then click the Advanced tab.
Under Startup and Recovery, click Settings.
Under Write Debugging Information, click Complete Memory Dump, and then click OK.
Edit the registry to configure the memory dump file. To do this, follow these steps:
Compress the performance log and the memory dump file
Use a file compression tool to zip the performance log and Memory.dmp file to a single file. Contact the Microsoft support professional who is working with you for additional information about how to send the zipped file to him or her.