phw1443 said:
Excuse me, but I never intended to waste anyones time. My original
question was pretty simple and stated quite well. It was to gain a
method, methodology, procedure to examine the process and determine
what the heck it was doing. I read all of the entries about this
problem in the newsgroup and i was aware of the standard answers
given. Microsoft should have a documented procedure to investigate
this problem. I was asking for that. But I forgot, its Microsoft.
Maybe some else has a differnt opinion than running all of those
programs.
Look, this isn't Microsoft. This is a peer-to-peer newsgroup where
everyone reading and posting is a volunteer. You didn't state what you
had done to troubleshoot, so I gave you the "method, methodology,
procedure" to start with, which in a Windows enviroment is usually to
scan for viruses and remove spyware first. Then one normally uses
msconfig to see what is starting with Windows so one can do some sort
of logical deduction. A great deal of tech support consists of
eliminating factors and seeing what's left. As far as your desire to
not do "running all of those programs", I'm sorry but there is no
one-button quick click way to troubleshoot a pc, particularly via
Usenet postings.
There was no way to know that you were "aware of the standard answers"
from your post. Otherwise, I wouldn't have *given* you the standard
answers as a starting point. The next thing for you to do is to Google
for what others have found out if you haven't done this already. When I
use the search term, "rundll high cpu usage", I get quite a few links
that look promising.
Good luck,
Malke