STOP 0x000000ED UNMOUNTABLE_BOOT_VOLUME

  • Thread starter Thread starter George Hester
  • Start date Start date
G

George Hester

I just recently lost an installation of Windows XP SP2 and posted earlier
about the issue here but I guess no one ever came across this issue. Anyway
I just got the thing up and running this evening and after about 5 hours the
machine again just quit. I heard the plates on the boot disk banging and
then the machine went out to lunch.

Anyway when I tried to boot it back up I got the message you see in my
subject. I found this article:

http://support.microsoft.com/kb/297185

followed it and was able to boot the system after doing a chkdsk /r. The
disk is a Seagate Cheatah 9.1 GB. I have heard these disks can be
problematic. Do you think based on the fact that the file system was
corrupted (yes the second parameter of the STOP message was 0xC0000032) that
the disk is just bad?
 
You should never hear undo noise from the hard drive. After using a drive
for an amount of time, you should become aware as to what its "normal" sound
is. If all of a sudden the sound begins to deviate, get louder, bang, click
etc., it's time for a new drive.

--

Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
 
George said:
I just recently lost an installation of Windows XP SP2 and posted earlier
about the issue here but I guess no one ever came across this issue. Anyway
I just got the thing up and running this evening and after about 5 hours the
machine again just quit. I heard the plates on the boot disk banging and
then the machine went out to lunch.

Anyway when I tried to boot it back up I got the message you see in my
subject. I found this article:

http://support.microsoft.com/kb/297185

followed it and was able to boot the system after doing a chkdsk /r. The
disk is a Seagate Cheatah 9.1 GB. I have heard these disks can be
problematic. Do you think based on the fact that the file system was
corrupted (yes the second parameter of the STOP message was 0xC0000032) that
the disk is just bad?
Click to expand...

The HD should be replaced, especially after evidence of a
physical crash. Not a good omen to hear sounds emanating
from the hard drive.
 
Yes I know. I can put a different one in. What I did in the meantime is
move the system away from the SCSIs it was using and got it going again.
The sound has stopped for now and it has been running without incident for
24-hours. I am starting to think the SCSI card, an Adaptec AHA-2940UW PCI
SCSI Conntroller might be bad or one of the SCSIs on the ribbon is. Do you
think the card or its devices could cause the issue I wrote in the subject?
I am thinking of hooking the SCSI devices back up to the system today. I
looked in the knowledge base about any issues with SCSI cards and Windows
XP. Some issues looked similar but nothing exact. Maybe the sound wasn't
the disk going bad but a bad signal from the SCSI card to the system disk???
 
Back
Top