Hello, So I've been using this site extensively for at least a year, and since I haven't found an article specifically for this anywhere, I figured I'd contribute. I realize it might not help me in time for delivery, but it might help someone else later. So heregoes... I finished this build last week for a customer, had everything setup and working except the raid 10 storage array. I'll list the parts here... Relevant components: - ABS DARK BERET seriesDB1000-M-BRZ 1000W PSU - GIGABYTE GA-880GA-UD3H - AMD Phenom II X4 955 Black Edition Deneb 3.2GHz - G.SKILL ECO Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 - A-DATA 500 Series AS592S-32GM-C 2.5" 32GB SATA II SSD (x 2 - raid 0) - HIS H577FM1GD Radeon HD 5770 - SAMSUNG Spinpoint F3EG HD203WI 2TB 5400 RPM SATA (x 5 - raid 10 + 1 native) - OS: Win7 64bit pro Anyway, Friday, 3 days before delivery, I get artifacting. On desktop, not in game. Immediately turned off aero, which fixed it mostly. Checked CCC for overheating, kept an eye on card. Nothing abnormal, EXCEPT that with the artifacting came massive system slowdown, errors and BSODs. Checked PSU for overheating or irregularity, but mm readings were normal. Tried several backlogged CCC versions thinking "must be drivers." But that didn't fix anything, so I decided it was just bad mem on card, and took it out. Integrated VGA works fine for now. I'll explain to end-user, no big deal. But problems persisted... Almost immediately after, the system would halt whilst booting Win7 (in the middle of the color-swirl) and repair startup function always led to a BSOD where the CPU fan would gradually climb to 100% velocity. I read about CPU compatibility issues with the F1 BIOS of my board which apparently was the source of a lot of other issues, so I just q-flashed BIOS to F2, which fixed it. To make sure, I performed a 10 round extended RAM diagnostic which took forever and resulted in "no errors." Sweet, it's all fixed. If only... Now I have disk trouble. Yesterday, I enable onboard raid for SATA ports 0-3 (the Samsung drives), reboot, and there's immediately knocking from all of them in sequence. They don't post either. I let it go through the process just to be thorough: raid function doesn't detect drives, BIOS doesn't detect drives, "Computer" sees no drives, "Disk Management" sees no drives. I set them back to Native IDE. They still don't show anywhere. I notice the abnormal sounds continue only until I leave the computer off for a minute or so, then on bootup they sound normal, but still won't post. I pull all drives and check them one-by-one in the dock. All but one work fine. I replace the one bad Samsung with the hot-swap extra I had bought. Partitioned/formatted each drive, checked each with Active@ and wrote/read a few files. They were fine. Put back in case, but they still wouldn't read as native IDE drives. Replaced SATA data and power cables. Still no go. This morning, I turn the computer on and.... voila, they post! I can read them natively and everything. We now have 8TB of storage, ladies and gents. But here's where I make my mistake. After awhile of working on software, I decide to retry the onboard controller to get the raid 10 storage the customer had requested. Again, upon rebooting, all drives knock in sequence and refuse to post from there forward. I am now back to where I was last night. So here's the only explanations my ill-equipped brain can think up: 1. I've missed a step along the way; 2. I got a whole batch of bad disks; 3. Onboard raid is somehow f'ing up these disks: --a. Perhaps the board is delegating a function/parameter the drives don't support? --b. Perhaps I am overlooking a BIOS setting that is disabling these drives? I'm at a loss. What do you think?