Hi all,
has anyone encounter this kind of problem, as one of the XP pro machine runing at 100% CPU usage for hours this case it is already been days, as I didn't shutdown that computer for a week to observe what it is doing, (if some of you has experience 100% cpu usage, you know how slow of your pc is)
I tried virus scan, and all kind of tricks, none of them would work, and finally I had to stop the service one by one to see what cause that, from the process viewer in the task manager, the 'system' uses 99% of the time, but no help cannot directly stop this process, if I select 'End process tree' it will end some service but what was ended has no answer, as I didn't enable logging on it.
finally, when I disable indexing service, cpu usage back to normal, now and then I had to manually restart the index service on that XP box, no article from microsoft KB mentioned this problem, no patch either, but the restart indexing trick works for me.
now I found some posts in this forum mentioning similar issue like high cpu usage, may be this is the trick, I will try to use the performance log to find out what exactly it is doing...when I have time,
has anyone encounter this kind of problem, as one of the XP pro machine runing at 100% CPU usage for hours this case it is already been days, as I didn't shutdown that computer for a week to observe what it is doing, (if some of you has experience 100% cpu usage, you know how slow of your pc is)
I tried virus scan, and all kind of tricks, none of them would work, and finally I had to stop the service one by one to see what cause that, from the process viewer in the task manager, the 'system' uses 99% of the time, but no help cannot directly stop this process, if I select 'End process tree' it will end some service but what was ended has no answer, as I didn't enable logging on it.
finally, when I disable indexing service, cpu usage back to normal, now and then I had to manually restart the index service on that XP box, no article from microsoft KB mentioned this problem, no patch either, but the restart indexing trick works for me.
now I found some posts in this forum mentioning similar issue like high cpu usage, may be this is the trick, I will try to use the performance log to find out what exactly it is doing...when I have time,