Need advice on running Chk dsk on Windows XP

Started by pastywhitegurl, June 06, 2011, 02:01:43 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

pastywhitegurl

I'm gong to be unable to continue working on this until this weekend, unfortunately.  So please keep this topic open till then. Thanks! :)

Corrine

Photoshop uses a lot of resources, so it is likely there will be times that it will just crash.  As to Firefox, I note that you have Firebug installed.  It is one of the slowest performing add-ons.  See Slow Performing Add-ons :: Add-ons for Firefox.  You can test Firefox in Safe Mode going to Firefox > Help > Restart With Add-ons Disabled. 


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

pastywhitegurl

Ran the /f function of chckdsk tonight  ( automatically fix file system errors )

It took about 5 minutes to complete.   But the report didn't stay on the screen long enough for me to read it. :(


So how do I find the report?  I couldn't figure that out from the documentation.  I assume I used the auto-check since it ran the chckdsk function after a reboot.  I found this about a report:
"If you choose to let Autochk run, you can review the Autochk report in the application log of the Event Viewer snap-in. Autochk information is logged by the Winlogon service, so look for entries with Winlogon listed as the source of the entry."
But I have no idea what an event view snap in is.

I did not run this operation:
Scan for and attempt recovery of bad sectors

Reason: I was confused as to whether it was an either/or choice or not.  Should I do this again and run that part?

pastywhitegurl

I found  the autochk report:

Log:

Checking file system on C:
The type of the file system is NTFS.
Volume label is Local Disk.


A disk check has been scheduled.
Windows will now check the disk.                        
Cleaning up minor inconsistencies on the drive.
Cleaning up 1944 unused index entries from index $SII of file 0x9.
Cleaning up 1944 unused index entries from index $SDH of file 0x9.
Cleaning up 1944 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Windows has made corrections to the file system.

312560608 KB total disk space.
 34858912 KB in 178328 files.
    71360 KB in 15009 indexes.
        0 KB in bad sectors.
   382600 KB in use by the system.
    65536 KB occupied by the log file.
277247736 KB available on disk.

     4096 bytes in each allocation unit.
 78140152 total allocation units on disk.
 69311934 allocation units available on disk.

Internal Info:
e0 fd 02 00 44 f3 02 00 e9 8a 04 00 00 00 00 00  ....D...........
12 49 00 00 02 00 00 00 8a 0e 00 00 00 00 00 00  .I..............
c4 3e b2 0e 00 00 00 00 b2 7b 44 79 00 00 00 00  .>.......{Dy....
ce 9a ea 1f 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 8a 07 22 b5 00 00 00 00  ..........".....
60 40 22 83 00 00 00 00 98 38 07 00 98 b8 02 00  `@"......8......
00 00 00 00 00 80 9e 4f 08 00 00 00 a1 3a 00 00  .......O.....:..

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

Corrine

Other than Photoshop and Firefox occasionally freezing -- which will likely continue to occur, regardless of the utilities you run based on my comments above -- you'll now need to sit back and see how your computer performs. :)


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

pastywhitegurl

ok. will do.

So far no change in the shutdown sequence. I still have to power completely down to get windows to shut off.

I use FireBug constantly, so if it is causing an issue, I guess I will just put up with it.   I'll try the safe-mode test later today and see if I can determine anything about it.


It doesn't seem like chckdsk found much wrong. So I suppose that is a good sign.