When I start or "restart" Windows 7, I often encounter the system running a Chkdsk that finds no "errors" to correct. A search of the Web for why this happens (why a "dirty bit" gets set when Windows 7 shuts down) suggests that in some cases, the problem involves the antivirus program ("fixes" to these routines make the frequent Chkdsk runs go away). I have two different PCs (a desktop and a laptop) running Windows 7, and both show this behavior (and both run Norton 360 version 3). Of interest is that it is almost always the D: disk that is checked -- I use D: as the place for "My Documents", to separate "data" from "programs/system". Before migrating to Windows 7, I had run Windows XP in just such a configuration on both machines (also with Norton 360) and had never seen Chkdsk run when starting Windows. Now, I'd say it happens about 30% of the time. Any possibility that Norton Antivirus is "interacting badly" with Windows 7 on shutdown so as to mark a drive as "dirty", causing Chkdsk to run when Windows reboots?
That is interesting BSchor. I have the same issue on an XPsp3/Win 7 dual boot. In my case, the disc check is always the XP/C drive, not the Win 7 D drive. I'm thinking it has something to do with the full system scan happening on both drives. In my case, there are two system drives and a different Norton version of NIS on each, which could cause an issue as they both scan each other. In your case, unless you have an operating system on your D drive as well, that would not be the same issue.
Very interesting, indeed. As it happens, my three Windows 7 PCs are also "former XP" machines, and are also all dual-boot. I didn't emphasize it in the original post, as I have seen this "feature" even when I'm only running/restarting Windows 7 (without booting to XP).
Here's my configuration(s): Originally, C: was Windows XP, and D: was Data (including My Documents). Windows 7 was installed on its own partition, call it E:. When Windows 7 installs and reboots, it rearranges the drive letters so that it now lives on the C: drive. I "manually" change the letters on the other drives so that C: is "the current OS", D: is "Data", and E: is "The Other OS". When Windows starts, I either let it default to Windows 7 or simply hit "Enter" so I don't have to wait, and it boots (and usually runs Chkdsk).
Aha -- I just did a test with one of these machines. I had been running Windows 7, so I did a "Restart" (after closing all active windows). I got the "choose the OS" screen, hit "Enter" to accept the default of Windows 7, had Windows 7 (the four colors coming into the center), then Chkdsk popped up, saying "One of your disks needs to be checked for consistency", and it was D:. At the end of the check, "No problems were detected", and Windows 7 is now waiting for me to log on. Just a sec, I'll see if it happens twice in a row ... Logged in, immediately went to Restart, again chose Windows 7 by hitting Enter, and this time, no Chkdsk. Of course, I did no work, so I probably made no changes to D: ...
The more I think about it, the more I'm worried that this is really a Windows 7 issue, and not a Norton (or other Antivirus) issue. Earlier Web discussions seemed to "point the finger" in the direction of at least one AV program, but maybe it is deeper than that ...
Bob Schor
Hi BSchor:
Yes, mine has been doing the same thing. When it happens, which seems to be sporadically, when I boot into Win 7 on D, it calls for a check on the C Drive. If I boot into XP, it also calls for a check. If I let it run, it doesn't happen for a few days, but it is difficult to tell what is changing that causes it.
On one occasion there was an index entry to do with the dual core that was noted. What processors are you running? I also have an issue with the Intel Management Interface Engine.
It could well be Windows errors causing it, or Windows errors caused by changes in some other program. Unfortunately, since I installed Win 7 and Norton at the same, I have no comparison.