Random reboots with HDD not being detected

Miller

Limp Gawd
Joined
Aug 30, 2004
Messages
207
Now, first of all, I haven't been around any single time this has happened (which isn't very often, but it happens every few days).

I'll come back to my computer and it will have restarted, and on the screen there'll be a screen showing two out of the three disk devices being detected (the two being my disk drives, and the one not being detected is my HDD). Normally, all I have to do is restart my computer and make sure no cables popped loose or anything - a minor annoyance, to be sure. But it is rather inconvenient - I was half an hour through an hour-long download, and while I was doing something else it happened again and now I have to wait another hour to download it again. -_-

I have a Western Digital 80GB HDD (7,200 RPM). Due to some issues when building and setting up my computer it's configured as a slave drive, but it works all the same (there is no other drive connected, so it shouldn't make a difference). It's connected to an ABIT AS8 motherboard, which has also worked fine. Nothing has been damaged throughout all of this. Perhaps a cable has popped loose, but I honestly can't tell - everything checks out when I take a look inside.

Does anyone have any possible solutions for this? Could it be a virus or bug or something?

Thanks in advance.
 
for some reason after a hard reset (reset button push) my harddrives won't be detected at bootup and it just stalls there. this was after i had unplugged my floppy to test some things and was getting freezes in windows for not having disabled it [the floppy] in the bios first i suppose (ps, i plugged the floppy back in since im done testing and i dont get the freezes any more. but this is beside the point, you are not alone in having your drives not detected after a reset. when this was happening i would have to hit the power button and power it all the way down then bring it backup.
 
This error just happened again, so I kind of feel I should bump this.

I tried switching it to be a master, but the computer wouldn't get past the opening boot-up screen (displaying the ABIT logo and all of that), so I just went back to Slave and it's fine.

Could it be possible it'd have something to do with cables coming loose? I examined my computer, and maybe because of something I touched when changing around cables on my HDD or maybe just because of the messy wire set-up, a cable had fallen out of one of my drives.

Also, this is the first time I've been around when it's happened: My comp freezes for a split second, displays a blue screen really fast and then reboots with the HDD not being detected.

Any thoughts?
 
Back
Top