Microsoft Windows Search Indexer has stopped working?

[chris]

All -

I'm having an odd issue with the Indexer Service - it just stops
working. I thought is was related to the most recent Vista update but
it still happens after having rolled back. Has this happened to
anyone? Short of turning off the indexer, has anyone found a workable
solution? The damn search was part of my reason for running Vista!

 

[Guest]

Yeah Im having the same problem. It seems DEP keeps closing it down then it
re opens its self again.
Any help would be great

 

[Kris]

Same here, I finally had to just shut it down, it was making me nuts popping
up all the time! If someone has an idea, I'd love to hear it - that search
would be so handy! I'm also getting the same message for Intel Alert Service
on bootup every single time (and both have been doing it since I opened the
door and brought the computer into the house!)

 

[Dave Wood [MS]]

If you are getting a "Microsoft Windows Search Indexer has stopped working"
message regularly can you go the Problem Reports and Solutions and see if
the crashes are listed there? If you have the BucketId number {which will be
there if you have enabled sending error reports to Microsoft automatically}
and send it to me then I can investigate.

Dave Wood

 

[Kris]

Here's the Bucket ID for the Intel Alert Service crash: 368278928; I turned
the indexer back on a week or so ago, and it seems to be working ok (maybe
an update took care of that?). I still get the Intel Alter Service has
stopped working ALL the time

 

[Guest]

Where is "Problem Reports and Solutions"?

If you are getting a "Microsoft Windows Search Indexer has stopped working"
message regularly can you go the Problem Reports and Solutions and see if
the crashes are listed there? If you have the BucketId number {which will be
there if you have enabled sending error reports to Microsoft automatically}
and send it to me then I can investigate.

Dave Wood

 

[Cal Bear '66]

Control Panel

 

[Dave Wood [MS]]

I can see the details on this bucket and I'll make sure we investigate it.
There isn't a simple way you could fix this unfortunately - it looks like it
may be some sort of file corruption issue so my suggestion is to use the
"Restore Defaults" button in the Indexing Control Panel -> Advanced pane
which will rebuild the index from scratch.

Dave

 

[Dave Wood [MS]]

If you are comfortable modifying the registry you can get the same effect as
Restore Defaults by changing the value of
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
Search\SetupCompletedSuccessfully to 0 and rebooting ...

 

[Guest]

I Am having the same problem and if one MS person in another thread said to
find some arcane files in a long directory name and copy them to
somewhere...but I couldn't find the files. Your suggestion to reset the
INdexer to default cannot be done on my new ACER machine either...it says the
indexer is not running.

The little error windows tells me that WINDOWS will tell when there is a
'fix'.

I looked at the four files I get when clicking the reported errors and they
don't tell me what to do with them to get the indexer working. Not much help.

We are USERS out here not programmers. I saw many reports of this problem
and if this cropping up a lot then a NEW solution should be found that the
windows update should fix automatically...after all isn't that why we're with
windows and not a mac?

Right now I would like MS Windows Vista to help me get this indexer
working...if its a matter of a couple files being a certain name in a certain
directory to 'build on' then have windows check that directory and if not
there put it there with those files...seems simple to me from a user
standpoint.

Hope you can help.

Thank you in advance

Robert

 

[Guest]

I entered regedit.exe in the Start search box and modified the value you
indicated and rebooted. I then went to Control Panel\System and
Maintenenance\Indexing Options and verified that indexing was active. The
buttons were no longer grayed out.

The question remains: Why did the Indexer stop working in the first place
and will it fail again? I will respond next week to let you know if my
Indexer is still running.

 

[Guest]

I said I would return with a status of the Windows Indexer fix. It is still
working after a about week. Whatever caused it to fail in the first place
has obvioulsy not re-occurred. Thanks for the fix.

Neil

 

[Guest]

I said I would return with a status of the Windows Indexer fix. It is still
working after a about week. Whatever caused it to fail in the first place
has obvioulsy not re-occurred. Thanks for the fix.

Neil

Mine is also working it seems for this past week or so. Finally found the
CORRECT spot...which is why I HATE going in to change setting way down deep
within widows.

 

[Guest]

I opened registry editor till HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
Search but setup completed successfully is not there. Please suggest what to
do or where do I need to go for the "restore default" option.
Please pardon my limited knowledge of computers.

 

[Guest]

Well, I think that I may have figured out what has been causing the indexing
popup nonsence at least on my end of things.
As everything had been working nicely for all this time, untill yesterday
when I decided to install the latest nVidia 162.22 drivers for my video card.
After the reboot, not only did the card perform like you know what, but then
that stupid indexing nonsense had started up "again" like it had done before.

So, now I'm highly suspecting that these really crummy new nVidia drivers
have been the culprit all along, as I had been always updating to the newest
versions and all, only to find they just seemed to be getting worse and worse.

Maybe it was just purely a coincidence, by sure looks suspicious to me?

Just a thought for all of you out there to see if you too have been using
the nVidia drivers.
Right now, I am back to using the default Vista drivers on my 7950 KO
SuperClocked card.
And yes, I am aware of the 79XX series and their problems too.

Anyway, I was sure glad to find that Registry fix, as the only way I was
ever able to fix things was to do a restore or something and even that didn't
always work.

Now to see if I can figure out why my Help Files never let me update, as I
always get that message about can't download the files, so I never get to use
the Help programs, but thats another search in these forums LOL

Thanx too, to Dave for that fix tip!

..................md

 

[Guest]

I also get the "Intel Alert Service stopped working.." message every time I
start up.

I checked and found that the problem has been reported each time, here is
the most recent Bucket ID: 368278928

 

[Guest]

So, I see no one has said whether or not they too have any time recently or
before the problems started with their indexing, if they had also installed
any display card drivers from nVidia?
Have any of you?
I'm trying to pin point for sure where the screw up comes from.
I need a bit of feedback to fully determine?
But, for me, it DID start right after I had installed the nVidia 162.22
drivers and has done that with every other previous driver back to 158.18.

Only it never occured to me that the nVidia drivers might have something to
do with what was corrupting the indexing.exe?
It could very well be Registry machanic, except that I use that frequently
and never have any problems.
But you never can tell?
I do know though that this last time, things were working perfectly fine
until right after I had installed the nVidia drivers and after rebooting this
time I was able to see that error message right away on the reboot and had to
think it was caused because of that driver?
Sure doesn't feel like a coincidence to me?

Please, post if any of you had done anything like this as I like to find
where problems are coming from so I can know what to look out for later as
well as report this to the proper people.

Thanx.................md

 

[Guest]

I had this same problem, but not after upgrading Nvidia drivers. Mine
started after upgrading the Z-Engine software for the Ideazon Fang gamepad.
I'm going to try the fixes mentioned in this thread; hopefully my problem
will be solved. Thanks to all for the info!

 

[zachd [MSFT]]

Isn't that from Intel? What do they say about this issue/crash?