HiI have a strange "problem". Sometimes, my windows 7 pro client reports during boot that the disk has to be checked and runs chkdsk. Unfortunatly, I don't see any error in the event log. The previous shutdown was (to me) normal. There is also no scheduled task that should check the disks.I don't know what the run interval is.anyone an idea why the chkdsk is runned?ThxOlivier

Usually, because it detects something is amiss. Don't look for errors in the event log...look for wininit under the application log that is where chkdsk stores its results inVista and Windows 7Did it find anything?

This issue may be caused by the incorrect settings on the computer. You can use the below method to test this issue: Method 1: Using CHKNTFS utility ======================== 1. Click the Start Button, type "cmd" (without quotation marks) in the Start Search bar. 2. Right click on the search result listed upper and click Run as Administrator. 3. If you want to disable check disk on C: drive, use the following command on command prompt. chkntfs /X C: If you want to disable check disk on two or more drives, just keep on adding the drives: chkntfs /X C: D: E: This will disable check disk on C, D and E drives. 4. Restart the computer Method 2: Using Registry ======================== 1. Click the Start Button, type regedit in the "Start Search" text box and then press ENTER. 2. Navigate to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager Right click the {Session Manager} entry, choose "Export", select Desktop in the Save in box and type backup in File Name. Click Save. Please Note: The backup file is on the Desktop and named backup.reg. We can simply restore the registry by double-clicking the backup.reg file. 3. In the right hand pane, double click BootExecute. 4. The default value of the key is autocheck autochk * 5. To disable the autocheck on C: drive, change the key to autocheck autochk /k:C * If you want to add more drives, the key should look like this: (disabling C and D drives) autocheck autochk /k:C /k:D * 6. Exit the registry and restart the computer.Please restart the computer to check this issue agian. Hope the above information can help you solve this issue.

Usually, because it detects something is amiss. Don't look for errors in the event log...look for wininit under the application log that is where chkdsk stores its results inVista and Windows 7Did it find anything? Checking file system on C: The type of the file system is NTFS. One of your disks needs to be checked for consistency. You may cancel the disk check, but it is strongly recommended that you continue. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 3)... 81664 file records processed. File verification completed. 46 large file records processed. 0 bad file records processed. 2 EA records processed. 41 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)... 112190 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)... 81664 file SDs/SIDs processed. Cleaning up 187 unused index entries from index $SII of file 0x9. Cleaning up 187 unused index entries from index $SDH of file 0x9. Cleaning up 187 unused security descriptors. Security descriptor verification completed. 15264 data files processed. CHKDSK is verifying Usn Journal... 35156360 USN bytes processed. Usn Journal verification completed. Windows has checked the file system and found no problems. 625027071 KB total disk space. 35498212 KB in 50950 files. 39076 KB in 15265 indexes. 0 KB in bad sectors. 201547 KB in use by the system. 65536 KB occupied by the log file. 589288236 KB available on disk. 4096 bytes in each allocation unit. 156256767 total allocation units on disk. 147322059 allocation units available on disk. Internal Info: 00 3f 01 00 b2 02 01 00 50 0d 02 00 00 00 00 00 .?......P....... a4 00 00 00 29 00 00 00 00 00 00 00 00 00 00 00 ....)........... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Windows has finished checking your disk. Please wait while your computer restarts.

Betty I don't want to exclude my drive from beeing scanned but I want to know what produces the scan. Please see above the event log entry. thx

Regarding the Check disk produces, you can check the below article:TheProduces of Check Disk (Chkdsk.exe)You will see the detail explanation of the check disk produces. Notice: the Windows 7's scan produces is the same as Windows XP.Betty

I have the same problem as the OP stated. I tried the method one to resolve the problem. After typing in the command all i get is "The type of file system is NTFS" is that all I am suppose to see? after this just restart the computer? I just installed windows 7 pro an another computer and when the system starts I get the same "checking file system" or something like that sorry can't remember the exact quote.

hiI made a backup & a system image of my drive. Then I used a tool named data lifeguard from western digital to write zeros to the entire disk. I loaded back the image.Since then, no NTFS errors anymore.The strange thing is that under vista i never had any problems....

I have the same problem as well on two systems that I installed Windows 7 Pro (one x86, the other x64). It wants to run the chkdsk about 50% of the time at boot up. Even if I let it run through, it finds nothing and still wants to do it the next time. No issues like this until I put Windows 7 on.If I use the fix above, does this mean it will never want to run a chkdsk evn if there may be an actual legit need to do it? I don't want to disable the check if it is going to leave my computer unprotected, but at the same time why is it asking to run the check everytime when there is no reason for it?

Hi I didn't disable the autocheck function with the "hint" above. Instead, I reformated my entire drive with "zeros" and the Western Digital tool. Since then, no problems. I hope that it will hold :-)

I'm afraid that since this question has already been marked with an answer know one will click on the question and help us out with our problem. I wonder if i should start another thread with same topic to see if someone can help with additional questions we might have on this issue. I'll give it a couple of more days and hopefully someone answers by then

It's also possible (and the "zero rewriting"solution reminds me of that) that you used a preformatted disk for the installation (preformatted by manufacturer or another disk formatting program/OS). Windows 7 seems a bit picky with that and prefers its own NTFS, so the install partition should be always formatted by Windows 7 setup. And no, NTFS is not = NTFS, there are small differences concerning the cluster arrangement.Mobile AMD64 3000+, VIA Apollo K8T800 chipset, 1 G RAM, ATIRadeonMobility 9700, 20x DVDRW, C:XPSP3 (55G),D:WIN7 (25G),F:DATA (250G)

If I use the fix above, does this mean it will never want to run a chkdsk evn if there may be an actual legit need to do it? I don't want to disable the check if it is going to leave my computer unprotected, but at the same time why is it asking to run the check everytime when there is no reason for it? I have exactly the same problem and the same question as don242... and I'm afraid, as xicanonaztlanca said, that the question has already been marked with an answer, but actually it has not replied to our concerns.

BTW: you can also write zeros with diskpart "clean all" commands.

This started to happen to my WinXp SP3 install in May of this year. I immediately suspected the drive and ran all sorts of diagnostic software only to learn that my drive was fine. Turned out that I had updated the app 'Sandboxie' and other users ( forum ) were experiencing the same anomaly. This is the first time I have seen software do this.

FWIW, Me too No error just running it.I think I will reinstall and try the reformat optionAs of today, still no CHKDSK - Bill

It is still happening with me as well. Never did find a solution to this. Now it pretty much runs the chkdsk everytime I restart the computer. Never finds a problem and has only happened since putting Windows 7 on my computers (happens on all Win7 machines). I just hibernate most of the time anyway so it isn't a big deal...still it should be fixed.

Don't know why, but did complete reinstall using custom option and deleted all partitions. A couple of days and no CHKDSK....- Bill

This started to happen to my WinXp SP3 install in May of this year. I immediately suspected the drive and ran all sorts of diagnostic software only to learn that my drive was fine. Turned out that I had updated the app 'Sandboxie' and other users ( forum ) were experiencing the same anomaly. This is the first time I have seen software do this. Do any of you have Antivir Personal, Premium or Suite? It apparently causes this problem on Windows 7. It can cause Event ID 55 and 5038 Audit Failure errors in Event Viewer. I have a 5038 Audit Failure error for every boot/reboot since I installed Antivir Personal version 9 on Oct 24. I have not yet had chkdsk run at boot but others who have Avira are currently reporting that they have chkdsk running at every boot until they uninstall Avira 9 after which time chkdsk never runs again. I was given a Hotfix from Avira to try last Friday. It solved the 5038 Audit Failure error immediately and some others who have the hotfix have reported that it also solved the problem with the volume being marked as dirty and chkdsk running on each boot (finding nothing amiss). For some though, this hotfix did not correct the problem. I have experienced crashing of avcenter.exe with a Runtime error three times since installing the hotfix. Avira is now saying that they are "leaning toward" this being a Microsoft bug rather than an Avira problem. They cite this article: http://www.pcpro.co.uk/blogs/2009/11/16/the-windows-7-chkdsk-bug-that-wont-go-away/ With this thread having been marked solved when obviously there is a problem which may or may not be an Avira problem, a Microsoft bug, or a combination of these, it does appear, as the blog's author points out, that Microsoft has put its head in the sand regarding this and is ignoring the increasing number of Windows 7 users reporting the problem. Permanently disabling chkdsk is NOT a viable solution. It seems obvious to me that in some cases, including mine, this problem stems from Avira as the hotfix has fixed the problem for me so far (while causing some instability in Antivir Personal). This is not the first time that an antivirus program has caused chkdsk problems. Kaspersky version 6 did this a few years ago causing severe damage in some cases.

This started to happen to my WinXp SP3 install in May of this year. I immediately suspected the drive and ran all sorts of diagnostic software only to learn that my drive was fine. Turned out that I had updated the app 'Sandboxie' and other users ( forum ) were experiencing the same anomaly. This is the first time I have seen software do this. Do any of you have Antivir Personal, Premium or Suite? It apparently causes this problem on Windows 7. It can cause Event ID 55 and 5038 Audit Failure errors in Event Viewer. I have a 5038 Audit Failure error for every boot/reboot since I installed Antivir Personal version 9 on Oct 24. I have not yet had chkdsk run at boot but others who have Avira are currently reporting that they have chkdsk running at every boot until they uninstall Avira 9 after which time chkdsk never runs again. I was given a Hotfix from Avira to try last Friday. It solved the 5038 Audit Failure error immediately and some others who have the hotfix have reported that it also solved the problem with the volume being marked as dirty and chkdsk running on each boot (finding nothing amiss). For some though, this hotfix did not correct the problem. I have experienced crashing of avcenter.exe with a Runtime error three times since installing the hotfix. Avira is now saying that they are "leaning toward" this being a Microsoft bug rather than an Avira problem. They cite this article: http://www.pcpro.co.uk/blogs/2009/11/16/the-windows-7-chkdsk-bug-that-wont-go-away/ With this thread having been marked solved when obviously there is a problem which may or may not be an Avira problem, a Microsoft bug, or a combination of these, it does appear, as the blog's author points out, that Microsoft has put its head in the sand regarding this and is ignoring the increasing number of Windows 7 users reporting the problem. Permanently disabling chkdsk is NOT a viable solution. It seems obvious to me that in some cases, including mine, this problem stems from Avira as the hotfix has fixed the problem for me so far (while causing some instability in Antivir Personal). This is not the first time that an antivirus program has caused chkdsk problems. Kaspersky version 6 did this a few years ago causing severe damage in some cases. Thanks, I will look into this as I also use Antivir.

Here's one thread: http://forum.avira.com/wbb/index.php?page=Thread&threadID=100428 and a second: http://forum.avira.com/wbb/index.php?page=Thread&threadID=101735 There are more threads in both Premium and Personal forums and also involving Windows 7 64bit. OT: I haven't posted here in ages and I cannot remember how to have my post show up with paragraphs. I recall I had this problem here before and there is nothing in Help here about it. Maybe this forum doesn't like Opera 1010? That is the browser I use on Windows 7. In the past, the problem was on Firefox which I don't have installed on Windows 7.

True... seems that not only Avira makes this problems. Other AV (MS Security essentials) produce the same.

Well that is interesting I have MS Essentials, and the problem has returned.......- Bill

Hi..I am facing the same problem but in diffrent way i am using XP & win7 in dule boot & both OS's CHKDSK fight with each other.http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/b898585b-b497-476b-99f8-52d3b8e59fdbBut we still need solution to this... as chkdsk is eating data.

Sorry - hit "propose as answer" button inadvertently then. Meant to hit REPLY.The chkdsk problem seems to be widespread. I ended up disabling autochk to avoid it after installing W7 x64 on a brand new, out of the boxSamsung F3 HD. No Avira, which is often suggesed as a cause, but chkdskproblem existed since day one, with corresponding multiple "Event id55 (source: NTFS)" entries in eventlog. Recently, I re-enabled autochk, just to see if the problem was still occurring. Checked for dirty bit, and it was not set. Have rebootedmany times since then, and no chkdsk. Found that odd, so spent a long time looking at system event log. I noticed that my previously functioning Maxtor One Touch 4 Pus external drive had been identified as a problem by the system (citing out of date firmware), and disabled. I also noticed an Event ID 57 (seemingly linked to the id55 error previously mentioned), indicating that a cache had failed to flush, and warning of possible file corruption occurring before the system disabled the Maxtor, but not afterwards. Since then, no event id55s, and no chkdsk at boot. I'm not an expert (apologies for gatecrashing this forum), but I'm just wondering if it was the Maxtor that was causing the problems as it seems either to be malfunctioning or, more likely, not compatible with W7. Might be worth a try if anyone else has got an external HD attached and getting this problem.

Avira has recently stated in their tech blog that they are in contact with Microsoft regarding this issue. They say that in their research they have found that other AV vendors are also affected by this problem. Avira says that they have a workaround that will ship this week. They believe that eventually Microsoft will be issuing an update to Windows 7 to actually fix the problem but in the interium the workaround solves the issue. Avast 5 beta has this problem on Vista Ultimate. I installed it a few days ago after removing Avira 9 personal. I immediately saw the 5038 Security Audit errors in Event Viewer connected to two Avast drivers. While I was there I looked back in the history of the Security Audit logs. I am embarrassed to say that I had never really paid attention to those in the past. I have Vista on a virtual machine only and do not like Event Viewer in Vista. I far prefer the less verbose one in XP Pro which I run on my host machine. So, I had been avoiding Event Viewer in Vista except when I knew there would be an error I needed to see. Anyhow, I found the 5038 error from the day I first installed Avira 8 way back in the summer of 2008! I have that error for every boot/reboot from that day forward and then have it for Avast for the past several days. I am really puzzled now as I had believed Event ID 5038 to be the precursor to Event ID 55 yet I never have had chkdsk run at boot on Vista in all this time. Avira says that the volume is NOT dirty and the hard disk is NOT damaged but there is the 5038 error and then the 55 error which finds nothing wrong when chkdsk is run. This points to a Microsoft problem. Avira states that, at this point in time, Microsoft has been trying to pinpoint the exact problem but has not yet been able to do so. When they finally find it, I suspect Avira is correct in its speculation that Microsoft will issue an update for Windows7 and probably Vista also.