Question Unable to Simultaneously Use NVMe and SATA

Nov 14, 2024
2
0
10
Build info:
ASUS Z170-A
Intel i7-7700k
Nvidia 2070 Super
AORUS wifi card

Drives:
PCIe WD Black 2TB
HDD WD Black 4TB
HDD WD Green 1TB

System previously ran on a SATA SSD with 4 other SATA connections with no issue. Since installing the NVMe drive the system will run continuously but not post unless the only drive connected is the PCIe (some rogue cases where if the 1TB is connected with the PCIe it will boot, but not consistent). Currently having it run fine on only PCIe and have since updated all drivers and my BIOS.

I haven't touched BIOS settings too much besides switching PCIe express to M.2, was considering toggling hotplug and testing how the PC handles that.
So far have been able to boot with all 6 plugs, for some reason also including the PCIe express which from my understanding shouldn't work so perhaps I've not configured my bios properly?

My current running theory is a power issue, whether that be from the PSU itself or perhaps from the motherboard. I think I'm on the tipping point for power usage as a rough estimate of my power usage puts me at about 700watts from my understanding. I heard running CCOT can help determine if my power is insufficient but I don't fully understand what that program shows so have so far ignored it.

Any ideas as to what the issue might be would be much appreciated!
 
read through your motherboard manual, especially added notes.

many times you will be sacrificing certain lanes of traffic by using different PCIe slots, M.2 ports, etc.

perhaps I've not configured my bios properly?
choosing to "Load Optimized Defaults" will usually set you up for basic higher-end system use.

if anything in your manual provides extra settings that may be necessary for your particular scenario,
then go in and change those values.

think I'm on the tipping point for power usage as a rough estimate of my power usage puts me at about 700watts from my understanding
your particular PSU has a lot to do with power usage, issues that may arise.

many units out there do not provide what they may state in the rated specs.
and even if they may under certain scenarios, with heavy usage and spikes from certain systems they still may not be able to handle the load.
 
Build info:
ASUS Z170-A
Intel i7-7700k
Nvidia 2070 Super
AORUS wifi card

Drives:
PCIe WD Black 2TB
HDD WD Black 4TB
HDD WD Green 1TB

System previously ran on a SATA SSD with 4 other SATA connections with no issue. Since installing the NVMe drive the system will run continuously but not post unless the only drive connected is the PCIe (some rogue cases where if the 1TB is connected with the PCIe it will boot, but not consistent). Currently having it run fine on only PCIe and have since updated all drivers and my BIOS.

I haven't touched BIOS settings too much besides switching PCIe express to M.2, was considering toggling hotplug and testing how the PC handles that.
So far have been able to boot with all 6 plugs, for some reason also including the PCIe express which from my understanding shouldn't work so perhaps I've not configured my bios properly?

My current running theory is a power issue, whether that be from the PSU itself or perhaps from the motherboard. I think I'm on the tipping point for power usage as a rough estimate of my power usage puts me at about 700watts from my understanding. I heard running CCOT can help determine if my power is insufficient but I don't fully understand what that program shows so have so far ignored it.

Any ideas as to what the issue might be would be much appreciated!
If using the sata express ports switch to the normal sata ports.....test.
 
Nov 14, 2024
2
0
10
Your motherboard manual will tell you which SATA ports are disabled when installing an NVME drive. If there are multiple slots then there will be additional restrictions applied.
Yes I've already noted the disabled ports (SATA express X2 in this case)

Oddly the first time I managed to get my PC to run with all drives active was when I hail Mary plugged my drives into it, though that could be due to the sockets being disabled and thus while being detected wouldn't actually function as I didn't test files in them.