09-26-2024 01:29 PM - edited 09-26-2024 09:55 PM
Problem: X670E-A QVL Memory, after setting EXPO, won't post after reboot. Stuck in memory training with yellow light on motherboard. Waited over 30 minutes.
Observations:
I've opened a support ticket with Asus and it's supposedly being "escalated" but I honestly don't know how far I'll get.
Anyone else experience this?
4 weeks ago - last edited 4 weeks ago
No, Asus wants to replace my board, although I'm not sure it's going to make any difference. I'm going through the process now.
3 weeks ago
Check your RAM's XMP/EXPO Profile: Ensure you're using a profile that's explicitly supported by your RAM manufacturer and is listed as compatible with your motherboard (even if it's on the QVL, it's crucial to check for specific profile compatibility). Try a different, more conservative profile if available. stbemu codes
3 weeks ago
It is the incompetence of asus to get anything right it has been like this through all bioses for sure and it gets old. They are so incompetent asd you cans ee even from youre own issues is the same with everytone else.
3 weeks ago - last edited 3 weeks ago
Why is it ASUS's fault you can't overclock your memory? The OP hasn't even posted what kit it is, either which is super unhelpful. If AMD updates FW then sometimes this can break overclocking - that's why manual tuning is available...
3 weeks ago - last edited 3 weeks ago
What you're missing is the QVL part. This means ASUS has tested and says "these kits work OC'd". Not that it matters for you, but my kit is F5-6000J3238F16GX2-TZ5NR, which is on the QVL list.
The other piece you're missing is I've stated it's stable. It works perfectly but only allows me to shutdown or power on. Reboots are where it faults out which is clearly a motherboard issue. Given the fact that Asus wants to replace the board should be the other indicator it's a board issue.
The final straw is that it works perfectly on BIOS 2007 and before. When I flashback, everything works. This...is a BIOS issue, plain and simple.
3 weeks ago
Of course its asus fault if you have been booting all the time like me and now all of a suddden you cant by changing bioses. Its time for asus to face the consequences of there hap hazard ways of breaking stuff all the time. Who is apparently reviewing bioses and stuff do not know what they are doing at all. period
3 weeks ago - last edited 3 weeks ago
"Boot times"? Assuming you're talking about memory training. That's also down to the platform, inital training routines can take up to 3 minutes or more, that's a trait of AM5. I don't think you understand the absurdity of the allegations you're making, although I appreciate that memory overclocking can be daunting when plug and play doesn't go how you expect it.
3 weeks ago - last edited 3 weeks ago
Not missing anything. ASUS doesn't have access to every combination of kit and CPU on the market. I'm sorry, but if you think that ASUS can accommodate all variance when overclocking then you don't understand the concept of it in the first place. You're running the system outside of specification. Why do you think ASUS gives you access to the voltage rails in the first place?
If you're stable in the OS, why don't you simply enable Memory Context Restore in the BIOS? That will stop the system trying to retrain at each boot. It's important to understand memory training and OS stability are quite different, but there are benefits from stopping the stopping the system from retraining each time in some instances depending on the condition of the OC.
The QVL is designed to help users, that much is obviously true - but it doesn't give guarantees. If overclocking was always assured it would be extremely dull...
If you don't want to open yourself up to the possibility of manual tuning, go back to a build that works with auto rules. You can't have auto rules that accommodate *every* CPU, not to mention when AMD AGESA updates have an impact on overclocking.
Or if you'd open yourself up to the possibility of asking how to potentially tune manually and ask for guidance that's also a possibility.