Booting Xp

G

Guest

When I bootup XP home edition the system I get a blue screen and
goes into scan disk mode and checks all the drives before booting up.
How can I stop this from happening and boot straight to windows?
 
G

Guest

George,
This sounds like the POST (Power On Self Test) that the BIOS/CMOS does.
This is normal and is necessary if you want to ensure each time that your
system is working properly. Hope that helps.

RAGMAN!!!
 
J

John in VA

When I bootup XP home edition the system I get a blue screen and
goes into scan disk mode and checks all the drives before booting
up. How can I stop this from happening and boot straight to
windows?

George,

Try this - When XP loads up, launch a command prompt (ensure you're
logged in as an administrator or a user who has admin priviledges)
type: chkdsk /f you will recv a warning that check disk will start
during next boot. reboot the machine - allow chkdsk to complete (the
/f switch will (hopefully) fix any errors. If this is happening for
more than one drive or partition, do the same for the others.

Questions to ask yourself:
When did this start?
What changes occured just prior to this incessant chkdsk request
(e.g. hardware/software install or deinstall)

Bottom line: something on your drive(s) is/are corrupt. If the
chkdsk fails, you may be able to restore windows to previous state
if the problem is in the OS (See
http://support.microsoft.com/winxp). You could always reload XP
(still maintaining your personal files and settings), or, if all
else fails - completely slick the drive and start from scratch. I
would suggest taking the least invasive course of action first - the
"chkdsk /f" - One other thing - your hard disk may also have
problems and be failing - but let's not get ahead of ourselves...

John in VA
 
S

Steve N.

S

Steve N.

Ragman1171 said:
George,
This sounds like the POST (Power On Self Test) that the BIOS/CMOS does.
This is normal and is necessary if you want to ensure each time that your
system is working properly. Hope that helps.

RAGMAN!!!

It isn't the POST, it's a disk check due to the volume being flagged dirty.

Steve
 
G

Guest

Thanks for the quick response to my Question.
Have done what you suggested, get the message
"Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
When I try to force dismount, it refuses. It then gives me the option to run
chkdsk on bootup but does not fix the problem. After the chkdsk inboot up
everything seems to run OK. It's just a hassle to see the blue screen and
have to wait for the system to chk the disks every time.
 
S

Steve N.

GeorgeV said:
Thanks for the quick response to my Question.
Have done what you suggested, get the message
"Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
When I try to force dismount, it refuses. It then gives me the option to run
chkdsk on bootup but does not fix the problem. After the chkdsk inboot up
everything seems to run OK. It's just a hassle to see the blue screen and
have to wait for the system to chk the disks every time.

Hmm, that's odd, whenever I do that it never asks if I want to dismount
the volume, it just gives the option to run the disk check next startup.

Do you have any 3rd party disk or partition utilities installed or used
in the past? I recall someone having a dirty bit problem when using
something like NDD on a drive but I don't recall a solution other than a
fresh format.

Regardless, I would try a couple of things from the Recovery Console.

Chkntfs (To check for the dirty bit being set. As the article I gave
link to states, you can use chkntfs /x c: to prevent autocheck from
running on that drive at bootup but it's not recommended; if there are
errors causing the dirty bit to be set they need to be corected.)

chkdsk /p (equivalent of chkdsk /f from cmd)

If chkdsk /p shows errors it can't fix then run

chkdsk /r

repeatedly until all errors are gone. If you get an error indicating
chkdsk cannot repair the errors, reboot into RC and do it again. Repeat
if necessary. I've seen some "unrecoverable" errors eventually get
cleared with repeated chkdsk /r runs.

Download the diagnostics from the drive manufacturer and test the drive
with it as well but be careful with in-depth/complete/surface tests,
some will flag bad sectors without warning you or giving you an
indication that certain files residing across bad sectors may become
unusable, and no way to back out, back up the file(s) in question and
restart the scan.

Steve
 
G

Guest

Thanks Steve
Had to run chkdsk 7 times, but finally got it working right. took a long
time to scan, It seems to run perfectly now.
 
S

Steve N.

GeorgeV said:
Thanks Steve
Had to run chkdsk 7 times, but finally got it working right. took a long
time to scan, It seems to run perfectly now.

Good to hear.

You're welcome.

Steve
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top