I missed this one mta, but I'm wondering if the "DOS CHKDSK" means you did it via command line.
hazel linked to an article recently which wasn't about this particular issue, but some chap mentioned in the article that he had tried fixing a problem using CHKDSK from the drives right click options menu with no success, but tried running it again from command line and it fixed the problem.
thanks for the link @DennisD, i followed yours then followed hers, plus from my experience, i am agreeing with @Andavari, i'll be doing my 'scans' from DOS from now on.
(and yes to answer your question, I did do it from the command line in DOS - thank {insert preferred religious deity} for DOS)
The only thing is it isn't DOS at all, it's just a command-line interface ("CLI") with more options than the GUI offers, the same goes for other Windows utilities such as Defrag, etc.
It is interesting that I've noticed on here and other help forums, members who are obviously technically proficient and knowledgeable, recommending someone run CHCKDSK to try fix an issue and usually giving them a command line instruction to copy or copy/paste.
I always assumed that the helper was probably "old school", and had always done it that way, but this topic and the snippet from hazels original link shows what probably the majority of computer users don't know, and that is the right click properties menu option of CHCKDSK isn't a user friendly equivalent to running it via command line.
The nice thing about the CLI option of using ChkDsk is that you can make a batch file to check all your hard disks one after another.
Of course doing it that way you'd have to leave C:\ for last since it must be scheduled on next reboot, and then have the system automatically reboot all via a single batch file is very convenient versus SLOWLY fumbling through the GUI.
This is what I personally use (which can be modified to suit anyone's needs of multiple hard disks/partitions:
@ECHO OFF
ECHO **********
ECHO Check Disk
ECHO **********
ECHO.
ECHO -----------------------------------------------------------
ECHO.
chkdsk.exe /X /V /F D:
ECHO.
ECHO -----------------------------------------------------------
ECHO.
chkdsk.exe /X /V /F E:
ECHO.
ECHO -----------------------------------------------------------
ECHO.
ECHO Information:
ECHO Press any key on the keyboard to schedule a
ECHO Check Disk scan on drive C and to have the
ECHO computer reboot immediately to run the scan.
ECHO.
ECHO Note:
ECHO If you don't want to run the scan right now
ECHO just close this Window by clicking the X at
ECHO the upper-most right of this window.
ECHO.
ECHO -----------------------------------------------------------
ECHO.
PAUSE
ECHO.
chkdsk.exe /F C:
shutdown.exe -r -t 20 -c Restarting to run Check Disk on drive C
ECHO.
ECHO -----------------------------------------------------------
ECHO.
ECHO To abort press any key on the keyboard.
ECHO.
ECHO -----------------------------------------------------------
ECHO.
PAUSE
ECHO.
shutdown.exe -a
CLS
EXIT
I like that GUI version, being one who was never into command line.
It also tells you if a drives "Dirty Bit" is set or unset, and for anyone following this thread and not knowing what that means, a useful explanation here ...
The GUI is running the command line version of CHKDSK, so at the very least you would get the same feedback, if any, that running it directly from command line would give you.
I think the point of the tool is to make the execution and running of the command line version of CHKDSK easier for less experienced users. Whatever the outcome of a scan is, it isn't going to be any worse than the outcome of running it directly, and maybe, and none of us know this, there may be a more user friendly outcome.
Either way, it's a boon to a lot of people, (like ERUNT GUI) who would probably just run CHKDSK from the shell properties menu.