View Single Post
  #2  
Old April 16th 06, 02:39 PM posted to microsoft.public.windowsme.internet
external usenet poster
 
Posts: n/a
Default Kernel32.DLL.Iexplore error

Hi,
I get this once every couple of weeks and have been unable to resolve it on
this machine, but see if the following helps...

It's likely that another program is interfering with IE- possibly an adware,
spyware, parasite program.
See:
The Parasite Fight http://www.aumha.org/a/quickfix.htm
Dealing with Unwanted Spyware and Parasites:
http://mvps.org/winhelp2002/unwanted.htm
More security tips at http://www.aumha.org/a/parasite.htm
Bugs, Glitches & Stuffups: http://www.mvps.org/inetexplorer/Darnit.html

Or...
A legitimate program running in the background may be causing this. Disable
(for diagnostic purposes) programs such as pop-up blockers, security,
anti-virus, etc. Also... notorious for causing problems- Gator, Kazaa and
some others. You may have to reinstall, or not reinstall, a program.

There are other possibilities for KERNEL32 errors, including corrupted or
outdated video drivers
http://inetexplorer.mvps.org/archive...s.htm#kernel32
Start at Control Panel Display Settings Advanced for information on your
video adapter/driver including (possibly) a link to the manufacturer's
website.

Additional information at:
http://www.colba.net/~hlebo49/erriex...RRKERNEL32.DLL
http://aumha.org/win4/a/kernel32.php

276393 - Understanding and Troubleshooting Unrecoverable Errors (Faults) in
Internet Explorer: http://support.microsoft.com/?kbid=276393

Hope this helps,
Don
[MS MVP- IE]

"Mopsy" Mopsy[at]discussions.microsoft.com wrote in message
...
I have a laptop that has WinMe as the operating system. I was told to
upgrade to IE6 so I could participate in a website. I did that and now I
constantly get the following message: Iexplore has caused an error in
Kernel32.DLL.Iexplore and will now close. At first it was once in a

while,
now it hangs there and you have to hard boot and even that doesn't

eliminate
it always. Do I try to uninstall or what? I can't find that particular
error covered with Microsoft or this discussion area.

Mopsy