XP won't start after installing 2nd hard drive

[Guest]

Hi,

I bought a Western Digital WD1600BB to act as a second hard drive on an old
PC. I installed it as a slave (via cable select) on my primary IDE circuit
(motherboard Asus A7V333, master drive an IBM/Hitachi 80GB
ICL35L080AVVA07-0). XP recognised the device, and I was able to allocate and
format the new drive, and give it a drive letter.

However, when I now try to start up my PC, while the BIOS recognises the
master and slave hard drives correctly, XP fails with a Blue Screen of Death
and an INTERNAL_POWER_ERROR message. If I unplug the WD1600BB, then the PC
starts up fine. If I start XP up in safe mode, then I can see the new drive
and write files to it. (In this case Device Manager says that the hard drive
is working fine.) The drivers associated with both hard drives are the
standard Microsoft ones from 2001. Why should the WD1600BB cause XP to fail
to start up except in safe mode ?

I've had the hard drive replaced, bought a new more powerful PSU, but have
had no success.

The parameters for the error message are 0x000000A0 (0x00000101, 0x0000007,
0xF79C17A4, 0x00000000).

Any help is greatly appreciated.

 

[DL]

Are you able to test with the hd connected to a different IDE, or even tried
a different IDE cable?

 

[Anna]

Hi,

I bought a Western Digital WD1600BB to act as a second hard drive on an
old
PC. I installed it as a slave (via cable select) on my primary IDE circuit
(motherboard Asus A7V333, master drive an IBM/Hitachi 80GB
ICL35L080AVVA07-0). XP recognised the device, and I was able to allocate
and
format the new drive, and give it a drive letter.

However, when I now try to start up my PC, while the BIOS recognises the
master and slave hard drives correctly, XP fails with a Blue Screen of
Death
and an INTERNAL_POWER_ERROR message. If I unplug the WD1600BB, then the PC
starts up fine. If I start XP up in safe mode, then I can see the new
drive
and write files to it. (In this case Device Manager says that the hard
drive
is working fine.) The drivers associated with both hard drives are the
standard Microsoft ones from 2001. Why should the WD1600BB cause XP to
fail
to start up except in safe mode ?

I've had the hard drive replaced, bought a new more powerful PSU, but have
had no success.

The parameters for the error message are 0x000000A0 (0x00000101,
0x0000007,
0xF79C17A4, 0x00000000).

Any help is greatly appreciated.

Lambert:
I guess I don't have to tell you you're dealing with a pretty old
motherboard there, do I? I do recall working on this MB and remember we
weren't exactly thrilled with its VIA chipset since we seemed to run into a
good many problems that we traced to that chipset. Also, as I recall, that
MB had more than its share of DIP switches & jumpers so one had to be
careful about correctly setting those items. I'm assuming you've already
checked that aspect out and there's no problem there, right?

But I guess at least up-to-now you've been satisfied with the MB.

Anyway, re your problem...

We'll assume of course that the HDD involved is non-defective and that
you've checked it out with the WD HDD diagnostic utility, notwithstanding
the fact that you were able to originally partition/format the disk and
assign a drive letter and that it's recognized in the BIOS. You mention that
you "had the hard drive replaced". Are you referring to the WD disk? This is
the second one with the problem? Or are you referring to a different boot
drive?

Change the jumper configuration from Cable Select to Slave as the drive is
connected on your Primary IDE channel. Don't forget to change the boot drive
to Master (I'm assuming its present jumper setting is also CS).

And you are using a 80-wire IDE data cable for the connections, right? Not
the 40-wire one.

If still no go, connect the secondary HDD on the Secondary IDE channel as
Master (or Slave if you have another device connected as Secondary Master).
Again, ensure you're using an 80-wire data cable.

Again, carefully review the ASUS Guide Manual to see if there's anything you
might have overlooked.
Anna

 

[Peter Foldes]

The error seems to be a driver issue. Update to the correct driver for the HD.

 

[Noozer]

I bought a Western Digital WD1600BB to act as a second hard drive on an

old
PC. I installed it as a slave (via cable select)

There you go... DON'T TRUST CABLE SELECT.

Set the jumpers on your drives for exactly what function they'll server,
either MASTER or SLAVE.

However, when I now try to start up my PC, while the BIOS recognises the
master and slave hard drives correctly

No, they are identified how you set them, as "whatever the computer decides
today."

 

[Guest]

Hi Noozer,

Tried this, but it didn't make any difference. To be honest, I haven't had
problems with cable select before (on PCs at my office), so I wasn't too
hopeful - tried it anyway, but I'm afraid it didn't help.

Thanks for your reply, though,

Lambert

 

[Guest]

Hi Peter,

Thanks for your reply. Having looked at both Asus' and Western Digital's
websites for some time, I can't find any drivers which might be related to
this HDD. Both sites have some Promise related drivers, but my A7V333
doesn't have the optional Promise connection, and I'm just running this on
the standard primary IDE channel.

I've also tried some creative googling for relevant drivers, but can't find
anything, and the main driver download sites I use don't appear to have
anything either.

If there is a particular driver you had in mind, or if you think I'm just
being a bit slow in how I'm searching for the needed driver, then I'm all
ears, and would be most grateful if you could point me to a more recent one.

Thanks,
Lambert

 

[Guest]

Hi Anna,

Thanks for a really useful reply, and there are several points there which I
hadn't considered. I haven't got to them all yet, but I did run the WD HDD
diagnostic utility, which showed the HDD as clean (on both quick and extended
tests).

It was indeed the WD1600BB that I had replaced - but, alas, no difference.

I haven't tried checking or playing around with the motherboard's jumpers -
I'll look through the manual to check whether there's anything noted there (I
had searched through it previously, but it's certainly worth having another
check).

I tried changing to Master / Slave rather than Cable Select, but same
problem. I also tried switching the two HDDs to the secondary IDE, but
agian, no joy. I haven't tried swapping just the second HDD onto the
secondary IDE - as I'd like to retain the CD-ROM and DVD I currently have
paired on that channel, I believe mixing and matching would give much poorer
performance on the HDDs as they would be limited to UDMA 2.

Rgds,
Lambert

I am using an 80 wire IDE cable for the HDDs - I'll get hold of a substitute
just to verify that this isn't the problem.

 

[Guest]

Are you able to test with the hd connected to a different IDE, or even tried
a different IDE cable?

Yes, and No. I'll try a different cable. Thanks for the suggestion, DL.