Windows 10: An unspecified error occurred 696e647863686b2e 148d

I'm having some problems with my notebook, tried to use 'chkdsk', and this happen - An unspecified error occurred 696e647863686b2e 148d

:)

 

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.

 

chkdsk - An unspecified error occurred

Since I could not boot anymore I mounted an SSD into an external case and run chkdsk /f, and it comes up with:

Stage 1: Examining basic file system structure ...

333056 file records processed.

File verification completed.

21395 large file records processed.

0 bad file records processed.

Stage 2: Examining file name linkage ...

An unspecified error occurred (696e647863686b2e 532).

An unspecified error occurred (6e74667363686b2e 1713).

I'd like to know if this is a hardware problem, or what to do, since the drive is still under warranty grace period.

I can browse the file system normally, and I came to this point after running chkdsk and, following directions in the events log, chkdsk /spotfix (however it went on asking for chkdsk /f).

In case it could be relevant, I am attaching
full log of these two attemps (before the one pasted on this post).