Are these normal chkdsk error messages?

[jzinckgra]

I revived my computer after recent freezing, BSOD screens, and finally not even loading windows. I thought the problem may have started originally with a failing HD, so after I got the puter up and running, I ran a chkdsk. I got error messages like these:
"correcting eror in index"
"deleting corrupt attribute record"
"deleting orphan file seg. record"

In the end the final screen came up with a bunch of info, but the puter restarted itself and loaded windows, so I never got to see what it all said. Is there a place in windows where there would be a log file of the chkdsk? Do the above errors indicate a failing HD? Everything seems to be running good for now.

 

[mpilchfamily]

The problem may not be a bad drive. But when Windows BSOD'd on you it probably caused some corruption to the drive. Though there is the chance the corruption was already there and was the cause of the BSOD. If you run into problems again where the drive gets corrupted again you need to start checking out the system a bit more. The drive could still be fine. If you have RAM going bad it can easily corrupt the HDD. So can a failing PSU. But any message displayed right before the restart was only going to tell you how many files where corrupted and fixed and maybe even how much HDD space you lost to sectors that couldn't be fixed.

 

[Roguestar]

Sometimes not properly shutting down, a copy gone wrong or any number of small things can cause errors in the file system; chkdsk generally spots these and either fixes or removes the files in question. Unless you're getting this kind of thing happening all the time I wouldn't worry about it.

 

[corkyg]

Those are normal messages from CHKDSK telling you what corrective action was taken. It would be more worrisome if it could not fix the problems indicated.

 

[RebateMonger]

If you want to check your hardware, download a memory tester (Memtest 86+ is a standard) and run an overnight memory test. Then download the hard drive maker's disk diagnostics program (either Windows-based or boot-Cd-based) and test the hard drive.

If both of those tests show no errors, then the cause of your errors was likely a software issue.

 

[Rubycon]

Run chkdsk c: /r and reboot.

When it's back up run just chkdsk c: and it should find no problems.