In the Event Viewer have found repeating error from the source NFTS, indentificator 55 :

"There has been found damage in the files structure of volumin Windows8_OS.

In the index structure of system files there has been found a damage. Reference numer to the  file :

0x100000000285d. Name of the file : "\Windows\System32\config." Attribute of damaged index : ":$130:$INDEX_ALLOCATION".

Have done as follows :

1/ sfc/scannow - the result :"Windows Resource Protection did not find any violations"

2/ dism/online/cleanup-image/restorehealth - the result : "The restore operation completed successfully. the component store corruption was repaired. The operation completed successfully".

3/ chds/f/r -after scanning no information about damages, moreover have checked the disc with HD tune program and  it is healthy.

What else can be done to repair this damage ?

Would appreciate your advise.

Thanks in advance, Ewa

Since CHKDSK does not show file system corruption I would go to the HD maker, download and run their HD checking utility.  You can find out who made the HD using Speccy, AIDA64, or belarc

If it is not file system (CHKDSK came back clean) it may well be the actual HD

Thanks for your reply. In my laptop Lenovo have the program for diagnostic Lenovo Solution Center - making regular scanning of the equipment. In the last  total test / and previous / the result is passed and no errors have been found.

Reg. HD - in a/m test there is information that the producer of HD is SEAGATE. There is available See tools for Windows program from Seagate to check the HD. Shall I use it or can also make such test with other program such like HDD Health or Disc checker ?

Have made already test using HD tune and no damage found.

Please advise what you recommend to do further.

Thank you in advance. Ewa

You should use the Seagate tool for a seagate hd.  It is more accurate than Generic tests.

Thank you very much for your assistance and advise. As since last 5 days there this error has not benn found in the Event Viewer I have taken no further action. Will use suggested Seagate tool when the error repeats.

Best regards, Ewa