Solved Error 0x80070570 is my drive kaput?

Hello

I have been getting the named error when trying to transfer files from certain locations on an usb spinning rust drive i have

Is the drive physically damaged? Is their any utility i can use to scan and avoid the damaged areas? Will the scanning take less than a week? Its a 4T drive.

0x80070570 = ERROR_FILE_CORRUPT The file or directory is corrupted and unreadable.

Run several tests overnight and the next day:

Sea Tools Windows Long Generic test


HD Tune Full Error scan


If the above pass then run chkdsk /b /v

0x80070570 (WIN32: 1392 ERROR_FILE_CORRUPT) -- 2147943792 (-2147023504)
Error message text: The file or directory is corrupted and unreadable.

Windows scan fixed the corrupt, undeletable, files, i was then able to delete them.

Lets see if anything else gets corrupted.
SMART looks ok.
Seatools scan was trending towards a total 12 hours of scanning but the drive entered stand by about 2/3 of the way and the scan failed. Don't know that i can do something about the drive going into stand by

Sea Tools and HD Tune Long Generic tests can run during regular computer use and they can run simultaneously.

For drives likely to have problems it's best to test the drive using Sea Tools bootable.

Sounds like a drive failure!

But it's recommended to also test the RAM, for DDR4 with >16 GB installed.
I'm wondering if there's a widespread DDR4 problem, where having more than 16 GB installed, makes it unstable. It may take months for it to become unstable, and if that's the case, then it looks like a problem with faulty RAM.

This may be because of unknowingly there being faulty batches of DDR4 that may have disproportionately affected RAM modules with more than 8 GB each.

As back during last May, I gained stability again with just 16 GB of DDR4. But, I have fresh 32 GB now, and it looks solid!
Note, that this may be a CPU RAM controller fault, if the RAM test fails.

My Ryzen 7 5800X, possibly has a faulty RAM controller. I took it out on Christmas, 2023, when I got my Ryzen 9 5900X.
Because I don't have time for that bull, on my daily driver!

I don't see signs of that at this time with my Ryzen 9 5900X.

Well if the drive is faulty I would avoid the chkdsk command. In the past I have lost some files when I attempted to fix a faulty drive with the chkdsk format. I would copy-paste as many files as I can to another drive. I would even use a data recovery utility to recover more files. There are data recovery utilities that group the results in documents, music, videos etc. This helps if you want to recover certain category files. I prefer data recovery utilities that show the drive structure (folders, subfolders and files), so I can navigate and save files from specific locations. One of these is Get Data Back.

I have some food for thought on this. MY experience with 80070570 always involves copying music files to a USB thumb drive and it always blames the source file but that is NEVER the cause.

No matter what the source, this error will eventually appears if I drag n drop a lot of files or directories. At other times I will go into the target device and find many of the target directories are empty, even though the copy process ended without any errors.

Another post I ran across implied the target Thumb Drives were not authentic [brand name?]. I'd buy that except I've had it fail on multiple drives over the years. I have yet to have a USB Hard Drive target exhibit these behaviors.