Dr Watson error when opening Internet Explorer 1

[zoeythecat]

Hi All,

I have an end user who has Internet Explorer 5.0 (trying to run Windows Update to install IE6). When opening the Internet Explorer window I immediately get the following error:
Dr. Watson for Windows NT. "An application error has occurred and an application error log is being generated". "iexplore.exe, Exception: access violation (0xc0000005), Address: 0x00da174a"

I have searched google and could not find anything relating to this exact message. I get some articles but not any that would resolve my problem. I can launch the Internet Explorer browser but this error comes up which prevents me from running Windows Update. Can anyone offer any help or articles on how I can resolve?

Thanks in advance,
Zoey

 

[bcastner]

You need to be a local Administrator.

 

[zoeythecat]

Bcastner,

Thanks for your response. This is happening logged on as the Administrator locally and on the domain.

 

[bcastner]

An access violation is literally an attempt to read or write to a registry key, or folder location, on which the user does not have sufficient permissions.

Approach the problem in a different way by using the direct download installation rather than Windows Update:

http://www.compu-docs.com/ieadmininstall.htm

 

[zoeythecat]

Bcastner,

Thanks....That did the trick. I really appreciate the link. I did not realize there was a way to install IE locally. The setup file I downloaded but when I executed the file it was looking for a download site.

This resolved the Dr. Watson error.

Thanks again,
Zoey

 

[zoeythecat]

Just to correct a typo to my response. I originally downloaded the setup file from the Windows Update site to a network location and when I extracted that file it was asking for a download site and then I got the error. The link Bcastner provided gave me a way to install IE6 locally.

Thanks again!!!!!!

 

[eyec]

i resolved the Dr. Watson issue by disabling him

MS still does not have a very good memory manager

 

[bcastner]

eyec,

If you can ignore a problem, does it then go away?
I do not think it is necessary to have DrWatson enabled. But the error is not because it is enabled.
The error is because there is a problem.
Fix the problem.

 

[eyec]

bcastner,

if MS can say, "reboot and that will fix your problem", then i can surely do without DW and manage on my own. besides DW has never played nice with a lot of good software just because it wanted to use resources MS never thought programs should use. remember, "nobody will ever need more than 640k of memory"?

DW does perform some valid tasks, i just have not found them.

 

[bcastner]

eyec,

If the Bill Gates quote is to show he is an idiot, or that Microsoft is a stumblebumb company, it carries no water for me. Under the original x86 model many moons ago Gates was correct. Unless an application supported Extended or Enhanced or various schemes, the memory model was against any user benefit from more memory.

I am concerned that the small debug model posed by Dr. Watson proves a performance or application issue for you. I have not personally seen this, but I have not personally seen a lot of things. Please consider the design and implementation intentions of the small debug model discussed in many sites, but in shorthand form here:

http://support.microsoft.com/default.aspx?scid=kb;en-us;315263&FR=1&PA=1&SD=HSCH

As I mentioned in my previous post, I do not think it a necessity to run a debug session for the "normal" user. I will request enabling Dr. Watson by end-users for diagnostic purposes. It is very rare that the mini-dump produced does not resolve hardware issues. As I am sure you are aware, there are other registry-based settings that allow one to explore issues with the TCP/IP, Winsock, and for AD settings, Group Policy diagnostics, and these are made active when needed. And the wealth of error logging information available under the client is impressive, as is the fact that the OS designers deliberately made provisioning for this.

If you have not found yet the resources available from a mini-dump, Microsoft offers a wealth of free TechNet, MSDN and other resources. And having produced a mini-dump, you can always then send to OCA for suggestions.

Microsoft through the WHDC web-site offers incredible resources, and their is a web-site for each product to discuss any performance issues or interpretation issues you might have:

http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx

 

[eyec]

Bill,

you resolved zoeythecat's problem quickly, i made a tongue in cheek comment (that you understood); end of story.

have a safe and joyous holiday season.

steve