Robert
Sat May 15 11:16:45 CDT 2004
"Steve" <ati@bgt.inv> wrote in message
news:vi07a0hfalougu27k6mqauaikb59n7neg8@4ax.com...
> Been having problems with IE crashing, with the dreaded exception code
> oxc0000005. I've seen a few references to the possible culprit being
> a corrupt SHDOCVW.DLL file. IE version is 6.0.2800.1106. Microsoft
> database indicates SHDOCVW.DLL file date 8/29/02, file size 1,338,368.
>
> I have 3 SHDOCVW.DLL files on the system. One is in
> \windows\ServicePackFiles\386, dated 8/29/02, file size 1,341,440.
> The two others are both dated 1/21/04, both file size 1,339,904,
> located in \windows\system32 and \windows\system32\dllcache.
>
> Looks like maybe two of these should be deleted, and the other one
> might be corrupt? If so, which one should be left in, and how do I
> replace it with the correct version?
I have no idea what you did to find that size in the DLL Help Database.
Unfortunately it doesn't list all the possible versions due to patches.
FYI More important details than size are Version and Modified date
but using your data yields the following:
1,338,368 => KB324920 => 6.0.2800.1133 (Dec. 2002 Cum. patch)
1,339,904 => KB813489 => 6.0.2800.1170 (April 2003 Cum. patch)
1,341,440 => (DLL Help Database) => XPsp1 base
According to the latest cumulative update 832894
what you should have for that module (assuming your OS is XPsp1) is:
22-Jan-2004 00:15 6.00.2800.1400 1,339,904 Shdocvw.dll X86
BTW that assumption about your OS is only helped by the fact that you have
cross-posted to an XP newsgroup. (I am posting from IE6.Browser.)
So based on that analysis and depending on what your maintenance
level is I would say it could be there is nothing wrong with that module.
If you are unsure about what your current maintenance level is
copy the following script fragment to your Address bar, press Enter
and copy the results in a reply.
javascript:navigator.appMinorVersion
(It's just a convenient way of capturing the Update Versions: list
from IE's Help, About display.)
Why did you choose this module as your possible culprit?
Do you have some evidence that it may be involved in your
crashes? FYI the most common cause of crashes is malware
(e.g. interfering third-party programs). Therefore, disabling
Enable third-party browser extensions (requires restart)
is usually a better approach to take by starting an investigation
of that type of cause. If it changes your symptoms (apart
from not being able to use some third-party programs)
you will know where to focus further diagnosis.
> Thanks!
HTH
Robert Aldwinckle
---