In our case, the problem was that every night at 23:30 a script started that makes a snapshot to a HP virtual disk S: that was mounted via Virtual replicator. Perfdisk would discover a new drive and start to monitor that disk. When the snapshot was done the disk was unmounted, but perfdisk was still trying to monitor that disk. Because the disk was no longer available, this error would occur in the event log every 10 sec.
The reason why you get this error is that the disk performance counters are permanently enabled on systems beyond Windows 2000. When you suddenly remove a drive Perfmon will still try and monitor this drive. The best way to get rid of these errors will be to use the diskperf command. Below is the syntax:
DISKPERF [-Y[D|V] | -N[D|V]] [\\computername]
-Y Sets the system to start all disk performance counters when the system is restarted.
-YD Enables the disk performance counters for physical drives when the system is restarted.
-YV Enables the disk performance counters for logical drives or storage volumes when the system is restarted.
-N Sets the system to disable all disk performance counters when the system is restarted.
-ND Disables the disk performance counters for physical drives.
-NV Disables the disk performance counters for logical drives.
\\computername Is the name of the computer you want to see or set disk performance counter use. The computer must be a Windows 2000 system.
I would disable my performance counters for the disks that are attached to the storage and leave the counter for the internal disks on server it self. See above for the syntax. Perfmon is not Plug-and-play, so you need to decide on how you want to implement this. Please contact me if you have further questions. See ME253251