CHKDSK runs and (terminates abnormally) every time I start Vista.

[Guest]

--Problem:
I have read of others having the same problem but I have never seen any post
that actually solves the problem (apart from reformatting the partition) so I
will try to describe the problem the best I can in hope of anyone coming up
with a fix or an idea.
Every time I boot Vista (Vista Ultimate 32bit) CHKDSK runs automatically but
it never finishes successfully. It always terminates when it has done 25% of
step 2. Step 1 is only done by 9% and then it proceeds with step 2 without
any message. After the 25% of step 2 it just terminates without any feedback
(good or bad). At that point Vista continues to boot and does so successfully
but CHKDSK will always be executed the next time I boot Vista.

--What I have done so far when trying to solve the problem:
1. Executing “fsutil dirty query c:†reports that the volume is dirty so
there is no surprise that CHKDSK runs when I boot but, since CHKDSK never
finishes successfully, the dirty bit is never cleared resulting in this
situation.
2. The hard disk manufacture provides a low level testing/diagnostic tool
and that report that the disk is working perfectly.
3. By booting Vista from the DVD, and going into repair mode, I have tried
to run CHKDSK from the command window. I tried any permutation of arguments
that made sense with slightly different results. The results are as follows:
Regardless of the arguments step 1 always ends at 9% (no feedback it just
ends).
If I specify /f step 2 terminates after 25% unless I also specify /I.
If I specify /I step 2 terminates after 46%.
If I specify /R step 2 terminates after 10%.
In the vast majority of cases (regardless of arguments) CHKDSK just
terminates (during step 2) without giving any sort of feedback but, once in a
while, it does terminate and report that “An unspecified error occurredâ€.
4. I have (in desperation) run diagnostics tools that check the ram memory
(primary memory 3GB) and there was no problem.

--The situation as I see it:
This has to be a bug in CHKDSK.
Obviously I understand that there might be situations that CHKDSK can’t
resolve but then it should report exactly that. Not just terminate as it does
now.
Accepted results would be one of the following reports.
1. There was no problem with the disk.
2. There were problems and they are fixed.
3. There were problems and they could NOT be fixed but that is reported.

--Questions:
Does anybody know is this is a known bug and if Microsoft has a solution?
Does anybody know of a way of fixing this problem?

--My system:
OS: Microsoft Vista Ultimate (32bit)
Motherboard: Asus P5B-Plus Vista Edition
CPU: Intel Core 2 Duo E6420 2.13GHz
Disk: Samsung SpinPoint T166 250GB SATA2 16MB 7200RPM
RAM: 2*1024 + 2*512 Crucial DDR2 PC6400 CL5
Vista was installed on a new (empty) disk 2-3 month ago.
Vista is up to date (Windows Update has nothing to add)

--Final thing:
If I had a back up of the system I could have restored that but I don’t :-(
I would be very happy if someone had any ideas that could help me.

/Regards

 

[Jon]

--Problem:
I have read of others having the same problem but I have never seen any
post
that actually solves the problem (apart from reformatting the partition)
so I
will try to describe the problem the best I can in hope of anyone coming
up
with a fix or an idea.
Every time I boot Vista (Vista Ultimate 32bit) CHKDSK runs automatically
but
it never finishes successfully. It always terminates when it has done 25%
of
step 2. Step 1 is only done by 9% and then it proceeds with step 2 without
any message. After the 25% of step 2 it just terminates without any
feedback
(good or bad). At that point Vista continues to boot and does so
successfully
but CHKDSK will always be executed the next time I boot Vista.

--What I have done so far when trying to solve the problem:
1. Executing “fsutil dirty query c:†reports that the volume is dirty so
there is no surprise that CHKDSK runs when I boot but, since CHKDSK never
finishes successfully, the dirty bit is never cleared resulting in this
situation.
2. The hard disk manufacture provides a low level testing/diagnostic tool
and that report that the disk is working perfectly.
3. By booting Vista from the DVD, and going into repair mode, I have tried
to run CHKDSK from the command window. I tried any permutation of
arguments
that made sense with slightly different results. The results are as
follows:
Regardless of the arguments step 1 always ends at 9% (no feedback it just
ends).
If I specify /f step 2 terminates after 25% unless I also specify /I.
If I specify /I step 2 terminates after 46%.
If I specify /R step 2 terminates after 10%.
In the vast majority of cases (regardless of arguments) CHKDSK just
terminates (during step 2) without giving any sort of feedback but, once
in a
while, it does terminate and report that “An unspecified error occurredâ€.
4. I have (in desperation) run diagnostics tools that check the ram memory
(primary memory 3GB) and there was no problem.

--The situation as I see it:
This has to be a bug in CHKDSK.
Obviously I understand that there might be situations that CHKDSK can’t
resolve but then it should report exactly that. Not just terminate as it
does
now.
Accepted results would be one of the following reports.
1. There was no problem with the disk.
2. There were problems and they are fixed.
3. There were problems and they could NOT be fixed but that is reported.

--Questions:
Does anybody know is this is a known bug and if Microsoft has a solution?
Does anybody know of a way of fixing this problem?

--My system:
OS: Microsoft Vista Ultimate (32bit)
Motherboard: Asus P5B-Plus Vista Edition
CPU: Intel Core 2 Duo E6420 2.13GHz
Disk: Samsung SpinPoint T166 250GB SATA2 16MB 7200RPM
RAM: 2*1024 + 2*512 Crucial DDR2 PC6400 CL5
Vista was installed on a new (empty) disk 2-3 month ago.
Vista is up to date (Windows Update has nothing to add)

--Final thing:
If I had a back up of the system I could have restored that but I don’t
:-(
I would be very happy if someone had any ideas that could help me.

/Regards

Try running it from an elevated command prompt from within Vista, with the
verbose option set, and without actually fixing anything. The information it
provides may be of more use in understanding what is happening, and why it
is failing ....

chkdsk /v c:

or to save the output to file for examination......

chkdsk /v c: > %userprofile%\Desktop\chkdsk_output.txt

chkdsk /?

 

[Guest]

Hi Jon,
Ok I did that with the following result:
C:\Windows\system32>chkdsk /v c:
The type of the file system is NTFS.
Volume label is Local Disk 1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
105472 file records processed.
File verification completed.
108 large file records processed.
0 bad file records processed.
2 EA records processed.
93 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
25 percent complete. (76663 of 401436 index entries processed)
C:\Windows\system32>

Again step 2 terminates after 25% (as always) but I actually got an error in
a popup dialog.
I copied the dialog to the clipboard and pasted it below:
[Window Title]
Microsoft Windows

[Main Instruction]
Check Disk Utility has stopped working

[Content]
A problem caused the program to stop working correctly. Windows will close
the program and notify you if a solution is available.

[Close program]

So, something with CHKDSK seems to be wrong :-(
Any ideas?

 

[Jon]

Very odd. Not seen anything like that before.

The only other thing that I can suggest, is that if you have a dual boot,
say with XP (preferably on a completely independent partition), that you
could boot into that and run a chkdsk from there on the Vista partition -
either from the command prompt or via the right-click drive > Properties >
Tools route

If that doesn't work either, then perhaps your original conclusion was
correct - you've run into a bug in chkdsk. Either way, I'd back up any
valuable data / documents to safe locations pretty sharpish, since the disk
may well be on the blink.

--
Jon

Hi Jon,
Ok I did that with the following result:
C:\Windows\system32>chkdsk /v c:
The type of the file system is NTFS.
Volume label is Local Disk 1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
105472 file records processed.
File verification completed.
108 large file records processed.
0 bad file records processed.
2 EA records processed.
93 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
25 percent complete. (76663 of 401436 index entries processed)
C:\Windows\system32>

Again step 2 terminates after 25% (as always) but I actually got an error
in
a popup dialog.
I copied the dialog to the clipboard and pasted it below:
[Window Title]
Microsoft Windows

[Main Instruction]
Check Disk Utility has stopped working

[Content]
A problem caused the program to stop working correctly. Windows will close
the program and notify you if a solution is available.

[Close program]

So, something with CHKDSK seems to be wrong :-(
Any ideas?

Try running it from an elevated command prompt from within Vista, with
the
verbose option set, and without actually fixing anything. The information
it
provides may be of more use in understanding what is happening, and why
it
is failing ....

chkdsk /v c:

or to save the output to file for examination......

chkdsk /v c: > %userprofile%\Desktop\chkdsk_output.txt

chkdsk /?

 

[Jon]

Another thought is that since it' appears to be failing on the 'Index
entries' stage, you could also try the same command with the /i option, to
see if it progresses any further ie ....

chkdsk /v /i c:

--
Jon

Very odd. Not seen anything like that before.

The only other thing that I can suggest, is that if you have a dual boot,
say with XP (preferably on a completely independent partition), that you
could boot into that and run a chkdsk from there on the Vista partition -
either from the command prompt or via the right-click drive > Properties

Tools route

If that doesn't work either, then perhaps your original conclusion was
correct - you've run into a bug in chkdsk. Either way, I'd back up any
valuable data / documents to safe locations pretty sharpish, since the
disk may well be on the blink.

--
Jon

Hi Jon,
Ok I did that with the following result:
C:\Windows\system32>chkdsk /v c:
The type of the file system is NTFS.
Volume label is Local Disk 1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
105472 file records processed.
File verification completed.
108 large file records processed.
0 bad file records processed.
2 EA records processed.
93 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
25 percent complete. (76663 of 401436 index entries processed)
C:\Windows\system32>

Again step 2 terminates after 25% (as always) but I actually got an error
in
a popup dialog.
I copied the dialog to the clipboard and pasted it below:
[Window Title]
Microsoft Windows

[Main Instruction]
Check Disk Utility has stopped working

[Content]
A problem caused the program to stop working correctly. Windows will
close
the program and notify you if a solution is available.

[Close program]

So, something with CHKDSK seems to be wrong :-(
Any ideas?

--Problem:
I have read of others having the same problem but I have never seen
any
post
that actually solves the problem (apart from reformatting the
partition)
so I
will try to describe the problem the best I can in hope of anyone
coming
up
with a fix or an idea.
Every time I boot Vista (Vista Ultimate 32bit) CHKDSK runs
automatically
but
it never finishes successfully. It always terminates when it has done
25%
of
step 2. Step 1 is only done by 9% and then it proceeds with step 2
without
any message. After the 25% of step 2 it just terminates without any
feedback
(good or bad). At that point Vista continues to boot and does so
successfully
but CHKDSK will always be executed the next time I boot Vista.

--What I have done so far when trying to solve the problem:
1. Executing “fsutil dirty query c:†reports that the volume is dirty
so
there is no surprise that CHKDSK runs when I boot but, since CHKDSK
never
finishes successfully, the dirty bit is never cleared resulting in
this
situation.
2. The hard disk manufacture provides a low level testing/diagnostic
tool
and that report that the disk is working perfectly.
3. By booting Vista from the DVD, and going into repair mode, I have
tried
to run CHKDSK from the command window. I tried any permutation of
arguments
that made sense with slightly different results. The results are as
follows:
Regardless of the arguments step 1 always ends at 9% (no feedback it
just
ends).
If I specify /f step 2 terminates after 25% unless I also specify /I.
If I specify /I step 2 terminates after 46%.
If I specify /R step 2 terminates after 10%.
In the vast majority of cases (regardless of arguments) CHKDSK just
terminates (during step 2) without giving any sort of feedback but,
once
in a
while, it does terminate and report that “An unspecified error
occurredâ€.
4. I have (in desperation) run diagnostics tools that check the ram
memory
(primary memory 3GB) and there was no problem.

--The situation as I see it:
This has to be a bug in CHKDSK.
Obviously I understand that there might be situations that CHKDSK can’t
resolve but then it should report exactly that. Not just terminate as
it
does
now.
Accepted results would be one of the following reports.
1. There was no problem with the disk.
2. There were problems and they are fixed.
3. There were problems and they could NOT be fixed but that is
reported.

--Questions:
Does anybody know is this is a known bug and if Microsoft has a
solution?
Does anybody know of a way of fixing this problem?

--My system:
OS: Microsoft Vista Ultimate (32bit)
Motherboard: Asus P5B-Plus Vista Edition
CPU: Intel Core 2 Duo E6420 2.13GHz
Disk: Samsung SpinPoint T166 250GB SATA2 16MB 7200RPM
RAM: 2*1024 + 2*512 Crucial DDR2 PC6400 CL5
Vista was installed on a new (empty) disk 2-3 month ago.
Vista is up to date (Windows Update has nothing to add)

--Final thing:
If I had a back up of the system I could have restored that but I don’t
:-(
I would be very happy if someone had any ideas that could help me.

/Regards





Try running it from an elevated command prompt from within Vista, with
the
verbose option set, and without actually fixing anything. The
information it
provides may be of more use in understanding what is happening, and why
it
is failing ....

chkdsk /v c:

or to save the output to file for examination......

chkdsk /v c: > %userprofile%\Desktop\chkdsk_output.txt

chkdsk /?

 

[Guest]

Thank you Jon,
Actually there was some new information I got by doing as you asked:
C:\Windows\system32>chkdsk /v /i c:
The type of the file system is NTFS.
Volume label is Local Disk 1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

WARNING! I parameter specified.
Your drive may still be corrupt even after running CHKDSK.

CHKDSK is verifying files (stage 1 of 3)...
105472 file records processed.
File verification completed.
108 large file records processed.
0 bad file records processed.
2 EA records processed.
93 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
46 percent complete. (90392 of 183931 index entries processed)

Errors found. CHKDSK cannot continue in read-only mode.

So, it terminated in the same way as before but now adding the "Errors
found...." statement.
I did not get the error message in the popup this time. It was reported in
the command window.
Since it can't continue in read-only I will try booting from the Vista DVD
and run this command with /f added. But... it is getting late in my time zone
so I will do that tomorrow.
Thank you very much though for your help. I will post the results tomorrow

Another thought is that since it' appears to be failing on the 'Index
entries' stage, you could also try the same command with the /i option, to
see if it progresses any further ie ....

chkdsk /v /i c:

--
Jon

Very odd. Not seen anything like that before.

The only other thing that I can suggest, is that if you have a dual boot,
say with XP (preferably on a completely independent partition), that you
could boot into that and run a chkdsk from there on the Vista partition -
either from the command prompt or via the right-click drive > Properties

Tools route

If that doesn't work either, then perhaps your original conclusion was
correct - you've run into a bug in chkdsk. Either way, I'd back up any
valuable data / documents to safe locations pretty sharpish, since the
disk may well be on the blink.

--
Jon

Hi Jon,
Ok I did that with the following result:
C:\Windows\system32>chkdsk /v c:
The type of the file system is NTFS.
Volume label is Local Disk 1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
105472 file records processed.
File verification completed.
108 large file records processed.
0 bad file records processed.
2 EA records processed.
93 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
25 percent complete. (76663 of 401436 index entries processed)
C:\Windows\system32>

Again step 2 terminates after 25% (as always) but I actually got an error
in
a popup dialog.
I copied the dialog to the clipboard and pasted it below:
[Window Title]
Microsoft Windows

[Main Instruction]
Check Disk Utility has stopped working

[Content]
A problem caused the program to stop working correctly. Windows will
close
the program and notify you if a solution is available.

[Close program]

So, something with CHKDSK seems to be wrong :-(
Any ideas?


:

--Problem:
I have read of others having the same problem but I have never seen
any
post
that actually solves the problem (apart from reformatting the
partition)
so I
will try to describe the problem the best I can in hope of anyone
coming
up
with a fix or an idea.
Every time I boot Vista (Vista Ultimate 32bit) CHKDSK runs
automatically
but
it never finishes successfully. It always terminates when it has done
25%
of
step 2. Step 1 is only done by 9% and then it proceeds with step 2
without
any message. After the 25% of step 2 it just terminates without any
feedback
(good or bad). At that point Vista continues to boot and does so
successfully
but CHKDSK will always be executed the next time I boot Vista.

--What I have done so far when trying to solve the problem:
1. Executing “fsutil dirty query c:†reports that the volume is dirty
so
there is no surprise that CHKDSK runs when I boot but, since CHKDSK
never
finishes successfully, the dirty bit is never cleared resulting in
this
situation.
2. The hard disk manufacture provides a low level testing/diagnostic
tool
and that report that the disk is working perfectly.
3. By booting Vista from the DVD, and going into repair mode, I have
tried
to run CHKDSK from the command window. I tried any permutation of
arguments
that made sense with slightly different results. The results are as
follows:
Regardless of the arguments step 1 always ends at 9% (no feedback it
just
ends).
If I specify /f step 2 terminates after 25% unless I also specify /I.
If I specify /I step 2 terminates after 46%.
If I specify /R step 2 terminates after 10%.
In the vast majority of cases (regardless of arguments) CHKDSK just
terminates (during step 2) without giving any sort of feedback but,
once
in a
while, it does terminate and report that “An unspecified error
occurredâ€.
4. I have (in desperation) run diagnostics tools that check the ram
memory
(primary memory 3GB) and there was no problem.

--The situation as I see it:
This has to be a bug in CHKDSK.
Obviously I understand that there might be situations that CHKDSK can’t
resolve but then it should report exactly that. Not just terminate as
it
does
now.
Accepted results would be one of the following reports.
1. There was no problem with the disk.
2. There were problems and they are fixed.
3. There were problems and they could NOT be fixed but that is
reported.

--Questions:
Does anybody know is this is a known bug and if Microsoft has a
solution?
Does anybody know of a way of fixing this problem?

--My system:
OS: Microsoft Vista Ultimate (32bit)
Motherboard: Asus P5B-Plus Vista Edition
CPU: Intel Core 2 Duo E6420 2.13GHz
Disk: Samsung SpinPoint T166 250GB SATA2 16MB 7200RPM
RAM: 2*1024 + 2*512 Crucial DDR2 PC6400 CL5
Vista was installed on a new (empty) disk 2-3 month ago.
Vista is up to date (Windows Update has nothing to add)

--Final thing:
If I had a back up of the system I could have restored that but I don’t
:-(
I would be very happy if someone had any ideas that could help me.

/Regards





Try running it from an elevated command prompt from within Vista, with
the
verbose option set, and without actually fixing anything. The
information it
provides may be of more use in understanding what is happening, and why
it
is failing ....

chkdsk /v c:

or to save the output to file for examination......

chkdsk /v c: > %userprofile%\Desktop\chkdsk_output.txt

chkdsk /?

 

[Jon]

yw.. Good idea with the DVD. Sometimes switching between the various
different ways of running the chkdsk does do the trick ie you get so far
with one approach, and then another one gets further than it did previously,
until eventually they all complete successfully. Well, that's the ideal
scenario anyhow....

--
Jon

Thank you Jon,
Actually there was some new information I got by doing as you asked:
C:\Windows\system32>chkdsk /v /i c:
The type of the file system is NTFS.
Volume label is Local Disk 1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

WARNING! I parameter specified.
Your drive may still be corrupt even after running CHKDSK.

CHKDSK is verifying files (stage 1 of 3)...
105472 file records processed.
File verification completed.
108 large file records processed.
0 bad file records processed.
2 EA records processed.
93 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
46 percent complete. (90392 of 183931 index entries processed)

Errors found. CHKDSK cannot continue in read-only mode.

So, it terminated in the same way as before but now adding the "Errors
found...." statement.
I did not get the error message in the popup this time. It was reported in
the command window.
Since it can't continue in read-only I will try booting from the Vista DVD
and run this command with /f added. But... it is getting late in my time
zone
so I will do that tomorrow.
Thank you very much though for your help. I will post the results tomorrow

Another thought is that since it' appears to be failing on the 'Index
entries' stage, you could also try the same command with the /i option,
to
see if it progresses any further ie ....

chkdsk /v /i c:

--
Jon

Very odd. Not seen anything like that before.

The only other thing that I can suggest, is that if you have a dual
boot,
say with XP (preferably on a completely independent partition), that
you
could boot into that and run a chkdsk from there on the Vista
partition -
either from the command prompt or via the right-click drive >
Properties
Tools route

If that doesn't work either, then perhaps your original conclusion was
correct - you've run into a bug in chkdsk. Either way, I'd back up any
valuable data / documents to safe locations pretty sharpish, since the
disk may well be on the blink.

--
Jon


Hi Jon,
Ok I did that with the following result:
C:\Windows\system32>chkdsk /v c:
The type of the file system is NTFS.
Volume label is Local Disk 1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
105472 file records processed.
File verification completed.
108 large file records processed.
0 bad file records processed.
2 EA records processed.
93 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
25 percent complete. (76663 of 401436 index entries processed)
C:\Windows\system32>

Again step 2 terminates after 25% (as always) but I actually got an
error
in
a popup dialog.
I copied the dialog to the clipboard and pasted it below:
[Window Title]
Microsoft Windows

[Main Instruction]
Check Disk Utility has stopped working

[Content]
A problem caused the program to stop working correctly. Windows will
close
the program and notify you if a solution is available.

[Close program]

So, something with CHKDSK seems to be wrong :-(
Any ideas?


:

--Problem:
I have read of others having the same problem but I have never seen
any
post
that actually solves the problem (apart from reformatting the
partition)
so I
will try to describe the problem the best I can in hope of anyone
coming
up
with a fix or an idea.
Every time I boot Vista (Vista Ultimate 32bit) CHKDSK runs
automatically
but
it never finishes successfully. It always terminates when it has
done
25%
of
step 2. Step 1 is only done by 9% and then it proceeds with step 2
without
any message. After the 25% of step 2 it just terminates without any
feedback
(good or bad). At that point Vista continues to boot and does so
successfully
but CHKDSK will always be executed the next time I boot Vista.

--What I have done so far when trying to solve the problem:
1. Executing "fsutil dirty query c:" reports that the volume is
dirty
so
there is no surprise that CHKDSK runs when I boot but, since CHKDSK
never
finishes successfully, the dirty bit is never cleared resulting in
this
situation.
2. The hard disk manufacture provides a low level
testing/diagnostic
tool
and that report that the disk is working perfectly.
3. By booting Vista from the DVD, and going into repair mode, I
have
tried
to run CHKDSK from the command window. I tried any permutation of
arguments
that made sense with slightly different results. The results are as
follows:
Regardless of the arguments step 1 always ends at 9% (no feedback
it
just
ends).
If I specify /f step 2 terminates after 25% unless I also specify
/I.
If I specify /I step 2 terminates after 46%.
If I specify /R step 2 terminates after 10%.
In the vast majority of cases (regardless of arguments) CHKDSK just
terminates (during step 2) without giving any sort of feedback but,
once
in a
while, it does terminate and report that "An unspecified error
occurred".
4. I have (in desperation) run diagnostics tools that check the ram
memory
(primary memory 3GB) and there was no problem.

--The situation as I see it:
This has to be a bug in CHKDSK.
Obviously I understand that there might be situations that CHKDSK
can't
resolve but then it should report exactly that. Not just terminate
as
it
does
now.
Accepted results would be one of the following reports.
1. There was no problem with the disk.
2. There were problems and they are fixed.
3. There were problems and they could NOT be fixed but that is
reported.

--Questions:
Does anybody know is this is a known bug and if Microsoft has a
solution?
Does anybody know of a way of fixing this problem?

--My system:
OS: Microsoft Vista Ultimate (32bit)
Motherboard: Asus P5B-Plus Vista Edition
CPU: Intel Core 2 Duo E6420 2.13GHz
Disk: Samsung SpinPoint T166 250GB SATA2 16MB 7200RPM
RAM: 2*1024 + 2*512 Crucial DDR2 PC6400 CL5
Vista was installed on a new (empty) disk 2-3 month ago.
Vista is up to date (Windows Update has nothing to add)

--Final thing:
If I had a back up of the system I could have restored that but I
don't
:-(
I would be very happy if someone had any ideas that could help me.

/Regards





Try running it from an elevated command prompt from within Vista,
with
the
verbose option set, and without actually fixing anything. The
information it
provides may be of more use in understanding what is happening, and
why
it
is failing ....

chkdsk /v c:

or to save the output to file for examination......

chkdsk /v c: > %userprofile%\Desktop\chkdsk_output.txt

chkdsk /?

 

[Frenchy]

I was always told to run it (in XP) as:

CHKDSK /R /F

Hope you solve it

Frenchy

Hi Jon,
Ok I did that with the following result:
C:\Windows\system32>chkdsk /v c:
The type of the file system is NTFS.
Volume label is Local Disk 1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
105472 file records processed.
File verification completed.
108 large file records processed.
0 bad file records processed.
2 EA records processed.
93 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
25 percent complete. (76663 of 401436 index entries processed)
C:\Windows\system32>

Again step 2 terminates after 25% (as always) but I actually got an error
in
a popup dialog.
I copied the dialog to the clipboard and pasted it below:
[Window Title]
Microsoft Windows

[Main Instruction]
Check Disk Utility has stopped working

[Content]
A problem caused the program to stop working correctly. Windows will close
the program and notify you if a solution is available.

[Close program]

So, something with CHKDSK seems to be wrong :-(
Any ideas?

Try running it from an elevated command prompt from within Vista, with
the
verbose option set, and without actually fixing anything. The information
it
provides may be of more use in understanding what is happening, and why
it
is failing ....

chkdsk /v c:

or to save the output to file for examination......

chkdsk /v c: > %userprofile%\Desktop\chkdsk_output.txt

chkdsk /?

 

[Guest]

Unfortunately running CHKDSK after booting from the DVD did not give any new
information nor did it succeeded any more :-(
I also tried to add the /r argument as Frenchy suggested but no progress.
When looking in the Event Viewer I have some events related to the problem
(example below):
Log Name: System
Source: Ntfs
Date: 2007-08-01 12:28:11
Event ID: 55
Task Category: (2)
Level: Error
Keywords: Classic
User: N/A
Computer: Hebbe-PC
Description:
The file system structure on the disk is corrupt and unusable. Please run
the chkdsk utility on the volume Local Disk 1.

Obviously my disk is not feeling good.
Most likely the (logical) left side of my brain has to convince the
(emotional) right side of my brain that the only reasonable thing to do is to
delete this failing partition and start over…. but how fun is that on a scale
from 1 to 10? Close to 1 :-(
Anyhow, thanks for trying to help

yw.. Good idea with the DVD. Sometimes switching between the various
different ways of running the chkdsk does do the trick ie you get so far
with one approach, and then another one gets further than it did previously,
until eventually they all complete successfully. Well, that's the ideal
scenario anyhow....

--
Jon

Thank you Jon,
Actually there was some new information I got by doing as you asked:
C:\Windows\system32>chkdsk /v /i c:
The type of the file system is NTFS.
Volume label is Local Disk 1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

WARNING! I parameter specified.
Your drive may still be corrupt even after running CHKDSK.

CHKDSK is verifying files (stage 1 of 3)...
105472 file records processed.
File verification completed.
108 large file records processed.
0 bad file records processed.
2 EA records processed.
93 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
46 percent complete. (90392 of 183931 index entries processed)

Errors found. CHKDSK cannot continue in read-only mode.

So, it terminated in the same way as before but now adding the "Errors
found...." statement.
I did not get the error message in the popup this time. It was reported in
the command window.
Since it can't continue in read-only I will try booting from the Vista DVD
and run this command with /f added. But... it is getting late in my time
zone
so I will do that tomorrow.
Thank you very much though for your help. I will post the results tomorrow

Another thought is that since it' appears to be failing on the 'Index
entries' stage, you could also try the same command with the /i option,
to
see if it progresses any further ie ....

chkdsk /v /i c:

--
Jon


Very odd. Not seen anything like that before.

The only other thing that I can suggest, is that if you have a dual
boot,
say with XP (preferably on a completely independent partition), that
you
could boot into that and run a chkdsk from there on the Vista
partition -
either from the command prompt or via the right-click drive >
Properties
Tools route

If that doesn't work either, then perhaps your original conclusion was
correct - you've run into a bug in chkdsk. Either way, I'd back up any
valuable data / documents to safe locations pretty sharpish, since the
disk may well be on the blink.

--
Jon


Hi Jon,
Ok I did that with the following result:
C:\Windows\system32>chkdsk /v c:
The type of the file system is NTFS.
Volume label is Local Disk 1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
105472 file records processed.
File verification completed.
108 large file records processed.
0 bad file records processed.
2 EA records processed.
93 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
25 percent complete. (76663 of 401436 index entries processed)
C:\Windows\system32>

Again step 2 terminates after 25% (as always) but I actually got an
error
in
a popup dialog.
I copied the dialog to the clipboard and pasted it below:
[Window Title]
Microsoft Windows

[Main Instruction]
Check Disk Utility has stopped working

[Content]
A problem caused the program to stop working correctly. Windows will
close
the program and notify you if a solution is available.

[Close program]

So, something with CHKDSK seems to be wrong :-(
Any ideas?


:

--Problem:
I have read of others having the same problem but I have never seen
any
post
that actually solves the problem (apart from reformatting the
partition)
so I
will try to describe the problem the best I can in hope of anyone
coming
up
with a fix or an idea.
Every time I boot Vista (Vista Ultimate 32bit) CHKDSK runs
automatically
but
it never finishes successfully. It always terminates when it has
done
25%
of
step 2. Step 1 is only done by 9% and then it proceeds with step 2
without
any message. After the 25% of step 2 it just terminates without any
feedback
(good or bad). At that point Vista continues to boot and does so
successfully
but CHKDSK will always be executed the next time I boot Vista.

--What I have done so far when trying to solve the problem:
1. Executing "fsutil dirty query c:" reports that the volume is
dirty
so
there is no surprise that CHKDSK runs when I boot but, since CHKDSK
never
finishes successfully, the dirty bit is never cleared resulting in
this
situation.
2. The hard disk manufacture provides a low level
testing/diagnostic
tool
and that report that the disk is working perfectly.
3. By booting Vista from the DVD, and going into repair mode, I
have
tried
to run CHKDSK from the command window. I tried any permutation of
arguments
that made sense with slightly different results. The results are as
follows:
Regardless of the arguments step 1 always ends at 9% (no feedback
it
just
ends).
If I specify /f step 2 terminates after 25% unless I also specify
/I.
If I specify /I step 2 terminates after 46%.
If I specify /R step 2 terminates after 10%.
In the vast majority of cases (regardless of arguments) CHKDSK just
terminates (during step 2) without giving any sort of feedback but,
once
in a
while, it does terminate and report that "An unspecified error
occurred".
4. I have (in desperation) run diagnostics tools that check the ram
memory
(primary memory 3GB) and there was no problem.

--The situation as I see it:
This has to be a bug in CHKDSK.
Obviously I understand that there might be situations that CHKDSK
can't
resolve but then it should report exactly that. Not just terminate
as
it
does
now.
Accepted results would be one of the following reports.
1. There was no problem with the disk.
2. There were problems and they are fixed.
3. There were problems and they could NOT be fixed but that is
reported.

--Questions:
Does anybody know is this is a known bug and if Microsoft has a
solution?
Does anybody know of a way of fixing this problem?

--My system:
OS: Microsoft Vista Ultimate (32bit)
Motherboard: Asus P5B-Plus Vista Edition
CPU: Intel Core 2 Duo E6420 2.13GHz
Disk: Samsung SpinPoint T166 250GB SATA2 16MB 7200RPM
RAM: 2*1024 + 2*512 Crucial DDR2 PC6400 CL5
Vista was installed on a new (empty) disk 2-3 month ago.
Vista is up to date (Windows Update has nothing to add)

--Final thing:
If I had a back up of the system I could have restored that but I
don't
:-(
I would be very happy if someone had any ideas that could help me.

/Regards





Try running it from an elevated command prompt from within Vista,
with
the
verbose option set, and without actually fixing anything. The
information it
provides may be of more use in understanding what is happening, and
why
it
is failing ....

chkdsk /v c:

or to save the output to file for examination......

chkdsk /v c: > %userprofile%\Desktop\chkdsk_output.txt

chkdsk /?

 

[Guest]

I tried that but no luck :-(
Thank you for trying to help

I was always told to run it (in XP) as:

CHKDSK /R /F

Hope you solve it

Frenchy

Hi Jon,
Ok I did that with the following result:
C:\Windows\system32>chkdsk /v c:
The type of the file system is NTFS.
Volume label is Local Disk 1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
105472 file records processed.
File verification completed.
108 large file records processed.
0 bad file records processed.
2 EA records processed.
93 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
25 percent complete. (76663 of 401436 index entries processed)
C:\Windows\system32>

Again step 2 terminates after 25% (as always) but I actually got an error
in
a popup dialog.
I copied the dialog to the clipboard and pasted it below:
[Window Title]
Microsoft Windows

[Main Instruction]
Check Disk Utility has stopped working

[Content]
A problem caused the program to stop working correctly. Windows will close
the program and notify you if a solution is available.

[Close program]

So, something with CHKDSK seems to be wrong :-(
Any ideas?

--Problem:
I have read of others having the same problem but I have never seen any
post
that actually solves the problem (apart from reformatting the
partition)
so I
will try to describe the problem the best I can in hope of anyone
coming
up
with a fix or an idea.
Every time I boot Vista (Vista Ultimate 32bit) CHKDSK runs
automatically
but
it never finishes successfully. It always terminates when it has done
25%
of
step 2. Step 1 is only done by 9% and then it proceeds with step 2
without
any message. After the 25% of step 2 it just terminates without any
feedback
(good or bad). At that point Vista continues to boot and does so
successfully
but CHKDSK will always be executed the next time I boot Vista.

--What I have done so far when trying to solve the problem:
1. Executing “fsutil dirty query c:†reports that the volume is dirty
so
there is no surprise that CHKDSK runs when I boot but, since CHKDSK
never
finishes successfully, the dirty bit is never cleared resulting in this
situation.
2. The hard disk manufacture provides a low level testing/diagnostic
tool
and that report that the disk is working perfectly.
3. By booting Vista from the DVD, and going into repair mode, I have
tried
to run CHKDSK from the command window. I tried any permutation of
arguments
that made sense with slightly different results. The results are as
follows:
Regardless of the arguments step 1 always ends at 9% (no feedback it
just
ends).
If I specify /f step 2 terminates after 25% unless I also specify /I.
If I specify /I step 2 terminates after 46%.
If I specify /R step 2 terminates after 10%.
In the vast majority of cases (regardless of arguments) CHKDSK just
terminates (during step 2) without giving any sort of feedback but,
once
in a
while, it does terminate and report that “An unspecified error
occurredâ€.
4. I have (in desperation) run diagnostics tools that check the ram
memory
(primary memory 3GB) and there was no problem.

--The situation as I see it:
This has to be a bug in CHKDSK.
Obviously I understand that there might be situations that CHKDSK can’t
resolve but then it should report exactly that. Not just terminate as
it
does
now.
Accepted results would be one of the following reports.
1. There was no problem with the disk.
2. There were problems and they are fixed.
3. There were problems and they could NOT be fixed but that is
reported.

--Questions:
Does anybody know is this is a known bug and if Microsoft has a
solution?
Does anybody know of a way of fixing this problem?

--My system:
OS: Microsoft Vista Ultimate (32bit)
Motherboard: Asus P5B-Plus Vista Edition
CPU: Intel Core 2 Duo E6420 2.13GHz
Disk: Samsung SpinPoint T166 250GB SATA2 16MB 7200RPM
RAM: 2*1024 + 2*512 Crucial DDR2 PC6400 CL5
Vista was installed on a new (empty) disk 2-3 month ago.
Vista is up to date (Windows Update has nothing to add)

--Final thing:
If I had a back up of the system I could have restored that but I don’t
:-(
I would be very happy if someone had any ideas that could help me.

/Regards





Try running it from an elevated command prompt from within Vista, with
the
verbose option set, and without actually fixing anything. The information
it
provides may be of more use in understanding what is happening, and why
it
is failing ....

chkdsk /v c:

or to save the output to file for examination......

chkdsk /v c: > %userprofile%\Desktop\chkdsk_output.txt

chkdsk /?

 

[Jon]

Unfortunately running CHKDSK after booting from the DVD did not give any
new
information nor did it succeeded any more :-(
I also tried to add the /r argument as Frenchy suggested but no progress.
When looking in the Event Viewer I have some events related to the problem
(example below):
Log Name: System
Source: Ntfs
Date: 2007-08-01 12:28:11
Event ID: 55
Task Category: (2)
Level: Error
Keywords: Classic
User: N/A
Computer: Hebbe-PC
Description:
The file system structure on the disk is corrupt and unusable. Please run
the chkdsk utility on the volume Local Disk 1.

Obviously my disk is not feeling good.
Most likely the (logical) left side of my brain has to convince the
(emotional) right side of my brain that the only reasonable thing to do is
to
delete this failing partition and start over.. but how fun is that on a
scale
from 1 to 10? Close to 1 :-(
Anyhow, thanks for trying to help

Oh well, sorry it didn't work out. Yep, there's often more fun in the chase
than the conquest.

 

[Michael Solomon]

Unfortunately running CHKDSK after booting from the DVD did not give any
new
information nor did it succeeded any more :-(
I also tried to add the /r argument as Frenchy suggested but no progress.
When looking in the Event Viewer I have some events related to the problem
(example below):
Log Name: System
Source: Ntfs
Date: 2007-08-01 12:28:11
Event ID: 55
Task Category: (2)
Level: Error
Keywords: Classic
User: N/A
Computer: Hebbe-PC
Description:
The file system structure on the disk is corrupt and unusable. Please run
the chkdsk utility on the volume Local Disk 1.

Obviously my disk is not feeling good.
Most likely the (logical) left side of my brain has to convince the
(emotional) right side of my brain that the only reasonable thing to do is
to
delete this failing partition and start over…. but how fun is that on a
scale
from 1 to 10? Close to 1 :-(
Anyhow, thanks for trying to help

yw.. Good idea with the DVD. Sometimes switching between the various
different ways of running the chkdsk does do the trick ie you get so far
with one approach, and then another one gets further than it did
previously,
until eventually they all complete successfully. Well, that's the ideal
scenario anyhow....

--
Jon

Thank you Jon,
Actually there was some new information I got by doing as you asked:
C:\Windows\system32>chkdsk /v /i c:
The type of the file system is NTFS.
Volume label is Local Disk 1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

WARNING! I parameter specified.
Your drive may still be corrupt even after running CHKDSK.

CHKDSK is verifying files (stage 1 of 3)...
105472 file records processed.
File verification completed.
108 large file records processed.
0 bad file records processed.
2 EA records processed.
93 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
46 percent complete. (90392 of 183931 index entries processed)

Errors found. CHKDSK cannot continue in read-only mode.

So, it terminated in the same way as before but now adding the "Errors
found...." statement.
I did not get the error message in the popup this time. It was reported
in
the command window.
Since it can't continue in read-only I will try booting from the Vista
DVD
and run this command with /f added. But... it is getting late in my
time
zone
so I will do that tomorrow.
Thank you very much though for your help. I will post the results
tomorrow


:

Another thought is that since it' appears to be failing on the 'Index
entries' stage, you could also try the same command with the /i
option,
to
see if it progresses any further ie ....

chkdsk /v /i c:

--
Jon


Very odd. Not seen anything like that before.

The only other thing that I can suggest, is that if you have a dual
boot,
say with XP (preferably on a completely independent partition), that
you
could boot into that and run a chkdsk from there on the Vista
partition -
either from the command prompt or via the right-click drive >
Properties
Tools route

If that doesn't work either, then perhaps your original conclusion
was
correct - you've run into a bug in chkdsk. Either way, I'd back up
any
valuable data / documents to safe locations pretty sharpish, since
the
disk may well be on the blink.

--
Jon


Hi Jon,
Ok I did that with the following result:
C:\Windows\system32>chkdsk /v c:
The type of the file system is NTFS.
Volume label is Local Disk 1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
105472 file records processed.
File verification completed.
108 large file records processed.
0 bad file records processed.
2 EA records processed.
93 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
25 percent complete. (76663 of 401436 index entries processed)
C:\Windows\system32>

Again step 2 terminates after 25% (as always) but I actually got an
error
in
a popup dialog.
I copied the dialog to the clipboard and pasted it below:
[Window Title]
Microsoft Windows

[Main Instruction]
Check Disk Utility has stopped working

[Content]
A problem caused the program to stop working correctly. Windows
will
close
the program and notify you if a solution is available.

[Close program]

So, something with CHKDSK seems to be wrong :-(
Any ideas?


:

--Problem:
I have read of others having the same problem but I have never
seen
any
post
that actually solves the problem (apart from reformatting the
partition)
so I
will try to describe the problem the best I can in hope of
anyone
coming
up
with a fix or an idea.
Every time I boot Vista (Vista Ultimate 32bit) CHKDSK runs
automatically
but
it never finishes successfully. It always terminates when it has
done
25%
of
step 2. Step 1 is only done by 9% and then it proceeds with step
2
without
any message. After the 25% of step 2 it just terminates without
any
feedback
(good or bad). At that point Vista continues to boot and does so
successfully
but CHKDSK will always be executed the next time I boot Vista.

--What I have done so far when trying to solve the problem:
1. Executing "fsutil dirty query c:" reports that the volume is
dirty
so
there is no surprise that CHKDSK runs when I boot but, since
CHKDSK
never
finishes successfully, the dirty bit is never cleared resulting
in
this
situation.
2. The hard disk manufacture provides a low level
testing/diagnostic
tool
and that report that the disk is working perfectly.
3. By booting Vista from the DVD, and going into repair mode, I
have
tried
to run CHKDSK from the command window. I tried any permutation
of
arguments
that made sense with slightly different results. The results are
as
follows:
Regardless of the arguments step 1 always ends at 9% (no
feedback
it
just
ends).
If I specify /f step 2 terminates after 25% unless I also
specify
/I.
If I specify /I step 2 terminates after 46%.
If I specify /R step 2 terminates after 10%.
In the vast majority of cases (regardless of arguments) CHKDSK
just
terminates (during step 2) without giving any sort of feedback
but,
once
in a
while, it does terminate and report that "An unspecified error
occurred".
4. I have (in desperation) run diagnostics tools that check the
ram
memory
(primary memory 3GB) and there was no problem.

--The situation as I see it:
This has to be a bug in CHKDSK.
Obviously I understand that there might be situations that
CHKDSK
can't
resolve but then it should report exactly that. Not just
terminate
as
it
does
now.
Accepted results would be one of the following reports.
1. There was no problem with the disk.
2. There were problems and they are fixed.
3. There were problems and they could NOT be fixed but that is
reported.

--Questions:
Does anybody know is this is a known bug and if Microsoft has a
solution?
Does anybody know of a way of fixing this problem?

--My system:
OS: Microsoft Vista Ultimate (32bit)
Motherboard: Asus P5B-Plus Vista Edition
CPU: Intel Core 2 Duo E6420 2.13GHz
Disk: Samsung SpinPoint T166 250GB SATA2 16MB 7200RPM
RAM: 2*1024 + 2*512 Crucial DDR2 PC6400 CL5
Vista was installed on a new (empty) disk 2-3 month ago.
Vista is up to date (Windows Update has nothing to add)

--Final thing:
If I had a back up of the system I could have restored that but
I
don't
:-(
I would be very happy if someone had any ideas that could help
me.

/Regards





Try running it from an elevated command prompt from within Vista,
with
the
verbose option set, and without actually fixing anything. The
information it
provides may be of more use in understanding what is happening,
and
why
it
is failing ....

chkdsk /v c:

or to save the output to file for examination......

chkdsk /v c: > %userprofile%\Desktop\chkdsk_output.txt

chkdsk /?

Sorry if this has already been asked or suggested but have you run the hard
disk manufacturer's diagnostic tools on this disk. The tools and
instructions for making a tools disk are usually at the hard drive
manufacturer's website. I'm not suggesting there's anything wrong with the
hard drive but before jumping through hoops trying to figure out what's
wrong, it's always best to rule out some sort of hard drive failure.