Windows Explorer crashes in several circumstances

[SantistaS]

I told about this problem but it still remains, so I send it again:

Windows Explorer crashes when it is pointing to a file or a folder and:
1) I try to delete them (using keyboard or the Delete toolbar icon);
2) I try to view their properties (using the mouse button or toolbar
icon).
3) I click in File or Edit menu of Windows Explorer.

The "Copy to" and "Move To" buttons of Windows Explorer are working fine.
So, to delete a file or a folder I have use the button "Move to" ...
Recycle Bin.

Windows Explorer works fine in the situations 2 and 3, if it is pointing
to a drive.

Windows Explorer also crashes if the file or folder is sitting in the
Desktop and I try to delete or view their properties.
Windows Explorer does not crash if I delete or view the porperties of a
Desktop link.

Below are the information given by the system after the error and the
processes running, when the problem occurs.

I already run "sfc /scannow" and reinstalled "Windows XP SP3".

Any help?
Thanks,

Information given by the system after the error:
AppName: explorer.exe
AppVer: 6.0.2900.5512
ModName: kernel32.dll
ModVer: 5.1.2600.5512
Offset: 0000cffd

Processes running when the problem occurs
PROCESS EXECUTABLE
GbpSv.exe C:\PROGRA~1\GbPlugin\GbpSv.exe
ccSvcHst.exe C:\Program Files\Common Files\Symantec
Shared\ccSvcHst.exe
ccSvcHst.exe C:\Program Files\Common Files\Symantec
Shared\ccSvcHst.exe
jqs.exe C:\Program Files\Java\jre6\bin\jqs.exe
AluSchedulerSvc.exe C:\Program
Files\Symantec\LiveUpdate\AluSchedulerSvc.exe
explorer.exe C:\WINDOWS\explorer.exe
alg.exe C:\WINDOWS\System32\alg.exe
csrss.exe C:\WINDOWS\system32\csrss.exe
lsass.exe C:\WINDOWS\system32\lsass.exe
services.exe C:\WINDOWS\system32\services.exe
smss.exe C:\WINDOWS\System32\smss.exe
spoolsv.exe C:\WINDOWS\system32\spoolsv.exe
svchost.exe C:\WINDOWS\system32\svchost.exe
svchost.exe C:\WINDOWS\system32\svchost.exe
svchost.exe C:\WINDOWS\system32\svchost.exe
svchost.exe C:\WINDOWS\system32\svchost.exe
svchost.exe C:\WINDOWS\system32\svchost.exe
svchost.exe C:\WINDOWS\System32\svchost.exe
winlogon.exe C:\WINDOWS\system32\winlogon.exe
wuauclt.exe C:\WINDOWS\system32\wuauclt.exe
-----------------------------------------------------------

 

[CBoom]

Hello,


you should download nirsofts shellexview

http://www.nirsoft.net/utils/shexview.html

and temporality disable all pink (non microsoft) shell extensions

restart and

see if this resolves the problem.. then you can slowly add back the ones you
think you need

until you reach the one causing the problem

please provide feedback if this resolves your problem

I blogged this here:

http://computerboom.blogspot.com/2008/12/windows-explorer-crashes-in-several.html

 

[SantistaS]

Thanks a lot, CBoom,

I disabled about 60 shell extensions and it worked!
Now I will enable, for example, 10 of them and see if the problem returns,
and so on.
Do I have to restart Windows each time?
Is it enough to log off and logo on?

Thanks again!
Sorry about my delay,

DC

 

[SantistaS]

Thanks a lot, CBoom,

I disabled about 60 shell extensions and it worked!
Now I will enable, for example, 10 of them and see if the problem returns,
and so on.
Do I have to restart Windows each time?
Is it enough to log off and logo on?

Thanks again!

DC

 

[SantistaS]

Disabling and enabling progressively the shell extensions, I found and
isolated the origin of the crash:



IT WAS NORTON 360!



How can a so old and traditional company sell a product with such a bug?



DC

 

[Ron Badour]

Surprise surprise <G>. Thanks for the feedback

--
Regards

Ron Badour
MS MVP
Windows Desktop Experience

 

[Twayne]

I had exactly the same crash as you did (offset 0000cffd in
kernel32.dll) in both Windows Explorer and PowerDesk on Mar. 20, 2009.
In my case I had to disable the Norton Internet Security shell
extension to stop the crashes. Eventually I found out that the
problem was really PowerDesk. I was able to get an updated PowerDesk
shell extension from avanquest.com. Then I was able to re-enable the
Norton Internet Security shell extension and the problem was gone!

The point is that if you have PowerDesk installed you could have the
same problem I had.

That's interesting; I went through almost exactly the same process you
describe and the culprit was one of the PowerDesk7 shell contect
entries; the ZIP extension to be precise. ShellExView was the program
that allowed me to finally pin it down after hours of chasing it.

From my research it appears that there are other possible culprits, too,
such as DivX which was most mentioned, and several others. All 3rd
party apps that affected the Context Menu in one way or another.

Twayne