Computer Having Trouble Booting

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am using a Promise Ultra 100TX2 PCI card. I have two W.D. 250gb
hard drives (Master & Slave) on the Ultra's IDE 0 port running XP Pro SP2.
For the past two weeks I am having trouble booting my computer. When I boot
the master drive I get an error (cannot read boot disk). This also happens
when I hibernate and then later start the computer. I get the same error and
it asks me to delete Restoration Data & restart. The only way I can start the
computer at this point is to use a boot disk and boot an operating system on
the slave drive. After I start the slave drive, I can then restart the
computer and it will read the boot options on the computer’s master drive and
I can then boot the XP operating system as usual. I tried reinstalling the
card's driver on the XP's operating system but that didn't help. What could
be causing this problem?
 
Try running a chkdsk on the disk in question. Get a disk checking
utility from the HD manufacturer and run it on the disk, the disk may be
failing.

John
 
I ran WinDiag and it checks OK. Could it be another issue other than the
hard disk. Both disks are about a year old. Bob
 
Upon startup I am now getting a blue screen with the "windows is shutting
down to protect the operating system" error . Could this have been caused by
a Windows Update or something?
 
Hard to say. Is there any code with the error message? Personally I
think that if your disk is repeatedly refusing to boot after a short
time of use it is going bad, disks can fail at anytime for any reason,
(young) age is not an indication that a disk is OK, they can fail right
out of the box or within a few months of installation. I think you
should run the utilities from the disk manufacturer.

If I were you I would put each of these disks on a controller of its own
instead of having them in a Master/Slave relationship, with your TX2
controller that should be possible. Bad IDE cables could also be
causing problems, check those out. Another possibility, maybe bad RAM?
Bad RAM can cause all kinds of mysterious problems.

John
 
John John,

Just wanted to let you know you were right on the money. It was a
bad IDE Cable.


Thanks Again, Bob
 
You're welcome. Thanks for the follow up!

John
John John,

Just wanted to let you know you were right on the money. It was a
bad IDE Cable.


Thanks Again, Bob


:
Click to expand...
 
Back
Top