My X399 AORUS Gaming 7 (version 1.0) functions properly with 128GB of memory as of October 1, 2017.
My X399 AORUS Gaming 7 (version 1.0) functions properly with 128GB of memory as of October 1, 2017.
Recent updates indicate BIOS version F3d with memory interleaving enabled in Channel mode contributed to system stability. Further details will be added if more information becomes available. A September 19 update notes replacing the 980Ti with a Quadro K1200 made full memory visibility possible in BIOS, while disabling the built-in WiFi adapter in Windows helped achieve stable booting on 128GB RAM. The System Control Panel now displays the complete 128GB availability. Later attempts to install Ubuntu nightly encountered persistent PCI Express errors related to the WiFi adapter. A post references a Gigabyte forum thread discussing this issue, suggesting a widespread problem with filling all DIMM slots with 16GB modules. Windows 10 reports 128GB total but only 95.9GB usable due to instability. The author advises against using AORUS Gaming 7 for systems with 128GB RAM and mentions the F2 BIOS remains relevant.
It seems the system defaults to 1.2V in BIOS, but the manual shows 1.4V. That difference might be a bug. I'm testing with 96GB and still see 95.9 GB available, even after running MemTest.
It's disappointing to see Gigabyte not meeting expectations for the Zen platform. It's surprising given their past use with older K8 and Phenom setups.
I've never encountered anything similar before. The system becomes unstable when I use the final portion of memory with 96GB installed, indicating a problem.
I'm really frustrated. No update from Gigabyte either. My Asus board was already bad—there was a problem with the Foxconn screw—and now it's worse. Please do your part. Edit: Received a reply. They recommended re-seating the CPU, but that didn't help. I had only 96GB installed, then added another 32GB and swapped in a Quadro K1200 card instead of the 980Ti. Now the BIOS shows 128GB, but Windows 10 crashes right after login, claiming it tried to write to read-only memory.