Access Violation Error in Urlmon

[daywatch201]

Am using XP, IE6 for the past year with NO problems.
Downloaded WinZip last week and suddenly IE6 is NO longer
working. I get the "Microsoft Internet Explorer has
encountered a problem....needs to close" message. The
Error Signature I receive is as follows:

Appname: iexplore.exe AppVer: 6.0.2800.1106 ModName:
Urlmon.dll ModVer: 6.0.2800.1259 offset:00016491

Microsoft Knowledge Base Article - 810948 confirms
that "this is a problem in Microsoft Internet Explorer 6,
and that there is a "fix"....but how do you get the fix???

PS: I removed WinZip and all files....no change, IE6 is
still NOT working.

 

[H Leboeuf]

The only way to get the fix for article 810948 is to contact Microsoft and
ask for the fix only.
There will not be any charges.

First rule out parasites.
IE 6.

Try this: Tools > Internet Options > Advanced > Browsing
Uncheck the Enable 3rd party browser extensions

If this clears your problem then find out who the culprit(s) is/are with
these tools.

Let AD-Aware Scan your system for advertising Spyware
http://www.lavasoftusa.com

and:

SpyBot-S&D
http://security.kolla.de/

p.s Reset the 3rd party browser setting.

More:
Dealing with Unwanted Spyware, Parasites, Toolbars and Search Engines
http://mvps.org/winhelp2002/unwanted.htm
-

These articles are for IE 5 but it may give your some clues.

Error Message When Starting Internet Explorer
When you try to start Internet Explorer, you may receive the following error
message:
IEXPLORE caused an Invalid Page Fault in module Urlmon.dll
http://support.microsoft.com/?kbid=254490 (i. e. 5. W95/98/se 5/12/2003)

Iexplore Caused an Invalid Page Fault in Module Urlmon.dll
http://support.microsoft.com/?kbid=309476 (i. e. 5. W98/se 9/30/2002)

Henri Leboeuf
Web page: http://www.generation.net/~hleboeuf/index.htm

 

[Robert Aldwinckle]

Microsoft Knowledge Base Article - 810948 confirms

that "this is a problem in Microsoft Internet Explorer 6,
and that there is a "fix"...

<quote>
The English version of this fix has the file attributes
(or later) that are listed in the following table.
</quote>


Compare the versions (actually the "build numbers")
You have 1259. The article refers to 1155.
The implication is that that fix could be incorporated
in the version you have.


It's possible that the cause of the problem is in a calling module
rather than in the module where the crash is occurring.
If you would like to investigate that possibility extract the
Stack Back Trace for the failing task from drwtsn32.log.
In an English dump you can find the appropriate Stack Back Trace
by doing a find for FAULT -> prefixing the crash address
and the interpreted instruction. (Since there are usually multiple
dumps in the drwtsn32.log it is usually easiest to find that line
by searching up from the bottom of the log.) In any case,
once you find the correct dump just page forward and you will
find its Stack Back Trace. It should show you the module
names and other clues about the calling routines.


However, before going that far it may be simpler just to assume
that the problem might be caused by interfering third-party programs
such as bad BHO and spyware. Search this newsgroup
for posts by MVPs and other frequent posters for answers which refer
to those issues.


Good luck

Robert Aldwinckle