scandisk doesn't work...?

[arsta]

sfc/scandisk gets stuck on 49%, then after a while it just says that it cannot be completed.

Why could that be? And how exactly does it work? Tried in safe mode too, didn't help.

 

[denis280]

what os are you running
and it's sfc/scannow for windows files and chkdsk for hdd

 

[pcgeek11]

chkdsk as above. How full is the drive? How much free space?

 

[arsta]

Sorry, I misspelled. I meant sfc/scannow. I'm running 7 Home Premium x64.

In C, there's 4.2Gb free, out of 31Gb.

Chkdsk passes with no errors, by the way.

 

[denis280]

try sfc /verifyonly.
If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 or more times to completely fix everything that it's able to.

 

[arsta]

Tried scannow trice actually.

Just tried verifyonly, it also crashed on 49%.

 

[Steltek]

It would probably be a good idea to download a bootable diagnostic CD ISO from the hard drive manufacturer. Burn it to a CD, boot the machine with it, and test the hard drive for faults.

 

[arsta]

It would probably be a good idea to download a bootable diagnostic CD ISO from the hard drive manufacturer. Burn it to a CD, boot the machine with it, and test the hard drive for faults.

I'm gonna do that later next week. Lots of stuff to do, no time to run tests for a few days now. I'll post back with the results.

 

[Steltek]

I'm gonna do that later next week. Lots of stuff to do, no time to run tests for a few days now. I'll post back with the results.

When you do it, if you don't find any hardware faults on the hard drive, download the bootable ISO of MEMTEST86+. Burn it to a CD, and test your memory through several passes (preferably one module at a time). Defective memory can have all sorts of seemingly unrelated side effects (including damage to the OS file system installed on the hard disk).