HELP! IE gives error message and cannot load websites

[sk]

In the last few weeks many websites just shut down. After
several attempts sometimes I am able to load them. My
internet connection stays up and is fine, but it's just
the websites that shut down (some,not all). My ISP is AOL
(which otherwise works fine), but get the same problem
when I go through Internet Explorer. The details in IE's
illigal operation message box is: ""IEXPLORE caused an
invalid page fault in module MSVCRT.DLL at 017f:78015ca2."
Went to Knowledge Base but could find this error. I
cannot seem to identify what it is about certain sites
that shut down.
My PC is Win 98.
So far here's what I've done:
-ran anti virus
- cleared all my temp internet files/cookies
-fixed IE
-ran defrag
-ran 2 spyware programs (adaware and spybot)
-downloaded updates from Microsoft site
-spent countless hours on the phone with AOL tech support

NONE OF THE ABOVE WORKED! . Any suggestions? Anyone
know why this
is happening and what's causing it?

 

[kim]

I posted this same question last night, it s really
annoying to be able to get some sites but get this same
message about thisproblem.

I found the answer to be this, go to Srart, run type in
cmd and type in the following one at a time and hit enter
after each one, once you get the message that the file
was registered successfully go on the to the next one:

regsvr32 Shdocvw.dll
regsvr32 Shell32.dll
regsvr32 Oleaut32.dll
regsvr32 Actxprxy.dll
regsvr32 Mshtml.dll
regsvr32 Urlmon.dll

It sorts the problem out completely. By the way I am
using Windows XP pro and Internet explorer 6 and it
worked just fine for me.

Kim

 

[Guest]

Hey Kim,

Yes, this problem is very, very annoying! I tried you
suggeston, and it did not work. Maybe it only works well
for XP and not 98

 

[Robert Aldwinckle]

I posted this same question last night, it s really
annoying to be able to get some sites but get this same
message about thisproblem.

I found the answer to be this, go to Srart, run type in
cmd and type in the following one at a time and hit enter
after each one, once you get the message that the file
was registered successfully go on the to the next one:

regsvr32 Shdocvw.dll
regsvr32 Shell32.dll
regsvr32 Oleaut32.dll
regsvr32 Actxprxy.dll
regsvr32 Mshtml.dll
regsvr32 Urlmon.dll

It sorts the problem out completely. By the way I am
using Windows XP pro and Internet explorer 6 and it
worked just fine for me.

Kim,

You probably got that list from KB281679?

There is an improved list in KB831429.
(Note the addition of the /i switches where appropriate.)

Even better though for an XP user who has installed IE6sp1
before upgrading to XPsp1 is to use its setupwbv.dll:

rundll32 setupwbv.dll,IE6Maintenance

Users of any other OS should try their IE Repair because they always
have that module and the list of re-registrations implied by it using
FixIE.inf is much more comprehensive, besides the fact that they
are done in a more controlled setting during a forced reboot.


FYI

Robert Aldwinckle
---

 

[Robert Aldwinckle]

The details in IE's illigal operation message box is:

""IEXPLORE caused an invalid page fault in module MSVCRT.DLL
at 017f:78015ca2."

If none of the standard repair suggestions are helping you may need
to try to find out more about your crash. It is highly likely that the cause
of the crash is the *caller* of the crashing module but this information
is not provided with the Error Signature unless you try digging deeper
into the more details. (I haven't even worked out how to make good
use of those details yet.)

If it is an easily reproducible crash you might be able to capture the
necessary information by running your Dr. Watson utility.

<title>KB275481 - How to Troubleshoot Program Faults with Dr. Watson</title>

A related alternative is to guess that the cause is one of your third-party
programs, even though you have attempted to eliminate sources of known
malware. Use tools such as BHODemon (instead of just unchecking
Enable third-party browser extensions...) and msconfig to try to selectively
avoid using programs that you are currently running. If you are systematic
in your diagnosis you may eventually figure out what module is causing the
crash.


Good luck

Robert Aldwinckle