Issue with X299 RAM
Issue with X299 RAM
Hello everyone, I’m facing a somewhat odd issue that’s left me puzzled about what’s going on and how to resolve it. This might be a lengthy post since I’ll share the troubleshooting steps I’ve tried to narrow down the possibilities. I tried exchanging RAM modules between two of my PCs—one with a X299 motherboard and the other with an AM4 setup. In the X299, I used Corsair LPX 64GB (3200mts, C16, four 16GB sticks). On the AM4 side, I had Corsair Vengeance RGB Pro 32GB (3200mts, C16, four 8GB sticks). The main reason for swapping wasn’t crucial, but it was needed because the AM4 model includes a Noctua NH-D15 cooler. The Vengeance RAM is quite tall, so I had to raise the CPU fan mount on the heatsink to improve airflow and improve appearance. After the swap, my Ryzen system started up normally, showing all four RAM modules and running at the XMP 3200 setting without issues. However, when I swapped back to the Intel system with the Vengeance kit, it failed to boot. The fans spun up, some lights flashed, then the system reset itself. It didn’t even reach BIOS mode. I suspected an incompatibility, so I restored the original RAM and everything worked again. The Intel setup booted correctly, with proper XMP values. But now the Intel machine was stuck in a loop using its original RAM. I’ve gone through several troubleshooting steps and listed them below. Unfortunately, nothing resolved the problem, and I’m running out of ideas. - It’s important to note that whenever I changed RAM in the X299, I would power off the PC, disconnect the power cable, and reset the CMOS using jumpers on the motherboard. This worked when the system booted under different configurations, but then it would trigger a BIOS warning during setup. - I also checked the motherboard manual to confirm I was selecting the right RAM slots based on the number of DIMMs installed. - At several points, I left the system booting in a loop for 5–10 minutes, hoping it would identify the correct RAM. Nothing changed.
1. Verified RAM installation was secure and used compressed air to clear slots and DIMMs.
2. Tested a spare kit (Crucial 16GB, 2133mts, C15, two 8GB sticks) – system booted normally.
3. Tried another spare kit (Crucial 16GB, 2133mts, four 4GB sticks) – also worked correctly.
4. Used only two original LPX sticks; looping persisted.
5. Ran tests with just two of the original LPX modules – loop continued.
6. To ensure BIOS reset, I disconnected everything, removed the CMOS battery, and left the PC idle for 15 minutes to drain power. Also used a motherboard reset. After installing the original kit, the loop still occurred.
I’m currently limited to options. The RAM functions properly in my Ryzen system, all slots are functional, and previous configurations were reset correctly. The only remaining concern is whether the memory controller might be failing, but I don’t have a spare X299 board or CPU to test this.
The specs of my Intel system include:
- Intel i9 10980xe
- Gigabyte X299 Aorus Ultra Gaming
- Corsair H150i Pro XT
- 6 x 120mm fans
- EVGA 2070 Super
- Samsung 2TB NVME (boot drive)
- 970 Evo
- Several SATA SSDs and a mechanical HDD
- Additional PCIe cards, TP Link wireless/BT card, 10GbE NIC
- Corsair HX850i PSU
My motherboard has been in use for over a year and a half, and I haven’t experienced any problems before. I apologize for the lengthy explanation and hope this helps clarify the situation. Feel free to share any feedback or suggestions. Cheers.
It seems like a typical x99 / x299 problem. My motherboard failed right after installing a USB Wi-Fi card after roughly four years of use. It was really annoying—spent about seven hours trying various fixes, but nothing helped. It feels like if you can access the BIOS, consider a full update then retry with RAM. If you're using the latest version, a fresh flash might be the solution. HEDT platforms usually have few reports of these kinds of issues. You’ll need spare parts to check, and at least some extra RAM kits work.
Thank you for the ideas. I'll attempt a BIOS reflash to check its impact. I'm hoping it won't lead to further issues. My choices would be installing 2133 RAM with a 10980xe or swapping out the motherboard. Currently, X299 boards are pricier than they used to be.
I completed additional troubleshooting and testing. 7) I re-flashed the BIOS using the identical version to check for corruption. No changes detected. 8) I updated to the latest BIOS release, which was only available in December to fix security issues. No noticeable difference. 9) I switched to a different RAM package. Corsair Vengeance LPX 2666 64gb (4 x 16gb). I’ve only experimented with two of the DIMMS yet, but it boots normally. I investigated further into the variations between RAM modules. The only clue that stands out is the voltage levels. The two 3200 kits operate at 1.35v, whereas all three other options (both 2133 series and the 2666 model) run at 1.2v. Now, with the 3200 kits, they’re only noted as needing 1.35v when XMP is active. According to the specs, they should require 1.2v at base rate (2133). It seems XMP might be automatically activating itself, even after resetting CMOS. This issue persists despite that. I’m uncertain if adjusting the voltage settings in the BIOS would help, or if I can temporarily use higher voltages during shutdown and swap in other RAM. If anyone in Melbourne, Australia has a spare X299 board available for testing, please contact them. Any additional advice would be greatly appreciated.
Further checks were performed. 10) Adjusted the RAM voltage in BIOS to 1.35v according to the 3200 kits. This was applied to both standard run levels and memory training levels. No modifications made. Currently, the 2666 kit is installed and functions properly with an XMP profile. Someone can confirm if this problem likely stems from the motherboard or the CPU—presumably the memory controller. I’m not very familiar with it beyond its role in managing memory, but I think it’s part of the CPU. I’m trying to identify which components to test next.
I’m facing the same problem on nearly identical hardware. My ASUS X299 Sage/10G ran perfectly before, but now with OEM Samsung DDR4 at 2666 MHz everything’s stable. I have eight 16GB Corsair Vengeance LPX sticks working fine with XMP and all setups. One day it began looping, then later stopped looping but kept showing code 62 and the VGA light came on. It turns out my Vega 64 has a VBIOS glitch—last night I swapped in a 6900XT which fixed that. Whenever I try different RAM combinations or slots, the boot issues persist and the system crashes immediately after loading. I’m unsure if my memory controller is damaged or if the motherboard is beyond repair. Fortunately, the board still has warranty with the 10980XE, and the Samsung RAM is performing well now except for the speed drop noticed during video exports. My specs include: Asus X299 Sage/10G 128GB DDR4 Corsair Vengeance LPX (not installed), currently running 16GB DDR4 at 2666 with auto settings. I also have a Sapphire Toxic Air Cooled AMD Radeon 6900XT, Intel 10980XE, Corsair H150i Pro, and a WD Red NVMe card with two 8TB drives. Firmware is modified for Hackintosh, and I’m using a Seasonic 1300W power supply. I removed the GPU in 2020 to install the board and it’s functioning as expected. This situation is really frustrating.
I look forward to hearing about the outcome. I replaced my old processor (7820x) and haven’t been able to check that part. Right now I’m stuck, really. I’m using a 64GB Corsair LPX 2666 in that PC, which is fine but not perfect. It might be because of the memory controller or the voltage needed for faster RAM modules. I don’t know for sure unless I upgrade or get access to different boards or CPUs. Please let me know what you found.
Last night I installed my 9900X. It didn’t improve much. My ASUS x299 Sage/10G seems fine with the RAM, but I still have warranty until October. I suspect a pin on the board is bent. The board type is LGA 2066 and it felt odd at first, but after checking for an hour it looked normal. I replaced the 10980XE and used Corsair RAM (all 8 sticks at 128 GB with XMP) – it didn’t work. At auto and 2133 it got into the OS, but opening any window caused a reboot. It didn’t progress very far before that. This RAM had worked for two years, even after swapping in a brand new set from Kingston, which suggests the problem isn’t with the RAM itself. I put the generic Samsung RAM back in and everything functioned at auto 2666. I recorded a 1-hour 4K/23.98 timeline in Final Cut without pre-rendering, and it completed in about 11 minutes. I ran it several times and it was stable. I’m considering sending it to RMA this week (ASUS is nearby – I hope they allow me to drop it off as they did with friends). If it’s a socket issue and they find a bent or broken pin, I’ll pay for the replacement, since the board cost over $1000 CAD and I want this machine to last at least another five years.
Really annoying. Not impressed by the CPU swap not helping. It seems to point at the motherboard, though. I've used the same board for more than four years and it's beyond warranty. I'm hoping the Asus returns can help. Would love to know what they discover.
I’ll submit the board tomorrow. If a pin on the socket is damaged, I’ll cover the cost to repair it. The remaining parts are covered by warranty—hopefully, if they replace or fix it, they’ll let me know what else might be faulty. For instance, if better VRM cooling could be the issue, I’d like to explore that further. They mentioned a 15-day turnaround including shipping (probably due to COVID restrictions), so I’ll wait about two weeks before making a decision.