Error 0X80070571 - D: Partition Corrupted

[Terry Smerling]

I keep posting this problem as I continue to seek an elusive solution. My
D: drive (the second, logical partition of my hard drive) keeps getting
corrupted. The symptoms are many and include: an inability to copy or
download files to the drive and an inability to unzip files already located
on the drive. The only solution I have found is to offline defrag the
drive, which as I understand works on system files. The drive then operates
for a while until it again becomes corrupted. I ran Western Digitals hard
drive diagnostics program, and the drive checks out fine. I also ran two
memory diagnostics (MS's memory checking tool and Memtest86), and memory
likewise checked out fine.

The new wrinkle is that the error message I receive when the drive becomes
corrupted is 0X80070571. I Googled this error message, which others have
posted, but no one seems to have a real solution.

I am wondering this: since an offline defrag is the only thing that "fixes"
the problem and since my system files reside on my C: primary partition,
could virtual memory, located on the D: drive be the culprit? What other
system files would sit on the D: drive or affect the D: drive. As I
understand it, virtual memory should not be located on the C; drive.

Does anyone out there have any thoughts or suggestions?

 

[Colin Barnhorst]

I keep posting this problem as I continue to seek an elusive solution. My
D: drive (the second, logical partition of my hard drive) keeps getting
corrupted. The symptoms are many and include: an inability to copy or
download files to the drive and an inability to unzip files already located
on the drive. The only solution I have found is to offline defrag the
drive, which as I understand works on system files. The drive then
operates for a while until it again becomes corrupted. I ran Western
Digitals hard drive diagnostics program, and the drive checks out fine. I
also ran two memory diagnostics (MS's memory checking tool and Memtest86),
and memory likewise checked out fine.

The new wrinkle is that the error message I receive when the drive becomes
corrupted is 0X80070571. I Googled this error message, which others have
posted, but no one seems to have a real solution.

I am wondering this: since an offline defrag is the only thing that
"fixes" the problem and since my system files reside on my C: primary
partition, could virtual memory, located on the D: drive be the culprit?
What other system files would sit on the D: drive or affect the D: drive.
As I understand it, virtual memory should not be located on the C; drive.

Does anyone out there have any thoughts or suggestions?

The cabling may be the culprit. You do not say what controller it is
attached to, SATA, IDE, or other. Try a different cable.

 

[Mark H]

No matter how many times you've posted, if we don't know some of the
rudimentary information, new help cannot be forth coming. We haven't all
been following along.

0. What version of windows are you running?
1. Is D: drive your recovery drive? (Is this an OEM system with a recovery
partition?)
2. Is the pagefile.sys setup to work on d: drive?
3. Is System Restore turned on for d: drive?
4. Is this a dual boot machine?
5. Is the error provided in a small window with other text, or a BSOD?
If a BSOD, what is the stop code provided?
6. Have you looked in error reporting logs for more details?

An offline "only" defrag implies the drive, or files are locked. Locked
means that drive d: is setup as a primary drive, or there are files on it
that are protected from change by windows. Some of the questions above would
cause this condition.

7. Have you run an offline CHKDSK /f scan to repair bad spots on the drive?


The error number you have posted normally applies to a CD/DVD drive and is
presented when the media is corrupt. (e.g. cannot burn to scratched disk)
http://www.computerperformance.co.uk/Logon/code/index.htm

Looking at your other posts, you declare:
"My system files in Vista Home Premium keep getting corrupt"
8. Are you stating your system files are on drive d:, but your primary
partition is drive c:?
That is usually a bad mixture, but not necessarily your problem.

Also based on your other posts, the error messages, context menu problems,
and host of other issues are probably a symptom and not really the problem.
You indicate your secondary drive has no issues with the same functions.

I suspect:
1. Your primary drive (c has failed, but manages to pass the WD diagnostic
tool test.

a. Get a new HDD, re-install windows.
b. Or, take it to a tech for analysis.

The problem does not sound software related.