If System Monitor has missing counters, or counters without data, your performance counter libraries may be corrupted or some WMI (Windows Management Instrumentation) program may have corrupted some extensible counter information in the registry.

To resolve the problem, you need to rebuild the base set of counter libraries and rebuild the extensible counters.

Extensible counter information is store in the registry at the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Perflib\009 key and in the %Systemroot%\System32\Perfc009.dat and %Systemroot%\System32\Perfh009.dat files.

To rebuilds the base performance counter libraries:

1. Mount the Windows 2000 CD-ROM in your CD drive.

2. Open a CMD prompt and type:

        Expand <CD-ROM Drive Letter>:\I386\PERFC009.DA_ %SystemRoot%\System32\PERFC009.DAT
        Expand <CD-ROM Drive Letter>:\I386\PERFH009.DA_ %SystemRoot%\System32\PERFH009.DAT

3. Use Regedt32 to navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVerison\Perflib.

4. Double-click the Last Counter value name and set the data value to 1846, using the Decimal Radix.

5. Double-click the Last Help value name and set the data value to 1847, using the Decimal Radix.

6. Run Exctrlst.exe to get a list of services that have a Performance sub-key.

7. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\<ServiceName>\Performance and delete the First Counter, First Help, Last Counter, and Last Help value names, if they exist.

8. Open a CMD prompt and type:

        CD %SystemRoot%\System32
        findstr drivername *.ini

        This will display information similar to:

        axperf.ini:drivername=ASP
        esentprf.ini:drivername=ESENT
        faxperf.ini:drivername=fax
         . . . . .
        rasctrs.ini:drivername=RemoteAccess
        rsvp.ini:drivername=RSVP
        w3ctrs.ini:drivername=W3SVC

9. For each .ini file returned, type:

        lodctr <DriverName>

        where <DriverName> was returned from step 8. Example: lodctr asp