Weird problem

  • Thread starter Thread starter Tcs
  • Start date Start date
T

Tcs

On my machine at work, I run sp2.

About a year or so ago, I started having this problem...a program
would grab 50% of my cpu, and keep it. Until I would use TM to end
the task. Sometimes another program would take its place, using 50%
of my cpu. Sometimes not.

At first it was...infrequent. Then I started rebooting my PC every
morning, because it was happening more often. I even had the cpu
replaced by gateway, in an attempt to resolve this.

It has no progressed to the point where it's happening prettty much
EVERY DAY, sometimes multiple times a day.

I've run memtest 86+ over an entire weekend ( more than once ), but no
errors. I have had error messages when shutting down, but none
lately.

The only thing I haven't done, is something that I don't really want
to do...reinstall windows from scratch. ( I CAN...I just don't WANT
to. )

Does anyone have any suggestions/thoughts/ideas as to what might be
going on? Or even just how to track it down?

Thanks in advance,

Tom
 
What programs?
What do they have in common?
What task?
Only one task?
Don't you think that info is not important????????????????
Jack
 
Tcs said:
On my machine at work, I run sp2.

About a year or so ago, I started having this problem...a program
would grab 50% of my cpu, and keep it. Until I would use TM to end
the task. Sometimes another program would take its place, using 50%
of my cpu. Sometimes not.

At first it was...infrequent. Then I started rebooting my PC every
morning, because it was happening more often. I even had the cpu
replaced by gateway, in an attempt to resolve this.

It has no progressed to the point where it's happening prettty much
EVERY DAY, sometimes multiple times a day.

I've run memtest 86+ over an entire weekend ( more than once ), but no
errors. I have had error messages when shutting down, but none
lately.

The only thing I haven't done, is something that I don't really want
to do...reinstall windows from scratch. ( I CAN...I just don't WANT
to. )

Does anyone have any suggestions/thoughts/ideas as to what might be
going on? Or even just how to track it down?

Thanks in advance,

Tom

Nothing weird here - just prevent the unamed and mysterious task from
starting, e.g. by renaming the folder where it resides.
 
Most often...console.exe from LanDesk. I had thought ( hoped ) that
it was because it wasn't patched. It was v8.7. Well, I applied sp6
about 3 weeks ago. It still happens. When I've ended the process
using TM, another may take its place. Outlook.exe, explorer.exe, etc.
I've never seen it be some "unknown" program, or some "hidden"
program. It's always, as far as I can tell, legit program. It just
starts sucking up the cpu and won't let go.

In common? I don't know. They're all on MY PC?

Only one. So the app that sucks up the cpu, is useless after it has
grabbed the cpu. Otherwise, the PC is usable.
 
Sorry...it's not unamed or mysterious. It's console.exe from LanDesk,
outlook.exe, explorer.exe, etc. I recently patched LanDesk.exe, but
it still happens.
 
Programs: USUALLLY starts with console.exe from LanDesk, but not
always. Other programs that have taken 50% are Outlook.exe,
Iexplorer.exe, Explorer.exe, and a couple others I don't recall right
now.

If I use TM to end the task, another program will take its place,
after a few minutes. Last Friday I ended the task for console.exe,
waited about a minute then cranked up LanDesk again. And once again
console.exe took its 50%. So then I had an idea. What if I cranked
up something that I DIDN'T CARE ABOUT? After I killed console.exe, I
cranked up another instance of IE. And sure enough, it grabbed the
CPU. But I didn't care, because the only app that is affected, is the
one that grabs the cpu. Everything else keeps working. I had finally
found a way to keep working, with out having to reboot my PC. ( Which
I still do every morning so I get off to a clean start. )

Does this help any? Any ideas?

I may find out soon, if it's hw or sw. I've put in to upgrade my PC,
so I can move this one into our Server Room. When I do so, I expect
to install Windowss Server 2003 on it. If it keeps happening after
that, I go for hw being the source...
 
Back
Top