Windows Vista Resources Monitor

Hello,
I noticed that the Resources monitor is not working, no data whatsoever. I clicked on the monitor tab and then on "start" but nothing happened and when I tried again "start" seems always lit. Is there any registry tweak or maybe a service that may be disabled?.


mario

 

Hello mario,

In TM itself under the Performance tab, are the numbers there, such as Physical Memory - Kernel Memory, and under those: Processes - CPU Usage - Physical memory?

Have you looked in the Performance Monitor help under Learn more? > Configure the Performance Monitor Display

 

No readings at all. When I go to monitor and choose start (stop is dim)nothing happens no readings at all. If I go to monitor again I get the same result start lit and stop dim with the only option is to click on start but again with no success. I have another computer running vista and I can see that resources monitor is working perfectly without doing anything.

 

Hi mario,

Have you been in the Event Viewer > System? Any consistent errors showing some system process not being able to start?

If there are any, right click on the line > event properties.

Scanned thru Vista's services and the only items that caught my eye are these:

Diagnostic Policy Service default is auto
Diagnostic Service Host default is manual

Disabled both from running, didn't affect Resource monitor on my system.

As an FYI - Black Viper's Vista Services page for some info on what the service entries do http://www.blackviper.com/WinVista/servicecfg.htm

 

Iwent to event viewer but strangly enough I got en error "Event viewer is unavailable. Veryfy that the service is running ". I then checked services Windows event log which is auto startup but still not started, I tried to start and got another error
---------------------------
Services
---------------------------
Windows could not start the Windows Event Log service on Local Computer.



Error 4201: The instance name passed was not recognized as valid by a WMI data provider.


---------------------------
OK
---------------------------
I checked this error with google and found this is a very common problem but still unsolved