I am running Xp & a few days ago my PC locked up so I had to manually switch it off

Ever since then as soon as I start the PC I get the message on a blue screen

Checking File system on D: (my hard disc is split into C & D) The type of file system is NTFS

etc etc etc

It gives you a few seconds to by pass it by hitting any key & then proceeds to run it, I have run it several times & its always OK, It wont let me defrag the disc as every time I try that it asks for the check to be run again. I have run an on line check on the disc & its fine, I have checked scheduled tasks & its not listed

Anyone any thoughts Please

use something else to defrag the windows app is pants

use something else to defrag the windows app is pants

not to worried about the defrag bit, I just want to stop the check disc every time I fire up the PC

1st - MAKE SURE EVERYTHING YOU HAVE IS BACKED UP. WELL. AND TEST THAT THE BACKUP WORKS.

Then running a physical check on the disk - this will take some time. Ask for a scan as normal, then check *both* boxes ("Automatically ..." and "Scan for and ...")

It will restart and the check may run into hours.

1st - MAKE SURE EVERYTHING YOU HAVE IS BACKED UP. WELL. AND TEST THAT THE BACKUP WORKS.

Then running a physical check on the disk - this will take some time. Ask for a scan as normal' date=' then check *both* boxes ("Automatically ..." and "Scan for and ...")

It will restart and the check may run into hours.[/quote']

Backing up every night so hopefully thats covered

re the physical check, I have done the Start - My Computer - Right click over D: - Properties - Tick Both Boxes & run, Did 5 segments of checks, took about an hour & was all OK.

It appears to be an XP Problem where every time you fire up the Disc Check is carried out yet its not listed in Scheduled tasks. When you try to defrag it also says chk disc is scheduled to be carried out, its sort of in a bit of a loop

Stuart

If you're sure the disk is physically OK, check that the following registry key ...

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\BootExecute

... reads ...

autocheck autochk *

If it already reads just this then the "dirty bit" on the NTFS partition is not being properly reset for some reason. This can be reset manually, but requires use of a disk editor and nerves of steel!

I'm having a bit of trouble posting to Briskoda from work, so if you need any further help and nobody else notices this thread, please PM me an e-mail address.

If you're sure the disk is physically OK' date=' check that the following registry key ...

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\BootExecute

... reads ...

autocheck autochk *

If it already reads just this then the "dirty bit" on the NTFS partition is not being properly reset for some reason. This can be reset manually, but requires use of a disk editor and nerves of steel!

I'm having a bit of trouble posting to Briskoda from work, so if you need any further help and nobody else notices this thread, please PM me an e-mail address.[/quote']

Thanks but Im a computer numptie !!!! can you guide me from the very begining to find the registry key bit. As for the second bit, The first packages I used on a PC back in the 80's everything ran in Dos & I ****ed up many times & had to be saved by others, hence my fear of doing anything too major so nerves of steel I definately dont have.

I also need to be careful as this PC Earns me my living & at the moment its running OK once started. Im just trying to avoid having to pay someone a load of money to fix it although if it comes to that I would rather pay a Briskodian rather than a stranger.

If anyone genuinly knows what they are doing & fancies earning a large beer PM me or mail me on [email protected]

I may be quoting the obvious but why not use system restore and put the PC back to a couple of days before the "whoops" should be OK then

I've just remembered that fsutil comes with WindowsXP - so we should at least be able to read the dirty bit without a disk editor

Des, System Restore probably won't sort this out, although trying it might be a last resort, depending on how long ago the snapshot was done.