SATA problem

[Andrilyn]

Lately I've been having some computer problem, The thing is my PC would give some random SATA error after it booted up Windows.
First off I didn't think much of it (PC just worked normally no error cept for that SATA one) everything worked nicely untill about 3 days after I had first encountered the SATA error after my PC got booted up.
All of a sudden there were some .sys files 'missing' and I got a BSOD loop while booting so I just reinstalled Windows to fix that problem.

The thing was the SATA error still remained (translated to English it would be something like "can't read blablabla sector on the HD").
Now aprox 3 days after the Windows reinstall I got a black screen (no peeping sound(s)) and my PC didn't boot up again.
So I reinstalled Windows (again) and yet the SATA error remained.
In fear of having to reinstall Windows in the next 3 days again I looked up what SATA actually means and does and apperantly it's some connection between my motherboard and my HD's (HD's are in RAID 0 setup).
So if it fails to work properly it can cause my PC to not read certain bits of my HD (which can and did include system files).

Now my question is do I have to replace my entire motherboard to fix this (HD's are fine as I tested them in another PC)?
Or is there a way to fix this SATA (am no comp hardware wiz keep in mind) without having to pay about $300-400 for another Asus Striker Extreme Motherboard?

 

[Twist]

You could try updating the MB & SATA drivers and/or updating the BIOS - all quite easy things to do and the latest versions will be available free from the ASUS website.

 

[Ballard]

After doing the above recommended steps (bios/sata drivers) try using a new SATA cable. SATA cables are not flexible and should never be bent past 90 degrees so at some point in its life it could have easily been damaged. If you still have problems chances are its not your MOBO but rather your HD.

 

[Cromcruaich]

Note that if you mess around doing bios updates, expect to lose all the data on the disks if they are in a striping array.

Ive also seen this happen in overheating and/or overclocked systems. But thats an outside chance if you havent overclocked.

 

[rynnor]

I had a similar problem recently - I'd say its your HD failing - while its still useable get a new SATA HD and copy the data you need over before it dies completely.

Are you using any RAID functions (prob not with only 1 HD).

 

[Andrilyn]

Thanks for the help, updating the SATA and Mobo drivers didn't work but after I reconfigured the RAID 0 to RAID 1 (ofc making the HD's a bit slower) the error is not popping up anymore and it seems (only have it running for about 2 hours) that it's alot more stable now as I can do a checkdisk and (virus)scan without having them report that the HD(s) are not readable anymore.

 

[Amiga]

Raid 1 is mirroring though which means you get half the size. On the other hand you always have backup =)

 

[Littles]

Sounds to me like one of your HDDs are working and when striped it was causing problems but when mirrored the other is taking over.....i dont really know much about RAID but that sounds like the logical answer to me.

 

[Cromcruaich]

And you dont wanna be running raid one with one dodgy disk - problems arise because the controller doesnt know which disk has the right data set - cheap raid one protects against sudden outright failure - but is bad at protecting against creeping corruption.