Vista - What codec makes explorer.exe load CPU?

Hello!
explorer.exe uses 90% of CPU for a minute when I open a folder with movies
or scroll the list of the files. The view mode is the list. The thumbnails
are not shown.
How to know what codec makes explorer.exe use 90% of CPU? I uninstalled Divx
Pro 7, this did not help. How to uninstall VP6 VFW Codec? I cannot fild a
uninstaller for it. I do not see any other codecs. VLC Player is installed.
Regards,
Dima

"Dima" <Dima@xxxxxx> wrote in message
news:9A7E5D6B-A8C3-42C9-A85F-C6891A875088@xxxxxx..
How do you know that a codec is causing the problem? I'm also seeing heavy
use of explorer.exe at times when I open any directory with a large number
of
files, even when none of them are videos.

Robert Miles

Thanks Robert for replying!
People in groups and in forums write that this is because a codec tries to
decode a media in the folder.
Why does explorer.exe uses 90% of CPU Intel E6750 (RAM 6 gb) for a minute
after opening a folder with many files or scrolling the file list or
selecting a file in the folder?
Regards,
Dima
"Robert Miles" wrote:

I wish I knew - it might help me solve some of the problems
I've had recently.

Robert Miles

"Dima" <Dima@xxxxxx> wrote in message
news:A3D4A459-B931-486F-A232-AE2AD82B9112@xxxxxx

Hello!
I stopped Windows Search service and in 6 hours explorer.exe stopped using
90% of CPU after opening an HDD in a Windows explorer window. Other account
in my Windows do not have this problem at all. How to prevent explorer.exe
from using 90% of CPU?
Regards,
Dima

"Robert Miles" wrote:

Hi, Dima:

I personally use Process Explorer's Thread tab
(http://technet.microsoft.com/en-us/s.../bb896653.aspx) to identify
which thread in Explorer.exe is consuming 90-100% of CPU. If you
double-click Explorer.exe, go to the Thread tab and double-click the thread
that is consuming the most CPU, you'll see its stack, and probably one of
the functions in that stack will be located in a codec file (.ax file).

In some cases, after disabling the codec the problem will reproduce again
with another codec involved. In that case, the probably culprit is a damaged
video file.

Of course, it's possible that the problem is NOT caused by a codec or a
damaged video file.

--
Regards/Saludos,
Daniel MartÃ*n
Microsoft MVP Windows Desktop Experience


"Dima" <Dima@xxxxxx> wrote in message
news:9A7E5D6B-A8C3-42C9-A85F-C6891A875088@xxxxxx

I had a similar problem with explorer.exe using up almost all the CPU time,
causing all sorts of other "inconveniences." I found and used the Process
Explorer as you mention below. I discovered that, within explorer.exe, there
was a thread running the program wsil32.dll that was hogging all the CPU
time. The program showed me that wsil32.dll is "Winlogon Startup
Initialization Library" which I don't know anything about (yet). I killed the
thread process to see what happened and my system "calmed down" to "normal."
Now that I found the culprit, I need to find out if it is necessary, what
does it do, and is it working properly. At least I have been able to make
progress since I found Process Explorer.

"Daniel MartÃ*n [MVP]" wrote: