O arquivo leu o erro em arquivos grandes e o checkdisk falha. O meu HDD precisa ser substituído?

Question

Eu enfrentei recentemente problemas de leitura de arquivos em vários arquivos grandes (> 3 GB) no sistema Windows 10 que estão em um disco específico (disco rígido comum, não SSD). A reprodução mais fácil é copiar esse arquivo para outro disco. Então, quando a cópia está na metade, ela pára (a E / S do disco trava em 100%) e, após um minuto, o Windows me avisa que ela falhou devido a um erro de leitura.

Isso não acontece com todos os arquivos grandes ...

Eu tentei verificar este disco com chkdsk e ele também falha devido a falhas de leitura. Aqui está o relatório chkdsk do meu visualizador de eventos:

Chkdsk was executed in scan mode on a volume snapshot.  

Checking file system on E:
Volume label is Data2.

Stage 1: Examining basic file system structure ...

  969216 file records processed.                                                         File verification completed.

  208 large file records processed.                                                                                                                           
  0 bad file records processed.                                      
Stage 2: Examining file name linkage ...

  2599 reparse records processed.                                                                                                                              
  1266028 index entries processed.                                                        Index verification completed.

  2599 reparse records processed.                                       
Stage 3: Examining security descriptors ...
Security descriptor verification completed.

  148407 data files processed.                                            CHKDSK is verifying Usn Journal...
Read failure with status 0xc000009c at offset 0x8deacfc000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x8dead0b000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x8dead0c000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x8dead0e000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x8dead0f000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x8dead0f000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x8dead10000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x8dead10000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x8dead11000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x8dead12000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x8dead13000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x8dead13000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x8dead14000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x8dead1c000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x8dead1d000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x8dead1d000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x8dead1e000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x8dead2c000 for 0x1000 bytes.
Usn Journal verification completed.
Read failure with status 0xc0000483 at offset 0xba594000 for 0x10000 bytes.
A disk read error occurredc0000483

----------------------------------------------------------------------


Stage 1: Examining basic file system structure ...

Stage 2: Examining file name linkage ...

Stage 3: Examining security descriptors ...
An unspecified error occurred (6c6f6766696c652e 2a9).

Meu medo é que o disco rígido esteja quebrado (pelo menos parcialmente). Alguém pode confirmar meu medo ou me apontar para uma possível solução?