Just want to share my experience:
I had my Gigabyte Z390 MASTER with i9-9900K up and running for some months (at stock speeds with bios F6).
Now I added the GC-TITAN RIDGE PCIe x4 card in order to have dual Thunderbolt 3 ports. The card is installed in the bottom x4 slot, which is served from the Z390 chipset. The internal USB 2.0 header of the card is connected to the M/B and also the dual 6-pin power connectors to the PSU.
The card works really well with a Samsung X5 NVMe Thunderbolt 3 external 2TB bus-powered SSD.
From a Samsung 970 Pro 1TB MLC NVMe M.2 (served by PCIe 3.0x4 CPU lanes), a simple file copy of a large 16GB file to the X5 is at around 1.5GB/sec (with the X5 being less than 30% full).
Software is:
- Windows 10 Enterprise 1903.
- GC-TITAN Ridge Thunderbolt driver 1.41.648.4 (dated 2019/06/28) with NVM firmware 23.0 (via Gigabyte website)
- Thunderbolt Control Centre version 1.0.18.0 (via the Windows Store)
Important remark: I had to enable write caching on the X5 via Windows Device Manager to achieve expected write speeds; without write caching enabled the write speeds were maxing out at less than 400MB/sec.
/Toad
I had my Gigabyte Z390 MASTER with i9-9900K up and running for some months (at stock speeds with bios F6).
Now I added the GC-TITAN RIDGE PCIe x4 card in order to have dual Thunderbolt 3 ports. The card is installed in the bottom x4 slot, which is served from the Z390 chipset. The internal USB 2.0 header of the card is connected to the M/B and also the dual 6-pin power connectors to the PSU.
The card works really well with a Samsung X5 NVMe Thunderbolt 3 external 2TB bus-powered SSD.
From a Samsung 970 Pro 1TB MLC NVMe M.2 (served by PCIe 3.0x4 CPU lanes), a simple file copy of a large 16GB file to the X5 is at around 1.5GB/sec (with the X5 being less than 30% full).
Software is:
- Windows 10 Enterprise 1903.
- GC-TITAN Ridge Thunderbolt driver 1.41.648.4 (dated 2019/06/28) with NVM firmware 23.0 (via Gigabyte website)
- Thunderbolt Control Centre version 1.0.18.0 (via the Windows Store)
Important remark: I had to enable write caching on the X5 via Windows Device Manager to achieve expected write speeds; without write caching enabled the write speeds were maxing out at less than 400MB/sec.
/Toad
