Viz Vista by Ed Tittel

In yesterday's blog, I reported on the appearance of reports for numerous (9 one day, 10 the next) "corrupt and unusable" VolumeShadowCopyXX entries in the System Log in Event Viewer. All of these originated from source Ntfs, the Vista file system manager.

In the past couple of months, I 've been grappling with graphics stability issues. Mostly, this has meant driver restarts where you get a message that reads something like "Display driver stopped responding and has recovered." Occasionally, this has involved a BSOD that mentions the Nvidia driver files nvlddmkm.dll or nvlddmkm.sys. When it happens, it seldom occurs more than twice a week. I keep checking the Nvidia driver download page, grabbing new drivers as they become available (including occasional betas), and hoping for the best.

This looked just plain weird to me. When I checked Reliability Monitor and the installation of the generic volume shadow copy devices I couldn't make out a pattern even though it was there to be found. I even posted queries about this to vistaforums.com, techsupportforum.com, and to Microsoft Tech Support, but it took a Facebook email to one of the demiurges in the Windows pantheon--namely, Mark Russinovich--to get to the bottom of the matter (more on this to follow at the end of this story).