Thank you. I'll try these things, although I =can= say that this doesn't
happen when Windows turns on. It seems to happen out of the blue after I've
been working an hour or so. Sometimes when I try to copy a file using to File
Explorer windows the system will 'try to calculate how big the files are' for
an extended period of time. If I go to Task Manager & cancel that process &
then try again, File Explorer then behaves properly. I haven't paid attention
to whether these things happen only when ArcMap is running. I will keep track
from now on. Today was the first time that explorer.exe just kept going &
going without any apparent reason.
Actually, now that I think about it, this has been happening at the same
time that the clock has been slowing down (for about the past 2 weeks). My
department's computer person has been on vacation, so I've only been able to
bother the person who asks him to help rather than the computer person
himself. I'll add this explorer.exe behavior to the list of things to tell
him.
Thank you again for your help.
Marian
"NetLink_Blue" wrote:
> A bit of clarification first. I use the term File Explorer to refer to the
> window for managing folders / files. This is what came to mind when you
> mentioned Windows Explorer. I have seen Web Pages that referred to "Windows
> File Explorer" and Windows Explorer. I think we are on the same page here.
>
> As this time, if ArcMap is needed to be kept running -- maybe be patient and
> wait till it finishes. That would be a better time to isolate when/how
> explorer.exe process goes hyper-active. Does explorer.exe consume CPU
> cycles right after booting up? Do you have a lot of programs that start up
> when Windows does? When did you first notice the problem? Does the problem
> start up / is it related to ArcMap running it's routines? Any particular
> routine? The suspect list can get rather long.
>
> Get a computer geeky friend to come over and help troubleshoot. Hopefully,
> it will be a simple and quick fix. Good luck.
>
> - Net
>
>
>
> "Marian M." <> wrote in message
> news:21405E45-8447-49AF-A46C-...
> > Can you recommend which processes I can close down within killing
> > everything?
> >
> > Actually, there were few processes running at the time that explorer.exe
> > was
> > 'doing' so much. These were explorer.exe, taskmgr.exe, ArcMap.exe, and
> > sometimes a flicker of dwm.exe. ArcMap is a GIS program that was running a
> > routine that had been ongoing for 2 days. I didn't want to shut it down
> > because it was almost done with it's calculations. Also, this is something
> > I
> > do often (leave ArcMap running for days on end).
> >
> > Explorer.exe 'reset' itself somehow without my touching ArcMap.exe (the
> > reset conincided with me reinitializing the window by which one manages
> > files
> > on the hard disk, though I realize this doesn't necessarily mean that the
> > reinitialization caused explorer.exe's behavior to change).
> >
> > TIA,
> > Marian
>
>
>
>
> >
> > "NetLink_Blue" wrote:
> >
> >>
> >> "Marian M." <> wrote in message
> >> news:35C3FAEE-CD74-4009-B50B-...
> >>
> >> > I've seen a few messages on this, but none with cures or explanations.
> >> >
> >> > Am on dual core machine with 32 bit Vista, so explorer only hogs up to
> >> > 51%
> >> > of CPU instead of all, though this still is enough to stop me from
> >> > being
> >> > able
> >> > to get work done.
> >>
> >> If explorer.exe constantly uses this much CPU time, then you do have a
> >> problem.
> >>
> >> The explorer.exe process will always show in Task Manager. If you ended
> >> it,
> >> your Taskbar and all desktop icons would disappear. That is the "shell"
> >> that lets you interface to Windows. Closing explorer window does not
> >> stop
> >> explorer.exe.
> >>
> >> Something is making it run/work overtime. Troubleshooting is in order.
> >> Usually, folks stop programs, processes one-by-one until things return to
> >> normal. The last program/process closed would be the suspect.
> >>
> >> - Net
> >>
> >>
> >> > On this latest instance, I turned the Win Explorer window
> >> > off & waited for ~ an hour, which did nothing to alleviate the problem
> >> > (task
> >> > manager still showed explorer.exe going strong). Then tried 'regsrvr32
> >> > somedll' that someone in this discussion group recommended for a
> >> > similar
> >> > problem under XP, which earned me "error code 0x800a0046", so I guess
> >> > that
> >> > wasn't the thing to do.
> >> >
> >> > So, what =is= going on? What is win explorer trying to do? It feels
> >> > like
> >> > the
> >> > throttle won't shut down, or some such thing. Is there a cure besides
> >> > turning
> >> > the Win Explorer window off and on?
> >>
> >>
> >>
> >>
> >>
>
>
|