I can't get it to work!?!

[TwoRails]

I regularly run CHKDSK and have rarely had a problem since switching to NTFS. Today, however, I am having problems on my 'C' drive. I've run CHKDSK from the Command prompt multiple times with the /F and /X switches, and from the drive's Properties sheet with a full surface scan.

In each case on reboot (both warm and cold boots) Win XP Pro SP1 does it's thing, and after checking the disk and before Windows starts, it does another reboot and then goes into Windows.: Not only do I still have drive errors, but my USB mouse isn't recognized each time (seems like every other boot it's found).

The system has been running just fine otherwise.

Any and all help is appreciated!!

TIA

TR

[TwoRails]

Just an update: I just finished running a full PowerMax diagnostic on the drive, including a full surface scan. No problems found. Chkdsk still give me the message that the File System still has problems.

[Gimpy]

I don't know for sure if it would help, but have you tried running the SFC?

[Gizmo]

It sounds like XP's the culprit. I don't think filing system issues can be fixed by running chkdsk. Formatting a fresh filing system over the top and reinstalling XP will do the job. Backing up any important data first of course.

[ktkendall]

I think there are some enhanced things you can do with chkdsk and sfc if you boot from the xp cdrom and go into repair console..

[Panama Red]

Here's the How To for SFC /Scannow.

[TwoRails]

Hi All,

I ran sfc /scannow and there was no change. I did experience a bit of "weirdness" on reboot, though: I booted into BIOS and was told my overclock settings were messed up... I don't OC !?!

Nice link, PR! I'll be trying some of the tips / tricks in the article

I didn't mention it earlier, but it may be helpful: I did have another bit of weirdness after runing the full disk scan in PowerMax. On that reboot, I didn't boot... I found that my boot disk sequence was changed to the HD on the Secondary Master channel !?! I re-ordered the sequence and everything is fine for that problem.

I don't normally check temps, but I did today: I'm running at 36°C. (It's a cool day.)

I did the other normal things: run full AV scan; ran AdAware SE 1.05, then updated to version 1.06, ran SpyBot, MS's malicious code checker, and looked for any new / unusual startup programs: All came up clean.

The only other clues I can think of right now is that I've recently installed NAV 2005 which also has a worm and trogan checker built in. I wonder if that could have put some kind of hook into the file system to make sure bad changes don't happen?? This is my first chkdsk since that install.

The system still seems to be working just fine in all other aspects.

Any other ideas??

[TwoRails]

Well... still no joy. I've spent hours researching this and at least I'm not the only one with this problem so I don't feel alone. I've discovered lots of theories but no absolute / actual fixes. Theories range from software problems (Norton gets slammed as usual, but Nero and a bunch of others get it as well) to hardware problems (HDs of course, but theories also claim Turtle Beach sound cards is the culprit).

One common theme points to a problem / bug with chkdsk itself and apparently Win 2K had a know issue in this area.

So here’s my update:

The HD is fine and passes all tests.
Checking the drive from the Property sheet reports no errors.
Checking the drive with chkdsk from the command prompt give errors. (See below.)
Checking the drive with Norton Disk Doctor reports no errors.
Defrag finds no errors.
Running chkntfs comes up “clean.”
The computer is running just fine.

The error(s) I receive are below. The tmp.edb error is no longer present on the last several chkdsk runs, however the errors in the Volume Bitmap continue.

I’ve done everything I can think of, including little things like turning off the Swap file.. Any ideas?

WARNING! F parameter not specified. Running CHKDSK in read-only mode. CHKDSK is verifying files (stage 1 of 3)... File verification completed. CHKDSK is verifying indexes (stage 2 of 3)... Index verification completed. CHKDSK is recovering lost files. Recovering orphaned file tmp.edb (12817) into directory file 13927. CHKDSK is verifying security descriptors (stage 3 of 3)... Security descriptor verification completed. Correcting errors in the master file table's (MFT) BITMAP attribute. Correcting errors in the Volume Bitmap. Windows found problems with the file system. Run CHKDSK with the /F (fix) option to correct these. 15687440 KB total disk space. 10054600 KB in 44017 files. 13920 KB in 2888 indexes. 0 KB in bad sectors. 110368 KB in use by the system. 53280 KB occupied by the log file. 5508552 KB available on disk. 4096 bytes in each allocation unit. 3921860 total allocation units on disk. 1377138 allocation units available on disk.

[jayb1234]

Are you running CHKDSK in read only mode as that log shows, or is that just an example.

WARNING! F parameter not specified. Running CHKDSK in read-only mode. Windows found problems with the file system. Run CHKDSK with the /F (fix) option to correct these.

[TwoRails]

Yes, that's just an example. I've run it with multiple times with the /F switch as well as the /R and /X switches.