AMD-SiS series motherboard issue?

  • Thread starter Thread starter r.groves
  • Start date Start date
R

r.groves

Just put together a WinXP new machine, it has been unexpectedly
crashing hard. When rebooting, the bios doesn't recognize the Hard
drive. I have to open up the tower, remove the ribbon cable from the
HD, plug back in, and restart, then the HD is recognized.

Would this be a motherboard problem or a HD problem? Anyone had this
issue before? Got the barbones server from CompUSA awhile back.
 
Just put together a WinXP new machine, it has been unexpectedly
crashing hard. When rebooting, the bios doesn't recognize the Hard
drive. I have to open up the tower, remove the ribbon cable from the
HD, plug back in, and restart, then the HD is recognized.

Would this be a motherboard problem or a HD problem? Anyone had this
issue before? Got the barbones server from CompUSA awhile back.

Could be a cable problem, try a new one first..
 
It is possible that a small delay may help the mobo to recognize the
HD. You don't mention if the problem occurs on cold boot or warm
boot. If it occurs on cold boot, try entering the CMOS setup program
immediately during the cold boot, then merely exit, and see if the
mobo recognized the HD. I recently had a cold boot HD recognition
problem with a WD 80 Gig HD and an ECS mobo. If your problem does not
happen on cold boot, then just ignore my babbling. If there is a
"quick boot" option in your CMOS setup, you might try disabling this
feature to slow down the mobo and give the HD a bit more time to power
up and be recognized.

--
Best regards,
Kyle
| Just put together a WinXP new machine, it has been unexpectedly
| crashing hard. When rebooting, the bios doesn't recognize the Hard
| drive. I have to open up the tower, remove the ribbon cable from the
| HD, plug back in, and restart, then the HD is recognized.
|
| Would this be a motherboard problem or a HD problem? Anyone had this
| issue before? Got the barbones server from CompUSA awhile back.
|
 
It happens on both cold and warm boot. When it crashes, the system
automatically tries to restart. But when i power off completely for 30
secs, then power on, its still doesn't recognize the drive.

I'm pretty sure its a hw problem, as windows does not contain any
entries in the eventlog before the crash. I will try going into bios
next time it happens, and seeing if exiting will cause recognition.
 
Could be a simple power plug problem to the HD. Some drive power leads from
the PSU occasionally have loose fitting plugs. Try a different lead
(there's usually two or three that are available) or try tightening the
plug's inserts by a little judicious bending with a small screwdriver.

Nick
 
Back
Top