"MAP" wrote:
> ...
>
<font color=purple> > <a rel="nofollow" style='text-decoration: none;' href="http://www.ntcompatible.com/thread26131-1.html</font" target="_blank">http://www.ntcompatible.com/thread26131-1.html</font</a>>
<font color=purple> > <a rel="nofollow" style='text-decoration: none;' href="http://cexx.org/dlder.htm</font" target="_blank">http://cexx.org/dlder.htm</font</a>>
Hello MAP
I've just finished running antivirus (AVG and ClamWin) and spyware (adware
and spybot) verification. I've manualy
verified that I don't have the dlder virus in my system. In fact, I'm not
even suprised, since I've been trying to
install and configure XP and I haven't had time to surf the net or do
anything else.
Actually, the synthoms I observe in my system are different than those
listed there. While many people report that
Explorer.exe gets more than 90% of CPU, after some time, in my system it is
always the same behavior. Every few
seconds, Explorer.exe gets some CPU (Taskmanager show only 2-3%) for almost
one second and then releases it. This
cycle happens since boot time. Everything that is running in the foreground
when this happens freezes for almost
half a second (ie a sound playing, a menu opening, a window moving, the
mouse pointer travelling).
The process monitor shows that at these times, the CPU has 20% peek
processing time and also there is an interrupt
process time of 20% at peek. The form of the graph is a thin triangle.
Does anybody know how in the world I can locate what process, DLL or driver
that is doing that? Is it possible to
monitor what IRQs are firing at those moments?
Yesterday I was desperate. I launched system monitor and task manager. Then
I started to kill every process in an
order that I thought was of "decreasing importance". Suddenlly, when I
killed of the svchost processes the system
monitor stopped showing those nasty triangles every few seconds. However, a
few moments later, the system showed a
dialog box, sating that the system had to be rebooted because some process
had suddenly stoped. Those 40 seconds or
so were the only time that my system behaved without the hipcups!
I wonder if the SVCHOST that I killed was indeed causing trouble or if it
was so vital that the monitor didn't work
anymore at that time.
Please, is there anything I could do to determine what process, driver or
piece of hardware is causing all this?
Again, Windows98SE worked without a glitch and so does Linux in another
partition. Do I have to downgrade back to
Win98SE and lose NTFS?
Thanks in advance for any help,
RS
>> Stay informed about: Explorer.exe executes every 2 seconds and locks the system