Internet explorer crashes when accessing microsoft.com

  • Thread starter Thread starter Richard Brockie
  • Start date Start date
R

Richard Brockie

Hi,

I am running IE6 SP1 on XP Pro. When I attempt to access microsoft.com,
the window hangs, causing the system to run very slowly. If I wait long
enough, I get an error message telling me that IE has encountered a
problem and needs to close and apologising for the inconvenience and
requesting that I tell Microsoft about this problem - I have done so,
many times...

If I look at the data the report, I see the following information in the
"Error signature" section:

AppName: iexplore.exe
AppVer: 6.0.2800.1106
ModName: msxml3.dll
ModVer: 8.30.9926.0
Offset: 000be2c7

I should say that I am able to use the browser to view a variety of
other sites without problem, yahoo.com, google.com etc. I seem to have a
problem with all microsoft sites including windowsupdate.com.

I though about un- and re-installing the thing, but there doesn't seem
to be an easy way of doing this. Can someone suggest what might be going
wrong and a possible fix?

Thanks,
--
R.

<> Richard Brockie "Categorical statements
<> The tall blond one. always cause trouble."
<> (e-mail address removed)
 
I seem to have a problem with all microsoft sites
including windowsupdate.com
Click to expand...

Another site where you will probably have trouble is the
Windows Update Troubleshooter where you could find
what I call their Catch-22 suggestion:

< http://v4.windowsupdate.microsoft.com/troubleshoot/ >

(since the troubleshooter has been implemented with XML.)

There really ought to be a separate KB article which we could
point them to. ;)

Here is how I usually reply to this problem.


<example>

Previous users have fixed this symptom by as little as clearing the TIF.

Otherwise it could indicate a problem with XML support.

Can you open other XML files Ok? E.g. open iuhist.xml and
verify that its nesting works. That isn't exactly the XML feature
that the Troubleshooter exploits but if you can't even open that
file it would be a problem.

And in that case you will need the resolution from the "Catch-22" article
of the Troubleshooter:

<topic title>
Windows Update site displays Initialization error 0x800A01AD.
Windows Update.log has error 0x80040154
</topic title>

<extract>
Resolutions:
Suggestion 1:

Make sure the MSXML files are registered correctly by following the steps
below.

NOTE: You may not have the files listed in Steps 2 and 3 installed on your
PC but please perform all 3 steps. If you don't have one of the files, when
you try to register it you will see a popup window that has this text:

LoadLibrary("filename.dll") failed - The specified file name could not be
found.

Just disregard the error and continue to the next step.

Follow these steps:

1. Click on Start, Run and type "REGSVR32 C:\WINDOWS\SYSTEM\MSXML.DLL" (w/o the quotes).
You should see a popup message that this process succeeded.
2. Click on Start, Run and type "REGSVR32 C:\WINDOWS\SYSTEM\MSXML2.DLL" (w/o the quotes).
You should see a popup message that this process succeeded.
3. Click on Start, Run and type "REGSVR32 C:\WINDOWS\SYSTEM\MSXML3.DLL" (w/o the quotes).
You should see a popup message that this process succeeded.
Now try the Windows Update site and see if you get the same error.

Suggestion 2:

This error can be the result of a file mismatch or corruption of the MSXML.DLL files. Try upgrading your XML parser to the most
recent version, which is currently MSXML Parser 3.0 Service Pack 2 Release. You can download the latest parser from this site:

http://msdn.microsoft.com/library/default.asp?url=/downloads/list/xmlgeneral.asp
--------------------------------------------------------------------------------



Issue Applies To:
Windows 2000
Windows 98 and Windows 98 Second Edition
Windows Millennium Edition
Windows XP



Did this resolve your problem?

Your answer is anonymous and is used to help improve content on this site. Your privacy is protected. More about this

</extract>


HTH

Robert Aldwinckle
 
Back
Top