Glad we got your setup corrected. Hopefully, on the right ports and rivers you stop getting the bsod.
Cheers matey, appreciate the help.
Two heads are always better than one and I've learned something about the big performance hit one can see on a third party "6Gb/s" port that doesn't actually deliver said speed.
No one thought to mention to you to use the Intel Grey sata ports with 6GB/s because we all assumed you knew better.
Next time we wants pictures.
SO... bad cable and bad port sums it up or you don't know yet?
I do know better, I'd just forgotten about it and I did figure it out on my own. C'mon dude don't crucify me for being a fallible human, lol.
Anyway, the point of this thread was to troubleshoot the Marvell port/cable/SSD not just find a quickie workaround, which I did.
btw, there's a JMicron SATA port on there, too.
At this point, I can say that the cable is very likely faulty or marginal and it was coupled to a slightly suspect port. Hence, it might just work ok on the Intel port and I could reconnect it to see what happens, but no, I don't wanna go through that hassle again over a cheap cable, hehe. Every time there's a bsod it fucks up Windows that little bit more until it needs to be scrapped and reinstalled clean so I just don't need that headache.
That bsod now is so intermittent (like in the past, sometimes only happening once every several days) that it's really hard to get a positive diagnosis of it, but what I've seen over time, not just this thread, does somewhat suggest that it's not quite right. If it's really connected via PCI-E, then it really doesn't take much for there to be a translation error between the interfaces which corrupts data on rare occasions, especially with consumer grade equipment like this.
Now I'm on the Intel port, I'm confident I've seen the back of these crashes. Until tomorrow. Kidding.
EDIT @EarthDog , just seen your post at 1:05. The bold bit applies to your comment as well, as you guys seem a little confused over the intention of this thread.