re: what abt the
Monday, June 7, 2004 at 6:05 pm
Windows XP Annoyances Discussion Forum
Posted by Tony Stewart
(1 messages posted)
I suspect the Explorer.exe crash in XP is due to resources that have been exceeded
or an explorer APP stack failure occured. Or perhaps a permission conflict between
the virus running and the protection of on-access AV scanners.... File Handles and
GUI objects both are much better handled than win98/ME but are not infinite. 98 was
limited to 2MB regardless on how much RAM you had. I have XP Pro with 1GB of RAM
can vouch for dozens of situations on different APPs that are "resource hogs" that
cause Explorer.exe or another APP to crash. Check Ctl-Alt-Del > Process List and
View > Select Columns and add File Handles and GUI Objects. If you have several
apps with handles > 1000, wonder why and reduce it if possible or trim all the fat
in startup APPS and resource hogs. For example AVG is much leaner than NAV and is
adequate. AVAST (ashserve) an A.V. APP can consume 9999 handles when on-access scanning
is monitored in popup lists when , svchost.exe can be sharing many Services to find
out RUN > CMD Tasklist.exe -svc and compare PIDs with Process list in Task Manager.
and see the # Handles. Don't confuse VM or memory of APP in memory and resources.
Get Proc. Explorer from Sysinternals.com to see and learn.
Your Best tools are un-install, Restore, run SFC /SCANNOW and disable most Startups
and un-ncessary APPS to trim your XP resources and it will run faster and smoother.
But don't discount a worm causing a stack overflow in explorer from the on-access
AV scanner in NAV or the TCP rule scanner in NIS or similar resource hogs.
On Saturday, May 22, 2004 at 2:52 am, Mike wrote:
>I seem to be narrowing down the problem.
>
>There is definately a compatability issue between XP Home and NIS2003 which has
only
>arisen as a result of a recent update. XP Pro does not seem to have the same problem.
>
>While upgarding to NIS 2004 resolves the system speed and internet speed problems
>and prevents the timing out etc, depending whether you have a network installed
you
>may appear to lose some of your notification icons and have problems with your email.
>
>
>The problem seems to be caused by the new network identification facility built
into
>NIS2004. If you are running on a peer to peer network and had other computers running
>during the original installation it will set this as the default network, and after
>installation and some configuration everything seems to be fine and dandy. But
later,
>should you boot up and the other pcs are not turned on, NIS thinks "I can't see
the
>other PCs therefore you must be on a different network, therefore I'm going to screw
>up all your settings and block everything in a very unuser friendly way."
>
>Depending on how you use your network the best solution seems to be to uninstall
>NIS2004, turn all the other pcs on the network off and reinstall it on the machine
>you usually switch on first. You can install it on the others with this machine
>still running as it normally would be when you boot them up.
>
>I know this won't solve all the problems being reported in this thread but I know
>it has solved mine, and 2 colleagues.
>
>Regards
>Mike
>
- Written in response to:
- re: what abt the (Mike: Saturday, May 22, 2004 at 2:52 am)
Responses to this message:
|
|
All messages in this thread [show all]
 |  | | |  | re: what abt the (Tony Stewart: Mon, Jun 7, 2004, 6:05 pm) |
| |
| |
Return to the Windows XP Discussion Forum
|
|
