A
Anonymous
I've had a problem with Windows XP for years now (ever
since I first installed it) on several different machines.
Whenever I would copy large directory structures with many
files using windows explorer, there would be a good chance
that explorer.exe would start taking 99-100% of the CPU
time for a few minutes and eventually crash.
This has happened on tens of reinstalls of windows, and on
3 completely different sets of hardware. (Now that I've
figured out what is causing it, I've also had a friend
reproduce the problem on his system.)
Today, I finally found the cause. One of the first things
I do whenever setting up windows is create a folder on the
start menu / programs called "Quick". I put my most common
shortcuts in that folder, and then add it as a toolbar to
my taskbar. I need it to be on the start menu so that the
keyboard Shortcut Keys I assign will work. This is why I
don't use the standard "Quick Launch" bar. One of the first
shortcuts I always put in this folder is one to "My Computer".
Using SysInternal's File Monitor (which I just discovered
today), I found that when explorer.exe freaks out, it is
continually opening, reading, and closing the .lnk file for
the My Computer shortcut.
Removing the shortcut solves my problem. Explorer.exe no
longer crashes during copies of large directory structures
or large numbers of files -- even when I try to copy my
entire "Program Files" tree, which would have nearly 0%
chance of working before.
So, my question now is, what is causing this internally?
Is this an already-known issue? Is there anything that can
be done that will allow me to have my shortcut to My
Computer on my task bar without making explorer unstable?
For now, I've removed the shortcut, but I find myself
depressed and empty inside every time I go to my taskbar
out of habit and realize that "My Computer" isn't there.
Aside from that, I'd like to know if there are other
forbidden shortcuts that could cause similar problems.
This problem doesn't seem to be related to any Shell
Extensions (at least none that ShellExView is capable of
disabling). Disabling all but about 5 Shell Extensions
(no, I don't remember which ones), the problem still
occurs. It also isn't related to "Indexing Service" as
I've disabled that service (along with many other
non-critical services). So basically, the problem happens
even with a very bare-bones configuration.
This happens on a clean install of windows without any
extra software. With SP2, SP1, or no service pack (But
I've only verified that that removing the shortcut solves
the problem on SP2).
I'd really be interested if anyone can provide any insight
or answers to the questions I've already asked, and I'd
also be interested in seeing if any of you can reproduce
the problem (or if you can't reproduce the problem).
Here's more on how to reproduce the error:
1.) Create a new folder in Start Menu \ Programs called "Quick"
2.) On the windows taskbar, right click, choose "Toolbars"
and "New Toolbar..."
3.) Choose the folder "Quick" you just created
4.) Right-click-drag "My Computer" from your desktop onto
this new toolbar, choose "Create Shortcuts Here"
5.) Log off of windows and log back on (You need to let
explorer.exe shut down gracefully to remember the toolbar)
6.) Open up "My Computer" using the icon on your taskbar,
open your primary harddrive. Create a new folder on the
drive, and open that folder. Open up another copy of "My
Computer" using the icon on your taskbar. Go into your
main harddrive. Right-Click-Drag your "Program Files"
folder (Or any other at-least-moderately-complicated
directory structure with many files) into the new folder in
the other explorer window. Choose "Copy Here"
7.) Ctrl-Alt-Delete and open Task Manager. Sometime within
a few minutes of copying, explorer.exe should jump from
around 15% CPU time usage to around 80-100% usage. After
this happens, cancel the copy.
8.) explorer.exe will continue to use ~99% of the processor
time for a few minutes and will eventually crash.
It is possible that this is specific to the Corporate
version of windows XP. Hopefully seeing who can/can't
reproduce the error will clarify that.
since I first installed it) on several different machines.
Whenever I would copy large directory structures with many
files using windows explorer, there would be a good chance
that explorer.exe would start taking 99-100% of the CPU
time for a few minutes and eventually crash.
This has happened on tens of reinstalls of windows, and on
3 completely different sets of hardware. (Now that I've
figured out what is causing it, I've also had a friend
reproduce the problem on his system.)
Today, I finally found the cause. One of the first things
I do whenever setting up windows is create a folder on the
start menu / programs called "Quick". I put my most common
shortcuts in that folder, and then add it as a toolbar to
my taskbar. I need it to be on the start menu so that the
keyboard Shortcut Keys I assign will work. This is why I
don't use the standard "Quick Launch" bar. One of the first
shortcuts I always put in this folder is one to "My Computer".
Using SysInternal's File Monitor (which I just discovered
today), I found that when explorer.exe freaks out, it is
continually opening, reading, and closing the .lnk file for
the My Computer shortcut.
Removing the shortcut solves my problem. Explorer.exe no
longer crashes during copies of large directory structures
or large numbers of files -- even when I try to copy my
entire "Program Files" tree, which would have nearly 0%
chance of working before.
So, my question now is, what is causing this internally?
Is this an already-known issue? Is there anything that can
be done that will allow me to have my shortcut to My
Computer on my task bar without making explorer unstable?
For now, I've removed the shortcut, but I find myself
depressed and empty inside every time I go to my taskbar
out of habit and realize that "My Computer" isn't there.
Aside from that, I'd like to know if there are other
forbidden shortcuts that could cause similar problems.
This problem doesn't seem to be related to any Shell
Extensions (at least none that ShellExView is capable of
disabling). Disabling all but about 5 Shell Extensions
(no, I don't remember which ones), the problem still
occurs. It also isn't related to "Indexing Service" as
I've disabled that service (along with many other
non-critical services). So basically, the problem happens
even with a very bare-bones configuration.
This happens on a clean install of windows without any
extra software. With SP2, SP1, or no service pack (But
I've only verified that that removing the shortcut solves
the problem on SP2).
I'd really be interested if anyone can provide any insight
or answers to the questions I've already asked, and I'd
also be interested in seeing if any of you can reproduce
the problem (or if you can't reproduce the problem).
Here's more on how to reproduce the error:
1.) Create a new folder in Start Menu \ Programs called "Quick"
2.) On the windows taskbar, right click, choose "Toolbars"
and "New Toolbar..."
3.) Choose the folder "Quick" you just created
4.) Right-click-drag "My Computer" from your desktop onto
this new toolbar, choose "Create Shortcuts Here"
5.) Log off of windows and log back on (You need to let
explorer.exe shut down gracefully to remember the toolbar)
6.) Open up "My Computer" using the icon on your taskbar,
open your primary harddrive. Create a new folder on the
drive, and open that folder. Open up another copy of "My
Computer" using the icon on your taskbar. Go into your
main harddrive. Right-Click-Drag your "Program Files"
folder (Or any other at-least-moderately-complicated
directory structure with many files) into the new folder in
the other explorer window. Choose "Copy Here"
7.) Ctrl-Alt-Delete and open Task Manager. Sometime within
a few minutes of copying, explorer.exe should jump from
around 15% CPU time usage to around 80-100% usage. After
this happens, cancel the copy.
8.) explorer.exe will continue to use ~99% of the processor
time for a few minutes and will eventually crash.
It is possible that this is specific to the Corporate
version of windows XP. Hopefully seeing who can/can't
reproduce the error will clarify that.