• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

RAPTORS F*(^&%

M

MaMMa

Supreme [H]ardness
Joined
Aug 11, 2004
Messages
6,778
Third one died on me today. Only about 3 months now and I go through 3 of them. It pisses me off, their drive is awsome, so is their support but WTF!

I'm beggining to think there's something wrong on my part. Could it be my PSU?

I have an antec neopower 480, no multimeter to test but I can get one if needed.

Anyclues? I formatted the drive maybe 3 times since I had it, it is an RMAed one. Defrag with O&O maybe 10 or so times.

- I OC a lot.
- hard reset quite often when PC locks up from a bad OC.
 
are they being subjected to any shocks while you're messing around in your case?
 
nope, i was just sitting there, then i restarted and i get the NLTDR is missing

tried everything. put it in a nother machine nothing.

I put the metal electrical tape all over my SATA cables from a thread I read here that Ice Czar wrote on these cables not being "closed" forgot the name of that word.

other wise there should be no shockage in my case. My other SATA drive is fine. Same with everything else in the case :mad:
 
MaMMa said:
nope, i was just sitting there, then i restarted and i get the NLTDR is missing
Click to expand...

never seen that error, but my brother got it the other day after rebuilding his machine and a simple clearing of the CMOS fixed it

if your other drive is fine, a bad PSU seems unlikely :confused:
 
Does your board have locks for SATA? Im not a pro on the subject, but I had to operate my Raptor in SATA #3 in order to get Windows to boot.
 
that error happens when u get a new drive and it has no OS or if the drive is fubar'd to my knowledge.

i've cleared CMOS. defaulted all the settings to no OC. and i put the drive into my bros pc and still same thing!
 
xyoufailmex said:
Does your board have locks for SATA? Im not a pro on the subject, but I had to operate my Raptor in SATA #3 in order to get Windows to boot.
Click to expand...

i've had SATA drives in my pc for over 6 months now. They were on #1 and #2

#1 is my raptor #2 is my storage

Its always worked like that. I'll try #3 though. Thanks for the suggestion.

Agian I had windows on it, restarted and it died.
 
had you noticed anything unusual before, i.e. clicking, unusually long (30+ seconds) access periods before launching something, and other typical signs of impending hdd failure?
 
nothing unusual has happend. This drive is less then a month old. It just crapped out just like that :( I've had some die on me before and would notice this type of stuff but this one just strait up died. :confused:

Thanks for the link B18_Cya
 
then it's not a physical problem... try accessing it as a slave drive; it should read. you can then repair it from there.
 
I'll try that, I dont see why though. I've ran all three of my previous drives like this. They all worked fine.

Will return in like 20 mins gotta eat
 
files corrupting during normal use is rare but not unheard of.

my guess is you got a worm and it took out NTLDR.
 
I really think that I don't have a worm that did this. I did recieve an email from a friend that was an excel doc. WHen I opened it and finished going through it all it froze and I rebooted and this is when it happened. She's sent this email to other people and no one had issues with it.

I'm running zone alarm and norton 9 corporate, I seriously doubt its a worm.

As far as trying to run the raptor on as a slave, I looked at the sticker for jumper settings to slave and it doesnt say anything about it.

It says SSC_DIS ; PM2 ; CPT1 ; and CPT2

Nothing says CS SL or Master. It also says SSC (Spread Spectrum Clocking) and PM2 ( Power up in Standby)

I tried putting the drive on SATA #3 and still no go.
 
:rolleyes: ah, one of those wierd ones... look up in the manual how to set it as a slave drive... or as secondary master (set as master, on secondary connector)
 
starhawk said:
:rolleyes: ah, one of those wierd ones... look up in the manual how to set it as a slave drive.
Click to expand...

Damn, why must they make a wierd one! I'm gonna look for the wierd manual now maybe on their site i can search "wierd manual". thanks!
 
"Serial ATA hard drives do not have a jumper block to designate whether the drive is master, slave, single, or cable select, as EIDE hard drives do. There is only one Serial ATA drive per channel (cable), so no master/slave relationship exists."

`Western Digital

This blows. But I learned this now, I guess you did too starhawk (we shoulda known this) :)

ANy other suggestions !?
 
however it determines which drive to boot from... set up another drive to do that. set your current one as a non-boot drive.
 
Thats what I did on my brothers. His drive has windows on it and is SATA on slot #3. I put mine on slot#4. The jjumpers only tell it to do the SSC (Spread Spectrum Clocking) and PM2 ( Power up in Standby).

There's nothing to tell it slave/master. It still won't pick up on his computer either. Its not detected at all. If I run just this drive in my pc without the storage drive present it no longer says NLTDR missing, it says Boot up error, something like that. The raptor is not even picking up at all but I can hear it spinning.
 
hmmm... try swapping the controller board (the board mounted on the drive) in from a perfectly good (and perfectly identical) drive. this sounds suspiciously like a bad board.
 
I dont have another raptor to do this. I'm just gonna RMA it. Wish I could use it for another day or so :( I didnt even get to back up anything, wasnt much but I coulda used it.

Damn raptors are starting to get to me. 3rd one in less then half a year.

I'm going to SLI soon so hopefully this curse doesnt follow me. Thanks starhawk, agian any other suggestions is alway appreciated from anyone!
 
if you want to give it to me (or sell it to me real cheap) then i might get some use out of it (either i'll tinker around with it and make it actually run, or i'll hang it on my wall :p )
 
Naw, its still got 5 years on it. Gonna RMA first thing tomorrow. I think if you look on Ebay u can find borked ones
 
Killing 3 of anything in a computer in a row should be an indication that something is very very wrong. What are the odds you and only you got 3 bad drives in a row?

I’d be looking elsewhere at this point, bad motherboard, bad over clock and every other component in the system.

Anytime you break that many of anything you have to stop and re-think what’s really going on.

Luck
 
BillR said:
Killing 3 of anything in a computer in a row should be an indication that something is very very wrong. What are the odds you and only you got 3 bad drives in a row?

I’d be looking elsewhere at this point, bad motherboard, bad over clock and every other component in the system.

Anytime you break that many of anything you have to stop and re-think what’s really going on.

Luck
Click to expand...

Yea thats what I was thinking and stated in the OP. I am moving on the SLI and passing this mobo down to my bro to try out. If the same issue occurs its gonna be wall decoration
 
I had 3 IBM 75GXP's fail on me in less than a year and no one thinks that's odd. ;)
 
I very much doubt that this is a problem with the drive. B18 Cya has the answer pegged, though the source of the problem might not be from OCing. On the page he linked (http://www.computerhope.com/issues/ch000465.htm ) go to the middle of the page where you see Windows XP users (assuming you are running XP), and follow the instructions to fix your drive.

The way your two previous drives failed might also give us some clues. What exactly happened to them?

Good luck
 
uzor said:
I very much doubt that this is a problem with the drive. B18 Cya has the answer pegged, though the source of the problem might not be from OCing. On the page he linked (http://www.computerhope.com/issues/ch000465.htm ) go to the middle of the page where you see Windows XP users (assuming you are running XP), and follow the instructions to fix your drive.

The way your two previous drives failed might also give us some clues. What exactly happened to them?

Good luck
Click to expand...


O man, I skimmed through that page and didn't notice that. Thanks I'll give it a shot first chance I get! Only thing is that the hard drive isn't even picking up at all so we'll see what happens. I know its not the SATA controller drivers because my mobo pics up other SATA drives.
 
You're problem isn't anything else... it's your motherboard.
One deficiency of the lanparty is that it eats drives if the AGP/PCI lock fails to function, and occasionally it just may eat a sata drive past stock speeds. I've witnessed it first hand.

edit: expecially over 250FSB
 
AT that time it failed , i didnt have it running anywhere near 250 FSB. Oh well its RMAed
 
MaMMa said:
AT that time it failed , i didnt have it running anywhere near 250 FSB. Oh well its RMAed
Click to expand...

I know what you mean, but I'm just warning you for the future.
 
Make sure you have good air flow over the drives. Could be they are getting too hot. I always make sure I have a low power/quiet fan directly on the drives in my case.
 
trust me I've got really nice airflow and direct air blow in my drives :)
 
Did you even bother to run the WD Diagnostics to see if they think the drive is corrupt? For all you know, your Windows installation could have been corrupted, tricking you into thinking that you have a drive failure.
 
Daynja said:
I had 3 IBM 75GXP's fail on me in less than a year and no one thinks that's odd. ;)
Click to expand...

Neither did the thousands of other people that had those drives either. IBM had the problem and it was very obvious.

WD has no such problem, at least not at the moment.
 
slowbiznatch said:
Did you even bother to run the WD Diagnostics to see if they think the drive is corrupt? For all you know, your Windows installation could have been corrupted, tricking you into thinking that you have a drive failure.
Click to expand...

the drive is not even picking up at all, I cant run any diagnostic
 
You must log in or register to reply here.
Back
Top