(cross-post added to Vista Perf & Maint)
"Chiefs" wrote in message ...
I have a 64 bit windows vista os and recently IE8 gives me the message
"Internet Explorer has stopped working...windows is checking for a solution
to the problem" When I click "close" on the message box, it goes away but IE
is still up and running. Then a box pops up informing me about the DEP
causing the problem. I tried disabling almost all IE add-ons but the problem
persists. I ran an AVG scan and no virus shows up. When I tried to switch the
DEP settings to add IE8.exe to be excluded, I couldn't find the file that
ended in "exe". I found the IE8 folder, but no "exe" file.


Disabling DEP is not a good idea IMO. Find out the cause of the crash.
It is very likely going to be an incompatible third-party program which is
somehow involved in the calling sequence which led up to the crash.
An example would a toolbar which runs independently and can not be
stopped by IE's No Add-ons mode.


Any help or suggestions are greatly appreciated!!!


You need to get the Stack Back Trace associated with the DEP event.
Using ProcMon would be one way if drwtsn32.log doesn't capture it.
Apparently Vista no longer provides drwtsn32.exe. I don't know what
it provides as an alternative for capturing stack information. You can
at least get information about the loaded modules from the Error Report
details window but it is not searchable or even capturable AFAIK.
If the problem symptom is not easily reproducible you could also get some
module and stack info from Process Explorer (aka ProcExp) but that would
be post-event data and therefore potentially not as useful.


Good luck

Robert Aldwinckle
---

"Robert Aldwinckle" wrote in message
...
(cross-post added to Vista Perf & Maint)
"Chiefs" wrote in message
...
I have a 64 bit windows vista os and recently IE8 gives me the message
"Internet Explorer has stopped working...windows is checking for a
solution
to the problem" When I click "close" on the message box, it goes away
but IE
is still up and running. Then a box pops up informing me about the DEP
causing the problem. I tried disabling almost all IE add-ons but the
problem
persists. I ran an AVG scan and no virus shows up. When I tried to switch
the
DEP settings to add IE8.exe to be excluded, I couldn't find the file that
ended in "exe". I found the IE8 folder, but no "exe" file.


Disabling DEP is not a good idea IMO. Find out the cause of the crash.
It is very likely going to be an incompatible third-party program which is
somehow involved in the calling sequence which led up to the crash.
An example would a toolbar which runs independently and can not be
stopped by IE's No Add-ons mode.


Any help or suggestions are greatly appreciated!!!


You need to get the Stack Back Trace associated with the DEP event.
Using ProcMon would be one way if drwtsn32.log doesn't capture it.
Apparently Vista no longer provides drwtsn32.exe. I don't know what
it provides as an alternative for capturing stack information. You can
at least get information about the loaded modules from the Error Report
details window but it is not searchable or even capturable AFAIK.
If the problem symptom is not easily reproducible you could also get some
module and stack info from Process Explorer (aka ProcExp) but that would
be post-event data and therefore potentially not as useful.


Good luck

Robert Aldwinckle
---

Some things that MAY capture enough information to give some hint
about whether this DEP event is related to the DEP event problems
I'm seeing, but in the Windows Mail program instead:

1. Have Windows Task Manager running on part of the screen while
you have IE8 running on another part. Check if, shortly before the
problem, Windows Task manager shows a little more than 50% of
Physical Memory in use.

2. Remember if you were doing a search for anything at the start of
the problem.

3. Check your Favorites folder and any subfolders under it, and tell
us how many entries you have in the largest folder or subfolder you
have in the Favorites folder tree.

4. Run the Disk Cleanup program before and after the IE8 session
with problems, and record any changes in space allocated to system
error memory dumps or any other types of error reports, but DON'T
use this program to erase any of them. Somewhere, I've found a
program to send these error reports to Microsoft, and then check
if there are any known fixes for the problems, but I don't remember
the details now. It may be named Problem Reports and Solutions.

Robert Miles