Sounds like a failing hard drive. Back-up all your data immediately. Check your hard drive manufacturer's website for a diagnostic tool. If none is available use Seagate's Seatools. You can download either the ISO version and boot from the disc or you can use the windows version and run the test while logged on. My experience is that I have better luck with the iso in repairing bad sectors. Rarely, however, are the ever repaired.
http://www.seagate.com/www/en-us/support/downloads/seatools
Well if it is a failing hard drive it has been failing for about 5 years with no manifestation of the problem whatsoever.
I will refer you to this thread.
https://www.techspot.com/vb/topic150127.html
It is Hitachi.
I have tried to used their drive tool but I cannot get it to work.
This is the user manual.
http://www.hitachigst.com/hdd/support/downloads/FTool_User_Guide_215.pdf
I do not have a floppy drive. (might get one).
So not much I can do at moment so it is a nusiance, I have to stop it running by rebooting
cos it takes ages and I think it may not complete.
I will try it overnight.
fsutil reports C as dirty.
This is no surprise as I got quite a lot of reboots when I had bad ram.
I have good ram now so the problem should not get worse, I am very sure the bad ram has
lets some file in a bad state however it does not appear to affect my computers usage.
IT runs fine otherwise.
Chance are the bad file is unimportant and it maybe a temporary internet file.
I read someone could get chkdsk to run by clearing temporary internet files.
I mean it is unlike a important system file was being written during a reboot?
I may have to put in a fake chkdsk file to make sure it does not run.
I wonder is deleting temporary files will help and stop chkdsk running?
I feel confident my drive is basically OK, chkdsk has never ran properly on my system and I have had years of trouble free use (apart from when I had the bad ram in, the bad ram is going back to the retailer and not back in my machine!!.
Sometime the chkdsk has done a repair on pass one but I don't think it ever gets past pass two without complaining.
I have just reread your post and I will try seagates tools.
Thanks for that!
As I see it basically a file was being written and it rebooted, thus the computer has a bit set somewhere to say the write operation was not complete?