ASUS TUF Gaming X670E-Plus
AM5, AMD X670E, ATX
Question about ASUS TUF Gaming X670E-Plus
I've had a lot of problems with the board so far. Bought this RAM https://www.digitec.ch/de/s1/product/corsair-vengeance-rgb-2-x-16gb-6000-mhz-ddr5-ram-dimm-ram-21580100?supplier=406802 Could it be that these are not really compatible?. I have a strange problem that the PC does not boot up at the first boot attempt after it has been switched off for a while, e.g. 12 hours or overnight (The PC boots up, but no picture appears, although the screen DP is recognised). The POST LED then changes to green fairly quickly and the screen shows that it is active and DP is running. But then there is no mainboard logo and nothing, the picture remains dark and the PC runs on its own. So I can't even get into the BIOS. When I restart it on the second try, it starts normally. I haven't found a solution to the problem yet. The two RAM bars run at 4800mhz each and are not overclocked at 6000mhz. The same problem exists when I run them at 3600mhz. But when the PC then runs, it runs reliably and without problems. Does anyone have any ideas?
I have the same kind of problem. I've now noticed that the first ram bar sometimes just lights up in its rainbow colour again as if it wasn't even activated. It doesn't appear in the system either, but it works :D.
Had the Corsair Dominator 2x16Gb 6000 inside. The problem with being off for longer than 12 hours was also constant. Sometimes it took up to 2 hours before I got a desktop image. Bios updates didn't help either. Expo or not.
Now a new attempt with the Vengeance and no problems since then. My guess is still the board. As another latch disconnects from the RGB
Had the Corsair Dominator 2x16Gb 6000 inside. The problem with being off for longer than 12 hours was also constant. Sometimes it took up to 2 hours before I got a desktop image. Bios updates didn't help either. Expo or not.
Now a new attempt with the Vengeance and no problems since then. My guess is still the board. As another latch disconnects from the RGB
In general, this board is about the last I've had from ASUS in a long time. Especially disappointing is that ASUS doesn't seem to care; incompatibility with specified RAM, the necessary throttling of the clock for 128GB Ram, unusable PCIe socket if you need 4 m2.sata and so on. Unfortunately, the whole board is a disaster.
I have some problems until it runs, then RAM update to 128GB... that's it... The board doesn't come up any more, gets stuck either at the error RAM (LED indicator yellow) or then at the CPU (LED indicator red).
I have some problems until it runs, then RAM update to 128GB... that's it... The board doesn't come up any more, gets stuck either at the error RAM (LED indicator yellow) or then at the CPU (LED indicator red).
Sounds like a solution that doesn't work with 2Rams 😔
Update on my problem: Apparently it is normal that the initial training of the RAM (after a BIOS change or similar) can sometimes take 5-10(!) minutes (during which the Q-LED lights up yellow) if you have 4 DIMMs with a total of 128GB occupied. In addition, it is probably normal that on DDR5 boards larger and especially more than 2 RAM sticks can only be used with a slower clock rate. After the eternal, first boot, the RAM must be throttled to 3600MHz in the BIOS (more is not possible with 128GB). After that, everything works wonderfully and the box boots within seconds.
So if you want to use more than 2 DIMMs, you can just buy the cheaper, lower clocked RAM.
So if you want to use more than 2 DIMMs, you can just buy the cheaper, lower clocked RAM.
By the way, nothing has changed with the current bios (1410). In the meantime, I have upgraded my memory to 64GB (G.Skill 64GB DDR5-6000, CL32, EXPO) or replaced the kit. If the computer is switched off overnight, the screen remains dark when I switch it on. The debug light then lights up red. A reset then leads to everything working again in perfect sunshine.
The Vengeance should have Samsung ICs. I run the board with Kingston Fury Renegade, with Hynix chips. The behaviour after a full shutdown is sometimes similarly cryptic. The normal behaviour seems to be that the box turns on, initialises briefly, turns off again and then restarts. All in all, the platform is still quite fresh, and the currently available bios from November is only the third (?) ... Since the box otherwise runs fine, I have decided to accept this for the time being and hope for selective improvements with bios updates.