Need help with a Blue CHKDSK screen

Started by Calum, Nov 04, 2008, 18:08:44

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Calum

Not IDNet related, just wondered if anyone could help me out. :fingers:

My computer crashed a little while ago and i had to restart it without shutting windows down properly. :no:
when i first logged back in i got this on a blue screen

Checking file system on C:
The type of the file system is NTFS
One of your disks needs to be checked for consistency you may cancel the disk check but it is strongly recommended that you continue windows will now check the disk
CHKDSK is verifying files
CHKDSK is verifying indexes
CHKDSK is verifying security descriptors
:mad:
The check when through after about 5-10 min and all came back fine, windows started like normal, but now every time i restart windows, even after shutting down properly, the screen reappears, this has been happening for about 3 days now and is starting to be a real annoyance. I'm running XP so you know.

If anyone could help it would be much appreciated.

Thanks in advance. :thumb:
Meribel. The heart of the Three Valleys!

Rik

Hi Calum

When NT boots it performs a check on all volumes to see if the dirty bit is set, and if it is a full chkdsk /f is run. To stop NT performing this dirty bit check you can exclude certain drives. The reason you may want to do this is for some type of removable drive, e.g. Iomega drives:

   1. Run the Registry Editor (Regedt32.exe). You must use Regedt32.exe and not Regedit.exe
   2. Goto HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
   3. Change the BootExecute value from:
      autocheck autochk *
      to:
      autocheck autochk /k:x *

Where x is the drive letter, e.g. if you wanted to stop the check on drive f: you would type autocheck autochk /k:f *. To stop the check on multiple volumes just enter the drive names one after another, e.g. to stop the check on e: and g: autocheck autochk /k:eg *, you do not retype the /k each time.

If you are using NT 4.0 with Service Pack 2 or above, you can also use the CHKNTFS.EXE command which is also used to exclude drives from the check and updates the registry for you. The usage to disable a drive is

chkntfs /x <drive letter>:
e.g. chkntfs /x f: would exclude the check of drive f:

To set the system back to checking all drives just type

chkntfs /d

I think there may also be a fix at Kelly's Korner, I'll just go and look.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

Thats impressive Rik, straight off the top of your head
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Calum

Very impressive more like.

Ill try that now, thank you very much.
Meribel. The heart of the Three Valleys!

Rik

Quote from: Glenn on Nov 04, 2008, 18:16:03
Thats impressive Rik, straight off the top of your head

Straight from my notes, more like, Glenn. :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

Quote from: Rik on Nov 04, 2008, 18:19:24
Straight from my notes, more like, Glenn. :)

You shouldn't of said that, it spoils the illusion
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

I only do omniprescience at weekends, ;D
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Calum

Yep, thats got it. thanks very much, just one small question.

This now means windows cannot check my C: drive for errors?

So does that mean windows cannot fix any errors that may occur in my system??
Meribel. The heart of the Three Valleys!

Rik

It won't check at startup, but you can run a manual check to see if there are any issues.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Calum

Ok, will avg do that when it scans my computer,

I don't much fancy the idea of having to run a check every time i log on
Meribel. The heart of the Three Valleys!

Steve

Perhaps boot in to safe mode,get a command prompt and run a chkdsk repair on  drive C: and see if it finds anything, if all is well apply the opposite reg fix. Or run a chkdsk repair on that drive from Bart PE. Probably time also to make sure everything is backed up just in case, the harddrive health can be checked by using the manufacturers diagnostic utilities.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Calum

also, i'm sorry if it takes a while to post, my internet acting up and being VERY sloooooow!
Meribel. The heart of the Three Valleys!

Rik

Are you seeing any dropped connections, or is it just speed?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Calum

Cutting some times, ive phoned IDNet and i will have to do it again tomorrow, (i hate the 9 to 6 thing, because im can only get to the phone at 5 earliest)

I got a removable hard drive a short time ago and they suggested moving it away from my router (it was next to it) however it doesn't seem to have made a difference.
Meribel. The heart of the Three Valleys!

Rik

IDNet are open 8-6:30, 6 on Fridays. They'll arrange an out of hours call back if you ask. :)

Have a read through this, it may give you some ideas to try.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Calum

Meribel. The heart of the Three Valleys!

Sebby

Yep, great link posted by Rik (I have to admit I forget it's their sometimes!). The most likely cause of disconnections is internal wiring, so try that and see how you go. If you still have problems, it's most probably a line fault.