CHKDSK damages Partition Table

AndyTampa · Nov 5, 2012

Every time CHKDSK runs, Windows fails to start. I have to boot up to the recovery window and do a startup repair. I've had plenty of issues that I've already resolved, but these little things won't go away. CHKDSK always finds the same things and never fixes them either; deleting the same index files and recovering files it just deleted.

Any ideas on what could be causing this?

NoelDP · Nov 6, 2012

This sounds like you have some major issues -

I'd start with an SFC scan...

SFC -System File Checker - Instructions
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.
At the Command prompt, type
SFC /SCANNOW
and hit the Enter key

Wait for the scan to finish - make a note of any error messages - and then reboot.
Copy the CBS.log file created to your desktop (you can't manipulate it directly) and then compress the copy and upload it to your SkyDrive (http://skydrive.live.com ) and post a link to it so that I can take a look.

MilesAhead · Nov 6, 2012

Might be time to run a diagnostic on the HD before it dies altogether.

AndyTampa · Nov 13, 2012

The last time I posted to get help, I included all of the details. It was too much to read so most people just ignored the post.

The drive already died before I posted this. It was the circuit board. It has been repaired and the drive is running again, though it has some logic disruption which is what I'm trying to fix now.

SFC always reports the same files are damaged and it cannot fix them. Nobody really knows how to fix them either. Canot repair member files WINSPOOL.DRV.MUI, VBSCRIPT.DLL, and RSWOP.ICM. Source file in store is also corrupted. While I can find two of the files on an install disk, nobody knows where to put them. Everything appears to be working fine, but these files keep getting reported as damaged. VBSCRIPT is in 12 different places on the hard disk and all modified on different dates and times.

I'm trying to repair the file system before I do a backup image, but every run of CHKDSK fines and repairs file, then Windows won't start. I do a start-up repair and it says it repaired the partition table.

NoelDP · Nov 13, 2012

Please post your full CBS.log file - we CAN fix most problems!

AndyTampa · Nov 13, 2012

I've attached the full CBS.log file. The original file was 7MB which is too large to upload here so I deleted the log file, ran SFC, and then uploaded the new full log file as requested.

However, this is contradictory to what Brink said in another thread. I had posted in the thread "Extract Files From Vista Installation DVD" that SFC kept showing the same problem files and didn't fix them. He said to sort out the CHKDSK problem first.

NoelDP · Nov 14, 2012

If CHKDSK is contiually finding broken files, then something is creating them - and that can mean either bad hardware, or bad software.
So long as there's no physical damage to the disk (i.e. no bad sectors) then we have to look at other things.

Code:

 Line 1932: 2012-11-13 17:56:44, Info                  CSI    00000210 [SR] Repairing 3 components
 Line 1933: 2012-11-13 17:56:44, Info                  CSI    00000211 [SR] Beginning Verify and Repair transaction
 Line 1936: 2012-11-13 17:56:44, Info                  CSI    00000213 [SR] Cannot repair member file [l:32{16}]"winspool.drv.mui" of Microsoft-Windows-Printing-Spooler-Client.Resources, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 1939: 2012-11-13 17:56:44, Info                  CSI    00000215 [SR] Cannot repair member file [l:24{12}]"vbscript.dll" of Microsoft-Windows-Scripting-VBScript, Version = 9.1.8112.16450, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 1942: 2012-11-13 17:56:44, Info                  CSI    00000217 [SR] Cannot repair member file [l:18{9}]"RSWOP.icm" of Microsoft-Windows-WindowsCodecExt, Version = 7.0.6002.18107, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 1945: 2012-11-13 17:56:44, Info                  CSI    00000219 [SR] Cannot repair member file [l:24{12}]"vbscript.dll" of Microsoft-Windows-Scripting-VBScript, Version = 9.1.8112.16450, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 1946: 2012-11-13 17:56:44, Info                  CSI    0000021a [SR] This component was referenced by [l:150{75}]"Package_1_for_KB2744842~31bf3856ad364e35~x86~~9.1.1.0.2744842-2_neutral_GDR"
 Line 1951: 2012-11-13 17:56:44, Info                  CSI    0000021d [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\WINDOWS\System32"\[l:24{12}]"vbscript.dll"; source file in store is also corrupted
 Line 1954: 2012-11-13 17:56:44, Info                  CSI    0000021f [SR] Cannot repair member file [l:32{16}]"winspool.drv.mui" of Microsoft-Windows-Printing-Spooler-Client.Resources, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 1955: 2012-11-13 17:56:44, Info                  CSI    00000220 [SR] This component was referenced by [l:164{82}]"Package_44_for_KB936330~31bf3856ad364e35~x86~en-US~6.0.1.18000.936330-60_en-us_GDR"
 Line 1960: 2012-11-13 17:56:44, Info                  CSI    00000223 [SR] Could not reproject corrupted file [ml:520{260},l:58{29}]"\??\C:\WINDOWS\System32\en-US"\[l:32{16}]"winspool.drv.mui"; source file in store is also corrupted
 Line 1963: 2012-11-13 17:56:44, Info                  CSI    00000225 [SR] Cannot repair member file [l:18{9}]"RSWOP.icm" of Microsoft-Windows-WindowsCodecExt, Version = 7.0.6002.18107, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 1964: 2012-11-13 17:56:44, Info                  CSI    00000226 [SR] This component was referenced by [l:160{80}]"Microsoft-Windows-DGT-Package~31bf3856ad364e35~x86~~7.0.6002.18107.WindowsCodecs"
 Line 1969: 2012-11-13 17:56:44, Info                  CSI    00000229 [SR] Could not reproject corrupted file [ml:520{260},l:86{43}]"\??\C:\WINDOWS\System32\spool\drivers\color"\[l:18{9}]"RSWOP.icm"; source file in store is also corrupted
 Line 1974: 2012-11-13 17:56:44, Info                  CSI    0000022b [SR] Repair complete

are the relevant error messages from the log - and one at least could be the cause of the problems in CHKDSK, since it's the VBScript dll which is required for all vbscripting, and which is loaded at boot.

I'll work up a repair at some stage today, and we'll see what happens.

NoelDP · Nov 14, 2012

I've uploaded a file - andyt.zip - to my SkyDrive at https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21526
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
This should create a folder C:\rewdi
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\andyt
hit the enter key - if you get a 'Not Found' error try
DIR D:\andyt
or
DIR E:\andyt

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...
XCOPY <drive>:\andyt <drive>:\windows\winsxs /y /i /s /v /h
run the command (it should take almost no time)and when the prompt return, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your SkyDrive Public folder, and post a new link
Also run a new MGADiag report, and post the result.

Cytherian · Nov 15, 2012

Hard drives do not cost a lot, relatively speaking, but repairing one would likely cost more than a new drive. I take it you have some valuable data that wasn't backed up anywhere else and so you had to go for a repair.

If I were you, I'd get a new hard drive and then attach this old one as a slave to copy off needed data. After that, get rid of it as it seems to be unreliable. Where computers are concerned, data is the most valuable thing above all else. Unless you're employing the hard drive in a secondary system and it's being used for incidental data that you don't mind losing, I'd get rid of it ASAP if all the repair tips given don't get rid of all the issues you are having with it.

NoelDP · Nov 15, 2012

Nobody has yet determined the physical state of the HD (mea culpa!) - but the errors in the CBS log look more liely to me to be a software problem (malware, etc) than a failing drive.

@andyt

Please check the CHKDSK log in Event Viewer - it in the Windows logs/Application as a Wininit event.
If there are ANY bad sectors reported, then the hard drive is at risk of failure.

AndyTampa · Nov 18, 2012

NoelDP,

1) The folder created was c:\andyt.
2) The tasks you have given me are irreversible since it will be overwriting files. Should I create a restore point or make a backup using AShampoo? I don't quite remember how to use Ashampoo, but it was easy enough the last time I used it, although it took quite a while.
3) I tried to make backup "old" copies of the files, but I can't unless I take ownership of the folders
4) Will this work even though I haven't taken ownership?
5) I don't have a skydrive account, but I can upload the log as I did earlier. Shall I also limit it to the [SR] lines as you have done? Although I've forgotten a little, I started out with DOS.

Cytherian,

The drive already died when the circuit board fried. While that was slowly dieing out, I had all kinds of errors. During chkdsk processes, the board would momentarily disappear from the BIOS and Windows. When that happened it would start marking every sector bad. I had 31 Gb of chkdsk logs. As I had stated, I'm trying to repair Windows so that I can make an image. I will be transferring that image to a new, larger drive. I won't know the condition of this hard disk until I can reformat it and run chkdsk on it as a blank disk.

NoelDP · Nov 18, 2012

AndyTampa said:
NoelDP,

1) The folder created was c:\andyt..

Good

.

2) The tasks you have given me are irreversible since it will be overwriting files. Should I create a restore point or make a backup using AShampoo? I don't quite remember how to use Ashampoo, but it was easy enough the last time I used it, although it took quite a while..

There's not point in creating a System Restore point - it doesn't operate in Recovery Environment. All we are doing is correcting one file, so a full backup is unnecessary.
.

3) I tried to make backup "old" copies of the files, but I can't unless I take ownership of the folders.

...which is the reason we have to operate in the RE.
You can copy the folder using 'Send to... > Compressed (zipped) file'
.

4) Will this work even though I haven't taken ownership?.

.

Yes.
5) I don't have a skydrive account, but I can upload the log as I did earlier. Shall I also limit it to the [SR] lines as you have done? Although I've forgotten a little, I started out with DOS..

No - please post the full CBS log.
Upload it wherever you like so long as I have access

Cytherian,

The drive already died when the circuit board fried. While that was slowly dieing out, I had all kinds of errors. During chkdsk processes, the board would momentarily disappear from the BIOS and Windows. When that happened it would start marking every sector bad. I had 31 Gb of chkdsk logs. As I had stated, I'm trying to repair Windows so that I can make an image. I will be transferring that image to a new, larger drive. I won't know the condition of this hard disk until I can reformat it and run chkdsk on it as a blank disk.

Not so - you can check is using the hard disk manufacturer's Test utulity - download it from their site, and create the boot media then boot to that and run the utility.

AndyTampa · Nov 19, 2012

NoelDP,

I did what you asked. When I got to the Advanced Boot Menu, "Repair my Computer" was not an option. I could have booted into Safe Mode with command prompt, but I didn't know if that would suffice, so I started with a borrowed Vista CD. Then I was given the option to "Repair my Computer". All other tasks performed as expected.

I rebooted per your instructions and Windows would not load. Instead it booted into the Vista CD and did not see a Windows Installation when it was up and running. I did a startup repair and the details show that it didn't find a valid System Partition. It repaired it. Now I'm back in Vista. Attached is the CBS.log file. It appears that the only file still found to be damaged was the winspool.drv.mui, but SFC thinks it repaired it. After this post, I will run SFC again to see if it is still found to be damaged.

I've also attached the WININIT event details for 11/4/12 when I last ran CHKDSK.

AndyTampa · Nov 19, 2012

I just re-ran SFC and it did not find any corrupted files. Then on the reboot, it worked as it should. I will run CHKDSK again now to see if it's still damaging the Partition Table.

AndyTampa · Nov 19, 2012

I ran CHKDSK again. It took a couple of hours to run and found all the same indexes and orphaned files. This time though, a reboot worked as it should. Why is it still finding all the same files without fixing them? The command I used was CHKDSK /f /r /b. I've attached the details from the WININIT event log.

NoelDP · Nov 20, 2012

Please use teh following command for CHKDSK

CHKDSK C: /R

(the /F and /B are superfluous - and I think that /B actually restricts the scan to repairing bad sectors only!)

AndyTampa · Nov 20, 2012

NoelDP said:
Please use teh following command for CHKDSK

CHKDSK C: /R

(the /F and /B are superfluous - and I think that /B actually restricts the scan to repairing bad sectors only!)

I can't run chkdsk at the moment because I'm working from home on this computer. I had figured the /F and /R would be superfluous but I added them anyway. I based this reasoning on the following entries from the CHKDSK command help:

/F - Fixes errors on the disk.
/R - Locates bad sectors and recovers readable information (implies /F).
/B - NTFS only: Re-evaluates bad clusters on the volume (implies /R).

If /B implies /R and /R implies /F, then wouldn't /B imply both? Prior to posting here I had been using CHKDSK /F /R and the results were the same then as they are now. It's always the same index entries and orphaned files that are found. I can still run the command tonight after work and let it run while I'm at my meeting if you think it will make a difference.

NoelDP · Nov 20, 2012

I think it's a case of /B running a subset of the available dataspace (I've had problems with it myself at times) - but running the /R on its own will tell - it will almost certainly overflow the Eventlog buffer, and will need to be run twice anyhow to see if there is a difference in behaviour.

(thinking about it - the second time, you can just run a simple /F)

AndyTampa · Nov 25, 2012

Sorry it took so long to respond. Thanksgiving has been playing with my schedule.

I ran CHKDSK C: /R, then ran CHKDSK C: /F. Attached is the latest event log.

Nothing has changed except that the partition table did not get damaged this time. The computer rebooted normally.

NoelDP · Nov 25, 2012

There's something odd there, obviously.
Please Please run another SFC /SCANNOW, and post the updated log.
Please also run CheckSUR -
Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Method 2)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and attach the logs to your reply.

CHKDSK damages Partition Table

My Computer

Three-Toed Sloth

My Computer

Eclectician

My Computer

My Computer

Three-Toed Sloth

My Computer

My Computer

Three-Toed Sloth

My Computer

Three-Toed Sloth

My Computer

My Computer

Three-Toed Sloth

My Computer

My Computer

Three-Toed Sloth

My Computer

My Computer

My Computer

My Computer

Three-Toed Sloth

My Computer

My Computer

Three-Toed Sloth

My Computer

My Computer

Three-Toed Sloth

My Computer