Vista Tutorial - Explorer.exe pegging CPU when explorer is on root directory of dri

Hello-

I've noticed that any Windows Explorer explorer.exe pegs my single core CPU
whenever I have the Explorer opened to a root directory of any of my four
hard drives. (Each drive has one and only one partition, no RAID.)

Has anyone else seen this? I've turned off Norton Antivirus & Windows
Defender. No change. I know .dlls can attach themselves to Explorer (like
TortoseSVN, which I don't have installed on this machine.) Anyone know how
to find out what dlls I have attached to an Explorer and find out if one of
these is the culprit?

Thanks much! Highly annoying behavior... AL

So looking at Process Explorer (from Microsoft Sysinterals), the Explorer.exe
process shows that BrowseUI.dll and ntdll.dll are taking about 60% and 40% of
the CPU. The Hardware Interrupts piece under System Idle Process also shows
3% sometimes whil this problem is occuring. As soon as I click to a non root
directory, the browseui and ntdll go down to 0 and the Hardware Interrupt
goes to 0 % CPU.

Thanks for any help. AL



"A L" wrote:

> Hello-
>
> I've noticed that any Windows Explorer explorer.exe pegs my single core CPU
> whenever I have the Explorer opened to a root directory of any of my four
> hard drives. (Each drive has one and only one partition, no RAID.)
>
> Has anyone else seen this? I've turned off Norton Antivirus & Windows
> Defender. No change. I know .dlls can attach themselves to Explorer (like
> TortoseSVN, which I don't have installed on this machine.) Anyone know how
> to find out what dlls I have attached to an Explorer and find out if one of
> these is the culprit?
>
> Thanks much! Highly annoying behavior... AL

The Hardware Interrupts does it's 3% thing whether or not the BrowseUI and
ntdll are doing it's thing- so that is not a part of the problem I don't
think.

Running 32 bit Vista, upgraded from XP SP2.

Thanks again, AL

"A L" wrote:

> So looking at Process Explorer (from Microsoft Sysinterals), the Explorer.exe
> process shows that BrowseUI.dll and ntdll.dll are taking about 60% and 40% of
> the CPU. The Hardware Interrupts piece under System Idle Process also shows
> 3% sometimes whil this problem is occuring. As soon as I click to a non root
> directory, the browseui and ntdll go down to 0 and the Hardware Interrupt
> goes to 0 % CPU.
>
> Thanks for any help. AL
>
>
>
> "A L" wrote:
>
> > Hello-
> >
> > I've noticed that any Windows Explorer explorer.exe pegs my single core CPU
> > whenever I have the Explorer opened to a root directory of any of my four
> > hard drives. (Each drive has one and only one partition, no RAID.)
> >
> > Has anyone else seen this? I've turned off Norton Antivirus & Windows
> > Defender. No change. I know .dlls can attach themselves to Explorer (like
> > TortoseSVN, which I don't have installed on this machine.) Anyone know how
> > to find out what dlls I have attached to an Explorer and find out if one of
> > these is the culprit?
> >
> > Thanks much! Highly annoying behavior... AL