Is my Hardrive dying?

[funboyfun23]

I feel as if this is the end of my hard drive. It's been having troubles for months. I recently did 3 check disks to see if it could fix the problem and I was wondering if anyone could translate or give some insight on the latest report. I'm really close to buying a new hard drive, but I just need to be sure. Also I've been having some trouble booting up windows, sometimes it'll get stuck on the windows logo, but no spinning dots will show up.


Graphics Chipset - Radeon (TM) RX 480 Graphics
Memory Size - 8192 MB
Memory Type - GDDR5
Core Clock - 1303 MHz
Windows Version - Windows 10 (64 bit)
System Memory - 16 GB
CPU Type - Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz
Storage: ST200DM001-1ER164 200.3 GB

Checking file system on C:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
Attribute record of type 0xa0 and instance tag 0x4 is cross linked
starting at 0xaef2a for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0x322bc is already in use.
Deleting corrupt attribute record (0xA0, $I30)
from file record segment 0x322BC.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0xb9c4d for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x322bf is already in use.
Deleting corrupt attribute record (0xA0, $I30)
from file record segment 0x322BF.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xa46e4 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x3230d is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x3230D.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xba049 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x32d3f is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x32D3F.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xba0cd for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x32d49 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x32D49.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xaee5e for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x32d85 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x32D85.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xaee6c for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x32d86 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x32D86.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xaeebd for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x32dae is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x32DAE.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x1cab for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x32ea8 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x32EA8.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x1cc7 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x32ea9 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x32EA9.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x1cce for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x32eaa is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x32EAA.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x266aa for possibly 0x39 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x32fa3 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x32FA3.
Attribute record of type 0xa0 and instance tag 0x4 is cross linked
starting at 0x1cde for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0x32fa4 is already in use.
Deleting corrupt attribute record (0xA0, $I30)
from file record segment 0x32FA4.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0xb1bef for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x58332 is already in use.
Deleting corrupt attribute record (0xA0, $I30)
from file record segment 0x58332.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x13a9c for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x5835b is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5835B.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xb19b7 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x58394 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x58394.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x4627 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x5840a is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5840A.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x86a34 for possibly 0x50 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x5841e is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5841E.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x9ba21 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x5847e is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5847E.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x9ba24 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x58485 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x58485.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x9ba27 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x584ed is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x584ED.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xa46b3 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x584f2 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x584F2.
Attribute record of type 0xa0 and instance tag 0x4 is cross linked
starting at 0x8bce8 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0x58538 is already in use.
Deleting corrupt attribute record (0xA0, $I30)
from file record segment 0x58538.
Attribute record of type 0xa0 and instance tag 0x4 is cross linked
starting at 0xb1d36 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0x5853c is already in use.
Deleting corrupt attribute record (0xA0, $I30)
from file record segment 0x5853C.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xaaddb for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x58546 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x58546.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xb22a6 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x5855a is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5855A.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xb23b5 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x5858a is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5858A.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xb2d5a for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x585ac is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x585AC.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xb3ee8 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x585ae is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x585AE.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xb9e69 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x585b0 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x585B0.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xabee2 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x585b2 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x585B2.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xaa225 for possibly 0x10 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x585c9 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x585C9.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0xa46fa for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x585de is already in use.
Deleting corrupt attribute record (0xA0, $I30)
from file record segment 0x585DE.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xa4847 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x585e2 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x585E2.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xacaba for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x586cf is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x586CF.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x236d6 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x58a0b is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x58A0B.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x9be69 for possibly 0xa4a clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x5c064 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5C064.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x9cab0 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x5c4e7 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5C4E7.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xab512 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x5c4fa is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5C4FA.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x73a7b for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x5c507 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5C507.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x9fd6a for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x5c50e is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5C50E.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xb3bd5 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x5c57a is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5C57A.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xb3df7 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x5c586 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5C586.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x9f1fb for possibly 0x12 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x5c5f6 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5C5F6.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0x9fb70 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x5c674 is already in use.
Deleting corrupt attribute record (0xA0, $I30)
from file record segment 0x5C674.
Attribute record of type 0xa0 and instance tag 0x4 is cross linked
starting at 0x79580 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0x5c686 is already in use.
Deleting corrupt attribute record (0xA0, $I30)
from file record segment 0x5C686.
Attribute record of type 0xa0 and instance tag 0x4 is cross linked
starting at 0x79582 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0x5c687 is already in use.
Deleting corrupt attribute record (0xA0, $I30)
from file record segment 0x5C687.
Attribute record of type 0xa0 and instance tag 0x4 is cross linked
starting at 0x79584 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0x5c694 is already in use.
Deleting corrupt attribute record (0xA0, $I30)
from file record segment 0x5C694.
Attribute record of type 0xa0 and instance tag 0x4 is cross linked
starting at 0x79590 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
in file 0x5c699 is already in use.
Deleting corrupt attribute record (0xA0, $I30)
from file record segment 0x5C699.
392192 file records processed. File verification completed.
10368 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x32139 is incorrect.
e8 a0 0e cb 48 18 c8 88 ?? ?? ?? ?? ?? ?? ?? ?? ....H...........
Correcting error in index $I30 for file 32139.
The index bitmap $I30 in file 0x32139 is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 32139.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ?? ................
Sorting index $I30 in file 32139.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x321b3 is incorrect.
a6 32 a5 88 44 c1 03 d3 ?? ?? ?? ?? ?? ?? ?? ?? .2..D...........
Correcting error in index $I30 for file 321B3.
The index bitmap $I30 in

 

[kanewolf]

You have obviously upgraded the CPU and GPU several times, but you are using a 200GB HDD ? That drive is probably 10 years old. It is probably hurting your performance significantly. Toss it and get an SSD.

 

[funboyfun23]

You have obviously upgraded the CPU and GPU several times, but you are using a 200GB HDD ? That drive is probably 10 years old. It is probably hurting your performance significantly. Toss it and get an SSD.

Sorry I think I typed down the wrong thing for the drive. My hard drive is a 2 TB seagate 7200rpm HDD. I ran CHKDSK multiple times and it always has to repair something, do you think the HDD is dying?

 

[funboyfun23]

I tried to run "Error Checking" from the disk drives properties, it said it was unable to finish scanning.

 

[kanewolf]

You have obviously upgraded the CPU and GPU several times, but you are using a 200GB HDD ? That drive is probably 10 years old. It is probably hurting your performance significantly. Toss it and get an SSD.

Sorry I think I typed down the wrong thing for the drive. My hard drive is a 2 TB seagate 7200rpm HDD. I ran CHKDSK multiple times and it always has to repair something, do you think the HDD is dying?

The best thing would be to use the tools Seagate has to test the drive. It may still have errors to the point that it has to be replaced. Depending on the age, it may still be under warranty.

 

[funboyfun23]

You have obviously upgraded the CPU and GPU several times, but you are using a 200GB HDD ? That drive is probably 10 years old. It is probably hurting your performance significantly. Toss it and get an SSD.

Sorry I think I typed down the wrong thing for the drive. My hard drive is a 2 TB seagate 7200rpm HDD. I ran CHKDSK multiple times and it always has to repair something, do you think the HDD is dying?

The best thing would be to use the tools Seagate has to test the drive. It may still have errors to the point that it has to be replaced. Depending on the age, it may still be under warranty.

I downloaded the Seagate tools and ran it over night. It got too 10%, then it said it failed.

 

[kanewolf]

Sounds like a dead/dying drive. Backup what you can and get a new one... There is really no alternatives.

 

[funboyfun23]

Sounds like a dead/dying drive. Backup what you can and get a new one... There is really no alternatives.

Okay thanks, I just wanted to make sure buying a new drive was the right course of action. Ordered a new one today and should be here soon. Thanks again!