Dave,
Thanks for the help. Yes, I did a restart.
I cannot open the CBS.log
I tried everything that I could think of.
It just sat there and said "No Way" pal.
Jim,
Negative on the repair disk.
Right click > Open with > notepad.exe.
If that doesn't work you can email it to me.
OK, Terry, I received the log. Looks like you may have ran SFC again at around 9pm on the 17th. Is that correct?
If you open an elevated command prompt (Search for cmd.exe from the Start menu > Right click on cmd.exe and select Run as Administrator) and type the following:
fsutil dirty query c:
This should return the results of the dirty bit (not what it seems), which Windows uses to mark a corrupt volume,
or one that may be corrupt. It should reply with Volume c: is dirty (Assuming the above errors were correct).
If it does not I can only assume that there is corruption of the bit, or corruption of the data and the bit hasn't
been set correctly.
Type the following in the same command prompt window to force the bit to "dirty":
fsutil dirty set C:
This should set the bit state to "dirty" and force the chkdsk (Check Disk) utility to run after a reboot.
Check Disk scans the drive for damage and/or corrupt data and attempts to repair.
Thanks Dave. I leave in the AM for a couple of days. I'll get back on it Sunday PM.
Thank you
Dave,
Did the elevated command prompt and got the:
c: is Dirty
response.
I'll reboot and see what happens.
No luck. I still get the same message as in the above posts.
When you rebooted did it do a Check Disk? If so, what were the results. If not, open an elevated command prompt and try the command to force the dirty bit to "dirty" and reboot.
Completed the tasks as requested.
Still not able to do a disk ckeck.
thanks
Perhaps you could try this if all else fails.
http://windowssecrets.com/top-story/win7s-no-reformat-nondestructive-reinstall/
I like to keep this in my back pocket to try if I ever need it.
Trouble is, we have been unable to ascertain for sure and for certain if the cause is a faulty hard drive or corrupted system files. Very difficult to definitively diagnose without any hands on.
If it's the former, a repair installation would be of little use.
Of course, you could always try the repair install Terry and see how it goes. Make sure to create an image first.
Jim,
That's the problem....I can't create a system image due to the chkdsk problem.
Try this:
Run CMD and type fsutil dirty query c:
As already stated above this queries the drive, and more than likely it will tell you that it is dirty.
Next, type CHKNTFS /X C:
The X tells Windows to NOT check the drive on the next reboot. Reboot your computer, it should not do a Chkdsk and take you directly to Windows.
Now open a CMD prompt and type and type in CHKDSK /f /r c: note the spaces!
This should unset that dirty bit.
Finally, type fsutil dirty query c: and Windows should confirm that the dirty bit is not set on that drive.
1 Guest(s)
