On the very unlikely off chance that this could be the same problem I had...
I got the same error not long after I installed windows when I bought a new motherboard. Turns out since I was using an nLite copy I had the SATA drivers for my old chipset in the drivers section, so when I installed the new drivers during windows setup without realising the old drivers also installed, it caused conflicts.
As I say, very unlikely but more options are better than few.