Quote Originally Posted by saaya View Post
hmmm i emailed gary from anandtech but didnt get a reply yet...
ask xt0m, he had 2 hdds die on him, he should be able to give you some details.
if he tells you interesting details please post them here
I guess I need to check the spam folder.

Answered in our quote section -

"We have two 74GB Raptors that are basically dead, they will power up but cannot be low-level formatted. The WD 250GB drive basically had the same problem. The two 500GB Samsungs will power up and repeat a click-clack pattern. The Samsungs have been returned for analysis as will the 74GB Raptors.

I am getting ready to do the same for a pair of 150GB Raptors that I wrote off in December. However, those drives failed (no longer accessible) during RAID testing on the 780i board (usually I yell at myself when that happens as I have had far too many RAID 0 arrays drop a drive over the years). I did not think much of it until we started having these data corruption problems over the past six weeks.

Between Kris, Raja, and I there have probably been around 14~16 image reloads the past six weeks after overclocking. We fully except to trash the OS when exploring the boundaries of memory/fsb rates, but it might happen once or twice a month at best and is not limited to NVIDIA chipsets. However, all of these failures have been on the 780i/790i boards and we were not really pushing the systems except for two times when the drives failed or the images were corrupted.

The frustrating/perplexing problem is that the 790i testing with Kris resulted in some of the best overclocks we have ever experienced and they were 100% stable. We changed the settings to a normal overclock at 400FSB/1600 DDR3 and the images are corrupted or the drives went south. It is not repeatable at a given setting. We have seen results like ours in various forums so there is something amiss here, just trying to find it right now.

In all cases, we have had the memory settings set at something other than stock/default. I am still working with Derek as he has experienced several data corruption problems during SLI testing the past couple of weeks. I did not mention that until we figure out if his problems are related to ours."