Windows Explorer crashes

[Guest]

I have had this problem ever since I got this laptop. Everytime I try to open
certain folders with Windows Explorer, it crashes. I can open these same
folders with my desktop computer with no problem. The error message says
"windows
explorer has encountered a problem and needs to close, we are sorry for the
inconvenience". The error signature is "AppName: explorer.exe AppVer:
6.0.2900.2180 ModName: ntdll.dll ModVer: 5.1.2600.2180 Offset: 0003215b".

I am not sure why this happens, but it is really annoying. I have heard the
best solution is to reinstall Windows XP, but this is my last resort. I am
running Windows XP with Service Pack 2 Version 5.1 (Build
2600.xpsp.050622-1524:Service Pack 2).

Any suggestions on how to repair this problem?

 

[Guest]

I found my own fix and it actually worked!

http://forums.techguy.org/windows-n...?highlight=windows+explorer+crashes+ntdll.dll

"so the fix was to disable the thumbnail feature for photoshop files by:

1. right-click on file
2. properties
3. photoshop image tab
4. uncheck generate thumbnails

"since windows already has a built-in image thumbnail viewer and previewer
in windows explorer, it's not that bad to lose this photoshop feature.
besides, it took up time displaying a folder with many image files.")
it actually worked!

 

[Colliope .com]

"so the fix was to disable the thumbnail

feature for photoshop files by:
1. right-click on file
2. properties
3. photoshop image tab
4. uncheck generate thumbnails

I went thru the same thing months ago, and like you, traced the cause
back to Photoshop thru searching the internet.

When Explorer starts crashing the last thing one is going to think of is
a setting in their graphics program - and one you're only going to find
by checking an image's properties at that - so it can take hours to find
a mention of it being Photoshop related and thus find the cure.
Since it seems this is a fairly common problem-causing conflict, seems
it ought to be listed as a known issue in Photoshop's guide and also in
the MS knowledge base.

Anyway, thanks for posting back on what you found out - that's one more
lead someone might find in searching out the answer if this happens to
them.

C