Each time that I start my computer, chkdsk runs the disk check of a partition
(NTFS, non-system) on my hard drive. If I cancel the check, the system (WinXP
Pro SP2) starts and runs fine. I've run several tests of my hard drive
(Norton Disk Doctor, SpinRite, Ontrack Data Advisor), but all of them say
that the HDD has no problems.
I've read the article "Chkdsk Runs Each Time That You Start Your Computer"
(http://support.microsoft.com/?kbid=316506) from Microsoft Knowledge Base,
but:
1) chkdsk don't prevent the system to start and work well on my computer
2) I don't use any scanners
3) I haven't upgraded Windows from any version.
So, can anybody tell me what can I do and how can I disable the chkdsk on
Windows start (if it's possible)?
Thanks in advance.

Check Disk runs on every boot.

Open a command prompt...
Start | Run | Type: cmd | Click OK |
Type or paste the following line:

chkntfs /d

Hit the Enter key.

Chkntfs displays or modifies the checking of disk at boot time.

The /d switch restores the machine to the default behavior; all drives are
checked at boot time and chkdsk is run on those that are dirty.

Autochk.exe is a version of Chkdsk that runs only before Windows XP
starts. Autochk runs in the following situations:

Autochk runs if you try to run Chkdsk on the boot volume.
Autochk runs if Chkdsk cannot gain exclusive use of the volume.
Autochk runs if the volume is flagged as dirty.

This can happen if the drive's dirty bit is set.
When a drive's dirty bit is set, autochk automatically
checks the volume for errors the next time the computer is restarted.

This will report whether the dirty bit is set.

Start | Run | Type: cmd | Click OK |
Type or paste the following line:

fsutil dirty query C:

Hit the Enter key.

Volume C: is not dirty
Volume C: is dirty

[[If a volume's dirty bit is set, this indicates that the file system may be
in an inconsistent state. The dirty bit can be set because the volume is
online and has outstanding changes, because changes were made to the volume
and the computer shutdown before the changes were committed to disk, or
because corruption was detected on the volume. If the dirty bit is set when
the computer restarts, chkdsk runs to verify the consistency of the volume.

Every time Windows XP starts, Autochk.exe is called by the Kernel to scan
all volumes to check if the volume dirty bit is set. If the dirty bit is
set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f
verifies file system integrity and attempts to fix any problems with the
volume.]]
-----

This will also report whether the dirty bit is set.

Start | Run | Type: cmd | Click OK |
Type or paste the following line:

chkntfs c:

Hit the Enter key.

C: is not dirty.
-----

If this is not the problem.....

Go here:
http://www.kellys-korner-xp.com/xp_tweaks.htm

Read the instructions at the top of the page.
Scroll down to:
82. Disable or Enable Check Disk Upon Boot
Click on Disable.
-----

Additional information...
Chkdsk.exe or Autochk.exe starts when you try to shut down or restart your
computer
http://support.microsoft.com/kb/831426

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In newsE965B4A-E1C8-4E89-8CDC-(E-Mail Removed),
Saf <(E-Mail Removed)> hunted and pecked:
> Each time that I start my computer, chkdsk runs the disk check of a
> partition (NTFS, non-system) on my hard drive. If I cancel the check, the
> system (WinXP Pro SP2) starts and runs fine. I've run several tests of my
> hard drive (Norton Disk Doctor, SpinRite, Ontrack Data Advisor), but all
> of them say that the HDD has no problems.
> I've read the article "Chkdsk Runs Each Time That You Start Your Computer"
> (http://support.microsoft.com/?kbid=316506) from Microsoft Knowledge Base,
> but:
> 1) chkdsk don't prevent the system to start and work well on my computer
> 2) I don't use any scanners
> 3) I haven't upgraded Windows from any version.
> So, can anybody tell me what can I do and how can I disable the chkdsk on
> Windows start (if it's possible)?
> Thanks in advance.

I have had this happen (intermittently, but frequently) as a result of
a memory module going bad (it had developed a few "stuck bits").

On Tue, 18 Jul 2006 12:08:02 -0700, Saf
<(E-Mail Removed)> wrote:

>Each time that I start my computer, chkdsk runs the disk check of a partition
>(NTFS, non-system) on my hard drive. If I cancel the check, the system (WinXP
>Pro SP2) starts and runs fine. I've run several tests of my hard drive
>(Norton Disk Doctor, SpinRite, Ontrack Data Advisor), but all of them say
>that the HDD has no problems.
>I've read the article "Chkdsk Runs Each Time That You Start Your Computer"
>(http://support.microsoft.com/?kbid=316506) from Microsoft Knowledge Base,
>but:
>1) chkdsk don't prevent the system to start and work well on my computer
>2) I don't use any scanners
>3) I haven't upgraded Windows from any version.
>So, can anybody tell me what can I do and how can I disable the chkdsk on
>Windows start (if it's possible)?
>Thanks in advance.

Please respond to the Newsgroup, so that others may benefit from the exchange.
Peter R. Fletcher

Thank you very much, Wesley, for your valuable answer. The volume's dirty bit
is set, really. I'll try to run chkdsk from Recovery Console as soon as I
find my WinXP installation disk But can I do anything else to make dirty
bit go away?
P. S.: Why can't I rate posts? Don't see any button like "Rate this post".

"Wesley Vogel" wrote:

> Check Disk runs on every boot.
>
> Open a command prompt...
> Start | Run | Type: cmd | Click OK |
> Type or paste the following line:
>
> chkntfs /d
>
> Hit the Enter key.
>
> Chkntfs displays or modifies the checking of disk at boot time.
>
> The /d switch restores the machine to the default behavior; all drives are
> checked at boot time and chkdsk is run on those that are dirty.
>
> Autochk.exe is a version of Chkdsk that runs only before Windows XP
> starts. Autochk runs in the following situations:
>
> Autochk runs if you try to run Chkdsk on the boot volume.
> Autochk runs if Chkdsk cannot gain exclusive use of the volume.
> Autochk runs if the volume is flagged as dirty.
>
> This can happen if the drive's dirty bit is set.
> When a drive's dirty bit is set, autochk automatically
> checks the volume for errors the next time the computer is restarted.
>
> This will report whether the dirty bit is set.
>
> Start | Run | Type: cmd | Click OK |
> Type or paste the following line:
>
> fsutil dirty query C:
>
> Hit the Enter key.
>
> Volume C: is not dirty
> Volume C: is dirty
>
> [[If a volume's dirty bit is set, this indicates that the file system may be
> in an inconsistent state. The dirty bit can be set because the volume is
> online and has outstanding changes, because changes were made to the volume
> and the computer shutdown before the changes were committed to disk, or
> because corruption was detected on the volume. If the dirty bit is set when
> the computer restarts, chkdsk runs to verify the consistency of the volume.
>
> Every time Windows XP starts, Autochk.exe is called by the Kernel to scan
> all volumes to check if the volume dirty bit is set. If the dirty bit is
> set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f
> verifies file system integrity and attempts to fix any problems with the
> volume.]]
> -----
>
> This will also report whether the dirty bit is set.
>
> Start | Run | Type: cmd | Click OK |
> Type or paste the following line:
>
> chkntfs c:
>
> Hit the Enter key.
>
> C: is not dirty.
> -----
>
> If this is not the problem.....
>
> Go here:
> http://www.kellys-korner-xp.com/xp_tweaks.htm
>
> Read the instructions at the top of the page.
> Scroll down to:
> 82. Disable or Enable Check Disk Upon Boot
> Click on Disable.
> -----
>
> Additional information...
> Chkdsk.exe or Autochk.exe starts when you try to shut down or restart your
> computer
> http://support.microsoft.com/kb/831426
>
> --
> Hope this helps. Let us know.
>
> Wes
> MS-MVP Windows Shell/User
>
> In newsE965B4A-E1C8-4E89-8CDC-(E-Mail Removed),
> Saf <(E-Mail Removed)> hunted and pecked:
> > Each time that I start my computer, chkdsk runs the disk check of a
> > partition (NTFS, non-system) on my hard drive. If I cancel the check, the
> > system (WinXP Pro SP2) starts and runs fine. I've run several tests of my
> > hard drive (Norton Disk Doctor, SpinRite, Ontrack Data Advisor), but all
> > of them say that the HDD has no problems.
> > I've read the article "Chkdsk Runs Each Time That You Start Your Computer"
> > (http://support.microsoft.com/?kbid=316506) from Microsoft Knowledge Base,
> > but:
> > 1) chkdsk don't prevent the system to start and work well on my computer
> > 2) I don't use any scanners
> > 3) I haven't upgraded Windows from any version.
> > So, can anybody tell me what can I do and how can I disable the chkdsk on
> > Windows start (if it's possible)?
> > Thanks in advance.
>
>

Thanks, Peter. I hope my RAM is OK, but I'll test it if required. How did you
find out that it was RAM in particular that caused the problem?

"Peter R. Fletcher" пишет:

> I have had this happen (intermittently, but frequently) as a result of
> a memory module going bad (it had developed a few "stuck bits").
>
> On Tue, 18 Jul 2006 12:08:02 -0700, Saf
> <(E-Mail Removed)> wrote:
>
> >Each time that I start my computer, chkdsk runs the disk check of a partition
> >(NTFS, non-system) on my hard drive. If I cancel the check, the system (WinXP
> >Pro SP2) starts and runs fine. I've run several tests of my hard drive
> >(Norton Disk Doctor, SpinRite, Ontrack Data Advisor), but all of them say
> >that the HDD has no problems.
> >I've read the article "Chkdsk Runs Each Time That You Start Your Computer"
> >(http://support.microsoft.com/?kbid=316506) from Microsoft Knowledge Base,
> >but:
> >1) chkdsk don't prevent the system to start and work well on my computer
> >2) I don't use any scanners
> >3) I haven't upgraded Windows from any version.
> >So, can anybody tell me what can I do and how can I disable the chkdsk on
> >Windows start (if it's possible)?
> >Thanks in advance.
>
> Please respond to the Newsgroup, so that others may benefit from the exchange.
> Peter R. Fletcher
>

Thanks, Peter. I hope my RAM is OK, but I'll test it if required. How did you
find out that it was RAM in particular that caused the problem?

"Peter R. Fletcher" пишет:

> I have had this happen (intermittently, but frequently) as a result of
> a memory module going bad (it had developed a few "stuck bits").
>
> On Tue, 18 Jul 2006 12:08:02 -0700, Saf
> <(E-Mail Removed)> wrote:
>
> >Each time that I start my computer, chkdsk runs the disk check of a partition
> >(NTFS, non-system) on my hard drive. If I cancel the check, the system (WinXP
> >Pro SP2) starts and runs fine. I've run several tests of my hard drive
> >(Norton Disk Doctor, SpinRite, Ontrack Data Advisor), but all of them say
> >that the HDD has no problems.
> >I've read the article "Chkdsk Runs Each Time That You Start Your Computer"
> >(http://support.microsoft.com/?kbid=316506) from Microsoft Knowledge Base,
> >but:
> >1) chkdsk don't prevent the system to start and work well on my computer
> >2) I don't use any scanners
> >3) I haven't upgraded Windows from any version.
> >So, can anybody tell me what can I do and how can I disable the chkdsk on
> >Windows start (if it's possible)?
> >Thanks in advance.
>
> Please respond to the Newsgroup, so that others may benefit from the exchange.
> Peter R. Fletcher
>

Other bad things also started happening occasionally, so I ran a RAM
test, which picked up the stuck bits. Replacing the RAM cured ALL the
problems.

On Wed, 19 Jul 2006 07:08:02 -0700, Saf
<(E-Mail Removed)> wrote:

>Thanks, Peter. I hope my RAM is OK, but I'll test it if required. How did you
>find out that it was RAM in particular that caused the problem?
>
>"Peter R. Fletcher" ?????:
>
>> I have had this happen (intermittently, but frequently) as a result of
>> a memory module going bad (it had developed a few "stuck bits").
>>
>> On Tue, 18 Jul 2006 12:08:02 -0700, Saf
>> <(E-Mail Removed)> wrote:
>>
>> >Each time that I start my computer, chkdsk runs the disk check of a partition
>> >(NTFS, non-system) on my hard drive. If I cancel the check, the system (WinXP
>> >Pro SP2) starts and runs fine. I've run several tests of my hard drive
>> >(Norton Disk Doctor, SpinRite, Ontrack Data Advisor), but all of them say
>> >that the HDD has no problems.
>> >I've read the article "Chkdsk Runs Each Time That You Start Your Computer"
>> >(http://support.microsoft.com/?kbid=316506) from Microsoft Knowledge Base,
>> >but:
>> >1) chkdsk don't prevent the system to start and work well on my computer
>> >2) I don't use any scanners
>> >3) I haven't upgraded Windows from any version.
>> >So, can anybody tell me what can I do and how can I disable the chkdsk on
>> >Windows start (if it's possible)?
>> >Thanks in advance.
>>
>> Please respond to the Newsgroup, so that others may benefit from the exchange.
>> Peter R. Fletcher
>>

Please respond to the Newsgroup, so that others may benefit from the exchange.
Peter R. Fletcher

At last I found my WXP installation disk. So I ran chkdsk command from
Recovery Console. It found and corrected errors on the problem partition.
Then I ran fixboot command. It showed that the boot sector on the partition
(that contained set dirty bit) was damaged. Then it wrote the new boot sector
and it solved the problem - chkdsk doesn't run on every boot.
By the way, it is possible to simply disable autochk.exe by using chkntfs /x
command. This excludes a drive from the default boot-time check.
Wesley Vogel, you helped a lot. Thank you very much once again.

"Saf" wrote:

> Each time that I start my computer, chkdsk runs the disk check of a partition
> (NTFS, non-system) on my hard drive. If I cancel the check, the system (WinXP
> Pro SP2) starts and runs fine. I've run several tests of my hard drive
> (Norton Disk Doctor, SpinRite, Ontrack Data Advisor), but all of them say
> that the HDD has no problems.
> I've read the article "Chkdsk Runs Each Time That You Start Your Computer"
> (http://support.microsoft.com/?kbid=316506) from Microsoft Knowledge Base,
> but:
> 1) chkdsk don't prevent the system to start and work well on my computer
> 2) I don't use any scanners
> 3) I haven't upgraded Windows from any version.
> So, can anybody tell me what can I do and how can I disable the chkdsk on
> Windows start (if it's possible)?
> Thanks in advance.

Glad to hear that you got it fixed.

You can also delete every thing in the Value Data for BootExecute here..
HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\Session Manager

The actual purpose of chkntfs /x is to postpone chkdsk from running when the
dirty bit is set until a more convenient time. I assume that this was
origianlly for servers or other machines that running chkdsk would be
inconvenient.

<quote>
The chkntfs utility works by modifying the BootExcecute value in the system
registry. The BootExecute value is located in the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\Session Manager

The default value is:
BootExecute:REG_MULTI_SZ:autocheck autochk *

Chkntfs /x adds a /k parameter prior to the asterisk. The /k parameter
excludes volumes from being checked for the presence of a dirty bit.
<quote>
CHKNTFS.EXE: What You Can Use It For
http://support.microsoft.com/kb/160963

Method 2 here addresses how to the same thing manually.

Chkdsk.exe or Autochk.exe starts when you try to shut down or restart your
computer
http://support.microsoft.com/kb/831426

<quote>
For heavily used computers that cannot be offline for the length of time
required to complete the repair process, you can use the Chkntfs.exe
command-line tool to exclude dirty volumes from being checked by Autochk.
You can also use Chkntfs to cancel previously scheduled sessions of Autochk
and to check the status of a volume.

Caution
If a volume is flagged as dirty, do not postpone running Chkdsk
indefinitely. File system damage can become worse over time, so you must
consider dirty volumes at risk until you run Chkdsk. Use Chkntfs only if you
need to control when Chkdsk is run.

Using the /x Parameter to Exclude Volumes
Use the /x parameter to prevent Autochk from running at startup on dirty
volumes. Although it is not recommended that you use this parameter to
postpone running Autochk indefinitely, you can use this parameter to prevent
Autochk from running. For example, when you know the volume is dirty, you
can use the /x parameter to postpone running Autochk until a period of low
computer activity, such as overnight or during the weekend.
<quote>
Using Chkntfs to Prevent Autochk from Running
http://www.microsoft.com/resources/d...d_tro_rgwn.asp

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:AB0C3597-1E2E-4D89-9B3B-(E-Mail Removed),
Saf <(E-Mail Removed)> hunted and pecked:
> At last I found my WXP installation disk. So I ran chkdsk command from
> Recovery Console. It found and corrected errors on the problem partition.
> Then I ran fixboot command. It showed that the boot sector on the
> partition (that contained set dirty bit) was damaged. Then it wrote the
> new boot sector and it solved the problem - chkdsk doesn't run on every
> boot.
> By the way, it is possible to simply disable autochk.exe by using chkntfs
> /x command. This excludes a drive from the default boot-time check.
> Wesley Vogel, you helped a lot. Thank you very much once again.
>
> "Saf" wrote:
>
>> Each time that I start my computer, chkdsk runs the disk check of a
>> partition (NTFS, non-system) on my hard drive. If I cancel the check,
>> the system (WinXP Pro SP2) starts and runs fine. I've run several tests
>> of my hard drive (Norton Disk Doctor, SpinRite, Ontrack Data Advisor),
>> but all of them say that the HDD has no problems.
>> I've read the article "Chkdsk Runs Each Time That You Start Your
>> Computer" (http://support.microsoft.com/?kbid=316506) from Microsoft
>> Knowledge Base, but:
>> 1) chkdsk don't prevent the system to start and work well on my computer
>> 2) I don't use any scanners
>> 3) I haven't upgraded Windows from any version.
>> So, can anybody tell me what can I do and how can I disable the chkdsk on
>> Windows start (if it's possible)?
>> Thanks in advance.

What a useful information you share here, Wes! Many thanks.

"Wesley Vogel" пишет:

> Glad to hear that you got it fixed.
>
> You can also delete every thing in the Value Data for BootExecute here..
> HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\Session Manager
>
> The actual purpose of chkntfs /x is to postpone chkdsk from running when the
> dirty bit is set until a more convenient time. I assume that this was
> origianlly for servers or other machines that running chkdsk would be
> inconvenient.
>
> <quote>
> The chkntfs utility works by modifying the BootExcecute value in the system
> registry. The BootExecute value is located in the following registry key:
>
> HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\Session Manager
>
> The default value is:
> BootExecute:REG_MULTI_SZ:autocheck autochk *
>
> Chkntfs /x adds a /k parameter prior to the asterisk. The /k parameter
> excludes volumes from being checked for the presence of a dirty bit.
> <quote>
> CHKNTFS.EXE: What You Can Use It For
> http://support.microsoft.com/kb/160963
>
> Method 2 here addresses how to the same thing manually.
>
> Chkdsk.exe or Autochk.exe starts when you try to shut down or restart your
> computer
> http://support.microsoft.com/kb/831426
>
> <quote>
> For heavily used computers that cannot be offline for the length of time
> required to complete the repair process, you can use the Chkntfs.exe
> command-line tool to exclude dirty volumes from being checked by Autochk.
> You can also use Chkntfs to cancel previously scheduled sessions of Autochk
> and to check the status of a volume.
>
> Caution
> If a volume is flagged as dirty, do not postpone running Chkdsk
> indefinitely. File system damage can become worse over time, so you must
> consider dirty volumes at risk until you run Chkdsk. Use Chkntfs only if you
> need to control when Chkdsk is run.
>
> Using the /x Parameter to Exclude Volumes
> Use the /x parameter to prevent Autochk from running at startup on dirty
> volumes. Although it is not recommended that you use this parameter to
> postpone running Autochk indefinitely, you can use this parameter to prevent
> Autochk from running. For example, when you know the volume is dirty, you
> can use the /x parameter to postpone running Autochk until a period of low
> computer activity, such as overnight or during the weekend.
> <quote>
> Using Chkntfs to Prevent Autochk from Running
> http://www.microsoft.com/resources/d...d_tro_rgwn.asp
>
> --
> Hope this helps. Let us know.
>
> Wes
> MS-MVP Windows Shell/User
>
> In news:AB0C3597-1E2E-4D89-9B3B-(E-Mail Removed),
> Saf <(E-Mail Removed)> hunted and pecked:
> > At last I found my WXP installation disk. So I ran chkdsk command from
> > Recovery Console. It found and corrected errors on the problem partition.
> > Then I ran fixboot command. It showed that the boot sector on the
> > partition (that contained set dirty bit) was damaged. Then it wrote the
> > new boot sector and it solved the problem - chkdsk doesn't run on every
> > boot.
> > By the way, it is possible to simply disable autochk.exe by using chkntfs
> > /x command. This excludes a drive from the default boot-time check.
> > Wesley Vogel, you helped a lot. Thank you very much once again.
> >
> > "Saf" wrote:
> >
> >> Each time that I start my computer, chkdsk runs the disk check of a
> >> partition (NTFS, non-system) on my hard drive. If I cancel the check,
> >> the system (WinXP Pro SP2) starts and runs fine. I've run several tests
> >> of my hard drive (Norton Disk Doctor, SpinRite, Ontrack Data Advisor),
> >> but all of them say that the HDD has no problems.
> >> I've read the article "Chkdsk Runs Each Time That You Start Your
> >> Computer" (http://support.microsoft.com/?kbid=316506) from Microsoft
> >> Knowledge Base, but:
> >> 1) chkdsk don't prevent the system to start and work well on my computer
> >> 2) I don't use any scanners
> >> 3) I haven't upgraded Windows from any version.
> >> So, can anybody tell me what can I do and how can I disable the chkdsk on
> >> Windows start (if it's possible)?
> >> Thanks in advance.
>
>