I
Ian Leslie
Between 5/5/2004 and 5/12/2004 explorer.exe and system (as seen in XP
Task Manager) would take all the cpu cycles for a few seconds every
minute of so. I disovered this when my ATI AIW card started dropping
25% - 35% of the frames when Iwas recording a TV show. No frames
dropped the evening of 5/5/2004 but bad a week later. Anyway, after
much searching on Google and thinking hard about what I might have
done to my computer over the past week I focused on the built in fax
software. I had tried to send a fax for the first time ever. I got a
busy signal and didn't try again, although XP tried the next time I
booted up. I also noticed that when I shut down, explorer.exe and
Connection Tray kept having problems ending (had to click "End Task").
Anyway, I wnet into Services and chnaged the fax service from
Automatic to Manual. I also stopped it. The problem of explorer.exe
and system taking up cpu cycles stopped immediately. Also the cpu
hogging was accompanied by a huge amout of memory usage that kept
growing. Started out with explorere.exe using 25,000 K and kept
climbing past 150,000 K.
I'm sure there are many ways for things to go wrong with explorer.exe.
This was mine. It still begs the question as to why the fax service
was causing this to happen.
Hope this helps someone.
Task Manager) would take all the cpu cycles for a few seconds every
minute of so. I disovered this when my ATI AIW card started dropping
25% - 35% of the frames when Iwas recording a TV show. No frames
dropped the evening of 5/5/2004 but bad a week later. Anyway, after
much searching on Google and thinking hard about what I might have
done to my computer over the past week I focused on the built in fax
software. I had tried to send a fax for the first time ever. I got a
busy signal and didn't try again, although XP tried the next time I
booted up. I also noticed that when I shut down, explorer.exe and
Connection Tray kept having problems ending (had to click "End Task").
Anyway, I wnet into Services and chnaged the fax service from
Automatic to Manual. I also stopped it. The problem of explorer.exe
and system taking up cpu cycles stopped immediately. Also the cpu
hogging was accompanied by a huge amout of memory usage that kept
growing. Started out with explorere.exe using 25,000 K and kept
climbing past 150,000 K.
I'm sure there are many ways for things to go wrong with explorer.exe.
This was mine. It still begs the question as to why the fax service
was causing this to happen.
Hope this helps someone.