I am using AppVer: 6.0.2800.1106 ModName: shell32.dll
ModVer:5.0.3700.6705 Offset:00003439
That shows that you have Win2000sp4 installed.
Was that done recently? Any post-sp4 patches?
(You need to think: "What changed?")
The MBSA or qfecheck tools if you have them might give you some
clues in that regard. SystemInfo from the command-line is another way
of getting similar information.
Plausible hypotheses for your crash could include:
1. misconfigured patches due to interference when they were applied
(e.g. was your anti-virus scanner active then?)
2. interference due to misapplied/broken hooks installed by malware
In the case of #1 improving the environment (e.g. disabling the interferer),
uninstalling the patch(es) and then reinstalling could be effective.
In the case of #2 try the plethora of suggestions you can find in this
newsgroup for dealing with that.
In either case it shouldn't hurt to try an IE Repair.
In fact a recent KB article documents an improved procedure for NT5
which you may want to try:
<TITLE>831429 - Windows XP stops responding when you download updates from Windows Update</TITLE>
<
http://support.microsoft.com/default.aspx?scid=kb;en-us;831429 >
For your convenience here is the main procedure for your OS
<quote>
Windows 2000
Method 1: Register your system files
To register your system files, follow these steps:
1.. Click Start, click Run, and then type:
regsvr32 /i Urlmon.dll
2.. Click OK.
3.. When you receive the "DllRegisterServer in urlmon.dll succeeded" message, click OK, and then try to use the Windows Update
site.
4.. If the problem repeats, repeat steps 1-3 for each of the following commands:
a.. regsvr32 /i Shdocvw.dll
b.. regsvr32 Msjava.dll
c.. regsvr32 Actxprxy.dll
d.. regsvr32 Oleaut32.dll
e.. regsvr32 /i Mshtml.dll
f.. regsvr32 /i Browseui.dll
g.. regsvr32 /i Shell32.dll
If the issue is not resolved, some system files may be incorrect. Go to the next method.
Method 2: Run the Internet Explorer Repair Tool
</quote>
The point of doing Method 2 will be to make use of the that tool's
verification procedure, since the actual list of modules re-registered
will only be a subset of the first.
There may be clues in the drwtsn32.log if you are not inhibiting it
and it is current. To capture salient information from drwtsn32.log
do a find up from the bottom for FAULT -> (assuming an English version
of Windows). That is the crash address. Page back a bit and you may
see some entrypoint information. More importantly though is the next
section, labeled Stack Back Trace. It contains information about the
caller of the crashing routine. Occasionally the section following it
(the Raw Stack Dump) contains clues in the interpreted portion which
has helped identify third-party causes.
I have just remembered that your OS by default seems not to include
much entrypoint information in the Stack Back Trace or even module
names in the module map! For that reason I have suggested to others
that they could temporarily enable the drwtsn32 Symbol Table Dump
to supplement those deficiencies. (Run... drwtsn32 and you will see
a check box for doing that.)
I'll try to download Netscape to this computer via disk so I can read
your link, as I don't have a browser on this computer since IE keeps
crashing before it even opens.
An alternative, if you have the space on your harddrive would be to
create a separate partition and load a parallel OS. Then use its browser.
BTW could you please test your assertion
with the following command (e.g. from the Run... dialog)
iexplore -nohome
In a sense that actually opens IE "before it opens". <g>
So if that works you might be able to use the Control Panel's
Internet Options applet to reset things, especially (for example)
- change your Home page to About:Blank
- disable search from the Address bar
- uncheck Enable third-party browser extensions (requires restart)
And if those kinds of things make your browser more usable
that in turn would more strongly suggest the possibility of malware
being the cause of your problem.
Good luck
Robert Aldwinckle
