Explorer restarts desperate for a solution

  • Thread starter Thread starter AustinZ123
  • Start date Start date
A

AustinZ123

All right I have tried every suggestion out there, the microsoft work
around: http://support.microsoft.com/?kbid=883791, looked in Google,
asked in IT forums and no solution, the problem with explorer
restarting with no error message persists, is there any solution??
My PC is clean no viruses or any of that sort, used hijack this, ewido
and everything but explorer keeps restarting with no error message.
 
First,in system properties,advanced,start up,uncheck the box "restart
computer
in system failure",close out,open C: drive,windows,locate mini dump,delete
all files if any are stored from the crash(s),close out.Also,for IE,thier
is a
hotfix for IE failure in SP2,the hotfix nos is:892052 You might run disk
clean
and defrag before you install it.
 
All right I have tried every suggestion out there, the microsoft work
around: http://support.microsoft.com/?kbid=883791, looked in Google,
asked in IT forums and no solution, the problem with explorer
restarting with no error message persists, is there any solution??
My PC is clean no viruses or any of that sort, used hijack this, ewido
and everything but explorer keeps restarting with no error message.

All sorts of people have reported symptoms of Windows Explorer crashing
repeatedly, almost always without anything in the event log or error
message to give anything to be able to track it down.

All sorts of things have been blamed for this.

Almost none of those were ever actually confirmed to be a real cause.

Nothing has been announced that scans a system and reports or repairs
any of these claimed problems.

All this appeared to start immediately following SP2.

You can google for old postings of mine in microsoft.public.windowsxp.general
that summarized all the claimed causes of this and which were reponses to
several hundred people describing very similar symptoms.

Apparently nothing has been done to change any of this.

My apologies.
And it isn't even my fault.
 
Don said:
All sorts of people have reported symptoms of Windows Explorer
crashing repeatedly, almost always without anything in the event log
or error message to give anything to be able to track it down.

Geez Louise. Give it a rest already. Service Pack 2 has been out for
over a year. Most of the regular helpers in these newsgroups, many of
us doing some kind of tech support for a living, have installed
hundreds (some thousands) of copies of Service Pack 2 with very few
problems. And those problems were solved. Only you seem to have
impossible-to-solve problems with SP2 - or are actively *looking* for
problems. You don't have enough to do with your time. Find a healthy
hobby unconnected with tech and/or help others in your local community.

To the OP - take your machine to a professional computer repair shop
(not your local version of BigStoreUSA) and have them take care of this
for you. Someone on-site working with the machine hands-on is going to
be able to diagnose and fix your computer far better than people
reading about it in a newsgroup. Some issues are easily solved in
writing; this is not one of them.

Malke
 
Malke said:
Don Taylor wrote:
Geez Louise. Give it a rest already. Service Pack 2 has been out for
over a year. Most of the regular helpers in these newsgroups, many of
us doing some kind of tech support for a living, have installed
hundreds (some thousands) of copies of Service Pack 2 with very few
problems. And those problems were solved. Only you seem to have
impossible-to-solve problems with SP2 - or are actively *looking* for
problems. You don't have enough to do with your time. Find a healthy
hobby unconnected with tech and/or help others in your local community.

Do something a customer really appreciates and they might tell a handful
of others. REALLY piss off a customer and they will tell anyone and
everyone they see what they think of you for the rest of your life and
beyond.

It isn't just me with these SP2 Win Explorer lockups and crashes, we see
people posting these same problems here again and again and again and again.
This guy's posting was just one more of the hundreds.
To the OP - take your machine to a professional computer repair shop
(not your local version of BigStoreUSA) and have them take care of this
for you. Someone on-site working with the machine hands-on is going to
be able to diagnose and fix your computer far better than people
reading about it in a newsgroup. Some issues are easily solved in
writing; this is not one of them.

Well, at least you didn't blame it all on spyware.
 
Sometimes there is a fall over point where continuing to analyze and
diagnose an ongoing issue isn't beneficial. Because Explorer is at the
heart of XP the issue could have hundreds of causes I've experienced
the "Don't Give Up, I'll fix this SOB". Lot's of times I've learned how
to make those fall over decisions about computer issues.
If not already attempted, I'd first do a Repair install of XP. If you've
already jumped that hurdle with no resolution then a fresh install of
XP is warranted. If you do take the Fresh install path, be sure to use
Imaging software at several steps in the process so you can "Backup"
if your issue starts to reappear (after a Driver or App is installed).
Also, I respect Malke's Technical expertise and demeanor. Try to
answer thousands of postings and not be a little brusk every now &
then. It isn't an easy thing to do.
 
R. McCarty said:
Sometimes there is a fall over point where continuing to analyze and
diagnose an ongoing issue isn't beneficial. Because Explorer is at the
heart of XP the issue could have hundreds of causes I've experienced
the "Don't Give Up, I'll fix this SOB". Lot's of times I've learned how
to make those fall over decisions about computer issues.
If not already attempted, I'd first do a Repair install of XP. If you've
already jumped that hurdle with no resolution then a fresh install of
XP is warranted. If you do take the Fresh install path, be sure to use
Imaging software at several steps in the process so you can "Backup"
if your issue starts to reappear (after a Driver or App is installed).

If you look at old postings to this group from me you it describes
in detail that I spent months with MS SP2 tech support doing more
and more and more things under their direction to try to diagnose
the problem. I was actually trying to be helpful and provide them
with the info to actually be able to track down and find at least
the very specific and repeatable bug that I had. I intentionally
didn't "just torch the system and start over", thinking we might
actually get them to find and fix this one, since so many people
were reporting very similar problems starting immediately after
SP2, and continuing to the present day. Back when I did high
reliability software for a living I would have killed for a customer
with a repeatable bug who actually wanted to help me find and fix it.
Also, I respect Malke's Technical expertise and demeanor. Try to
answer thousands of postings and not be a little brusk every now &
then. It isn't an easy thing to do.

I was very careful. I specifically didn't say anything about his
expertise or his demeanor. And I do realize that the volunteers
here ain't got a clue in the world how to track down, find and fix
this one. That's why it has gone on unchanged for for fifteen
months. If we had a tool that would actually capture these failures
then we might be to get the information needed to be able to put a bug,
no pun intended, in someone's ear and get the introduced bugs fixed.
 
Back
Top