HD's Not Always Detected on Startup

[BooYaKaSha]

I have this peculiar error that occurs every once in a while. Normally my computer operates fine, but once every 20-30 boots or so I get a strange internal beep (different from the usual internal beep that accompanies a normal startup) and I hear the HD's (I have 2) firing up. But the system doesn't recognize them in time and both are listed as "none" where the system automatically detects hardware, and my OS doesn't load. A restart returns the computer to normal operation. This only occurs after the computer has been off for a period of time.

At first, only my D: drive would experience this problem, and by the time Windows loaded, the drive would function normally anyway. But now both drives do it.

I am a concerned because I'm wondering if it is the sign of future hardware or disk failure. It seems the disks aren't powering up in time.

System Specs: AMD Athlon 1.4. Western Digital 20gb and Maxtor 40gb Hard Drives. I recently upgraded the motherboard and chip, but I did make sure to buy an approved AMD Power Supply. Windows XP. If any other info would be helpful let me know.

Thank you in advance for your help.

 

[FatesWebb]

you may need to change the boot delay or turbo boot to off, or if there is a precomp delay. sounds like the disk isnt spun up by the time the bios times it out... I gurss this could be a sign, but try to see if you can slow it down some and give it some more time for the drives to spin up. FatesWebb

if you do what I suggested it is not my fault...

 

[BooYaKaSha]

I don't think I have that option in my bios.