Chkdsk Problem

Microsoft Windows xp professional w/serv...
May 19, 2010 at 17:31:10
Specs: Windows XP Pro
Background to finding the problem: My computer was running very slowly after hibernation, so I restarted it and afterward ran some scans just to be sure it only needed restarting. Two out of three scans came back clean (antivirus and antimalware), but my scan by SuperAntiSpyware came back with double the usual amount of adware, same ones as usual but two of each. Usually that's all, but this time it needed to restart. After restart, I ran chkdsk just as a last check.

The scan finished, but claimed it found errors in the file system and needed to run at restart with /f, so I did so. After it was all restarted, I ran chkdsk again just to be sure. It said again at the end, direct quote:

Correcting errors in the Volume Bitmap.
Windows found problems with the file system.

Then it says to run chkdsk with the /f command to take care of it.

Is this a false positive? What should I try now? As I said, I ran chkdsk with the /f command just before doing it in read-only as a double check, but somehow, the problem seems to have come back immediately. I did not run anything before running chkdsk again after the restart.

Does anyone have any suggestions? This is getting me pretty worried.

(PS: This is a IBM laptop running Windows XP service pack 3, and the file system is NTFS.)

See More: Chkdsk Problem

Report •

May 19, 2010 at 18:57:52
If the problem comes back then it may be a real issue. Any part could cause this.

Get a ultimate boot cd and start with memtest's and then try hd diags.

It would be better to run IBM's diags if you can get them. They used to be online but may not now that junko bought it.

Try the hitachi diag tools too for hd.

If tests seem OK then you need to look at OS.

Playing to the angels
Les Paul (1915-2009)

Report •

May 21, 2010 at 07:57:44
Hey, just wanted to give a follow-up. I did a little more research and found a letter that had been posted by someone else having a similar problem who had contacted Microsoft. The text that they were given in read-only chkdsk was the same, and they were told to run chkntfs to see if the disk was dirty. If it was not, than it was the bug of Windows that sometimes has chkdsk give that message when run in read-only mode. I ran chkdsk /f on restart and chkntfs later, and neither found a problem, so I'm going to keep an eye on it but relax a little.

I will be checking out your ideas though, jefro, and saving them for later - just in case. Thanks for the hints.

Report •

May 21, 2010 at 09:37:00
Chkdsk /R will do a scan of the disk for weak/bad spots.

The three most important things in computing:
1. Backups, 2. Backups and 3. Backups.

Report •

Related Solutions

May 22, 2010 at 08:14:00
I was going to do a chkdsk /f scan of the computer on Sunday (tomorrow) when I start it up, since it's part of my new keep-the-comp clean routine, but I could do a chkdsk /r instead. One thing though - I keep trying to find out the difference between /f and /r, but no one seems to be able to tell me. Could anyone here make it a little clearer? All I've really been able to determine is that /r indicates that /f will happen as well, but not what /r does that is different from /f.

Report •

May 22, 2010 at 08:49:46
"I keep trying to find out the difference between /f and /r, but no one seems to be able to tell me"

Report •

May 22, 2010 at 11:22:36
Thanks for the link, that is the clearest the differences between /f and /r have been made so far to me.
I'll be back tomorrow with a follow-up of how the chkdsk /r scan goes - wish me luck.

Report •

May 23, 2010 at 09:59:45
I ran the chkdsk /r scan this morning - so far, so good. I checked the log in the event viewer - according to the log, it cleaned up a few little things and the disk is reported to be clean. I am thinking it may have been a false positive caused by chkdsk being run in read-only mode. I'll keep running chkdsk on a weekly basis, but I think I'll alternate using chkdsk/f and /r rather than using the read-only mode. Thanks for your help, everyone!

Report •

Ask Question