Microsoft maintains a knowledge base of articles on various subjects here:
http://support.microsoft.com/default.aspx?pr=kbinfo   When you define a
search, do it on all products initially.  If you get too many results, you
can cut back on the number of results by searching on a particular product.
The trick to finding information is to provide enough details so you get
what you want but not use so few details that the amount of articles are
staggering.  And, if you use too many details, you might miss what you are
looking for.  Only experience in conducting searches will tell you how many
details is just right.

Often you can find what you need by enclosing an error message in quote
marks; however, be careful not to include too much.  For example, here is an
error message:

IEXPLORE caused an invalid page fault in module KERNEL32.DLL at
0137:bff798fb.

If you search on this error message with it enclosed in quotes, the message
will have to appear verbatim in the KB article in order to get a match.
Quite often the KB article will list the article like this:

IEXPLORE caused an invalid page fault in module KERNEL32.DLL at memory
address.

If you use the entire message within quotes, you will not get a hit because
"0137:bff798fb" in the search criteria will not match "memory address"
listed in the article.  So, in this instance, your search criteria including
quote marks would be:

"IEXPLORE caused an invalid page fault in module KERNEL32.DLL"

You can use this same technique to search the Google search engine archives
<http://groups.google.com/groups>.  Include the info within quotes and you
might get a little better info if outside the quotes, you include:  MVP

There are a few articles containing "Explorer caused an invalid page fault
in module explorer"

In addition to Ron's information, it is quite likely that the error is due to damage
to the Windows shell through damage inflicted upon Internet Explorer, which is
integrated into the shell.  The damage may have been caused by one of those
uninstalls.

Follow the procedures here -->
Recovering From a Failed Internet Explorer Upgrade in Windows 98:
http://www.cs.bsu.edu/~gjjones/administrivia/stories/2003/03/21/recoveringFromAF
ailedInternetExplorerUpgradeInWindows98.html
or
http://tinyurl.com/r5ba

Especially the section at the end:

"If you still have boot problems after you reboot, you should use the command prompt
to edit the c:\windows\system.ini file. On the command line type edit
c:\windows\system.ini."

"Once it is open, change the line shell=explorer.exe to shell=progman.exe. What you
are doing here is changing the default shell (that is having problems) from the
Windows Explorer to the old Windows Program Manager shell."  Press Alt, F, S to save
the changes; then Alt, F, X to close.

"Reboot Windows. It should now successfully boot with no errors into an empty
Program Manager shell. Use the File | Run | Browse drop down menu selection to
browse to c:\program files\internet explorer (C:\Progra~1\Intern~1) or
C:\WINDOWS\Windows Update Setup Files (C:\Windows\Window~1) and launch ie5setup.exe
or ie6setup.exe (depending on what is there)."  Do a Minimal-custom install "and
check all the Bold faced options. When the setup program alerts you that these files
are already installed, tell it to reinstall all of the files."

"When the Internet Explorer Setup program is done and reboots, hit the F8 key to
bring up a Boot Menu. Choose Command Prompt and boot to the command prompt. Once
there, type edit c:\windows\system.ini and, once it is open, change the line
shell=progman.exe back to shell=explorer.exe. Save and exit the file. You have now
set the shell back to the original value."