Mikerlyte

This reply took a while, but I wanted to run with my change for a period of
time before posting what I learned...
Every time the browser had an issue, I noticed that the Phishing Filter
icon at the bottom of the browser window was buzzing continuously.
So, instead of going through all of those diagnostic gyrations, I disbaled
the phishing filter in the Internet Options, under the Advanced tab.
After that, I have not had a problem since.

"Robert Aldwinckle" wrote:

> "Mikerlyte" <Mikerlyte@discussions.microsoft.com> wrote in message
> news:225B5BF8-3E57-43A1-BCCA-36840AB4ECE0@microsoft.com...
> > Can pretty consistantly reproduce the 50% CPU issue with IE7 now by just
> > running through the three COMPUTERWORLD.COM articles that I veiwed on Monday,
> > again IE7 is running without Add-ons.
> > Tried another step in the experiment...
>
> > When logging into WindowsXP, I held the SHIFT key down, suppressing
> > certain items from starting when the profile loads. At this time, I'm not
> > totally sure of everything that is missing from a normal startup.
> > The failure was not able to be triggered in this one time that I used this
> > startup method.
>
> Then you may be able to refine that test by using msconfig
>
> BTW there are known interferers which can not be blocked by
> No Add-ons mode. Google's toolbar is one example, so it would
> be the first thing I might try disabling. Also, other products have
> preload programs in Startup, so you could have been suppressing
> other things you aren't even aware of which aren't essential anyway.
>
>
> > Restarted the PC and logged in as normal. Opened up two windows of IE7
> > without Add-ons and reproduced the error again by navigating through Monday's
> > history.
> > Restarted the PC again and used the SHIFT logon method. Opened two
> > windows of IE7 without Add-ons. While the first window had not yet fully
> > loaded all of the normal tabs assigned in the Home Page options, I fired up
> > the second IE window, upon which the second instance failed to fully start.
> > One of the two IEXPLORE.EXE processes went immediately to 50% CPU. Was able
> > to shut down the first window of IE without issue, except that it remains
> > listed in the Processes tab of Task Manager.
>
>
> Check with netstat to see if there are any residual connections which
> might be hanging that task. E.g. in a cmd window enter:
>
> netstat -ano | sort /+70
> and
> tasklist /fi "Imagename eq iexplore.exe"
>
>
> > One instance of Windows Internet Explorer remains listed in the
> > Applications tab of Task Manager, though it doesn't respond to closing the
> > window by using the X in the upper right corner. Had to use the "End Task"
> > to stop the application, triggering the "The program is not responding"
> > process. Gladly sent the error report!
> > Both processes of IEXPLORE.EXE remain in the Processes tab, one at 50% and
> > one at 0% CPU.
> > Restarting the PC yet again...
>
>
> Before doing that check with Task Manager (or Process Explorer)
> some of the other statistics. E.g. is there any I/O activity too?
> If so, you might get some clues from ProcMon. For that matter
> ProcMon could give you the Stack for the task when you used
> the End Task command. Also taskkill /IM iexplore.exe /f /t
> might succeed where Task Manager's End Task fails. ; )
>
>
> Good luck
>
> Robert
> ---
>
>
>