Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Windows 7: Recherche indexing is stuck

ayi

When I open Indexing Options, it says:

4,317 items indexed
Indexing in progress. Search results might not be complete during this time.

C'est stuck at 4,317 though; no more items ont été indexed. Worst of all, SearchIndexer.exe is taking up 100% CPU (well, 50%, but J'ai un dual core CPU; c'est taking up all processing power it can). Ce n'est pas causing disque dur activity though.

J'ai essayé clicking "Troubleshoot search and indexing" en bas du Indexing Options window, but it ne pouvait pas find any problème.

I've également tried the repair registry clé that several websites suggest; I change HKLM\SOFTWARE\Microsoft\Windows Search SetupCompletedSuccessfully to 0 and redémarré the ordinateur, and it apparemment repaired parce que it flipped back to 1, but the same problème continues to occur.

C'est reducing the batterie life of my laptop and making it really hot so that my fans are running all the time. J'ai eu to désactiver the Windows Search service. Comment puis-je fix this? Do J'ai besoin de just flat-out reformat my ordinateur?

Mise à jour:

J'ai essayé rebuilding a couple times. There's rien unusual about the locations J'ai to index, and Je n'ai pas any downloads in progress or anything like that. Je ne vois pas any reason why it stopped, and J'ai remarqué it much too late to do a système restore. At this point, I'm hoping quelqu'un will offer up some secret answer that will fix the problème, thus the bounty.

Another mise à jour:

J'ai essayé starting the service again, just to let it try yet again. It seemed okay at first (Indexing Options showed it operating at reduced speed due to utilisateur activity, and the number of fichiers was going up). A while later I checked, and the service had stopped. Event viewer revealed some erreurs like this:

Log Name:      Application
Source:        Application Error
Date:          2/1/2010 7:34:23 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ricky-win7
Description:
Faulting application name: SearchIndexer.exe, version: 7.0.7600.16385, time stamp: 0x4a5bcdd0
Faulting module name: NLSData0007.dll, version: 6.1.7600.16385, time stamp: 0x4a5bda88
Exception code: 0xc0000005
Fault offset: 0x002141ba
Faulting process id: 0x13a0
Faulting application start time: 0x01caa39f2a70ec02
Faulting application path: C:\Windows\system32\SearchIndexer.exe
Faulting module path: C:\Windows\System32\NLSData0007.dll
Report Id: b4f7a7ae-0f92-11df-87fc-e5d65d8794c2
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-02-02T00:34:23.000000000Z" />
    <EventRecordID>10689</EventRecordID>
    <Channel>Application</Channel>
    <Computer>ricky-win7</Computer>
    <Security />
  </System>
  <EventData>
    <Data>SearchIndexer.exe</Data>
    <Data>7.0.7600.16385</Data>
    <Data>4a5bcdd0</Data>
    <Data>NLSData0007.dll</Data>
    <Data>6.1.7600.16385</Data>
    <Data>4a5bda88</Data>
    <Data>c0000005</Data>
    <Data>002141ba</Data>
    <Data>13a0</Data>
    <Data>01caa39f2a70ec02</Data>
    <Data>C:\Windows\system32\SearchIndexer.exe</Data>
    <Data>C:\Windows\System32\NLSData0007.dll</Data>
    <Data>b4f7a7ae-0f92-11df-87fc-e5d65d8794c2</Data>
  </EventData>
</Event>

Si vous are having the same erreur and arrived ici from a Google search, veuillez comment or add an answer detailing your progress on this, if any...

ayi

Je pense you pourrait être correct when you say that there's a corrupted fichier that causes it to hang. A crude way of trying to identify the fichier is to go the fichiers tab and turn off half the fichiers types from being indexed. Let it run. Either it completes or it stops. Si cela stops, turn off half again. Si cela completes, you know the bad fichier tapez is dans le other half. Doing this should allow you to identify the bad fichier type.

Également, look through the fichier list that's indexed. Fichier types have different search providers, like HTML, plain text and so on. Are there any that look out of place, that might ont été installé by some third party application?

Another idea is let the search hang sur le 4,317th fichier. Ensuite run a invite de commandes. Tapez

CD c:\
DIR /s /TA /O-D >c:\newt.txt

Cela va créez un fichier named newt.txt that will hold all du fichiers and the last time they were accessed. Accessed, meaning read, not modified. Vous allez have to search through the fichier avec a fichier editor but cherchez the last several fichiers that were modified. If we're in luck, your bad fichier sera dans lere. Good luck!