cancel
Showing results for 
Search instead for 
Did you mean: 

ROG Strix Z790 BIOS Update 3001 broke XMP

BrianB1
Level 7

I recently updated the BIOS on my ROG Strix Gaming motherboard from 2801 to 3001. The reason was the fix for the VMIN Shift vulnerability on my Intel 14th GEN processor. I was using XMP1 with no problems until the update. My PC started crashing. When I turned off XMP everything became stable. I have tried both XMP1 and XMP2 to no avail. I have run memtest86 for 12 hours with zero RAM errors. I don't want to revert to 2801 because of the CPU fix. Can someone advise me what manual settings I should enter for my compatible Corsair CMT64GX5M2X5600C40 RAM to run stable at 5600 with the 3001 BIOS update?

1,352 Views
9 REPLIES 9

inge70
Level 15

Are there any entries in the event log and reliability history regarding the crash?
Did you run Memtest86 with XMP or without?

Without XMP, Memtest86 unfortunately doesn't tell you anything (other than that the RAM is OK) to attribute the PC crash to XMP and the current UEFI.

What CPU do you have exactly?
Have you configured any overclocking or undervolting?

I'm also using the current UEFI 3001 on my motherboard (see signature) with an i7-13700K (without overclocking), and my RAM runs at a full 5600 MT/s with XMP, despite being fully populated with four RAM modules (according to Memtest86).

Intel Core i7 13700K / AiO Fractal Design Lumen S36 v2 RGB / Asus Rog Strix Z790-F Gaming WIFI / Corsair Dominator Platinum DDR5-5600 64GB (4x 16GB) / Asus TUF RTX 5070 Ti OC / 4x Samsung 980 pro 1TB / Seasonic Prime GX 850 W Gold / Fractal Design Meshify 2 Lite RGB Black TG Light Tint / Monitor AOC Q27G2S/EU (WQHD)

I couldn't see anything related to the crash in the event log. Yes, I ran memtest86 twice. Once with XMP1 and once with XMP 2 and got zero errors. When I disable XMP, my RAM drops to 4800 and everything runs fine. Before updating to 3001 everything ran fine on XMP1 at 5600. My CPU is an Intel i7-14700k, and it is running on the BIOS defaults. No overclocking. I am running 2 Corsair Dominator Platinum 32GB Modules in the correct slots. They are model number CMT64GX5M2X5600C40 which are on the Motherboard's compatibility list.

OK - I went back into Event Logs and filtered per a recommendation I saw on the Internet. The only entry I can see is at 9:20AM and it simply says "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."


@BrianB1 wrote:

I am running 2 Corsair Dominator Platinum 32GB Modules in the correct slots. They are model number CMT64GX5M2X5600C40 which are on the Motherboard's compatibility list.


What is your total system memory? Are you saying you are running 2 kits i.e. 4 sticks of 32GB each with a total system memory of 128GB? Or are you using 2 sticks of 32GB each with a total system memory of 64GB?

Disclaimer: I am not an ASUS support person so my information may be incomplete. Always follow official documentation and material provided by ASUS representatives.

INTEL i9-14900K / CORSAIR VENGEANCE RGB 192GB (4x48GB) 5200 CAS38 / ROG Z790 DARK HERO / ROG TUF GAMING RTX 4090 OC / ProArt PA-602 Case / SEASONIC PRIME TX-1300 ATX 3.0 / CORSAIR MP700 PRO 2TB PCIe Gen5 / CRUCIAL T500 2TB PCIe Gen4 / EIZO CG2700X

I am running 1 set of 2 32gb sticks which are on the asus compatibility list and they worked fine on xmp prior to the bios update

Any Other thoughts?

 

No answer yet.

Devilish_Prince
Level 7

I have the same problem as yours, after updated BIOS version Version 2001 for my motherboard (ROG STRIX Z790-A GAMING WIFI II), My XMP profiles for my ram kits is no longer working as before, during gaming the system would hard crash, Kernal 41 Event is what showing on Event Logs. My ram Kits is Corsair Dominator Titanium RGB DDR5 48 GB (2×24 GB) DDR5-7200 CL36 (CMP48GX5M2X7200C36). I had to lower down to 6400 mhz for stability. We need get ASUS to fix it with new BIOS update

Thanks for posting. I agree. I had a ticket opened with ASUS but they basically didn't care to hear about it and brushed me off.