Windows 10: When I run chkdsk it says "file record segment 3D924 is corrupt" what does it mean? Should...

When I run chkdsk it says "file record segment 3D924 is corrupt" what does it mean? Should i have to buy a new hard drive?My system is going into hang many times whenever I turn it on and gives bsod every time it's turned on and restarts after that, it takes too long too restart after that.Also the sound driver was uninstalled unexpectedly without my knowledge automatically I have no idea what is happening Help!

:)

 

Attribute record (80, "") corrupt file segments

Keep getting a message that I need to restart to repair something. I restart and the drive is scanned and repair initiated but doesn't fix whatever needs fixing. I run CHKDSK from command prompt and get the following 10 files (see below) showing
as corrupt. I run /f, and /r and restart but the problem persists. I don't have a backup disc. Computer is about 10 years old AMD Phenom II X6 1100T Processor but I replaced the hard drive about 4 years ago. Any advice is appreciated!

Microsoft Windows [Version 10.0.17763.1098]

(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>chkdsk

The type of the file system is NTFS.

Volume label is New Volume.

WARNING! /F parameter not specified.

Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...

Attribute record (80, "") from file record segment 64E5

is corrupt.

Attribute record (80, "") from file record segment 12E9D

is corrupt.

Attribute record (80, "") from file record segment 132C8

is corrupt.

Attribute record (A0, $I30) from file record segment ****

is corrupt.

Attribute record (80, "") from file record segment 299AE

is corrupt.

Attribute record (80, "") from file record segment 32825

is corrupt.

Attribute record (80, "") from file record segment 43C23

is corrupt.

Attribute record (80, "") from file record segment 4F10D

is corrupt.

Attribute record (80, "") from file record segment 63E23

is corrupt.

Attribute record (80, "") from file record segment 99280

is corrupt.

825856 file records processed.

File verification completed.

41989 large file records processed.

Errors found. CHKDSK cannot continue in read-only mode.

C:\WINDOWS\system32>

 

Identify file name(s) associated with chkdsk corrupt file record segments

I have a Dell XPS15, 32 GB RAM, 1 TB SSD, Windows 10.

The following are the results from CHKDSK read-only:

Since it cannot continue, does that imply that there may be additional existing errors?

My understanding is that CHKDSK /R will recover 'READABLE' information.
So, before I run chkdsk /r, is there any way to identify the filename(s) associated with:

• file 7ADAE
  
• file record segment 1003F
  
• file record segment 21D8F
  
• file record segment 74337
  
• file record segment 74CF5
  

Once I identify the filenames I plan on restoring them from a recent backup after running
`chkdsk /r.

 

Transferable File Record Segments are unreadable? CHKDSK

Situation.

Two, twin 1 TB WD HDDs. D: and H:

D: showed it was corrupting, H: was healthy, moved all files to H:

Ran chkdsk on D: to begin recovery and repair procedures after moving as many files as possible to the H:, taking extensive hours to migrate the data.. To my knowledge, File Record Segments being unreadable are an indicator of a hardware fault... but here's
the kicker.

After the files were migrated, the errors went away on the D: and the same exact errors began to materialize on the H:. I got kind of excited, because I thought this may mean it's a simple file structure issue. But here's the problem. It's saying 300+ hours
to complete the chkdsk on the H: , D is chugging right along. The file error messages were verbatim identical in the sector number by letter and number. Anyone ever seen anything like this before and may be able to give me some guidance on what I'm looking
at?

Migrated data and programs are still working as if nothing is wrong.