I have 2 brand new Vista certified machines running Vista, I use Ultimate and
my wife uses Home Premium. I see the explorer hang now and then in Ultimate
and I run a fairly complex setup when it comes to applications. My wife sees
the problem several times a week since SP1 was installed. I have her running
in a simple non priviledged environment and all she does is use Outlook and
IE as they came out of the box NO ADDONS!
I read this thread because I was looking for solutions and all I got for the
most part was people pointing fingers at everything but the real problem.
If I wanted an operating system that would only allow me to run a
preconfigured menu of software I would buy an Apple. But no, I want the
flexibility of having an OS that is secure but still configurable enough to
give me a good user experience. Too many people in this discussion jumped
directly from the real problem to a solution that suits their own fantasies.
Finally the guy who started the conversation innocently and earnestly asking
for help provided the MS dude with the "buckets" and that is where the
solution search ended some 11 days ago. I guess the info wasn't as
enlightening as had been hoped.
This thread is a waste of time.
It is simple enough to follow.
Event............. application crash
Name.............. Windows internal build-in Explorer
Fault............. ntdll.dll (Windows NT kernel functions)
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!"
This is further confirmation that Vista and/or SP1 are FLAWED. Of
course the fanboy club prefers to stick their pointy heads in the sand
and pretend that can't be so.
For what it's worth I've seen the exact same thing you've experienced
on other systems. I or someone I know that is doing the install
correctly does a clean install of Vista, it comes up, you start to
test it BEFORE adding a damn thing, no addons, no patches, no third
party software and bam, Explorer crashes, with the system reporting
the laughable warning it has to shut down one of it's own modules
because it , nothing else caused problems.
Microsoft makes junk. Sad but true statement. Once you understand
that, everything else makes sense. Windows Explorer sadly a key
element in every version of Windows from the beginning is so
integrated into the kernel it causes all kinds of errors because it is
buggy as hell and never really has been fixed. Over twenty years and
counting. Think Microsoft cares? Don't look like it if something has
been poorly designed and "broken" for over two decades. Of course
Explorer has been patched and tweaked to death, but no matter what
Microsoft does with it never works right and is sure to crash without
warning.
