Windows 7 drive frustrations

[Selkit]

Silly Kay, necro'd thread is necro'd. I actually finally determined what the root cause of this issue is. It has to do with the Windows Indexing service, virtual drives, and version control software; It's the result of a process conflict occurring when the Windows Indexer attempts to access a file that version control is currently juggling, because it spots an opclock change with the file, then attempts to re-index it. As the version control isn't a system process, it causes multiple access collisions, then has to back down. The OS assumes that the issue with that particular file is not actually a process collision (owing to the way it happens), but a corrupt entry. Thus, it marks the volume dirty. Thankfully, service pack 1 included a patch for this particular issue.

[kayfox]

Welcome to Windows.

Also, as for the thread being old, Im not used to forums considering a thread to be dead quite that soon, but I guess its common these days with information being dead in a month.