RaptorLake Resources

[Shamino]

i will use this as a collection of test bioses/tools/info targeted towards Raptorlake + z69/790

NOTE for Z690: You must update ME on your Z690 to properly support raptorlake (if you are on dual bioses then you need to do this to both bioses)

1) d/l and install ME driver
https://dlcdnets.asus.com/pub/ASUS/mb/03CHIPSET/DRV_MEI_Intel_Cons_ADL_TP_W11_64_V2229320_20220809B....

2) update ME with ME Update Tool (I know there are newer versions but its not up on Asus official site yet so >= this version is fine)
https://dlcdnets.asus.com/pub/ASUS/mb/03CHIPSET/MEUpdateTool_16.1.25.1885_T.zip

3) update to Latest BIOS of your choice

Note 2 for Z690: i have some Z690s that are already LOW in battery so you are advised to use a new Battery during this upgrade.

New test bioses

Z690 Apex

Z690 Extreme

Z690 Hero

Z690 Hero Eva

Z690 Extreme Glacial

Z690 Formula

Z690 Strix E

Z690 Strix F

Z690 Strix G

Z690 Strix A WIFI D4

Z690 Strix A WIFI

Z690 Strix I

Z690 Creator

Z690 Prime A

Z690 Tuf

Z690 Tuf D4

Z690 Tuf WIFI

Z690 Tuf D4 WIFI

---------------------------------------------------------------------------------------------

Z790 Extreme

Z790 Hero

Z790 Apex

Z790 Strix I

Z790 Strix F

Z790 Strix E

Z790 Strix A D4

Z790 Strix A

Z790 ProArt

Z790 Strix H

Z790 Prime A WIFI

Z790 Prime M Plus D4

Z790 Prime P

Z790 Prime P D4

Z790 Prime P WIFI

Z790 Prime P WIFI D4

----------------------------------------------------------------------------------------

Latest ocpak

Turbovcore
https://www.dropbox.com/s/ifsr8x0zncxcvyd/TurboV_Core_1.10.20.zip?dl=0

----------------------------------------------------------------------------------------

[lastique]

> With the older microcodes that still had Intel's voltage bug, the settings in the UEFI were bypassed and the CPU could request high voltages despite other settings. That was the problem up to now, that despite other UEFI settings, the CPU could call up higher vids and visibly also received them in some cases.

Is this accurate? I believe, the "IA VR voltage limit" in the "Intel CPU Power settings" was always adhered and limited VIDs requested by the CPU, on any microcode. This behavior was confirmed by Buildzoid on microcode 0x125 (though on a Gigabyte board, which has an equivalent setting). I'm on a 12th gen and Z690 Hero BIOS 3501, and I can confirm this limit works on my system. By default, that limit is Auto (i.e. unlimited), but users could always set it to a reasonable value to protect against overvolting their CPUs. In particular, setting it to 1550 mV sets the same limit that is enforced by microcode 0x129 in the Intel Default Profile by default.

[inge70]

The 12th generation is not affected by this problem. The microcode bug did not bypass the UEFI settings.

According to Intel, only the 13th and 14th generations are affected by the eTVB bug and the bug in the microcode that led to high voltages.

So your observations on the 12th generation are not useful.

[lastique]

> The 12th generation is not affected by this problem.

> According to Intel, only the 13th and 14th generations are affected by the eTVB bug and the bug in the microcode that led to high voltages.

I think, this is also inaccurate. Intel admitted the problem in 13th and 14th gen CPUs, but to my knowledge they did not comment about 12th gen CPUs.

Based on online reports, there were much less problem reports on 12th gen than 13th and 14th gen, and this is understandable since 12th gen supports much lower clocks and therefore requests lower VIDs by default. In other words, 12th gen CPUs aren't frying themselves only because they don't reach as high clocks by default. That doesn't mean the 12th gen CPUs won't request insane VIDs when overclocked and not constrained, as 13th and 14th gen CPUs did at stock prior to the 0x129 microcode update.

[inge70]

It wasn't about what kind of video a CPU requests when it's overclocked, but rather that the 13th and 14th generation CPUs requested high voltages without OC and could be damaged as a result.
This is to be fixed with microcode 0x129.

It has been known for years that high voltages are sometimes applied during OC and every user who does OC should be aware of this.
Nobody gives a guarantee on the hardware for OC.

Anyone who does OC accepts that the specifications programmed into the microcode are being circumvented and runs the risk that the hardware could be damaged in the long term. That's why powerful cooling is important and you should know what you're doing when doing OC.

[Silent_Scone]

12th Gen CPU VID range is lower hence why they're not impacted.

[VincentMG22]

A few beginner questions: I have Prime Z790-V AX motherboard;

1. do I need to install the ME driver listed here and ME update tool or is that only for z690?
2. is this just the same as the Chip-set update listed on official ASUS?
3. are you folks not installing the official BIOS updates? I don't see my motherboard listed above, but ASUS has a newer official one. Seems like the official ones are giving people issues?

Thanks!

[inge70]

Firstly, the UEFI update updates the firmware of the Intel ME. As it says in the text about the UEFI update.

1) The driver for the Intel ME, which is displayed in the Windows Device Manager, has nothing to do with it.
This will probably be updated by Windows Update if an update is available. You can view this in Windows 11 under Settings/Windows Update/Advanced Options/Optional Updates.

2) The chipset driver does NOT update Intel ME. BUT the corresponding Intel ME driver is listed under "Chipset".
Therefore, if you click on "show all" under "Chipset" on the Asus website, there is also a separate driver for Intel ME. Unfortunately, it is out of date. But Windows will keep it up to date for you. At least that's how it was for me so far and I currently have driver version 2406.5.5.0 from 02/2024 installed.

3) A BETABios update has already been listed for your mainboard, which contains the current microcode 0x129.
The fact that your mainboard is not listed in the Shamino or Safedisk list is only because they were the first betas for various mainboards before Asus started to link the corresponding beta updates on the respective support pages of the individual mainboards.
It should also be said that the UEFI/Bios updates from Shamino linked above are outdated and the list was last edited in 10/2023.
The list here in the thread page 53 of Safedisk is more current, although your mainboard is not listed there, but @SAFEDISK does not guarantee that it is complete. Unfortunately, there are too many mainboard variants for that.
Asus itself has promptly started to link corresponding BETA updates to the respective mainboards.
But remember, they are BETAs, i.e. test versions. It usually takes about 1 week until they are declared final, if no serious errors are reported.

[VincentMG22]

Ok another beginner question. I updated my BIOS using the official ASUS update (PRIME-Z790-V-AX-ASUS-1662). I noticed that after the update X.M.P. was "disabled". It had previously been "enabled"... is this by design to fix the problem or am I save to enable it again?

[inge70]

XMP has never been active by default. That would be fatal, especially if RAM is used that may not appear in the motherboard vendor list.

What do you think would happen if it was automatically active but the RAM then didn't work with it and there were problems when starting up for the first time?

XMP always has to be activated manually. As far as I know, that's always been the case, as it's overclocking the RAM.

This is also the case with standard Intel settings, which Intel has now asked motherboard manufacturers to use.

If you want to use XMP, then activate it in the UEFI/BIOS.

Bear in mind that the next time you start up the PC, it will take a little longer and you won't have any image at first, as XMP first tests the RAM to see if the settings stored for XMP on the RAM are correct.

If the RAM settings are not correct, the motherboard should deactivate XMP again and run the RAM at the standard clock speed.

It should be noted that Intel CPUs of the 13th and 14th generation. officially only supports RAM up to 5600MHz. Anything above that is overclocking, which means it CAN work but doesn't have to.

[VincentMG22]

Thanks so much for your thoughtful replies. That helped a lot. So seeing as I'm still only using the RAM installed by manufacturer (and they had XMP enabled), I will assume it's safe to turn it back on after the BIOS update. Thanks again.