chck disk runs at startup, no problems detected

Judgeneo · 14 Jul 2011 at 21:30

For a while now, chck disk has been running every time I start up the computer, but never finds a fault.
The windows 7 system maintance tool says that I have volume errors or something, and today I had an error message on my log in screen :S

No idea what to do, or how serious it is.

Relevant specs:
Primary drive: 60Gb Corsair reactor SSD
Storage: 2x Samsung F1 1tb (no raid)
Motherboard: Asus crosshair IV

Judgeneo · 14 Jul 2011 at 21:56

Cheers for the advice, it seems C drive is indeed dirty.

However on step 5 I get this:

The type of the file system is NFTS.
Cannot lock current drive.

ChkDsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? <Y/N>

The reason the volume is in use is because its my boot drive :S
I said yes and rebooted and ChkDsk ran twice in a row. Both times this happens ( and every time I turn the computer on I might add)

Stage 1 of 3 completes, 209 large files tested, 44 are reparsed (what does this mean) it then goes on to start stage 2, but nothing happens and it goes on to run the computer or other ChkDsk in this case.

I got a better chance to see one of the error messages I get upon the log on screen now aswell, apparently logon.UI or something is corrupt, and I should run ChkDsk :S

If I installed ubuntu on a separate partition on another drive, would I be able to fix and repair errors easier from that?

Judgeneo · 15 Jul 2011 at 21:44

Giving this a bump, any and all advice appreciated.

Is there another way to fix disk errors?

Judgeneo · 8 Oct 2011 at 23:24

Bump because the problem is still there.

I started trying to solve it again today as skype doesn't seem to work any more :mad:

Basically:

1. Windows thinks my boot drive is dirty
2. Chkdsk runs everytime I boot
3. Chkdsk never completes, it gets stuck and finishes early in step 2
4. Several windows files are corrupted, including the logon files meaning booting now skips the whole asking for password thing.

I've tried scheduling multiple Chkdsks, and running it in safe mode. Scheduling multiple does nothing, but running in safemode allowed the checking to go further, and confirmed there was problems, but it couldn't do anything in read-only mode. Scheduling it to run before boot into safe mode doesn't work either...

Ideas people? Perhaps there is some sort of Corsair tool for this?