This article was previously published under Q175658
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit 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 explains how to gather information so that Microsoft SupportProfessionals can troubleshoot performance problems on a computer runningWindows NT. Please read all steps as you will be asked to provideinformation from several tools when contacting a support professional for assistance.
The basic tool used for troubleshooting performance issues is PerformanceMonitor. Follow the steps below to prepare for collecting performanceinformation:
Prior to Creating a Performance Monitor Log
Turn off screen savers permanently.
Click Start, point to Settings, click Control Panel, and then double-click Display.
Click the Screen Saver tab, click None, and then click OK.
Disable all non-essential services in the Services tool in ControlPanel.
For all possible disk issues, enable Diskperf.
Click Start, point to Programs, and then click MS-DOS Command Prompt.
Type the command diskperf -y to enable disk counters.
NOTE: Do not use diskperf -YE unless instructed to do so.
Document Lanman Server parameters.WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
NOTE: The above registry keys are one path; they have been wrapped for readability.
Write down all values on the right-hand side that are not equal to zero.
On the Registry menu, click Save Subtree As and then change the file type to Text File and give the file a name.
NOTE: Do not save the file as a *.REG file.
If instructed to do so by the support professional, install the SNMP service and Network Monitor Agent and Tools. This procedure will require the Windows NT compact disc or an appropriate share path.
To install on Windows NT 3.51
In the Main group, double-click Control Panel, and then double-click Network.
Click Add Software, select SNMP, and then click OK.
Repeat the previous step and select Network Monitor Agent and Tools. Click OK when you receive a prompt to restart the computer.
To install on Windows NT 4.0
Click Start, point to Settings, click Control Panel, and then double-click Network.
Click the Services tab.
From the list of Network Software, select SNMP and then click OK.
Repeat the previous step and select Network Monitor Agent and Tools.
Click No when prompted to restart the computer.
If there are any service packs installed, reapply the service pack.
Click OK when prompted to restart the computer.NOTE: These services install Network Interface, Network Segment, and TCP/IP counters in Performance Monitor.
Creating the Performance Monitor Log
Run Performance Monitor from the following location:
Click Start, point to Program, and then click Administrative Tools.
For specific details on creating the Performance Monitor log, please seethe following article in the Microsoft Knowledge Base:
150934 How to Create a Performance Monitor Log for NT Troubleshooting
In cases where the User Interface (UI) of the server in question is hangingor not responding, run Performance Monitor from another computer runningWindows NT Server or Workstation.
The counters recommended in the article above will change depending on theproblem that you are troubleshooting. See the "Recommended PerformanceObjects" section below or consult the Microsoft support professional forsuggested objects to monitor.
Recommended Performance Objects
If you are troubleshooting a performance issue or an issue that looks likea memory leak, the objects that Performance Monitor should log include, butare not limited to, the following:
For memory leaks:
Cache Memory Objects Paging file Process Processor System Terminal Services (if a Terminal Server)
For all other resource issues, add additional counters:
Logical disk NBT Connections Network interface Physical disk Redirector Server Server work queues Thread (do NOT capture if a terminal server) All Terminal Server counters (if a Terminal Server) All Protocol counters bound to network adapters
In addition, the smaller the update interval, the larger the log file, socheck to make certain there is sufficient disk space available on thecomputer running Performance Monitor.
Allow Performance Monitor to run a minimum of three days unless you havebeen instructed otherwise.
Do not log off of the computer where you are running Performance Monitor asthis will close out Performance Monitor. Minimize Performance Monitor ifpreferred and if needed lock the screen on this computer.
After Creating the Performance Monitor Log
Create a Windows NT Diagnostics Report.
Click Start, point to Programs, click Administrative Tools, and then double-click Windows NT Diagnostics.
On the File menu, click Save Report.
Click All Tab in the Scope Set, click Complete in the Detail Level, click File for Destination, and then click OK.
Save the System and Application Event Logs.
Click Start, point to Programs, click Administrative Tools, and then double-click Event Viewer.
On the Log menu, click System. If System is already selected, click Save As. Save the file as System.evt.
On the Log menu, click Application.
On the Log menu, click Save As. Save the file as Application.evt.
Zip the following files into one file using a compression tool.
Registry file or the written information in a text file.
Performance Monitor log (the .log file, not the *.pml file).
Windows NT diagnostics report.
Event logs: System.evt and Application.evt.
Contact the Microsoft support professional working with you for additional informationon sending the zipped file to the engineer.
Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51, Microsoft Windows NT Server 4.0 Standard Edition