If this event is logged when the computer is restarted this may be a temporary error. For other instances, the performance counter registries might be corrupt. See MSW2KDB
for more details.
If winmgmt /clearadap doesn't fix your problem, your performance counter registry entries may be corrupted. Every time you install an extensible performance counter, files like PerfStringBackup_nnn.ini are created in the %SystemRoot%\System32 folder, before the registry entries are updated. If you suspect that your performance counter registry entries are corrupt try the following:
1) Use Dir /ON %SystemRoot%\System32\PerfStringBackup*.ini to provide a chronological list of installed counters.
2) Look for a significant change in the size of these files. The file prior to the change is probably good. Restore the performance counter registry entries to this good state by opening a CMD prompt, switching to the %SystemRoot%\System32 folder, and typing lodctr /r:filename, where filename is the last good .ini file.
NOTE: This will remove any performance counters added after the PerfStringBackup_nnn.ini snapshot. You will need to reinstall the counters, or the programs that installed them. If you must reinstall the counter that caused the corruption, monitor the process.