cancel
Showing results for 
Search instead for 
Did you mean: 

Bios Update Causing memory problems Rog Strix x670e-f

jel2284
Level 8

Hi everyone,

I've got problems with my X670 E-F Rog Strix. Was happily working away with 2 dimms (32gb of Corsair Vengeance 6000mhz AMD timings) on version 2007 of the firmware, and decided to add extra memory.  Used the same type of memory, but after installation the machine became very unstable, giving yellow lights on the motherboard, and crashing on the few occasions when it managed to get through POST Tests.  Checked the memory sticks in a new machine and they were fine so assumed faulty bank of memory slots on the motherboard and exchanged the board.  New board worked fine on delivery firmware with all 4 dimms so assumed problem solved.  Upgraded firmware from delivery version to 2007 and now same problem with the new board.  Must be an issue with the firmware, but now I can't roll back and am told the file is not a valid bios file.  Machine operates with just 2 dimms okay, but given the work I am doing I really need the extra ram to work.  Would really appreciate any advice.  Clearly not a hardware issue and there's other's with similar dimm issues in this reddit thread: https://www.reddit.com/r/ASUS/comments/1cba29l/x670ee_gaming_wifi_bios_2007/ Thanks so much.  

1,552 Views
7 REPLIES 7

jel2284
Level 8

For anyone else dealing with this, I managed to rollback using the Bios Flashback utility.  Details of flashback in the manual and I had to rollback to firmware 1709 to ensure all 4 Dimms would work with expo enabled. Hope this helps someone else.  

Jiaszzz_ROG
Customer Service Agent

Hello, @jel2284 

Based on your scenario description, please ensure that all memory modules originate from the same validated memory kit and refrain from using DIMMs from different memory kits.
We advise you to consult the instructions provided in [Motherboard] How to query (CPU/memory) QVL List? and also review the "purchasing and installation guide" available in the "Memory" section on the official support page of the ROG STRIX X670E-F GAMING WIFI.

Ensure that all memory modules are from the same validated memory kit. Do not mix DIMMs from different memory kits—even if they are the same brand and model (e.g., two DIMMs each from two different memory kits). 

Mixing and matching DIMMs can result in a failure to boot and compatibility issues. 

In particular, the stability of a system with mixed DIMMs cannot be guaranteed when XMP (Intel)/D.O.C.P (AMD)/EXPO (AMD)/AEMP/AEMPII is enabled. 

For example, enabling XMP (Intel)/D.O.C.P (AMD)/EXPO (AMD)/AEMP/AEMPII to speeds above DDR5 4800MHz or above DDR4 3200MHz could result in an unstable system.

Thank you.

sharing complete hardware info & software config details will help us better understand the issue 🙂

Hello.
"Ensure that all memory modules are from the same validated memory kit. Do not mix DIMMs from different memory kits—even if they are the same brand and model (e.g., two DIMMs each from two different memory kits). "

I'm having a hard time understanding this sentence - is it actually suggestion that you aren't allowed to use 2 packs of 2 modules (16/24/32 gb each)? There aren't even any memory kits that comes with 4 modules for DDR5.

Either way, I'm running the same brand, same model and make of 2x 2x16GB G.Skill 6000 CL30 which is on the QVL list for this motherboard (and they came in packs of 2...) and I'm running into unstable memory issues with any firmware above 1602; and while 1602 is nearly stable, it is still throwing a random memory error every once in a while.

Hi there, 

Thanks for the reply.  It looks like my memory is not on the QVL list, but it is now working stable with EXPO on version 1709.  No firmware above works with this.  Looking at the Reddit link I shared, and the follow up poster below, there seems to be quite a few of us with memory issues on the later firmware builds.  It also seems pretty crazy that 2 packs of the same 2 DIMM kits might not work - whether they are on the QVL list or not...

Thank you - I've noticed that the BIOS above 1602 was notoriously unstable when it comes to memory for this motherboard... I was running crazy for a bit but I flashbacked to 1602 and now I get 1 error every 20+ pass of memtest86 instead of 100+ errors within first couple of minutes.

Hopefully I can get this stable without that 1 error by slight overvoltage adjustments - but I'm just running a EXPO II and no changes beyond that....

In my case, I use 4x G.Skill @ 6000 EXPO II

Jiaszzz_ROG
Customer Service Agent

Hello, @djIfanx 

In the ROG STRIX X670E-F GAMING WIFI memory QVL filtering options, selecting "Size" and checking the options for four modules of capacity will display a list of memory modules spanning two pages.
While you are free to purchase other RAM modules according to your hardware configuration and requirements, ASUS has verified the motherboard for optimal stability and compatibility when installed with the devices listed in the Memory QVL.
Regarding the unstable issue you described, as stated in the "purchasing and installation guide," mixing different memory modules may increase instability, especially when overclocking.
Meanwhile, memory overclocking can be influenced by your hardware configuration and build environment, such as the CPU or PSU.
If the default overclocking parameters optimized by ASUS or RAM cannot meet your settings requirements, we suggest manually adjusting overclocking settings.

Thank you.

sharing complete hardware info & software config details will help us better understand the issue 🙂

Jiaszzz_ROG
Customer Service Agent

Hello, @jel2284 

Due to the correlation between memory overclocking stability and your hardware, you may consider keeping the BIOS at a stable operating version, cross-testing memory modules from the QVL list, or attempting manual memory overclocking.
If there are discussions related to manual overclocking, you can start a discussion thread in the OVERCLOCKING & TWEAKING section if needed.

Thank you.

sharing complete hardware info & software config details will help us better understand the issue 🙂