Dan Seur said:
Mr. Lipman's reply is very helpful; it's a neat list of where to get
drive diagnostics, and lots of folks will probably copy/paste it into
their personal bibles.
The disk consistency check is what chkdsk does; it's a test for
integrity of the file structures and files themselves on a partition.
What the message you're seeing means is that during the OS boot process
the OS examination of resources found an anomaly of some kind on one or
more partitions. Run chkdsk on all of them; then run chkdsk /f on the
one(s) reported as problematic. You may not have to replace your hard
drive after all.
This is similar to a problem I am having, but mine is apparently more
developed. I was trying to set up some networking stuff, and got a particular
error. I looked up that error, and found that I might need an update to SQL
Server. I tried to download that update, but had to get the 2000 Server SP4
before it would work. After installing the service pack, I restarted to
finish installation.
At this point, I got the consistency check problem. The biggest problem was
that after the consistency check was done, it was in a loop of trying to
startup Windows, but having to check the consistency. If I stopped the
consistency check, I got a blue screen of death, telling me to uninstall any
new software, run chkdsk /f, and to start in safe mode.
I tried to start in all three different safe modes, in the last known good
configuration, and another of the startup options. None of them worked. Next
I went into the BIOS, and tried to load the original Fail-Safe config., but
that did not work either. I also did a scandisk from the BIOS setup screen. I
changed the BIOS to allow Boot from CD, and did so from my Norton AV. The
virus check was negative.
At one point in this process, the blue screen also said something about a
bad driver.
The next thing I tried, was to boot from an old NT CD. It was version 4 if
that matters. It would not let me install because it could not locate a Hard
Disk. The guy who works on our MAC's thought it might be that the old NT
could not communicate with an IDE Hard Disk. I was under the impression, that
the OS does not need to have any inherrent ability to communicate to a
certain type of hard drive, but that the motherboard determines what type of
drive may be used.
So, it comes down to the final question. Is our hard drive corrupt? Is there
some driver stored in Cache that is bad? Is there something wrong with our
motherboard, or a cable in-between it and the hard disk? I am really in over
my head on this one. Thanks for any help.
James