cant defrag c drive becuase of chkdsk self cancel win (xp home)

  • Thread starter Thread starter Matrix-27
  • Start date Start date
M

Matrix-27

this for my dad as this is his first comp .
got it for him for xmass and it worked fine and dandy.
just recently it wont let him derfrag the c drive as it says chkdsk is
schl'd to run. so he reboots and chkdsk starts ,then for some reason it
cancels itself like he hit esc to quit chkdsk.
i have seen this myself cuz i thought he was just canceling it himself. but
it still cancels out like someone hit the esc button with neither of us
around the keyboard.
any help would be great as he's starting to drive me nuts . lol
thanks ahead of time
 
this for my dad as this is his first comp .
got it for him for xmass and it worked fine and dandy.
just recently it wont let him derfrag the c drive as it says chkdsk is
schl'd to run. so he reboots and chkdsk starts ,then for some reason it
cancels itself like he hit esc to quit chkdsk.
i have seen this myself cuz i thought he was just canceling it himself. but
it still cancels out like someone hit the esc button with neither of us
around the keyboard.
any help would be great as he's starting to drive me nuts . lol
thanks ahead of time

Look in the Event Log for clues:

When chkdsk runs automatically on a reboot, the results are shown in
the Event Viewer Application
log.

To see the Event Viewer logs, click Start, Settings, Control Panel,
Administrative Tools, Event Viewer.

A shortcut to Event Viewer is to click Start, Run and in the box
enter:

%SystemRoot%\system32\eventvwr.msc

Click OK to launch the Event Viewer.

Look in the Application log for an event sourced by Winlogon,
something like:

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Description:
Checking file system on C:
The type of the file system is NTFS.


A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

39070048 KB total disk space.
25151976 KB in 78653 files.
48256 KB in 10264 indexes.
0 KB in bad sectors.
237080 KB in use by the system.
65536 KB occupied by the log file.
13632736 KB available on disk.

4096 bytes in each allocation unit.
9767512 total allocation units on disk.
3408184 allocation units available on disk.

Windows has finished checking your disk.
Please wait while your computer restarts.

If you need help looking at events from the log do this:

If you double click an event, it will open a Properties windows with
more information. On the right are
black up and down arrow buttons to scroll through the open events. The
third button that looks like
two pages on top of each other is used to copy the event details to
your Windows clipboard.

When you find an interesting event that occurred around the time of
your issue, click the third button
under the up and down arrows to copy the details and then you can
paste the details (right click, Paste
or CTRL-V) the detail text back here for analysis.

To get a fresh start on any Event Viewer log, you can choose to clear
the log (backing up the log is offered),
then reproduce your issue, then look at just the events around the
time of your issue.
 
Try run,type: cmd In cmd type: CLEANMGR Select C: Once thru,
type: Defrag C: Once thru,type: CHKDSK C: Type: CHKDSK C: /F
Agree to restart,type: EXIT Restart pc.
 
i tried what you said last nite and comp still does same thing and also
mixedup os it's xp pro not home dont think it matters much tho.
didnt get any disc's with the comp so reinstall is pretty much out of the
question,and he dosnt really want to bring it in to a shop to fix.
thinks it might be like a few min fix but the shop might say other wise and
charge a big bill. lol
 
what you can try is to boot
with an xp cd.

then at the setup screen
select repair to launch
the recovery console.

once you get to the disk
prompt run chkdsk /r

then exit, remove cd and
reboot computer.

a check disk will ensue
after booting.

however, it should be the
last time it runs.

--
--
db·´¯`·...¸><)))º>

DatabaseBen, Retired Professional

~~~~~~~~~~~~~~~
This NNTP newsgroup is evolving to:

http://answers.microsoft.com/en-us/default.aspx
 
i tried what you said last nite and comp still does same thing and also
mixedup os it's xp pro not home  dont think it matters much tho.
didnt get any disc's with the comp so reinstall is pretty much out of the
question,and he dosnt really want to bring it in to a shop to fix.
thinks it might be like a few min fix but the shop might say other wise and
charge a big bill.  lol

You are trying things. You need to figure out and fix things.

Chkdsk runs on boot if XP finds the drive "dirty".

After chkdsk runs on boot, the drive should be clean.

You need to look in the Event Log as indicated and see why chkdsk is
not finishing properly.

You do not need an XP CD to run Recovery Console - here are
instructions:

You can create a bootable XP Recovery Console CD when no XP media is
available:

http://www.bleepingcomputer.com/forums/topic276527.html

For each of your hard disks, you should then run:

chkdsk /r

For example, from the Recovery Console prompt, enter:

chkdsk c: /r

Running chkdsk /r from the Recovery Console will also clear the dirty
bit (if chkdsk /r completes successfully), but it would be more
interesting to see why XP can't do it itself. Running chkdsk /r from
Recovery Console will also let you see the results and what the
problem is on the screen.

Once you boot normally, you can even tell XP not to run chkdsk on the
dirty drive again (if the dirty bit will never clear for some
reason). It will not fix your problem of why it not behaving like it
should (that answer is in the Event Log), but chkdsk will not run when
XP boots again.
 
Back
Top