Trouble with Windows Search service - BSODs on indexing

Anonimowe
2021-12-22T16:35:35+00:00

For about one week I have trouble with search indexing. While indexing system is crashing with BSOD (either "critical service died" or "kernel data inpage error"). I tried many things to solve this. First I checked the system log. There were various errors regarding search service (for example error 7042: the catalogue is corrupt, error 465 ESENT etc.) I ran windows search trouble-shooter - I was given information that permissions to search folder are corrupted and indeed when I checked permissions, they were set to allow "all". Trouble-shooter was unable to solve issue. I tried icacls [search folder path] /reset /T /C, rebuilding index, changing search folder location, stopping the service and manually deleting search folder contents, I run sfc /scannnow, dism restore health, chcksdk, scannpst on my outlook data folders, I did scan with my antivirus program, I uninstalled antivirus program and run scan with windows defender. No effects and no errors or viruses found (system keeps crashing, trouble-shooter still shows permissions error). Finally I used instructions on the following website: https://docs.microsoft.com/en-us/troubleshoot/windows-client/shell-experience/fix-problems-in-windows-search (no effect). When I disable search service everything runs normally. Today I rechecked event viewer and other common error is volmgr, error 161 - it is registered at times when system crashes. I have about 200 000 - 300 000 items to index and windows.edb file is about 4gb. I run also full hardware diagnostics using Dell Support Assist and no errors were found. Please, give me any suggestions how to solve this problem. Kind regards BP

Windows dla domu | Windows 10 | Cortana i wyszukiwanie

Pytanie zablokowane. To pytanie zostało zmigrowane ze społeczności pomocy technicznej firmy Microsoft. Możesz zagłosować, czy pytanie jest pomocne, ale nie możesz dodawać komentarzy ani odpowiedzi, ani też śledzić pytania.

Komentarze: 0 Brak komentarzy

Odpowiedzi: 3

Sortuj według: Najbardziej pomocne
  1. DaveM121 927.4K Punkty reputacji Niezależny doradca
    2021-12-22T17:07:27+00:00

    Hi BartekP

    I am Dave, I will help you with this.

    Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

    Open Windows File Explorer.

    Navigate to C:\Windows\Minidump

    Copy any minidump files onto your Desktop, then zip those up.

    Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

    Then post the link here to the zip file, so we can take a look for you.

    Czy ta odpowiedź była pomocna?

    1 osoba uznała tę odpowiedź za pomocną.
    Komentarze: 0 Brak komentarzy
  2. DaveM121 927.4K Punkty reputacji Niezależny doradca
    2021-12-23T08:38:43+00:00

    Hi BartekP

    Your minidump files just indicate memory (RAM) corruption no specific driver is listed

    1

    Go to the support page for your PC or Motherboard on the manufacturers website, then from there, download and install the version of Chipset drivers they recommend and while there, check for any BIOS update that may need to be installed

    2

    Wait to see if your system stabilizes, if not, to try to force Windows 10 show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

    https://answers.microsoft.com/en-us/windows/for...

    Czy ta odpowiedź była pomocna?

    Komentarze: 0 Brak komentarzy
  3. Anonimowe
    2021-12-23T08:30:52+00:00

    Hi, there are no recent dumps. In the folder I have just 5 files older then 6 months: here is the link . In my event viewer I have multiple volmgr errors 161: "Dump file creation failed due to error during dump creation".

    Czy ta odpowiedź była pomocna?

    Komentarze: 0 Brak komentarzy