Vista - Re: Problem when closing IE 7--pops up dialog to send error report

(cross-post added to Vista General)
"James" <james@hotmail.com> wrote in message
news:%23KGbFuTZHHA.1244@TK2MSFTNGP04.phx.gbl...
>
> <bishnuch8@gmail.com> wrote in message
> news:1173745997.262835.12030@j27g2000cwj.googlegroups.com...
>> On Feb 25, 9:36 pm, MNJames <MNJa...@discussions.microsoft.com> wrote:
>>> Nearly every time I close a window of IE 7 an error occurs. Dialog pops
>>> up
>>> saying "Internet Explorer has encountered a problem and needs to
>>> close..."
>>> and asks if I want to send an error report. Upon clicking yes or no, IE
>>> closes, as well as any other intance of IE open at the time.
>>>
>>> The error signature will be something like:AppName:iexplore.exe AppVer:
>>> 7.0.6000.16414ModName:unknown ModVer: 0.0.0.0 Offset: 001b5f40
>>>
>>> This is incredibly annoying. Will sometimes do this without my closing
>>> the
>>> IE window. Anybody have any ideas how to fix?


Before you can fix it you have to identify the problem more clearly.
Crashes in module:unknown can mean just about anything wrong
has happened.

Look for clues in the drwtsn32.log associated with the crash.
E.g. the Stack Back Trace can show you some of what was happening
before the crash.


>>
>> I have also the same problem, do somebody know about it?


> I did a clean install with no IE add ons, and the problem started almost
> immediately. I have given up trying to fix this as all the suggestion made
> in this newsgroup proved to be totally worthless.


"Check for malware" is just a way of advising to look for the most common
cause of this symptom. If malware has been eliminated as a possible cause
you could go on to do a more comprehensive clean-boot troubleshooting
procedure. For example, another common cause is incompatible device drivers,
so if you have any unusual hardware attached or you're trying to use drivers
which were designed for use with XP try disabling it and removing those drivers
as another test.


> I have gone back to XP
> prof and regret having spent money to buy this business edition, which I now
> consider the worst software investment I have ever made. I cannot understand
> why IE behaves that way, because with FFox I have no problems whatsoever.



Most likely it is not a case of IE misbehaving but something else interfering.
Since IE is the most common browser and since it has more dependencies
on the OS than other browsers, there is more potential for interference
by other programs.


FYI

Robert Aldwinckle
---

"Robert Aldwinckle" <robald@techemail.com> wrote in message
news:e7Do33eZHHA.1220@TK2MSFTNGP03.phx.gbl...
> (cross-post added to Vista General)
> "James" <james@hotmail.com> wrote in message
> news:%23KGbFuTZHHA.1244@TK2MSFTNGP04.phx.gbl...
>>
>> <bishnuch8@gmail.com> wrote in message
>> news:1173745997.262835.12030@j27g2000cwj.googlegroups.com...
>>> On Feb 25, 9:36 pm, MNJames <MNJa...@discussions.microsoft.com> wrote:
>>>> Nearly every time I close a window of IE 7 an error occurs. Dialog
>>>> pops
>>>> up
>>>> saying "Internet Explorer has encountered a problem and needs to
>>>> close..."
>>>> and asks if I want to send an error report. Upon clicking yes or no,
>>>> IE
>>>> closes, as well as any other intance of IE open at the time.
>>>>
>>>> The error signature will be something like:AppName:iexplore.exe
>>>> AppVer:
>>>> 7.0.6000.16414ModName:unknown ModVer: 0.0.0.0 Offset: 001b5f40
>>>>
>>>> This is incredibly annoying. Will sometimes do this without my closing
>>>> the
>>>> IE window. Anybody have any ideas how to fix?
>
>
> Before you can fix it you have to identify the problem more clearly.
> Crashes in module:unknown can mean just about anything wrong
> has happened.
>
> Look for clues in the drwtsn32.log associated with the crash.
> E.g. the Stack Back Trace can show you some of what was happening
> before the crash.
>
>
>>>
>>> I have also the same problem, do somebody know about it?
>
>
>> I did a clean install with no IE add ons, and the problem started almost
>> immediately. I have given up trying to fix this as all the suggestion
>> made
>> in this newsgroup proved to be totally worthless.
>
>
> "Check for malware" is just a way of advising to look for the most common
> cause of this symptom. If malware has been eliminated as a possible
> cause
> you could go on to do a more comprehensive clean-boot troubleshooting
> procedure. For example, another common cause is incompatible device
> drivers,
> so if you have any unusual hardware attached or you're trying to use
> drivers
> which were designed for use with XP try disabling it and removing those
> drivers
> as another test.
>
>
>> I have gone back to XP
>> prof and regret having spent money to buy this business edition, which I
>> now
>> consider the worst software investment I have ever made. I cannot
>> understand
>> why IE behaves that way, because with FFox I have no problems whatsoever.
>
>
>
> Most likely it is not a case of IE misbehaving but something else
> interfering.
> Since IE is the most common browser and since it has more dependencies
> on the OS than other browsers, there is more potential for interference
> by other programs.
>
>
> FYI
>
> Robert Aldwinckle
> ---
A did a clean install wih a disc format prior to that, no other software
installed, all hardware and device drivers are Vista approved, no add-ons in
the browser and yet I am getting this problem with the first website I am
trying to open. A solution I found was to open IE7 as an administrator, but
that procedure is simply ridiculous and should not be necessary in my
opinion.
>

"Harry" <harry@home.nl> wrote in message
news:et85p9$i8g$1@news5.zwoll1.ov.home.nl...
>
> "Robert Aldwinckle" <robald@techemail.com> wrote in message
> news:e7Do33eZHHA.1220@TK2MSFTNGP03.phx.gbl...
>> (cross-post added to Vista General)


....
>> Before you can fix it you have to identify the problem more clearly.
>> Crashes in module:unknown can mean just about anything wrong
>> has happened.
>>
>> Look for clues in the drwtsn32.log associated with the crash.
>> E.g. the Stack Back Trace can show you some of what was happening
>> before the crash.


Another tool which can show you the Stack is Process Explorer.


> A did a clean install wih a disc format prior to that, no other software
> installed, all hardware and device drivers are Vista approved, no add-ons in
> the browser and yet I am getting this problem with the first website I am
> trying to open. A solution I found was to open IE7 as an administrator, but
> that procedure is simply ridiculous and should not be necessary in my
> opinion.



That's good. Now you have a point of comparison.
E.g. Run... ProcMon using an identical scenario for both cases
and compare the traces.



Good luck

Robert
---