F
Frank D. Nicodem, Jr.
I am running Windows XP Home Edition, and am experiencing crashes in
Explorer with increasing frequency. The symptom usually takes one of two
forms. Most commonly, I have a Windows Explorer window open, and I may (or
may not) be doing anything in it. Perhaps I've just clicked (or even
right-clicked) on a folder or file; or (occasionally) I'm doing nothing at
all at the moment, but the window is just open. Suddenly, an error message
pops up that there is an "Application Error" in the file ntdll.dll -- and
most commonly there is additional information about an inability to write to
memory. Then, when I click on "OK", the Windows Explorer window closes,
along with all other icons on my desktop (and on my Task Bar). There is a
brief (!) pause, after which all of the icons on my desktop are refreshed,
and I can (usually) re-open Windows Explorer and continue.
While this is the most common symptom, a secondary symptom is that, instead
of the "Application Error" message coming up, I get only the "Windows
Explorer has caused an error..." message, with the "Send..." and "Don't
Send..." buttons on it. (I almost always click "Send", although I have no
idea what Microsoft does with this information! Apparently very little.)
On *rare* occasions, after Explorer has crashed, my desktop icons do NOT get
refreshed. And I CANNOT re-open Windows Explorer (or, for that matter, do
much of anything else, except in windows that are already open). I can't
get to the Start button, or the Task Bar; and my only recourse at these
times is to shut the system down and re-boot (which I usually try to do via
the Task Manager -- if it will come up; sometimes I have to actually power
down, because NOTHING is working).
The problem used to occur once or twice a day; it is now occurring with
increasing frequency. I've been running my system for just over a year, and
during that time I am *extremely* careful to install all Windows Updates --
so I should be totally current. Likewise, I run various anti-virus and
anti-spyware programs (including rootkit revealers), so I can almost always
guarantee that my system is "clean". At the same time, as a software
developer, I have installed literally hundreds of applications on my system
(and uninstalled many of these, as well); so I'm sure that the Registry is
in terrible shape. (I do use several different Registry "cleaners", though.
I'm extremely anal about maintaining my system!)
I've run several different Scan/Check programs on my disk; and just
yesterday I used the System File Checker (sfc/scannow), to see if that would
help. I can't say for sure that it did. It *seemed* that the number of
crashes was reduced, but there were still several. (I was up to over a
dozen per day. Sometimes the system will crash only minutes after I've
re-booted it!)
I do have Visual Studio installed (as I'm an application developer), as well
as many other programming, utility, and maintenance tools -- many of which
"drill down" pretty deeply into the system. What could be causing this
repeated problem with "Application Errors" in ntdll.dll, and errors writing
to memory? And what (if any) solution might there be? I really don't want
to "scrub" the entire system, and re-install everything; it would take me
literally weeks, based on all of the software installations, configurations,
and modifications I've made over the last year or so.
Upon "Googling" anything about ntdll.dll errors, I find that it seems to be
a fairly common topic on the Internet. Any suggestions on what to do????
Explorer with increasing frequency. The symptom usually takes one of two
forms. Most commonly, I have a Windows Explorer window open, and I may (or
may not) be doing anything in it. Perhaps I've just clicked (or even
right-clicked) on a folder or file; or (occasionally) I'm doing nothing at
all at the moment, but the window is just open. Suddenly, an error message
pops up that there is an "Application Error" in the file ntdll.dll -- and
most commonly there is additional information about an inability to write to
memory. Then, when I click on "OK", the Windows Explorer window closes,
along with all other icons on my desktop (and on my Task Bar). There is a
brief (!) pause, after which all of the icons on my desktop are refreshed,
and I can (usually) re-open Windows Explorer and continue.
While this is the most common symptom, a secondary symptom is that, instead
of the "Application Error" message coming up, I get only the "Windows
Explorer has caused an error..." message, with the "Send..." and "Don't
Send..." buttons on it. (I almost always click "Send", although I have no
idea what Microsoft does with this information! Apparently very little.)
On *rare* occasions, after Explorer has crashed, my desktop icons do NOT get
refreshed. And I CANNOT re-open Windows Explorer (or, for that matter, do
much of anything else, except in windows that are already open). I can't
get to the Start button, or the Task Bar; and my only recourse at these
times is to shut the system down and re-boot (which I usually try to do via
the Task Manager -- if it will come up; sometimes I have to actually power
down, because NOTHING is working).
The problem used to occur once or twice a day; it is now occurring with
increasing frequency. I've been running my system for just over a year, and
during that time I am *extremely* careful to install all Windows Updates --
so I should be totally current. Likewise, I run various anti-virus and
anti-spyware programs (including rootkit revealers), so I can almost always
guarantee that my system is "clean". At the same time, as a software
developer, I have installed literally hundreds of applications on my system
(and uninstalled many of these, as well); so I'm sure that the Registry is
in terrible shape. (I do use several different Registry "cleaners", though.
I'm extremely anal about maintaining my system!)
I've run several different Scan/Check programs on my disk; and just
yesterday I used the System File Checker (sfc/scannow), to see if that would
help. I can't say for sure that it did. It *seemed* that the number of
crashes was reduced, but there were still several. (I was up to over a
dozen per day. Sometimes the system will crash only minutes after I've
re-booted it!)
I do have Visual Studio installed (as I'm an application developer), as well
as many other programming, utility, and maintenance tools -- many of which
"drill down" pretty deeply into the system. What could be causing this
repeated problem with "Application Errors" in ntdll.dll, and errors writing
to memory? And what (if any) solution might there be? I really don't want
to "scrub" the entire system, and re-install everything; it would take me
literally weeks, based on all of the software installations, configurations,
and modifications I've made over the last year or so.
Upon "Googling" anything about ntdll.dll errors, I find that it seems to be
a fairly common topic on the Internet. Any suggestions on what to do????