Explorer needs to restart

getting the error below when I right click on an icon on my desktop,
any ideas?

Rick


Log Name: Application
Source: Application Error
Date: 9/23/2008 3:53:18 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Blackie
Description:
Faulting application Explorer.EXE, version 6.0.6001.18000, time stamp
0x47918e5d, faulting module ntdll.dll, version 6.0.6001.18000, time
stamp 0x4791a7a6, exception code 0xc0000374, fault offset 0x000b015d,
process id 0xd4c, application start time 0x01c91c17b5fab43e.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2008-09-23T19:53:18.000Z" />
<EventRecordID>2161222</EventRecordID>
<Channel>Application</Channel>
<Computer>Blackie</Computer>
<Security />
</System>
<EventData>
<Data>Explorer.EXE</Data>
<Data>6.0.6001.18000</Data>
<Data>47918e5d</Data>
<Data>ntdll.dll</Data>
<Data>6.0.6001.18000</Data>
<Data>4791a7a6</Data>
<Data>c0000374</Data>
<Data>000b015d</Data>
<Data>d4c</Data>
<Data>01c91c17b5fab43e</Data>
</EventData>
</Event>

(I'll take a look at this tomorrow if no one else helps you sort it out
first.)

--
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.
--
"Rick" <> wrote in message
news:2026e352-3198-40b9-98ce-...
> getting the error below when I right click on an icon on my desktop,
> any ideas?
>
> Rick
>
>
> Log Name: Application
> Source: Application Error
> Date: 9/23/2008 3:53:18 PM
> Event ID: 1000
> Task Category: (100)
> Level: Error
> Keywords: Classic
> User: N/A
> Computer: Blackie
> Description:
> Faulting application Explorer.EXE, version 6.0.6001.18000, time stamp
> 0x47918e5d, faulting module ntdll.dll, version 6.0.6001.18000, time
> stamp 0x4791a7a6, exception code 0xc0000374, fault offset 0x000b015d,
> process id 0xd4c, application start time 0x01c91c17b5fab43e.
> Event Xml:
> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Application Error" />
> <EventID Qualifiers="0">1000</EventID>
> <Level>2</Level>
> <Task>100</Task>
> <Keywords>0x80000000000000</Keywords>
> <TimeCreated SystemTime="2008-09-23T19:53:18.000Z" />
> <EventRecordID>2161222</EventRecordID>
> <Channel>Application</Channel>
> <Computer>Blackie</Computer>
> <Security />
> </System>
> <EventData>
> <Data>Explorer.EXE</Data>
> <Data>6.0.6001.18000</Data>
> <Data>47918e5d</Data>
> <Data>ntdll.dll</Data>
> <Data>6.0.6001.18000</Data>
> <Data>4791a7a6</Data>
> <Data>c0000374</Data>
> <Data>000b015d</Data>
> <Data>d4c</Data>
> <Data>01c91c17b5fab43e</Data>
> </EventData>
> </Event>
>

Hm. It seems like you have a bogus shell extension installed. What
software did you install before this started happening?

That fault data from the Event Viewer is generally inferior to the data
found in the Problem Reports and Solutions Center control panel -
specifically the fault bucket number you get after Checking for Solutions
can be a great help in diagnostics. But regardless the data so far is a
little generic. If you get this crash again, the fault bucket number for
that crash might be interesting, but it may take inspection of an actual
crash DMP file from a crash to identify the probably culprit.

-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.
--
"Rick" <> wrote in message
news:2026e352-3198-40b9-98ce-...
> getting the error below when I right click on an icon on my desktop,
> any ideas?
>
> Rick
>
>
> Log Name: Application
> Source: Application Error
> Date: 9/23/2008 3:53:18 PM
> Event ID: 1000
> Task Category: (100)
> Level: Error
> Keywords: Classic
> User: N/A
> Computer: Blackie
> Description:
> Faulting application Explorer.EXE, version 6.0.6001.18000, time stamp
> 0x47918e5d, faulting module ntdll.dll, version 6.0.6001.18000, time
> stamp 0x4791a7a6, exception code 0xc0000374, fault offset 0x000b015d,
> process id 0xd4c, application start time 0x01c91c17b5fab43e.
> Event Xml:
> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Application Error" />
> <EventID Qualifiers="0">1000</EventID>
> <Level>2</Level>
> <Task>100</Task>
> <Keywords>0x80000000000000</Keywords>
> <TimeCreated SystemTime="2008-09-23T19:53:18.000Z" />
> <EventRecordID>2161222</EventRecordID>
> <Channel>Application</Channel>
> <Computer>Blackie</Computer>
> <Security />
> </System>
> <EventData>
> <Data>Explorer.EXE</Data>
> <Data>6.0.6001.18000</Data>
> <Data>47918e5d</Data>
> <Data>ntdll.dll</Data>
> <Data>6.0.6001.18000</Data>
> <Data>4791a7a6</Data>
> <Data>c0000374</Data>
> <Data>000b015d</Data>
> <Data>d4c</Data>
> <Data>01c91c17b5fab43e</Data>
> </EventData>
> </Event>
>

On Wed, 24 Sep 2008 12:01:26 -0700, "zachd [MSFT]"
<> wrote:

>
>Hm. It seems like you have a bogus shell extension installed. What
>software did you install before this started happening?
>
>That fault data from the Event Viewer is generally inferior to the data
>found in the Problem Reports and Solutions Center control panel -
>specifically the fault bucket number you get after Checking for Solutions
>can be a great help in diagnostics. But regardless the data so far is a
>little generic. If you get this crash again, the fault bucket number for
>that crash might be interesting, but it may take inspection of an actual
>crash DMP file from a crash to identify the probably culprit.
>
>-Zach

Again no answer why Windows Explorer constantly crashes, just more
attempts to blame third part software. You're a broken record Zach.

Here's a hint to point you in the right direction. Vista is the
operating system. It is suppose to CONTROL what other hardware and
software are doing. We've been told that under Vista everything is
suppose to be running in it's own protected memory space so one
application doing something bad, real or imagined WON'T crash another.
Strange that anytime there is a little burp the response always seems
to be the same ===> Windows "needs to shut down". Therefore it clearly
it isn't that big a leap to come to the conclusion it is WINDOWS that
is broke and not doing it's job properly.

The parallels in the real world are many. These days if a car starts
to go into a skid, a computer chip takes control helping the driver to
recover. If there is a power spike on the line, the power supply or a
UPS filer it out. If it rains hard and water enters your sump, it gets
pumped out. No user interaction required, no interruption of service.
No flashing neon sign saying it can't or won't.

When Windows detects something it doesn't like, what happens?

It crashes or complains and says it needs to shut something down. Tens
of millions of lines of code in Vista and Windows isn't smart enough
to handle them without freaking out. Pathetic and a sure sign of poor
design, sloppy, bloated programming that simply doesn't work very
well.

The question shouldn't be what third party something caused Vista to
shut down Explorer, but WHY Vista needs to shutdown Explorer since it
is part of the shell and should have been written well enough and
protected so it is bullet proof.

"Ringmaster" <> wrote in message
news:...
> On Wed, 24 Sep 2008 12:01:26 -0700, "zachd [MSFT]"
> <> wrote:
>
>>
>>Hm. It seems like you have a bogus shell extension installed. What
>>software did you install before this started happening?
>>
>>That fault data from the Event Viewer is generally inferior to the data
>>found in the Problem Reports and Solutions Center control panel -
>>specifically the fault bucket number you get after Checking for Solutions
>>can be a great help in diagnostics. But regardless the data so far is a
>>little generic. If you get this crash again, the fault bucket number for
>>that crash might be interesting, but it may take inspection of an actual
>>crash DMP file from a crash to identify the probably culprit.
>>
>>-Zach
>
> Again no answer why Windows Explorer constantly crashes, just more
> attempts to blame third part software. You're a broken record Zach.
>
> Here's a hint to point you in the right direction. Vista is the
> operating system. It is suppose to CONTROL what other hardware and
> software are doing. We've been told that under Vista everything is
> suppose to be running in it's own protected memory space so one
> application doing something bad, real or imagined WON'T crash another.
> Strange that anytime there is a little burp the response always seems
> to be the same ===> Windows "needs to shut down". Therefore it clearly
> it isn't that big a leap to come to the conclusion it is WINDOWS that
> is broke and not doing it's job properly.
>
> The parallels in the real world are many. These days if a car starts
> to go into a skid, a computer chip takes control helping the driver to
> recover.

And yet, cars still crash...even cars with traction control.
Bad examble.

If there is a power spike on the line, the power supply or a
> UPS filer it out.

You sure ?
You've tested all conditions, locations, building grounds, etc worldwide ?


If it rains hard and water enters your sump, it gets
> pumped out. No user interaction required, no interruption of service.
> No flashing neon sign saying it can't or won't.


Ask the people in New Orleans if the sump pumps worked as designed.
Yet another bad example.


>
> When Windows detects something it doesn't like, what happens?
>
> It crashes or complains and says it needs to shut something down. Tens
> of millions of lines of code in Vista and Windows isn't smart enough
> to handle them without freaking out. Pathetic and a sure sign of poor
> design, sloppy, bloated programming that simply doesn't work very
> well.
>
> The question shouldn't be what third party something caused Vista to
> shut down Explorer, but WHY Vista needs to shutdown Explorer since it
> is part of the shell and should have been written well enough and
> protected so it is bullet proof.
>

Even a bullet proof vest isn't bullet proof.

Give it up...you suck.

--
Ens causa sui
Fit caedes omnibus locis

"Ringmaster" <> wrote in message
news:...
> Again no answer why Windows Explorer constantly crashes, just more
> attempts to blame third party software.

Please reread what I wrote and let me know what offensive comments I made as
regards blaming third party software. If you can triage this faster or more
effectively, please do so. I'm much more interested in solving problems
than advocacy, and I apologize if my attempts to help people gets in your
way.

I think you're putting the cart before the horse here since we don't know
why what is crashing here how. If you really want to meaningfully insult,
why not figure that out and ~then~ make judgements? At some point you have
to cede control of elements of your data to extensions that can then party
(badly) with that data. *shrug*

I encourage you to take computing classes or read up if you would like to
discuss fundamentals of operating system or even Explorer design. You can
lay down guidelines, but in the land of unmanaged code, let me know how
you're going to enforce that. Note that breaking backwards compatibility
with applications would be frowned upon. =)

-Z
--
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.

On Wed, 24 Sep 2008 19:31:35 -0400, "D. Eth" <>
wrote:

>"Ringmaster" <> wrote in message
>news:.. .
>> On Wed, 24 Sep 2008 12:01:26 -0700, "zachd [MSFT]"
>> <> wrote:
>>
>>>
>>>Hm. It seems like you have a bogus shell extension installed. What
>>>software did you install before this started happening?
>>>
>>>That fault data from the Event Viewer is generally inferior to the data
>>>found in the Problem Reports and Solutions Center control panel -
>>>specifically the fault bucket number you get after Checking for Solutions
>>>can be a great help in diagnostics. But regardless the data so far is a
>>>little generic. If you get this crash again, the fault bucket number for
>>>that crash might be interesting, but it may take inspection of an actual
>>>crash DMP file from a crash to identify the probably culprit.
>>>
>>>-Zach
>>
>> Again no answer why Windows Explorer constantly crashes, just more
>> attempts to blame third part software. You're a broken record Zach.
>>
>> Here's a hint to point you in the right direction. Vista is the
>> operating system. It is suppose to CONTROL what other hardware and
>> software are doing. We've been told that under Vista everything is
>> suppose to be running in it's own protected memory space so one
>> application doing something bad, real or imagined WON'T crash another.
>> Strange that anytime there is a little burp the response always seems
>> to be the same ===> Windows "needs to shut down". Therefore it clearly
>> it isn't that big a leap to come to the conclusion it is WINDOWS that
>> is broke and not doing it's job properly.
>>
>> The parallels in the real world are many. These days if a car starts
>> to go into a skid, a computer chip takes control helping the driver to
>> recover.
>
>And yet, cars still crash...even cars with traction control.
>Bad examble.
>
> If there is a power spike on the line, the power supply or a
>> UPS filer it out.
>
>You sure ?
>You've tested all conditions, locations, building grounds, etc worldwide ?
>
>
>If it rains hard and water enters your sump, it gets
>> pumped out. No user interaction required, no interruption of service.
>> No flashing neon sign saying it can't or won't.
>
>
>Ask the people in New Orleans if the sump pumps worked as designed.
>Yet another bad example.
>
>
>>
>> When Windows detects something it doesn't like, what happens?
>>
>> It crashes or complains and says it needs to shut something down. Tens
>> of millions of lines of code in Vista and Windows isn't smart enough
>> to handle them without freaking out. Pathetic and a sure sign of poor
>> design, sloppy, bloated programming that simply doesn't work very
>> well.
>>
>> The question shouldn't be what third party something caused Vista to
>> shut down Explorer, but WHY Vista needs to shutdown Explorer since it
>> is part of the shell and should have been written well enough and
>> protected so it is bullet proof.
>>
>
>Even a bullet proof vest isn't bullet proof.
>
>Give it up...you suck.

Always fun to watch some clueless fanboy grasp at straws.

On Wed, 24 Sep 2008 16:58:42 -0700, "zachd [MSFT]"
<> wrote:

>
>"Ringmaster" <> wrote in message
>news:.. .
>> Again no answer why Windows Explorer constantly crashes, just more
>> attempts to blame third party software.
>
>Please reread what I wrote and let me know what offensive comments I made as
>regards blaming third party software. If you can triage this faster or more
>effectively, please do so. I'm much more interested in solving problems
>than advocacy, and I apologize if my attempts to help people gets in your
>way.

No matter the topic, you always end up saying the same thing. The
point is you don't solve problems, you make excuses for Microsoft's
software failing. Not once have I heard you admit, yes, that's a known
issue, we at Microsoft are working towards a solution.
>
>I think you're putting the cart before the horse here since we don't know
>why what is crashing here how.

The OP clearly stated Windows Explorer needs to shut down. THAT is the
problem. You're in denial. Since WE is an internal part of Vista, and
Vista itself says hey look, oops, I got to shut down, suggests WE is
easily crashed. If by something itself does or doesn't do or allowing
some third party routine to mess it up Windows Explorer must share at
least some of the guilt since that is what is crashing causing users
untold grief, over and over. I've seen it happen countless time
including when nothing but the OS itself was running. Zach blows all
that off. Always.

>If you really want to meaningfully insult,
>why not figure that out and ~then~ make judgements?

Factually pointing out what happens isn't an insult. You're too
defensive of Vista, maybe because you had a hand in screwing up the
coding?

>At some point you have
>to cede control of elements of your data to extensions that can then party
>(badly) with that data. *shrug*
>
>I encourage you to take computing classes or read up if you would like to
>discuss fundamentals of operating system or even Explorer design.

Who's being insulting now?

>You can lay down guidelines, but in the land of unmanaged code, let me know how
>you're going to enforce that. Note that breaking backwards compatibility
>with applications would be frowned upon. =)

Another nice tap dance. As always you simply skip over all the issues
I raised. You always do. You are little more than Frank with better
manners. You are both blind to all Vista flaws and don't even want to
hear about them and surely not discuss them. ;-)

"Ringmaster" <> wrote in message
news:...
> Not once have I heard you admit, yes, that's a known
> issue, we at Microsoft are working towards a solution.

I don't speak for Microsoft and so I am *unable* to say "we at Microsoft
are".

Blame-casting seems so much less interesting to me than solving problems. I
apologize that our priorities are not in alignment. Anything other than
identifying and solving problems to me seems like such a waste of time given
our limited life spans.

>>I think you're putting the cart before the horse here since we don't know
>>why what is crashing here how.

> The OP clearly stated Windows Explorer needs to shut down. THAT is the
> problem. You're in denial. Since WE is an internal part of Vista, and
> Vista itself says hey look, oops, I got to shut down, suggests WE is
> easily crashed.

Again, I'm not sure what you expect to have happen if you load things that
touch memory badly. I applaud and share your perfectionist ideals. I work
on reaching that goal through the available methods including identifying
what is broken where and how. Without identifying what is broken where and
how you probably cannot act.

> If by something itself does or doesn't do or allowing
> some third party routine to mess it up Windows Explorer must share at
> least some of the guilt since that is what is crashing causing users
> untold grief, over and over. I've seen it happen countless time
> including when nothing but the OS itself was running. Zach blows all
> that off. Always.

Um, I'm nobody's slave here. I'm here as a friend. =) Go read the Rules of
Conduct. It's not my job to be here. If I "blow" anybody off, maybe stuff
like life comes first. If you want to engage me in an official capacity, go
through actual Microsoft channels. I'm a helpful guy, but I only have so
much time.

If you have come to have expectations of service from me, I would ask you
politely to killfile me or otherwise ensure that you do not continue to have
any expectation of service. No one here has a service agreement with me.
I'm here as a friend because I like people and find computers and solutions
interesting. Given that I was up to 5AM earlier this week devising a
probably delightful solution that will greatly please some "N" chunk of
users once it's finished, I would find it strange and unsettling to be
construed as someone who "blows off" user concerns, but then again I don't
think your evaluation metric is fair nor valid. =)

I find solving problems thrilling. I find blame-casting oh so dreadfully
boring.

Even a problem that happens when "nothing but the OS itself was running" can
be triaged and identified. As we're trying to do in the thread here.
Until you do that, you're just wasting time.

>>I encourage you to take computing classes or read up if you would like to
>>discuss fundamentals of operating system or even Explorer design.

> Who's being insulting now?

The supposed response for your initial post in this thread was:
> Again no answer why Windows Explorer constantly crashes, just more
> attempts to blame third part software.
- I appreciate that as an excellent non-developer question. That is part of
the general call to excellence.

Given that you clearly can investigate the causes and whys yourself given
such tools as MSDN, the Windows Debugging Toolkit - why waste my time
wasting your time badly teaching you fundamentals of troubleshooting and
debugging? If you actually care about these things, learn.

-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.

On Thu, 25 Sep 2008 00:28:59 -0700, "zachd [MSFT]"
<> wrote:

>
>"Ringmaster" <> wrote in message
>news:.. .
>> Not once have I heard you admit, yes, that's a known
>> issue, we at Microsoft are working towards a solution.
>
>I don't speak for Microsoft and so I am *unable* to say "we at Microsoft
>are".

Of course, we all know MS muzzles it's employees, which is why they
always post under a disclaimer. Pretty sad state of affairs you aren't
free to say what you would like to. I guess you're unaware you could
obtain a account at any number of free providers and respond that way
without Microsoft knowing or caring. In other words you don't have to
hide behind MS policy. It sure does come in handy as a shield though
doesn't it.
>
>Blame-casting seems so much less interesting to me than solving problems.

Just once, stop the bullshit. Accepting responsibility isn't blame
casting. We both know Vista is messed-up in many areas. You trying to
pretend all problems are external totally blows YOUR creditability.
You get laughed at for the same reason Frank does. Everyone knows
you're just trying to cover up. If you can't take the first step...
admit Vista has problems, then you'll never "help" solve anything.

>> The OP clearly stated Windows Explorer needs to shut down. THAT is the
>> problem. You're in denial. Since WE is an internal part of Vista, and
>> Vista itself says hey look, oops, I got to shut down, suggests WE is
>> easily crashed.
>
>Again, I'm not sure what you expect to have happen if you load things that
>touch memory badly.

It isn't me, rather Microsoft that claims all application run in their
own protected space. Is that true or not? If not, Microsoft is caught
lying again. If true, how can some third party application mess with
the OS itself and crash it if it is running in "protected" space? It
just doesn't add up.

>If you have come to have expectations of service from me, I would ask you
>politely to killfile me or otherwise ensure that you do not continue to have
>any expectation of service.

Still playing word games? I have zero expectations from you. You post
something, I respond. That's how newsgroups work.

The point which zooms far over your head is advanced users of Windows
that know many of it's warts have ZERO expectations that Microsoft
will ever fix let alone admit anything is wrong with Windows. That's
the sad state of affairs we got to. Much like the current financial
mess this country finds itself it, Microsoft too is suffering from a
crisis of confidence. As a company it simply isn't believed any more,
because it has been found screwing things up too many times resulting
in untold grief and misery for it's users.

>No one here has a service agreement with me.

Wait a second... ok, continue, the violins are now playing softly in
the background. We needed to have some sad music before you repeat
your sob story you already have so many times before.

>I'm here as a friend because I like people and find computers and solutions
>interesting. Given that I was up to 5AM earlier this week devising a
>probably delightful solution that will greatly please some "N" chunk of
>users once it's finished, I would find it strange and unsettling to be
>construed as someone who "blows off" user concerns, but then again I don't
>think your evaluation metric is fair nor valid. =)
>
>I find solving problems thrilling. I find blame-casting oh so dreadfully
>boring.

You're skilled at dodging questions. You want applause? Ok, fine,
everybody clap for Mr. Z.

If Microsoft's position is never to accept responsibility for what it
messed up how can we expect it to ever fix what's wrong? Stop playing
the denial game. You realize it or not, that's what you're doing.

Oh wait... you said you don't speak for Microsoft. Well buddy for
somebody that doesn't speak for them you sure have the party line
memorized very well.
>
>Even a problem that happens when "nothing but the OS itself was running" can
>be triaged and identified. As we're trying to do in the thread here.
>Until you do that, you're just wasting time.

Ask the OP. I'm simply confirming the types of problem HE has I've
seen as well. Again, you seem in denial that Vista on it's own can
crash. Geez, wake up and actually read a few hundred posts on Google
about ANY Vista problem and educate yourself to what's REALLY
happening. I'll make it real simple. Vista is flawed. Badly. Customers
expect Microsoft to fix it. See, that wasn't too hard was it?
>
>>>I encourage you to take computing classes or read up if you would like to
>>>discuss fundamentals of operating system or even Explorer design.
>
>> Who's being insulting now?
>
>The supposed response for your initial post in this thread was:
>> Again no answer why Windows Explorer constantly crashes, just more
>> attempts to blame third part software.
>- I appreciate that as an excellent non-developer question. That is part of
>the general call to excellence.

What kind of double talk is that? You're still in denial that Vista
can crash on it's own. Until you wake up and realize it can, you're
right, we won't get anywhere.
>
>Given that you clearly can investigate the causes and whys yourself given
>such tools as MSDN, the Windows Debugging Toolkit - why waste my time
>wasting your time badly teaching you fundamentals of troubleshooting and
>debugging? If you actually care about these things, learn.

More of the denial game. You want to know what I've learned being a
Microsoft customer for over twenty years?

Fine, I'll tell you. Microsoft doesn't give a crap about what their
customers think or how much they suffer due to boneheaded decisions
some Microsoft software engineers make. They constantly ship new
versions of Windows knowing they contain bugs.

You're hopeless and useless as a source of help here. Obviously if you
can't even bring yourself to admit Vista has problems you'll never be
able to offer solutions to fix them. That's the bottom line.

You like Frank provide comic relief in that both of you are very
similar. While you can be reasonably civil you're still every bit as
pig headed as Frank and refuse to admit there's anything wrong with
Vista. Accordingly both of you get laughed at by more serious users
that know better.