I had the same problem. It was due to bad shutdown practices. Good luck.
G'day
Had the same problem with chkdsk running every time I booted up. The tips you gave to reset the chkdsk startup worked a treat. It even found some errors on the drive and fixed them with the cmd chkdsk run.
Thanks again, I will come often and query other issues from now on.
radarak47
This fixed the problem thanks a lot. This was the exact solution for my pcs problem.
very straight solution !
I upgraded my Symantec Norton System Works which included Go Back. The install went ok but when I rebooted the system hung on the Go Back screen. I tried unhooking Go Back and rebooted. I then got stuck on the Go Back screen which recycled over and over. I did some research and found out that Go Back sets up a protected partition which was part of the problem. I found a handy tool on the Web which allowed me to correct the partition issue. I had to boot off a floppy and run the tool. Once that was fixed I rebooted but got the chkdsk thing. When I found this useful info I used the method as described by Darin S. and it worked perfectly. Thanks Darin for your great bit of info.
John B.
I had this same problem and it took me forever to fix it. None of the different suggestions posted in this forum so far worked for me. The fix turned out to be simple, but I never saw it suggested anywhere; it was the result of an intuitive guess based on years of building PCs, plus some desperation.
All I had to do was SWAP THE TWO DRIVES on my IDE cable. I have an Abit motherboard with an AMD X2 3800+. The IDE cable that came with the motherboard has the far end labeled "master" and the near end labeled "slave." I ignored this when installing my drives, figuring that all that mattered was how I jumpered them. (That's been my experience in the past.) So my boot drive was jumpered as the master and my CD drive was jumpered as slave, but I had the boot drive hooked up to the near end (i.e., the end nearest the motherboard) and the CD drive hooked up to the far end.
When I swapped them, my scandisk problem went away. So: check to be sure the drive jumpered as master is on the far end of the IDE cable, and the drive jumpered as slave is on the near end of the cable. If you have only one drive, make sure it's on the far end.
I have no explanation for why this worked, but I know that for floppy drives, the A: drive is always the one hooked to the far end of the cable, so apparently in some drive subsystems, location of the drive on the ribbon cable can make a big difference.
thanks for your valuable solution darwin s , i almost tried evry silly thing: restored ma computer, tried "last known good configuration", and was heading to format ma computer and install windows afresh, but something made me to give it another try so i searched google for the solution one last time and i found this article and good lord!! it worked thank u
. my 1 hour search paid off.
farwa.
i found tht buy substuting the d with a c for c drive i could fix my problum srry i cant spell stuff lol
Hiya
I followed your above answer and got as far as going back into Command Prompt and typing chkdsk /f /r C:. It then said chkdsk could not run because the volume was in use by another process. It asks if I want the volume to be checked at the next restart.
So I have a couple of questions :-
would a scheduled check achieve the same goal and reset the Dirty Bit?
should I boot up in safe mode and run the cmd line syntax above?
Thanx for any help on this one
In response to the following written by Darin S.:
"How do I fix it, you ask?
Well, that's easy. First click Start> Run> bring up a command prompt by typing in "CMD" and type " fsutil dirty query d: ". This queries the drive, and more than likely it will tell you that it is dirty. Next, type "CHKNTFS /X D:". The X tells Windows to NOT check that particular drive on the next reboot. At this time, manually reboot your computer, it should not do a Chkdsk and take you directly to Windows."
DO NOT DO THIS IF YOU ARE RUNNING WINDOWS VISTA!!!
I turned on my chkdsk scheduler, not realizing how many hours it would take to run the 5 stage scan. This dirtied my drive so that it kept asking to check the disk on startup, which I had no time to do as this is my laptop which I need to work on.
So I tried following Darin's advice to tell Windows not to run chkdsk on bootup, and lo and behold, instead of a scan I now get a BLUE SCREEN OF DEATH - on startup. The computer is toast now, and there's no way for me to get in to change anything back to where it was. I am now FORMATTING my harddrive through the Windows Recovery Disk to reinstall the OS and will waste another 20+ hours of my time setting this system back up again - after losing a month's worth of irreplaceable files.
This is the last time I will ever run or schedule a chkdsk on Vista ever again, as soon as I get this computer re-installed. I have no idea why Microsoft would develop this system of dirtying drives so that the only way to undirty them is to spend 24 hours scanning it. I am royally peeved off.
| Forum legend: | |
| Locked thread | |
| Moderator | |
![]() |
CNET staff |
![]() |
Samsung staff |
| Norton Authorized Support team | |
| AVG staff | |
| Windows Outreach team | |
![]() |
Dell staff |
| Intel staff | |