Windows Search Index is crashing at log in/

Posted on 2008-10-06
Medium Priority
Last Modified: 2012-06-21
Recently we had a laptop networked to a domain, start crashing at startup with SearchIndexing.exe - Application error. then (Blue Screen). We have done nothing different in the system and I have checked the hardware (Memory, Hard Drive). This just happened out of the blue. The only thing I can think of is Service Pack 3 causing the problem. Please Help.
Question by:chaddy1976
  • 5
  • 2

Expert Comment

ID: 22655287
Can you start in Safe Mode?

If so, then try with:
sfc /scannow

Expert Comment

ID: 22655298
Otherwise, then boot from Windows CD, enter Recovery Console and use these commands (if not using dual boot):


10 things you can do when Windows XP won't boot:

Author Comment

ID: 22659367
I used windows cd and when i selected recovery console it blue screened. I switched out memory and still same problem. Currently testing hard drive for errors. The hard drive is 3 months old and Seagate. Using Seatools presently. Will post results when done. This laptop has had 3 hard drives in it since new. Its an MPC laptop. What could causing these to keep going out?
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Expert Comment

ID: 22659696
Do you remember the error message in the blue screen when trying to use recovery console?

Author Comment

ID: 22661294
Hard drive Seatools came back ok. However, the Blue screen is happening all the time (ntfs.sys) and I cannot repair the installation or scan disk because of this. The unit constantly comes up with ntfs.sys error. I also slaved it to another PC and on boot, the blue screen came up on it as well. (ntfs.sys)

Accepted Solution

pablovr earned 2000 total points
ID: 22664930
Ok, with that info, take a look at this post...
Solution in that article
Look here:


Troubleshooting Stop 0x24 or NTFS_FILE_SYSTEM Error Messages
The information in this article applies to:

* Microsoft Windows 2000 Professional

This article was previously published under Q228888
When you run Windows 2000, you may receive either of the following error messages:
Stop 0x00000024


This issue can occur if a problem occurred within the Ntfs.sys file. The Ntfs.sys file is the driver file that enables your computer to read and write to NTFS partitions. Damage in the NTFS file system, damaged portions of your hard disk, or damaged SCSI or IDE drivers can also cause this issue.
To resolve this issue:

   1. Interpret the error message. The stop error is followed by four parameters defined in order of appearance:

          * Source file and line number.
          * Optionally contains the address of the exception record.
          * Optionally contains the address of the context record.
    * Optionally contains the address where the original exception occurred.
      All stop errors due to problems with NTFS or FAT have encoded in their first parameter the source file and the line number within the source file that generated the stop error. The high 16 bits (the first four hexadecimal digits after 0x) identify the source file number, and the lower 16 bits (the last four hexadecimal digits of the parameter) identify the source line in the file where the stop occurred.
   2. Check Event Viewer for error messages from SCSI, FASTFAT (the System Log), or Autochk (the Application Log) that might help determine the device or driver that is causing the error.
   3. Try disabling any virus scanning programs, backup programs, or disk defragmenter tools that constantly monitor your computer, and if possible, run hardware diagnostics tools supplied by your computer manufacturer.
   4. Run chkdsk /r to detect and resolve any file system structural damage.
   5. Depletion of non-paged pool memory can cause this issue. If you create a Services for Macintosh (SFM) volume on a large partition (7 gigabytes or larger) with a large number of files (at least 100,000) while the AppleTalk driver Apf.sys is running, the indexing routine consumes a large amount of non-paged pool memory. If the non-paged pool memory is completely depleted, this error can cause your computer to stop responding (hang). However, if the amount of available non-paged pool memory is very low during the indexing process, another kernel-mode driver requiring non-paged pool memory can also cause this issue. To resolve this issue, increase the amount of installed RAM to increase the quantity of non-paged pool memory available to the kernel, or reduce the number of files on the SFM volume.

Any corrupted system or data volume that is using NTFS can cause this error message. If you receive a "stop 0x24" error message when you restart the computer or when you try to run Setup or Recovery Console, you may not be able to determine the cause of the problem by using the steps outlined above. Instead, use one of the following methods to resolve the corrupted NTFS volume.
FAT or FAT32 File System
If your system partition is using the FAT or FAT32 file system, disconnect or turn off any data disks that contain NTFS volumes. This allows you to start back into the operating system to perform troubleshooting steps. If you can determine which NTFS volume is causing the boot problem, use the following steps:

   1. Make sure the drive that contains the corrupted NTFS volume is disconnected, and then start Windows by using Safe mode.
   2. Rename the %SystemRoot%\System32\Drivers\Ntfs.sys file to Ntfs.old, and then shut down the computer (this action prevents the Ntfs.sys driver from loading).
   3. Reconnect the drive that contains the corrupted NTFS volume.
   4. Restart the computer, and then run the following command on the corrupted NTFS volume:

      chkdsk driveletter: /f
      NOTE: The Chkdsk tool has built-in support for NTFS and does not require the Ntfs.sys driver to make repairs.

   5. After you use the Chkdsk tool to repair the corrupted NTFS volume, rename %SystemRoot%\System32\Drivers\Ntfs.old to Ntfs.sys, and then shut down and restart the computer.

The computer should be operational again, and you can try to determine what caused the original problem.
NTFS File System
If your system partition is using the NTFS file system, it is possible that the system partition is corrupted and is causing the "stop 0x24" error message.

To determine if this is the case, disconnect or turn off all other data disks that contain NTFS volumes. After you determine which disk contains the corrupted NTFS volume, move the disk to another Windows 2000-based computer that is running on the FAT or FAT32 file system, or install Windows 2000 on a disk that contains the FAT or FAT32 file system. After you do this, use the steps that are outlined in the "FAT or FAT32 File System" section.
Using Recovery Console on a Single Drive Computer
If your computer contains only a single NTFS volume and no additional Windows 2000-based computers or hard disks are available to use for the previously described methods, you can boot from the four Setup disks to run the Chkdsk tool with the Ntfs.sys driver disabled. To repair a NTFS volume by using Recovery Console, use the following steps:

   1. Start the computer by using a Microsoft Windows 95/98 startup disk with CD-ROM support (or from another computer with a CD-ROM drive, insert the Windows 2000 installation CD-ROM).
   2. Change to the CD_ROM:\Support\Bootdisk folder, and then run Makeboot.exe or Makebt32.exe to create the four Windows 2000 Setup disks.
   3. Using Notepad, modify the Txtsetup.sif file on the first Setup disk you created in step 2:
         1. In the [FileSystems.Load] section, locate the line that begins with "ntfs."
         2. Insert a semicolon (;) at the beginning of the line, as shown in the following example:

fat      = fastfat.sys
;ntfs     = ntfs.sys

         3. Save your changes.
   4. Start the computer that is experiencing the "stop 0x24" error message by using the four Setup disks. When the Welcome to Setup dialog box is displayed, press F10 to start Recovery Console.
   5. Run the following command to repair the corrupted NTFS partition:

      chkdsk driveletter: /p
   6. Type exit to quit Recovery Console, and then restart the computer.

If none of these methods work, you may have to delete, re-create, and format the corrupted NTFS partition, and restore the partition from your last good backup of the volume. The fdisk command in MS-DOS 5.x, MS-DOS 6.x, or Windows 95 and Windows 98 lets you to delete NTFS partitions by selecting and deleting the NON-DOS partition.  

Expert Comment

ID: 22664945
Even when the microsoft kb says it is for Windows 2000, it worked as well for the person which had this problem in Windows XP.
As he says...
I did the windows 2000 boot disk procedure.. and I have recovered all the data !!! perfect !!!!!!  

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you have done a reformat of your hard drive and proceeded to do a successful Windows XP installation, you may notice that a choice between two operating systems when you start up the machine. Here is how to get rid of this: Click Start Clic…
For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
When cloud platforms entered the scene, users and companies jumped on board to take advantage of the many benefits, like the ability to work and connect with company information from various locations. What many didn't foresee was the increased risk…
Suggested Courses

621 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question