Dang! Wierd system problem, advice needed...

ZapZilla

Golden Member
Oct 9, 1999
1,027
1
71
I've a CUSL2 800EB@1032 (172/129/43 -> FSB/SDRAM/PCI).

Its been rock stable for months running OGR 24/7 as well as all
of my games and other home apps.

Now, after about 30 to 60 minutes, it freezes and the hard drive starts
clicking at about 1 second intervals. Reset doesn't cure it, but after a
hard boot it runs peachy, at least for another variable 30 to 60 minutes.

Running it at spec 800MHz gets the same fatal results too.

I've replaced the hard drive with another drive and the problem is gone.

So it seems that my original drive has a wierd problem, but what and why?

Its a WD Caviar 13.6GB.

It would freeze after 30 to 50 mins even if all possible apps (OGR, TSRs, etc)
were shut down.

Did I kill the drive with prolonged high 43MHz PCI bus exposure?

If so, why does it run OK for a variable period before dying again?

I've got my system O/Ced to get the best OGR rate possible and I don't
want to kill my spare drive too.

Anyone have a clue as to what might be happening/have happened?
 

Russ

Lifer
Oct 9, 1999
21,093
3
0
Sounds like Stiction. This is when the read heads begin banging in to the platters. Eventually, they will stick to them completely. RMA time for the hard drive.

Russ, NCNE
 

ZapZilla

Golden Member
Oct 9, 1999
1,027
1
71
Nov. 21, 1999 is when I got this drive.

How long a warranty do drives typically have? 1 year, or more?

If 1 year, I'm SOL.

Would a Low Level Format, ala SpinRite, help it at all?
 

ZapZilla

Golden Member
Oct 9, 1999
1,027
1
71
Not having experience "stiction" before, why is the problem occuring after
a period of time and not right away? Heat build up?

 

Russ

Lifer
Oct 9, 1999
21,093
3
0
You have a 3 year warranty on that drive, but that begins with the date on the drive, not the date that you purchased it. I don't know why the problem doesn't surface right away, only that I've seen it more frequently on WD's then any other brand.

No, a LLF will not solve the problem, it's hardware failure.

Russ, NCNE
 

Sukhoi

Elite Member
Dec 5, 1999
15,342
104
106
Jeez, with that kind of FSB SETI would fly on your system! :D You should find someone running SETI on a similar speed computer, and trade projects. :)