SP1 doesn't fix "Windows Explorer has stopped responding." Ready toput my fista through vista!

  • Thread starter Thread starter boeroboy
  • Start date Start date
What's the fault data for this rumored crash of yours? This marks the second
time you've referenced mythical crashes without providing any relevant
data - not crash data nor steps to reproduce the issue. I've generally been
pretty effective about getting things fixed when given the chance. =)

Generally most Microsoft software is tested insanely intensively and has
pretty high reliability. I'm not sure what unique scenarios you've found to
introduce problems. The developers on the Explorer team are generally
pretty excellent when it comes to fixing mistakes, but maybe that's my bias
since I know how they react when they actually get data to work with as
opposed to phantom rumors of crashes. I will admit that most companies and
most developers probably have an awfully hard time triaging and diagnosing a
problem summary of "I crashed!" - but as noted that's rather developer,
application, and OS agnostic. =)

-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
Adam Albright said:
It is simple enough to follow.
Click to expand...
Event............. application crash
Click to expand...
Name.............. Windows internal build-in Explorer
Click to expand...
Fault............. ntdll.dll (Windows NT kernel functions)
Click to expand...
If "I have her running in a simple non privileged environment and all
she does is use Outlook and IE as they came out of the box NO
ADDONS!"
Click to expand...
 
Thanks for clearing the dust on the guy with the HEX editor problem. I can
give you full assurance that my wife thinks HEX is some kind of "spell"
placed on someone by a witch. As I said her system is right out of the box
and all she uses are IE 7 and Outlook 2003 and occasionally plays solitaire.

It is not important to me whether these are unique problems in Microsoft's
view. In my view, and you can share it by Googling the problem description,
this problem is widespread and the only thing it is unique to is Windows
Vista. I will happily post the error dumps for several of these crashes that
have occurred in the past couple of days as soon as I can.
 
Whether or not these are "unique" problems is utterly irrelevant to me. I
fought passionately to get a fix for an issue that was crashing many people,
and I fought passionately to get a fix for an issue that had apparently only
crashed one person ever. I simply like excellence. I apologize for
confusing you in that regard. =)

My point was merely that YOUR problem is comparatively unique, and that
anyone attempting to analyze or comment upon your issue before being
provided the specifics that I ask for would be doing you a disservice. It's
not a qualitative analysis/priorization of your issue (again, I treat them
all the same- it's simply easier to get traction with others on Big Issues),
it's actually a technical analysis - I simply don't have anything to go on
because there's no data on the table. =)

As such, a reference to any other site is happily contextual irrelevant:
happy because hey, I'm here interested in YOUR problem. Let's do this. ;-)

Cheers,
-Zach
 
It turns out they rewrote Hex Editor - you were using version 3, their
version 4 looks like it works great.

People should see that helpful response('hey, you probably want to
update...) from "Known solutions" soon.
 
Back
Top