Windows 10: An unspecified error occurred 696e647863686b2e 532. An unspecified error occurred...

computer started getting laggy and generally failing. at this point I generally decide it time for a fresh wipe. so I turn off my pc pull out my 2nd drive with all im info on it. then procced to format my m.2 drive. had a lot of trouble with it. boot looping. but eventually fixed it. apparently my cpu was not correctly seated with enough pressure from the cooler. after 2 days i got it online and booting normally. but my 2nd drive no longer was accessible saying that it was RAW. so I ran chkdsk /f d: and got the errors"An unspecified error occurred 696e647863686b2e 532. ""An unspecified erro

:)

 

about An unspecified error occurred (696e647863686b2e 1482).

Hello Dear Authorized ;

I have chkdsk An unspecified error occurred (696e647863686b2e 1482).

and its :

Stage 2: Examining file name linkage ...

Correcting error in index $I30 for file 5.

Insufficient disk space to correct errors

in index $I30 of file 5.

Deleting index entry GENÇ HUKUKÇULAR.docx in index $I30 of file 5.

An unspecified error occurred (696e647863686b2e 1482).

can you help me about this error .

thank you

sincerely

 

Error an unspecified error occurred (696e647863686b2e 10d4). on chkdsk

Hello,

I just run a chkdsk on my external hdd and during the scan it stopped and i got this error:

An unspecified error occurred (696e647863686b2e 10d4).

The paramenters i used were:

chkdsk /F /R /X

I tried to search this error but i couldnt find any information.

 

CHKDSK /F fails with An unspecified error occurred.

I decided to run chkdsk /f on a 1TB external usb HDD. It failed with:

An unspecified error occurred (696e647863686b2e 1f66).
An unspecified error occurred (6e74667363686b2e 1713).






....then I tried another known good external HDD, same error. Then I tried an internal partition, same error. Then I freshly formatted a usb flash drive as ntfs and checked it, same error.

Then I tried three different PCs, 1809 17763.379 (x86 and x64) and 1803 17134.648 (x86). All failed a chkdsk /f with an unspecified error on any ntfs drive I checked.

Then I tried Windows 7 and it passed the drives with a clean bill of health!





Is it me, or is Windows 10's chkdsk /f broken as far as ntfs is concerned?


PS: chkdsk WITHOUT the /f runs fine in Windows 10 on all the drives and says they are healthy.