Indexing Service filter daemon keeps crashing on Windows XP; something worse underneath?

19
2014-04
  • IVR Avenger

    The Indexing Service filter daemon keeps crashing on my Windows XP Pro machine, with the following error message:

    Indexing Service filter daemon has encountered a problem and needs to close.  
    We are sorry for the inconvenience.
    

    Not a big deal, I can click "Don't Send Error Report" all day. But what's going on, here? Is this a service that I need? Is the frequent crashing indicative of something worse that's happening behind the scenes?

  • Answers
  • Oliver Salzburg
    1. Open My Computer
    2. Right click your hard drive icon and select properties.
    3. At the bottom of the window you'll see Allow indexing service to index this disk for faster searches, uncheck this and click Ok.
    4. A new window will pop up and select Apply to all folders and subfolders. It will take a a minute or two for the changes to take affect but then you should enjoy slightly faster performance

  • Related Question

    What Windows services can I safely disable?
  • Alconja

    I'm trying to improve the boot time and general performance of a Windows XP machine and figure the massive collection of services that Windows automatically starts have to have an impact. Are there any services that I can safely disable? If so what are they?

    Obviously the services are there for a reason, so when listing a service, please provide reasoning & examples of when you'd not disable it.


  • Related Answers
  • Django Reinhardt

    Black Viper maintains what is considered by many the definitive guide to Windows services.

    http://www.blackviper.com/category/guides/service-configurations/

  • Adam Gibbins

    If you wish to tweak the windows services to reduce memory usage theres quite a well known and respectable list here of what you can and cannot disable:

    Although that said, be careful, and only disable services you're absolutely sure you don't want/need. Don't be trigger happy, this isn't going to save you massive resources.

  • Marc Reside

    With services, it all depends on which services do jobs you need. I found a good link that talks about this here. Here's a small snippet from that link:


    "To have your system boot in a short time, you also need to enable only useful services. Here comes the problem: which are the useful services? The simple answer is: useful services are the ones that do a job you're interested in. As you can note, this is not a real answer."


    The advice is really good for Service Optimization.

    Other than services, I use some Sysinternals tools to keep track of what's bogging down my PC. Notably, Autoruns, Process Explorer, and Process Monitor are quite effective to identify processes that run on your system and hog resources.

    On a reasonably well-used PC, I would run defrag once a week, or once every two weeks. If it's used for only small things like internet access and a few applications, maybe once a month.

  • pavsaund

    Which services that need to be running on you pc really depends on what you use it for. There is usually a process of trial and error where you'll have to experiment a little to find out what actually helps and what you need.

    Check out this article which has an explanation of services, and a video walkthrough where he goes through all the potential services that could be disabled.

  • Qwerty

    Use the Black Viper Guides for tweaking XP and its services.

    The service tweaking guide has several profiles of different service configurations.

  • dmoisan

    My philosophy is to almost never disable services. I believe in having a very consistently configured machine with the least number of tweaks possible. That gets me, IMHO, a stable machine and no surprises at Windows Update. (I guess that means I'll never use vLite! :))

    The well known tweaking guides out there are not written from a sysadmin's viewpoint.

    However, you can go to Add/Remove Programs and go to Windows Features, and turn off those you don't use. I never ever use, for example, Simple TCP/IP Services, on anything. There are no doubt other examples. If you find you need the feature you can turn it back on.

    Same goes for server roles; if you have SNMP installed but don't use it because you don't have a device that uses it (or the tools to use it costs too much/are bloated/make no sense) then remove it.

    But I never go and disable a service just to try and make things "faster".

  • Seasoned Advice (cooking)

    I try to keep my prefetch clean (c:\windows\prefetch), disable most (if not all) of everything in start>run>msconfig >startup, and I constantly check and tweak start>run>services.msc

    Also remember that almost everything on your machine wants to run something at startup. Check it every time you install something. Java and quicktime both want to run something at startup. Your wireless card manufacturer most likely has something running at startup. I use Windows to manage my wireless.

    Oh...and I disable System Restore and Hibernation.

    My XP laptop has amazing boot time.