Hard drive CHKDSK errors since day 1

Topic

New Reply

I have a 320G hard drive in a Dell Inspiron 1710 laptop, that has always had CHKDSK errors since Day 1, almost 3.5 years ago!!
DISK: WDC 320G WD3200BEVT-75ZCT0
PC: Dell Inspiron 1710, running VISTA SP1 (and this error is preventing me from going to SP2 )

Over the years, I have gone round/round with DELL, who basically says “Not our problem”.

Event manager never shows an error.

DISK HEALTH check utilities never show an error.

Each time I run CHKDSK, I get this for results:

Microsoft Windows [Version 6.0.6000]Copyright (c) 2006 Microsoft Corporation. All rights reserved.X:Windowssystem32>chkdsk c: /fThe type of the file system is NTFS.Volume label is OS.CHKDSK is verifying files (stage 1 of 3)… 249728 file records processed.File verification completed. 978 large file records processed. 0 bad file records processed. 0 EA records processed. 73 reparse records processed.CHKDSK is verifying indexes (stage 2 of 3)…39 percent complete. (515718 of 938763 index entries processed)Deleting index entry msador15.dll in index $I30 of file 130.Deleting index entry msjro.dll in index $I30 of file 130.Deleting index entry adcvbs.inc in index $I30 of file 133.Deleting index entry msadce.dll in index $I30 of file 133.Deleting index entry msadcfr.dll in index $I30 of file 133.Deleting index entry msadcor.dll in index $I30 of file 133.Deleting index entry msadcs.dll in index $I30 of file 133.Deleting index entry msadds.dll in index $I30 of file 133.Deleting index entry msdaprst.dll in index $I30 of file 133.Deleting index entry msdaremr.dll in index $I30 of file 133. 938763 index entries processed.Index verification completed.CHKDSK is recovering lost files.63 percent complete. (1 of 14 unindexed files processed)Recovering orphaned file msador15.dll (7230) into directory file 130.Recovering orphaned file adcvbs.inc (7237) into directory file 133.Recovering orphaned file msadcfr.dll (7243) into directory file 133.Recovering orphaned file msadcor.dll (7245) into directory file 133.Recovering orphaned file msdaremr.dll (7252) into directory file 133.Recovering orphaned file msadcs.dll (126174) into directory file 133.Recovering orphaned file msadds.dll (135399) into directory file 133.Recovering orphaned file msjro.dll (137219) into directory file 130.Recovering orphaned file msdaprst.dll (138566) into directory file 133.Recovering orphaned file msadce.dll (180142) into directory file 133. 15 unindexed files processed.CHKDSK is verifying security descriptors (stage 3 of 3)… 249728 security descriptors processed.Security descriptor verification completed. 34740 data files processed.CHKDSK is verifying Usn Journal… 37613544 USN bytes processed.Usn Journal verification completed.Windows has made corrections to the file system. 299373560 KB total disk space. 109167964 KB in 197288 files. 132796 KB in 34741 indexes. 0 KB in bad sectors. 377384 KB in use by the system. 65536 KB occupied by the log file. 189695416 KB available on disk. 4096 bytes in each allocation unit. 74843390 total allocation units on disk. 47423854 allocation units available on disk.I have tried restoring from the ‘SYSTEM IMAGE’ (aka Factory Image) and I get the same results!
I have tried an DUMP / RESTORE with ACRONIS and I get the same results.

I am to the point where I am thinking of replacing the hard drive and restoring.

A) Will restore have the same problem?
B) Anyone have other ideas?
– I have toyed with running SPINRITE, but I have seen mixed results in GOOGLE searches
C) Any other ideas?

THANKS !!!

Reply | Quote

Replies

I have a 320G hard drive in a Dell Inspiron 1710 laptop, that has always had CHKDSK errors since Day 1, almost 3.5 years ago!! DISK: WDC 320G WD3200BEVT-75ZCT0 PC: Dell Inspiron 1710, running VISTA SP1 (and this error is preventing me from going to SP2 ) Over the years, I have gone round/round with DELL, who basically says “Not our problem”. Event manager never shows an error. DISK HEALTH check utilities never show an error. Each time I run CHKDSK, I get this for results: Microsoft Windows [Version 6.0.6000]Copyright (c) 2006 Microsoft Corporation. All rights reserved.X:Windowssystem32>chkdsk c: /fThe type of the file system is NTFS.Volume label is OS.CHKDSK is verifying files (stage 1 of 3)… 249728 file records processed.File verification completed. 978 large file records processed. 0 bad file records processed. 0 EA records processed. 73 reparse records processed.CHKDSK is verifying indexes (stage 2 of 3)…39 percent complete. (515718 of 938763 index entries processed)Deleting index entry msador15.dll in index $I30 of file 130.Deleting index entry msjro.dll in index $I30 of file 130.Deleting index entry adcvbs.inc in index $I30 of file 133.Deleting index entry msadce.dll in index $I30 of file 133.Deleting index entry msadcfr.dll in index $I30 of file 133.Deleting index entry msadcor.dll in index $I30 of file 133.Deleting index entry msadcs.dll in index $I30 of file 133.Deleting index entry msadds.dll in index $I30 of file 133.Deleting index entry msdaprst.dll in index $I30 of file 133.Deleting index entry msdaremr.dll in index $I30 of file 133. 938763 index entries processed.Index verification completed.CHKDSK is recovering lost files.63 percent complete. (1 of 14 unindexed files processed)Recovering orphaned file msador15.dll (7230) into directory file 130.Recovering orphaned file adcvbs.inc (7237) into directory file 133.Recovering orphaned file msadcfr.dll (7243) into directory file 133.Recovering orphaned file msadcor.dll (7245) into directory file 133.Recovering orphaned file msdaremr.dll (7252) into directory file 133.Recovering orphaned file msadcs.dll (126174) into directory file 133.Recovering orphaned file msadds.dll (135399) into directory file 133.Recovering orphaned file msjro.dll (137219) into directory file 130.Recovering orphaned file msdaprst.dll (138566) into directory file 133.Recovering orphaned file msadce.dll (180142) into directory file 133. 15 unindexed files processed.CHKDSK is verifying security descriptors (stage 3 of 3)… 249728 security descriptors processed.Security descriptor verification completed. 34740 data files processed.CHKDSK is verifying Usn Journal… 37613544 USN bytes processed.Usn Journal verification completed.Windows has made corrections to the file system. 299373560 KB total disk space. 109167964 KB in 197288 files. 132796 KB in 34741 indexes. 0 KB in bad sectors. 377384 KB in use by the system. 65536 KB occupied by the log file. 189695416 KB available on disk. 4096 bytes in each allocation unit. 74843390 total allocation units on disk. 47423854 allocation units available on disk.I have tried restoring from the ‘SYSTEM IMAGE’ (aka Factory Image) and I get the same results! I have tried an DUMP / RESTORE with ACRONIS and I get the same results. I am to the point where I am thinking of replacing the hard drive and restoring. A) Will restore have the same problem? B) Anyone have other ideas? – I have toyed with running SPINRITE, but I have seen mixed results in GOOGLE searches C) Any other ideas? THANKS !!!

Follow this link to Western Digital support and download/install “Data Lifeguard Diagnostics for Windows” This should give you an idea of whether or not your hard drive is faulty. Let us know what happens. Clicky: http://wdc.custhelp.com/app/answers/detail/search/1/a_id/940/c/130/p/227,194 Insure you carefully read the instructions before choosing an option-You do not want to choose “Write Zero’s” as an option as that will wipe your hard drive clean of all your data.

Reply | Quote

THANKS!

Does anyone know if the test options other that “Write Zeros” are destructive to drive contents?

The reason I ask is a line on the referenced pages says ”
[TABLE]
[TR]
[TD]Important: If any of the tests fail, including the Quick Test, you will need to replace the drive being tested. ”
Does that mean that the utility marks the drive unusable or what?

[/TD]
[/TR]
[/TABLE]
[/FONT][/COLOR]

Reply | Quote

Any test that writes is destructive. You should be able to do most tests without writing.
SMART data should give you a good indication of potential problems.

Check Disk reports logical errors which can be caused by turning the machine off mid-write. You may also have a controller problem, not a disk issue.

cheers, Paul

Reply | Quote

Try the tests I have outlined in yellow in the snippet. The quick test and the extended test will not harm your hard drive. They will tell you if your hard drive is still serviceable. I provided the link to Western digitals support section because you stated in your first post that you were thinking of replacing your hard drive. This software will help you to determine if that is necessary. If your hard drive checks out then you know you are looking for a different cause and check out your controller as Paul T has suggested. This way you know for sure that your hard drive is “Good to Go!

Reply | Quote

Dell will always say it’s not their problem until after you bought the machine. :rolleyes:

Whoa that’s a lot of files, If you use a one to one sector backup it’s probable that you get introduced image errors; Acronis should have raised an exception while reading the drive, did you try just using backup with files only?

I have used Spin Rite once, and after 16 hours all my data was intact and backed up. Two weeks later the drive died.

Have you seen severe longer delays while file transactions take place (without VM swapping), that usually happens with free space marked as used in the MFT bitmap table. I don’t see that here.

Some years ago before XP’s SP2 was release there was an NTFS.SYS update for fix such types of corruption.

Vista NTFS driver hotfix link, http://support.microsoft.com/kb/957065
an other http://support.microsoft.com/kb/976538

Is the drive firmware defective ?

Is Dell’s factory image defective ?

Does your computer ever shutdown correctly?

Is CHKDSK defective?

Reply | Quote

Hi There xzr1tv I was just wondering if you ran the test at Western Digitals support site. I would run it and if the drive is indicated as good then I would back up all my important data and do a clean re-install of the operating system. Have you recently or have you ever done a clean re-install? We are here to help Cheers, ranger72

Reply | Quote