CHKDSK runs every time I boot!

Thanks Knoj!! I had this problem for months and couldn't solve it by my means. Your fix worked immediately saving me a few more seconds upon startup for an old and slow laptop.

You deserve a raise!

Thanx a bundle for this tip. I was having a hell of a time stopping chkdsk on startup and was about to ditch the hard drive when I found this solution....pure genius. It works brill. Thanxs, thanxs

I installed a new 3rd hard drive on a Win XP machine , and configured the mft and paging file with diskeeper 9. A Chkdsk seemed to be required. After that, every time i booted the machine , it persisted doing a chkdsk on e,g,h an i partitions (a total of 750 gb !). One can imagine what that did to my cardiovascular system.
I found this thread , took me all of 5 minutes roblem solved.
My blood pressure is back to normal.
Thanks.

Wow. Awesome. Chkdsk problem of several months duration fixed in less than a minute. Many many thanks for this fix. Worked like a charm.

One more thank you to this list, awesome help !
I've identified the faulty driver that was doing that to my drive, the MB's SATA drivers. Seems to work slower but safer with the generic IDE drivers.
Thanks again !

Hi to all!
In my PC, the last time there is a chkdsk every single boot (3 steps):
When I run AusLogics Disk Defrag on disk C:, at the end appears an
alert:

"Diskdefrag.exe - Corrupt file
The file or directory c:/Windows/System32/hal.dll is corrupt and unreadable.
Please run the Chkdsk utility."

I run it, but this no solve the problem!

I try this way:

C:fsutil dirty query c:
Volume - c: is dirty

C:>chkdsk c: /f/x
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

I choose "Y" and ends.
But, later, when the PC boot, chkdsk runs (3 steps) but nothing happens.
The problem persist.
Any idea?
Thanks a lot,
calocaloo

You can't do the above actions from inside XP because this is your active system partition.
Try something like this :

1. Insert and boot from your Windows XP CD.
2. At the first R=Repair option, press the R key.
3. Press the number that corresponds to the correct location for the installation of Windows you want to repair.Typically this will be #1.
4. Type "chkdsk /f" to run once again the chkdsk(you may want to skip this if you trust your drive to be fully functional).
5. Type "bootcfg /list" to show the current entries in the BOOT.INI file. Type "bootcfg /rebuild" to repair it.
6. Take out the CD ROM and type "exit".

Hi Shoddan & Knoj,

After Windows XP insertion and boot my machine,
instead the "Windows XP Professional Setup" screen, appears the following text
in screen:


A PROBLEM HAS BEEN DETECTED AND WINDOWS HAD BEEN SHUT DOWN TO PREVENT DAMAGE TO TOUR COMPUTER.
IF THIS IS THE FIRST TIME YOU'VE SEEN THIS STOP ERROR SCREEN, RESTART YOUR COMPUTER. IF THIS SCREEN APPEARS
AGAIN, FOLLOW THIS STEPS:
CHECK TO BE SURE YOU HAVE ADECUATE DISK SPACE. IF THE DRIVER IS IDENTIFIED IN THE STOP MESSAGE, DISABLE
THE DRIVER OR CHECK WITH THE MANUFACTURER FO DRIVES UPDATES. TRY CHECKING VIDEO ADAPTERS.
CHECK WITH YOUR HARDWARE VENDOR FOR ANY BIOS UPDATES. DISABLE BIOS MEMORY OPTIONS SUCH AS CACHING OR
SHADOWING. IF YOU NEED TO USE SAFE MODE TO REMOVE OR DISABLE COMPONENTS, RESTART YOUR COMPUTER, PRESS
F8 TO SELECT ADVANCED STARTUP OPTIONS, AND THEN SELECT SAFE MODE.
TECHNICAL INFORMATION:
***STOP: OxOOOOOO7E (OxCOOOOOO5, OxF748EOBF, OxF78DA208, OxF78D9FO8)
***pci.sys Address F748E0bf base at F7487000, DateStamp 3b7d855c


Of course I have a lot of space in my disk.
What can I do?
A lot of thanks
calocaloo

The solution in this thread re/ fixing the dirty disk with fsutil was very helpful to me!
My problem was similar but just enough different to not be documented anywhere on the internet (that I could find).

I have a 2GB Sandisk U3 Flash Drive / memory stick. For the last 6 weeks, windows would not let me eject it (eject utilities would unmount the drive but not stop it, and then freeze every time I tried), and if I just got fed up and pulled it out, the drive would not remount again until I reboot my computer. Curiously, it worked on every computer but my desktop (For those in the know: Is "dirty" something written on the drive itself, or held by the OS as information somewhere in its internal workings?).

Today I finally checked its dirty status after having used this solution on my D-drive - coupling the two events that windows wanted to chkdsk my d-drive ever since it stopped working with the flash drive. Anyway, I ran fsutil/chkdsk on the flash drive, and now it works like it was intended.

Just posting this in the thought that someone out there might have a similar problem with their flash drive one day. Thanks again, this solution was very helpful.

http://forums.techguy.org/all-other...-drive-not.html

&/or

http://www.hftonline.com/forum/showthread.php?t=18615

List a "work-around" for this, in regards to a SPECIFIC error apparently caused by the "INDEXING SERVICE" (see services.msc for that), & it has worked a couple times for myself @ work on the job, as well as a couple times on forums, where the symptoms manifested themselves the same (indexing problem).

STEPS:

Go to the disk in question in Windows using explorer.exe (or, My Computer), & right-click on it to summon its popup menu, & use the PROPERTIES menu there.

Once in it, uncheck the "Allow Indexing Service to Index this disk for fast file searching", first.

(& while you're @ it, do it for your other disks too, & disable the INDEXING service in services.msc as well. Might as well @ this point, right? I personally don't find this service useful enough to keep it constantly running either, but that's personal opinion!).

===========================================

ANYHOW, ONCE INDEXING SERVICE IS OFF WHOLESALE via SERVICES.MSC, or JUST FOR THE DISK IN QUESTION?

Boot your system to RECOVERY CONSOLE from your OS install disk, & issue the commandline of:

chkdsk /p /r

Actual details are here (my commandline's a "BIT of overkill", but forces every switch needed, regardless of one overriding the other):

-----

http://support.microsoft.com/kb/314058

CHKDSK

chkdsk drive /p /r
The chkdsk command checks the specified drive and repairs or recovers the drive if the drive requires it.The command also marks any bad sectors and it recovers readable information.

You can use the following options:
/p : Does an exhaustive check of the drive and corrects any errors.
/r : Locates bad sectors and recovers readable information.

Note If you specify the /r option, the /p option is implied. When you specify the chkdsk command without arguments, the command checks the current drive with no options in effect.

When you run the chkdsk command, you are required to use the Autochk.exe file. CHKDSK automatically locates this file in the startup folder. If the Command Console was preinstalled, the startup folder is typically the Cmdcons folder. If CHKDSK cannot find Autochk.exe in the startup folder, CHKDSK tries to locate the Windows CD-ROM installation media. If it cannot find the installation media, CHKDSK prompts you for the location of the Autochk.exe file.

-----

& let it correct the problems on the disk that is troubled.

===========================================

The pertinent excerpt is "straight from the horses' mouth" (MS), & for the Recovery Console/RC chkdsk for your hassle is above, & what I used, exactly, & it worked for a very similar hassle.

The RC version of chkdsk It is more effective than the chkdsk (commandline OR graphical front to it in the disk tools you have access to via the rightclick menu you had used above to remove indexing) that running under "normal Windows" uses!

Also, since Windows is NOT operating really (RC is NOT the same as DOS or Windows really), files that might be locked against access typically are no longer locked in RC, vs. normal Windows operation (even SafeMode(s)).

It may help you here. As again, it did for me, in a VERY similar "pinch"...

APK