R7 3800x
2x16 G.Skill Trident Z Neo DDR4-3600 DIMM CL16-19-19-39
Asus Prime x370 pro
Vega 64
500GB Samsung 970 pro
Corsair RM1000i
EKWB watercooling (cpu+gpu)
Or just a noob doing noob stuff like using a cable from a different PSU.
"Many of you (and Corsair included) feel that it might be a case of wrong cable. We are working closely with Corsair to verify that the issue and I will follow up with the resolution when its definitive. If we screwed up then I take full responsibility in that. I've been using Corsair PSUs for years and never had any issues so this is definitely not indicative of any on going issues."
breixobaloca (04-20-2018), Philipus II (05-03-2018)
One drive survived the cable...
Sometimes SCP catches the short in time... sometimes it doesn't.
It's also possible there was a problem inside of the connector which could not be seen externally. I've run into this before with Molex to SATA adapters where a pin of the SATA power connector became loose and got pushed back. With a drive connected it would cause a short and the system would shut down.
Thankfully that HDD was fine but with a cheap connector or one that has been simply used a ton this can happen as I've also seen it happen on SATA HDD docks.
So, did he use a cable from a different PSU?
You know... he never followed up.
He said that there were no markings on the cable that plugged into the PSU, but that's as far as we got.
I'm not going to push the issue. I think he knows he screwed up, but if he addresses it, it's going to bubble it up to the top and he doesn't want that any more than Corsair does.
He did admit, he screwed up:
https://youtu.be/0JRY0Ri2VoM?t=246
R7 3800x
2x16 G.Skill Trident Z Neo DDR4-3600 DIMM CL16-19-19-39
Asus Prime x370 pro
Vega 64
500GB Samsung 970 pro
Corsair RM1000i
EKWB watercooling (cpu+gpu)
Ah. In a different video. Good for him.