Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Windows Indexing


  • Please log in to reply

#1
A1RotNBrat

A1RotNBrat

    Member

  • Member
  • PipPipPip
  • 102 posts

My windows indexing is not working.  My pictures, etc aren't where they are supposed to be.  When I tried to modify the index, the option is not there.  It just says Windows Indexing is not working.  It has my entire computer moving SLOWLY and hang up.  When I trying the troubleshooting tool, it's no help. See attached.  It tells me that the indexing isn't working (which I already know..ha).It also tells me to run as an administrator (which I am logged in as) but I click and allow it to run as administrator and it still won't fix itself.  Please help!!!  Indexing1.png Indexing2.png indexing3.png Indexing4.png

 


  • 0

Advertisements


#2
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,016 posts
  • MVP

In the search box  (Alternatively, bring up a command window) type:

 

services.msc

 

hit Enter. That should bring up the Services Window.  Find the Windows Search service and double click on it.  Is the service Running.  If not is the Startup Type set to Automatic (Delayed Start) then change it and hit Apply.  Try to start the service.  Do you get an Error?  If so what does it say?

 

If you don't see Windows Search then you need to:

 

 

  1. Open Control Panel > Programs and Features > Turn Windows Features on or off.
  2. Select Turn Windows Features on or off
  3. Check the box for Indexing Service and Windows Search then OK and reboot.

  • 0

#3
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts

Okay, did both of these.  Got an error (see attached) when I tried to start the service.  Then I don't even see the Indexing/Search Option under features.  See attached.Indexing5.png Indexing6.png


  • 0

#4
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts

Okay, did both of these.  Got an error (see attached) when I tried to start the service.  Then I don't even see the Indexing/Search Option under features.  See attached.Indexing5.png Indexing6.png


  • 0

#5
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,016 posts
  • MVP

In the search box or in a CMD prompt type:

 

eventvwr.msc 

 

This should open the Event Viewer.  Click on Windows Logs,  then right click on Applications and Clear Log. Clear.  Right click on System and Clear Log, Clear.

 

Open an elevated Command Window

 

http://www.eightforu...indows-8-a.html

Type with an Enter after each line:

sfc  /scannow

When it finishes

DISM  /Online  /Cleanup-Image  /RestoreHealth

Reboot

 

Go back into the services.msc and see if Windows Search is now started.

 

If not then get VEW.exe:

 

 
1. Please download the Event Viewer Tool by Vino Rosso
and save it to your Desktop:
2. Right-click VEW.exe and Run AS Administrator
3. Under 'Select log to query', select:
 
* System
4. Under 'Select type to list', select:
* Error
* Warning
 
 
Then use the 'Number of events' as follows:
 
 
1. Click the radio button for 'Number of events'
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.
 
 
Please post the Output log in your next reply then repeat but select Application.
 
 (Second time you run vew it will overwrite the first log so copy it to a reply or rename it first.)

  • 0

#6
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts
After I did the reboot my computer is just sitting here saying "Getting windows ready do not turn off your computer". Almost an hour now. Is this normal after the reboot? way longer than normally takes.
  • 0

#7
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,016 posts
  • MVP

certainly should not take that long.  Think you are going to have to hold down the power button and try again.


  • 0

#8
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts
Here's the System Log
 
Vino's Event Viewer v01c run on Windows 7 in English
Report run at 07/01/2016 10:50:11 AM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 07/01/2016 4:32:34 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 07/01/2016 4:32:34 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 07/01/2016 4:49:33 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly.  It has done this 9 time(s).
 
Log: 'System' Date/Time: 07/01/2016 4:49:22 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {B52D54BB-4818-4EB9-AA80-F9EACD371DF8} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 07/01/2016 4:47:22 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly.  It has done this 8 time(s).
 
Log: 'System' Date/Time: 07/01/2016 4:47:11 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {B52D54BB-4818-4EB9-AA80-F9EACD371DF8} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 07/01/2016 4:45:11 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly.  It has done this 7 time(s).
 
Log: 'System' Date/Time: 07/01/2016 4:45:00 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {B52D54BB-4818-4EB9-AA80-F9EACD371DF8} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 07/01/2016 4:44:32 PM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The Intel® Management and Security Application User Notification Service service hung on starting.
 
Log: 'System' Date/Time: 07/01/2016 4:43:00 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly.  It has done this 6 time(s).
 
Log: 'System' Date/Time: 07/01/2016 4:42:50 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly.  It has done this 5 time(s).
 
Log: 'System' Date/Time: 07/01/2016 4:42:26 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly.  It has done this 4 time(s).
 
Log: 'System' Date/Time: 07/01/2016 4:40:05 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly.  It has done this 3 time(s).
 
Log: 'System' Date/Time: 07/01/2016 4:40:04 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server windowsphone.App.wwa did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 07/01/2016 4:39:11 PM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Windows Search service terminated unexpectedly.  It has done this 2 time(s).  The following corrective action will be taken in 30000 milliseconds: Restart the service.
 
Log: 'System' Date/Time: 07/01/2016 4:38:52 PM
Type: Error Category: 0
Event: 7032 Source: Service Control Manager
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.
 
Log: 'System' Date/Time: 07/01/2016 4:38:29 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The ATT MAHostService service terminated unexpectedly.  It has done this 3 time(s).
 
Log: 'System' Date/Time: 07/01/2016 4:38:29 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The event description cannot be found.
 
Log: 'System' Date/Time: 07/01/2016 4:38:28 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  {7022A3B3-D004-4F52-AF11-E9E987FEE25F}  and APPID  {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}  to the user Martin\Amy Martin SID (S-1-5-21-3873701136-3596577701-2754614134-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 07/01/2016 4:38:28 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  {7022A3B3-D004-4F52-AF11-E9E987FEE25F}  and APPID  {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}  to the user Martin\Amy Martin SID (S-1-5-21-3873701136-3596577701-2754614134-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 07/01/2016 4:38:28 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  {7022A3B3-D004-4F52-AF11-E9E987FEE25F}  and APPID  {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}  to the user Martin\Amy Martin SID (S-1-5-21-3873701136-3596577701-2754614134-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 07/01/2016 4:38:28 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  {7022A3B3-D004-4F52-AF11-E9E987FEE25F}  and APPID  {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}  to the user Martin\Amy Martin SID (S-1-5-21-3873701136-3596577701-2754614134-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 07/01/2016 4:32:43 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device USB\VID_0BB4&PID_0BAD&MI_00\6&540db0c&0&0000.
 
Log: 'System' Date/Time: 07/01/2016 3:45:07 PM
Type: Warning Category: 0
Event: 1073 Source: User32
The attempt by user MARTIN\Amy Martin to restart/shutdown computer MARTIN failed

  • 0

#9
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts

Application Log

 

Vino's Event Viewer v01c run on Windows 7 in English
Report run at 07/01/2016 10:53:51 AM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 07/01/2016 4:51:45 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchIndexer.exe, version: 7.0.9600.17787, time stamp: 0x551b6346 Faulting module name: ntdll.dll, version: 6.3.9600.18146, time stamp: 0x5650b9bb Exception code: 0xc00000fd Fault offset: 0x0000000000030c72 Faulting process id: 0x1860 Faulting application start time: 0x01d1496ba9ff9bed Faulting application path: C:\WINDOWS\system32\SearchIndexer.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: ef27b94d-b55e-11e5-bf77-d9a9110a9782 Faulting package full name:  Faulting package-relative application ID: 
 
Log: 'Application' Date/Time: 07/01/2016 4:49:33 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchIndexer.exe, version: 7.0.9600.17787, time stamp: 0x551b6346 Faulting module name: msvcrt.dll, version: 7.0.9600.17415, time stamp: 0x545055fe Exception code: 0xc00000fd Fault offset: 0x0000000000001f4a Faulting process id: 0x1994 Faulting application start time: 0x01d1496b5c0440dc Faulting application path: C:\WINDOWS\system32\SearchIndexer.exe Faulting module path: C:\WINDOWS\system32\msvcrt.dll Report Id: a009d424-b55e-11e5-bf77-d9a9110a9782 Faulting package full name:  Faulting package-relative application ID: 
 
Log: 'Application' Date/Time: 07/01/2016 4:47:22 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchIndexer.exe, version: 7.0.9600.17787, time stamp: 0x551b6346 Faulting module name: ntdll.dll, version: 6.3.9600.18146, time stamp: 0x5650b9bb Exception code: 0xc00000fd Fault offset: 0x0000000000048ade Faulting process id: 0xe34 Faulting application start time: 0x01d1496b0e3e61ab Faulting application path: C:\WINDOWS\system32\SearchIndexer.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 5207e788-b55e-11e5-bf77-d9a9110a9782 Faulting package full name:  Faulting package-relative application ID: 
 
Log: 'Application' Date/Time: 07/01/2016 4:45:11 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchIndexer.exe, version: 7.0.9600.17787, time stamp: 0x551b6346 Faulting module name: msvcrt.dll, version: 7.0.9600.17415, time stamp: 0x545055fe Exception code: 0xc00000fd Fault offset: 0x00000000000022b0 Faulting process id: 0x3ec Faulting application start time: 0x01d1496abfa85079 Faulting application path: C:\WINDOWS\system32\SearchIndexer.exe Faulting module path: C:\WINDOWS\system32\msvcrt.dll Report Id: 044a997f-b55e-11e5-bf77-d9a9110a9782 Faulting package full name:  Faulting package-relative application ID: 
 
Log: 'Application' Date/Time: 07/01/2016 4:43:40 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program backgroundTaskHost.exe version 6.3.9600.17415 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.  Process ID: 1168  Start Time: 01d14969d4089f99  Termination Time: 4294967295  Application Path: C:\WINDOWS\system32\backgroundTaskHost.exe  Report Id: cb42af59-b55d-11e5-bf77-d9a9110a9782  Faulting package full name: Facebook.Facebook_1.4.0.9_x64__8xx8rvfyw5nnt  Faulting package-relative application ID: App 
 
Log: 'Application' Date/Time: 07/01/2016 4:42:59 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchIndexer.exe, version: 7.0.9600.17787, time stamp: 0x551b6346 Faulting module name: msvcrt.dll, version: 7.0.9600.17415, time stamp: 0x545055fe Exception code: 0xc00000fd Fault offset: 0x00000000000022a3 Faulting process id: 0x166c Faulting application start time: 0x01d1496a725d5db9 Faulting application path: C:\WINDOWS\system32\SearchIndexer.exe Faulting module path: C:\WINDOWS\system32\msvcrt.dll Report Id: b5ae2f5e-b55d-11e5-bf77-d9a9110a9782 Faulting package full name:  Faulting package-relative application ID: 
 
Log: 'Application' Date/Time: 07/01/2016 4:42:50 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchIndexer.exe, version: 7.0.9600.17787, time stamp: 0x551b6346 Faulting module name: ntdll.dll, version: 6.3.9600.18146, time stamp: 0x5650b9bb Exception code: 0xc00000fd Fault offset: 0x000000000004865e Faulting process id: 0x1878 Faulting application start time: 0x01d1496a6cb8dfe3 Faulting application path: C:\WINDOWS\system32\SearchIndexer.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: aff087af-b55d-11e5-bf77-d9a9110a9782 Faulting package full name:  Faulting package-relative application ID: 
 
Log: 'Application' Date/Time: 07/01/2016 4:42:25 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchIndexer.exe, version: 7.0.9600.17787, time stamp: 0x551b6346 Faulting module name: msvcrt.dll, version: 7.0.9600.17415, time stamp: 0x545055fe Exception code: 0xc00000fd Fault offset: 0x00000000000022b7 Faulting process id: 0x1a74 Faulting application start time: 0x01d1496a448b32f4 Faulting application path: C:\WINDOWS\system32\SearchIndexer.exe Faulting module path: C:\WINDOWS\system32\msvcrt.dll Report Id: a16e6d34-b55d-11e5-bf77-d9a9110a9782 Faulting package full name:  Faulting package-relative application ID: 
 
Log: 'Application' Date/Time: 07/01/2016 4:40:04 PM
Type: Error Category: 5973
Event: 5973 Source: Microsoft-Windows-Immersive-Shell
Activation of app Microsoft.WindowsPhone_8wekyb3d8bbwe!windowsphone.App failed with error: The app didn't start in the required time. See the Microsoft-Windows-TWinUI/Operational log for additional information.
 
Log: 'Application' Date/Time: 07/01/2016 4:40:05 PM
Type: Error Category: 0
Event: 35 Source: Outlook
Failed to determine if the store is in the crawl scope (error=0x800706be).
 
Log: 'Application' Date/Time: 07/01/2016 4:40:05 PM
Type: Error Category: 0
Event: 34 Source: Outlook
Failed to get the Crawl Scope Manager with error=0x800706be.
 
Log: 'Application' Date/Time: 07/01/2016 4:40:05 PM
Type: Error Category: 0
Event: 35 Source: Outlook
Failed to determine if the store is in the crawl scope (error=0x800706be).
 
Log: 'Application' Date/Time: 07/01/2016 4:40:05 PM
Type: Error Category: 0
Event: 34 Source: Outlook
Failed to get the Crawl Scope Manager with error=0x800706be.
 
Log: 'Application' Date/Time: 07/01/2016 4:40:04 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program LiveComm.exe version 17.5.9600.20911 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.  Process ID: 6b0  Start Time: 01d14969372d3997  Termination Time: 4294967295  Application Path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.5.9600.20911_x64__8wekyb3d8bbwe\LiveComm.exe  Report Id: 2d12d41b-b55d-11e5-bf77-d9a9110a9782  Faulting package full name: microsoft.windowscommunicationsapps_17.5.9600.20911_x64__8wekyb3d8bbwe  Faulting package-relative application ID: ppleae38af2e007f4358a809ac99a64a67c1 
 
Log: 'Application' Date/Time: 07/01/2016 4:40:04 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program UNKNOWN version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.  Process ID: 136c  Start Time: 01d14969de1d3d39  Termination Time: 4294967295  Application Path: UNKNOWN  Report Id: 24204dcc-b55d-11e5-bf77-d9a9110a9782  Faulting package full name: Microsoft.WindowsPhone_1.42.1701.1_x64__8wekyb3d8bbwe  Faulting package-relative application ID: windowsphone.App 
 
Log: 'Application' Date/Time: 07/01/2016 4:40:04 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchIndexer.exe, version: 7.0.9600.17787, time stamp: 0x551b6346 Faulting module name: msvcrt.dll, version: 7.0.9600.17415, time stamp: 0x545055fe Exception code: 0xc00000fd Fault offset: 0x00000000000022de Faulting process id: 0x60c Faulting application start time: 0x01d1496a018f1bc8 Faulting application path: C:\WINDOWS\system32\SearchIndexer.exe Faulting module path: C:\WINDOWS\system32\msvcrt.dll Report Id: 4d2c80d5-b55d-11e5-bf77-d9a9110a9782 Faulting package full name:  Faulting package-relative application ID: 
 
Log: 'Application' Date/Time: 07/01/2016 4:39:07 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchIndexer.exe, version: 7.0.9600.17787, time stamp: 0x551b6346 Faulting module name: msvcrt.dll, version: 7.0.9600.17415, time stamp: 0x545055fe Exception code: 0xc00000fd Fault offset: 0x00000000000022de Faulting process id: 0x1204 Faulting application start time: 0x01d14969d6513aea Faulting application path: C:\WINDOWS\system32\SearchIndexer.exe Faulting module path: C:\WINDOWS\system32\msvcrt.dll Report Id: 2b3fb571-b55d-11e5-bf77-d9a9110a9782 Faulting package full name:  Faulting package-relative application ID: 
 
Log: 'Application' Date/Time: 07/01/2016 3:45:58 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchIndexer.exe, version: 7.0.9600.17787, time stamp: 0x551b6346 Faulting module name: ntdll.dll, version: 6.3.9600.18146, time stamp: 0x5650b9bb Exception code: 0xc00000fd Fault offset: 0x0000000000030e5a Faulting process id: 0x51c0 Faulting application start time: 0x01d149626b170053 Faulting application path: C:\WINDOWS\system32\SearchIndexer.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: be831940-b555-11e5-bf76-cd723b81e503 Faulting package full name:  Faulting package-relative application ID: 
 
Log: 'Application' Date/Time: 07/01/2016 3:43:22 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchIndexer.exe, version: 7.0.9600.17787, time stamp: 0x551b6346 Faulting module name: ntdll.dll, version: 6.3.9600.18146, time stamp: 0x5650b9bb Exception code: 0xc00000fd Fault offset: 0x0000000000030c72 Faulting process id: 0x5a1c Faulting application start time: 0x01d149621e227009 Faulting application path: C:\WINDOWS\system32\SearchIndexer.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 611e7e6c-b555-11e5-bf76-cd723b81e503 Faulting package full name:  Faulting package-relative application ID: 
 
Log: 'Application' Date/Time: 07/01/2016 3:41:12 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchIndexer.exe, version: 7.0.9600.17787, time stamp: 0x551b6346 Faulting module name: ntdll.dll, version: 6.3.9600.18146, time stamp: 0x5650b9bb Exception code: 0xc00000fd Fault offset: 0x0000000000030c72 Faulting process id: 0x44cc Faulting application start time: 0x01d14961d0b7ff16 Faulting application path: C:\WINDOWS\system32\SearchIndexer.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 14285708-b555-11e5-bf76-cd723b81e503 Faulting package full name:  Faulting package-relative application ID: 
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

  • 0

#10
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts

Oh I forgot to attached these.  This is what it said when I did the other steps.Indexing7.png Indexing8.png Indexing9.png


  • 0

Advertisements


#11
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,016 posts
  • MVP

The dism command should take a while to run.  Did you wait for the prompt to return before rebooting?

 

Get the free version of Speccy:
 
http://www.filehippo...download_speccy (Look in the upper right for the Download
Latest Version button  - Do NOT press the large Start Download button on the upper left!)  Download, Save and Install it.  
 
Close all browsers and open progrms before running Speccy.  Run Speccy.  When it finishes (the little icon in the bottom left will stop moving), File, Save as Text File,  (to your desktop) note the name it gives. OK.  Open the file in notepad and delete the line that gives the serial number of your Operating System.  (It will be near the top about 10 lines down.)  Save the file and close notepad  Attach the file to your next post as it is usually too large for the forum (Click on More Reply Options then Choose file, select the file, Open, Attach this File) Uninstall Speccy.

  • 0

#12
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts

I don't think I waited long enough on the dism.  Maybe why the computer was taking so long to reboot.  So, I ran it again until completed (see attached).  Then rebooted and checked services again and it still wasn't working and when I tried to start it got the attached message. I also reran the scan after this and the results are attached too. I am going to run the speccy now and will post those results shortly.  THANKS!!  Indexing10.png Indexing11.png Indexing11.png  Indexing12.png


  • 0

#13
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts

Speccy results attached.Attached File  MARTIN.txt   868.11KB   146 downloads


  • 0

#14
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,016 posts
  • MVP

Looks like DISM fixed the stuff SFC was complaining about.  Still not clear why Windows Search is not starting.  Speccy says your temps are a bit warm but not to the point where it would cause trouble.  Your hard drive looks pretty good.  Search is very sensitive to disk errors tho so you should probably run a disk check.  

 

http://www.thewindow...cking-windows-8

 

 

You might try the procedure on this page:

 

http://www.windowswa...in-windows-8-1/

 

Skip down to where it says:

 

Undo Changes To The Windows 8 Registry

 

Ignore any recommendations to use a registry cleaner.


  • 0

#15
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts

Done these and the problem seems like it's back to before again.  It seemed some better after running the dism, etc even though the indexing wasn't working.  Now it's taking it forever to load when I reboot and is sloooooowwww again.  Still getting the error message when I try to start windows search.  The scan was fine.  Here's the screenshot of the results.Indexing13.png Indexing14.png


Edited by A1RotNBrat, 07 January 2016 - 08:18 PM.

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP