David Bixler

The drive is good. Left SATA power cable plugged in, connected SATA data cable to a ROSEWILL USB adapter and punched it into a USB3 slot, worked like a charm. Still no explanation why I can't use the HDD normally. Perhaps the drive is not compatible with the CPU? Microcode errors tend to point at the CPU from what I've read. That doesn't make sense to me because it worked perfectly fine until the BIOS updates.

My first post here. Be gentle. Know that I typically research and try every available option before asking for help. This is a pickle, which I'm not 100% certain an RMA will sort out for me. Let me start in the beginning. In the beginning I tried to play Crysis 3 and ARK Survival Evolved on 3x EVGA GTX 580s (SLI). I also tried video editing, 3D modeling, and other things. For a while, life was good. The 580s degraded in the last year or so and I have been muddling through. Last week I picked up a GTX 980, plugged it in, and had no joy. I learned I needed to update the BIOS, so I managed to find the .CAP converter, flashed the sucker using the EZ Flash utility and joy, my GTX 980 functions now. Buh bye to the 3x 580s. After the next reboot, something strange happened. I got a q-code error. 06. Then I got 0b, then I got 0E. Every thing I tried, resetting the OS (not reformat) flashing back to an earlier BIOS, all of it just failed. I would try flashing back to a BIOS where everything worked, but then I would lose my displays, as anything prior to 2100 series simply does not detect the 980. So this is what I know. If I disconnect the data or power SATA cable from my storage HDD, everything works fine, but I don't have access to my storage drive, so all of my project files are gone. If I reformat the RAID 0 config and reinstall the OS, prior to rebooting, if I plug in the HDD, the storage drive is detected and all files are readable. As soon as I reboot again, I begin getting q-codes which point to microcode issues or otherwise. I have tried switching the ASMEDIA controller to IDE, and disabling it entirely. I still get an error code so long as the HDD is plugged in during POST I have tried creating a windows recovery stick, and even a full windows installation USB, and ran troubleshooting, repaired master boot record, replaced mbr, ran chkdsk and a number of other command line processes. So far there is very little information on microcode errors that is human readable. OS Name Microsoft Windows 10 Pro Version 10.0.10586 Build 10586 Processor Intel(R) Core(TM) i7-3960X CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s) ASUS Rampage IV Extreme BIOS Version/Date American Megatrends Inc. 4804, 12/30/2013 BIOS Mode UEFI