Windows 10 Windows 10 Search Index keeps rebuilding itself

  • Thread starter Thread starter jxm28
  • Start date Start date
J

jxm28

Every month or so I'll notice that my search isn't finding stuff that I know is there. A quick check of the Search Index shows that it is rebuilding itself from scratch. Given that I have a lot of stuff, that usually takes a full day to rebuild completely. Which is somewhat annoying as I then can't search outlook for emails, or of course for any files on the hard disk. And I search quite a lot.


I've noticed that when this happens I get the following events in the system log and application log all around the same time -


08:15:02 System Error 7024 "The description for Event ID 7024 from source Service Control Manager cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event:

Windows Search %%2147749126 The locale specific resource for the desired message is not present"


08:15:02 System Error 7031 "The Windows Search service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service."


08:15:32 System Error 7032 "The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Windows Search service, but this action failed with the following error: An instance of the service is already running."

08:15:02 Application Error 7040 "The search service has detected corrupted data files in the index {id=4810 - onecoreuap\base\appmodel\search\search\ytrip\common\util\jetutil.cpp (296)}. The service will attempt to automatically correct this problem by rebuilding the index. Details: 0x8e5e0713 (0x8e5e0713)"

08:15:02 Application Information 1001 "Fault bucket , type 0
Event Name: WsearchHealth
Response: Not available
Cab Id: 0

Problem signature:
P1: Corruption
P2: 0x8e5e0713
P3: onecoreuap\base\appmodel\search\search\ytrip\common\util\jetutil.cpp
P4: 296
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_Corruption_97cca3dfb0a6d7064f154ea92e41a923bc3650_00000000_3c0d5448

Analysis symbol:
Rechecking for solution: 0
Report Id: 3bdd024a-bbbc-428c-afcd-c80df4699d6d
Report Status: 100
Hashed bucket:
Cab Guid: 0"

08:15:02 Application Error 7042 "The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt. Details: The content index catalog is corrupt. 0xc0041801 (0xc0041801)"

08:15:02 Application Information 103 "SearchIndexer (18268,T,97) Windows: The database engine stopped the instance (0).

Dirty Shutdown: 0

Internal Timing Sequence:
[1] 0.000002 +J(0)
[2] 0.000006 +J(0)
[3] 0.000003 +J(0) +M(C:0K, Fs:1, WS:4K # 4K, PF:0K # 0K, P:0K)
[4] 0.000001 +J(0)
[5] 0.003178 +J(0) +M(C:0K, Fs:5, WS:0K # 16K, PF:-52K # 0K, P:-52K)
[6] 0.000005 +J(0)
[7] -
[8] 0.000003 +J(0)
[9] 0.000790 +J(CM:0, PgRf:0, Rd:0/0, Dy:0/0, Lg:3480/2) +M(C:0K, Fs:2, WS:4K # 0K, PF:0K # 0K, P:0K)
[10] 0.002889 +J(CM:0, PgRf:0, Rd:0/0, Dy:0/0, Lg:66/1) +M(C:0K, Fs:7, WS:28K # 16K, PF:104K # 0K, P:104K)
[11] 0.000001 +J(0)
[12] 0.000548 +J(0)
[13] 0.000015 +J(0) +M(C:0K, Fs:0, WS:-4K # 0K, PF:-4K # 0K, P:-4K)
[14] 0.000116 +J(0) +M(C:0K, Fs:1, WS:4K # 0K, PF:0K # 0K, P:0K)
[15] 0.000008 +J(0) +M(C:0K, Fs:0, WS:-12K # 0K, PF:-32K # 0K, P:-32K)
[16] 0.000001 +J(0)."


08:15:02 Application Error 3057 "The plug-in manager <Search.TripoliIndexer> cannot be initialized.

Context: Windows Application Details: (HRESULT : 0x8e5e0713) (0x8e5e0713)"


08:15:02 Application Error 3029 "The plug-in in <Search.TripoliIndexer> cannot be initialized.

Context: Windows Application, SystemIndex Catalog Details: The specified object cannot be found. Specify the name of an existing object. (HRESULT : 0x80040d06) (0x80040d06)"


08:15:02 Application Error 3028 "The gatherer object cannot be initialized. Context: Windows Application, SystemIndex Catalog Details: The specified object cannot be found. Specify the name of an existing object. (HRESULT : 0x80040d06) (0x80040d06)"


08:15:02 Application Error 3058 "The application cannot be initialized. Context: Windows Application

Details: The specified object cannot be found. Specify the name of an existing object. (HRESULT : 0x80040d06) (0x80040d06)"

08:15:02 Application Error 7010 "The index cannot be initialized. Details: The specified object cannot be found. Specify the name of an existing object. (HRESULT : 0x80040d06) (0x80040d06)"

08:15:02 Application Warning 36 "Search cannot complete the indexing of your Outlook data. Indexing cannot continue for E:\.....pst (error=0x80940d23). If this error continues, contact Microsoft Support."

08:15:02 Application Information 1013 "Windows Search Service stopped normally."



08:15:02 Application Information 1001 "Fault bucket 1904117234015750461, type 5
Event Name: WsearchHealth
Response: Not available
Cab Id: 0


Problem signature:
P1: Corruption
P2: 0x8e5e0713
P3: onecoreuap\base\appmodel\search\search\ytrip\common\util\jetutil.cpp
P4: 296
P5:
P6:
P7:
P8:
P9:
P10:


Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5476.tmp.WERInternalMetadata.xml


These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_Corruption_97cca3dfb0a6d7064f154ea92e41a923bc3650_00000000_3c0d5448


Analysis symbol:
Rechecking for solution: 0
Report Id: 3bdd024a-bbbc-428c-afcd-c80df4699d6d
Report Status: 268435552
Hashed bucket: 7d3926df37f60e990a6cc8893035493d
Cab Guid: 0"



08:15:19 Application Warning 1008 "The Windows Search Service is starting up and attempting to remove the old search index {Reason: Index Corruption}. "


08:15:19 Application Information 1010 "The Windows Search Service has successfully removed the old search index. "


08:15:19 Application Information 1004 "The Windows Search service is creating the new search index {Reason: Index Corruption}. "


Followed by a few more entries about the new index being started etc.


ok, so it apparently got corrupted and decided to rebuild itself. But does anyone have any idea WHY it keeps happening, or how to stop it?


Once is an accident, twice is a coincidence, three times is a pattern, and any more is just an annoying pain in the ****.

Continue reading...
 

Similar threads

T
Replies
0
Views
18
TOG Avenged7x
T
A
Replies
0
Views
41
Alan Wortman
A
B
Replies
0
Views
31
Binux Anrolovic
B
S
Replies
0
Views
22
StevenMueller4
S
Back
Top