Sata ports 5 and 6 not detecting SSD on ROG Maximus X Hero

Aug 18, 2018
9
0
20
Hello everyone

I just built my pc few days ago and everything was working fine. Then I tried a simple 5 ghz overclock on my i7 8700k and got a BSOD after running Prime95 2.6.6 for 15 minutes. Reverted back to defaults but then found out that ssd wasn't being recognized at times.

I changed the SATA cable but to no avail. Finally changes ports, and everything was fine again.

Now both SATA ports 5 and 6 are not detecting the ssd at all, whereas it was working just fine before the stress test.

Does this necessarily mean that the SATA ports are faulty, or could this be due to a different reason? It was working fine before the stress test.

System specs are given below -
CPU - i7 8700k
MotherBoard -ASUS ROG Maximus X Hero
Cooler - Corsair H115i hydro series
Ram - Corsair Vengeance LPX 1x16gb DDR4 3000Mhz
PSU - Corsair TX850M
SSD - Samsung 860 Evo 250gb
OS - Windows 10 Insider build (18219.rs_prerelease)
 
Solution


And they were working before stress test? I hardly see any connection between failed stress test and SATA ports. Even if you set CPU voltages too high it would be unlikely to damage the chipset. I would rather bet on some problems with BIOS. Start with resetting CMOS (one more time). Next step would be trying to re-flash the BIOS. Only if neither helps I would start thinking about possible motherboard failure.
Ports 5 and 6 are disabled when the M.2_2 port is in use at x4 mode. Even if it is empty, it is possible certain BIOS settings could give priority to M.2 slot over SATA ports - specifically M.2_2 port set up in BIOS at x4 instead of Auto could do that.
 
I did try that, it was already at x2, but I tried auto and there was no difference
 


And they were working before stress test? I hardly see any connection between failed stress test and SATA ports. Even if you set CPU voltages too high it would be unlikely to damage the chipset. I would rather bet on some problems with BIOS. Start with resetting CMOS (one more time). Next step would be trying to re-flash the BIOS. Only if neither helps I would start thinking about possible motherboard failure.
 
Solution
Hmm, that does sound like the way I should test it. Will do that tonight and post the results