The More PowerTool (MPT) has undergone yet another revision to better recognize installed graphics adapters (keyword: Unicode) as well as various variations of driver entries. If in doubt, the VGA Devive Manager (freeware, last page) can assist with both the removal of unnecessary entries and the detection of the most recent entry. The Radeon RX 6500 and RX 6400 are now also supported by the MPT with various SPPT. The program offers enhancements in memory settings and other areas as normal in addition to beneficial defaults for the power budget and various voltages, which AMD’s Wattman regrettably does not provide. We are focusing on a continuous growth and eagerly anticipate Navi 3x as well!
The community laments the loss of the former overclocking or underclocking bonus, which made Navi cards like the Radeon RX 5700 (XT) at least slightly more interesting or efficient and was happily accepted along as a free bonus, since AMD has significantly restricted the use of the SoftPowerPlayTables and thereby indirectly also the MorePowerTool with the Adrenaline drivers from 2020. Unfortunately, this was over for the time being because of Adrenaline 2020. However, the Red BIOS Rebellion Team’s surrounding community has undoubtedly accepted this challenge.
My gratitude goes out to the R.B.R.T. and all the active community members that tested for days and weeks and reported bugs, the outcome of which is the RBE (Red BIOS Editor). The present, initial iteration of the new tool will enable you to directly modify, adapt, and save the Radeon RX 5700 (XT) BIOS entries in a manner similar to the MPT (More Power Tool). The capabilities of Wattman and other tools are clearly outstripped by those of this tool, although there are still certain limits with the other models at this time. We also presume that everyone has carefully read the disclaimer and the opening remarks.
Currently, the MPT (MorePowerTool) works with all released Navi cards, whereby the SPPT (SoftPowerPlayTables) stored in the registry are extremely slowed down or artificially limited by the drivers. The current version of the RBE (Red BIOS Editor) allows to write all modifications of the MPT directly into the BIOS of the RX 5700, 5700 XT(X) and RX 5600 XT and to output this BIOS as a flashable file. However, currently only a single, customized version of the ATI Flash Tool allows to write at least the BIOSes created in this way to RX 5700 and RX 5700 XT(X), while there is currently no suitable software available for RX 5600 XT. If someone from the community would like to contribute and / or has the appropriate software, please feel free to contact the editorial staff. We will of course document all progress and enhancements as usual and also update them in the article. Also look for the latest beta versions!
If you accept the terms of the disclaimer, the following pages will include a brief tutorial and an explanation of the key processes. We will purposefully not post any generally valid settings because of the intricacy of the topic and the still extremely unique aspects of each graphics card (chip quality, model type, cooling), leaving it to the forum community. The risk of novice users engaging in an adventure whose outcome they are completely unable to predict due to a lack of prior knowledge is likewise reduced in this way.
The process will be explained in the paragraphs that follow using a Sapphire RX5700 XT Pulse as an example. The values will also be converted, but only very slightly, to ensure that the hardware is not harmed. The user is ultimately responsible for everything else. Otherwise, the limitations and usage guidelines outlined on page one are applicable (please read before using the software!).
Extracting the VBIOS with GPU-Z
Of course, we must first retrieve the original BIOS of the concerned graphics card and store it to disk. We utilize TechPowerUp’s GPU-Z for this (TPU). We then proceed to work in the MPT after saving the BIOS to the hard drive.
Modification of the PowerPlayTables in the MPT
This is done as usual and already known, whereby I will briefly outline the individual steps again. Most of it is self-explanatory and for more in-depth interventions I ask to approach the community in the forum. If you are not familiar with the most important basic terms, you should protect yourself and your hardware from such programs anyway. But what is absolutely necessary: the program MPT has to be started as administrator and the buttons “Delete SPPT” and “Write SPPT” are not needed in combination with the BIOS editor!
Either you select “Run as administrator” by clicking with the right mouse button on the program icon, or you specify the matching permanent default in the shortcut properties. The default settings for your chosen graphics card can be loaded into the MPT using “Load” from the previously saved BIOS (or a settings file of the MPT) and saved later as a unique settings file by clicking “Save” in the lower area. The majority of the time, the application just modifies the upper and lower boundaries of the Wattman parameters, or it either disables or enables input options. Although the software expands their input options, it does not entirely replace the Wattman from the Radeon software or other overclocking tools.
You can specify which aspects of Wattman you want to enable or disable under “Overdrive Features.” The best course of action is to choose everything. There are several SoftPowerPlayTable options that appear to be optional or that will be accessible in next Wattman releases.
Overdrive-Limits, Power-/Voltage-Limits und Taktraten
The labeling of the separate fields is likewise simple and self-explanatory, and the name “Overdrive Limits” literally says it all (picture below right). The Wattman algorithm disregards values that are more than or lower than the permissible limits. You must enter a 1 in place of a 0 for “Zero Fan Control” if you wish to use the fan control with Zero Fan Speed. Use caution when using the voltage and power limits (see image below left). Using incorrect numbers may cause instability and system failures even if the graphics card has internal protection mechanisms! Overconfident specifications, especially with the SoC, might cause a rapid collapse or overheating and throttling of the card.
Of course, the frequency parameters are the same (bottom left picture). The fan control (shown in the image to the right below) is an excellent way to acoustically optimize the graphics card with air cooler and adapt it to the user’s needs and working environment. The option “Zero RPM Enable” simply changes the status to “active,” therefore it must already be set to 1 for the Overdrive Limits number to be shown at all (see above). Only when the fan control is set to “Automatic” is this feature visible and selectable. The “Zero RPM Control” is hidden if this option has ever been set to “Manual” (see also “Fan Curve” under Overdrive Features!).
Finally, the changes are written to the MPT settings file with “Save” and not to the registry with “Write SPPT”. We need this settings file for the BIOS editor!
Modify the NAVI BIOS with the RBE
We now launch RBE and select “Load” to load the previously saved BIOS (or a suitable BIOS of our choice). Although it is not essential, you can make your card an XTX by changing the GUID (visually). However, for the time being, it does not become faster. Even though the manufacturer’s identity is not really significant, you can at least act as though it is. It is significant to remember that the Radeon RX 5500 XT is not supported (yet) at this time.
After that, we select the “PowerPlay” tab and load the previously produced settings file from the MPT. Altering the VRAM settings is something you can do if you want to. You can choose to modify the settings for the identification of the memory modules if you use, for example, a foreign BIOS of another card. The community will undoubtedly learn if and exactly what this does. This also applies to the saved strings, which ought to be updated manually only if you are completely knowledgeable in doing so.
The operation is actually quite simple now. The only important thing is to pay attention to which RAM modules were installed on the card, whose BIOS you read in! The rest is actually almost self-explanatory. Switch to the tab “VRAM Timings” and you will first see the module selection (depending on the data read in so far) and the six strings for the individual clock stages. Afterwards you can open the actual editing window via the button for the individual frequencies, because the string stored in the BIOS is initially completely cryptic and thus unusable for almost all users. But that’s where the RBE comes in: what you see after opening the timing editor looks like the BIOS of a better equipped motherboard, and the timing settings are actually similar to those of the memory.
However, one should not make any changes at a whim without some basic knowledge, because this will definitely go wrong and in the best case will only lead to instability. But this is exactly where i see the experienced and experimental community now! if you have tested your own settings and think they are worth to be made publicly available to other users – go ahead! our forum is exactly the right place for that. And maybe one day we’ll have a Hall of Fame of sorts with the best DRAM mods? come on, you’ve got the tools for it now!
Modify the Polaris BIOS with the RBE
We already know that you can only see the Polaris tabs after loading the proper BIOS. Since it nearly always stops working after changing the GPU-ID (for example, from 570 to 580), changing it should be evaluated three times before proceeding. The settings that are most crucial for giving the card new life can be found under “Clocks and Voltages.” It is clear what each label means.
More resources are available with Power Tune, but you shouldn’t let that encourage you to overindulge. Therefore, never release more than is necessary; otherwise, roast piglets will be produced more quickly than you would like. You may customize the fan control, and it’s a pretty fascinating area for your own research. However, you should exercise extreme caution when using the memory timings. Up copying can be effective but is not required.
The last, but certainly not least, step is to flash the newly constructed BIOS back onto our card. Because the Adrenaline Driver has severely restricted the execution of the SPPT stored in the registry since 2020, this is necessary. The punishment for exceeding the PowerLimit, the frequency, or the voltages is a GPU clock of 300 MHz that is no longer able to be increased. Only the PowerPlayTables, which are permanently kept in the BIOS, can assist in getting beyond this intentionally inserted barrier.
Even if the checksum is accurate, a signed BIOS must still be obtained in the usual manner. We are forced to utilize a Flash tool that disregards this signature or does not test it because the RBE cannot offer it, also due to legal considerations. Additionally, the concerned graphics card needs to be technically supported. The tool that is linked here from the web can currently only flash the Radeon RX 5700 and the RX 5700 XT(X). This flashing tool would have to be modified for the RX 5600 XT. Sadly, the Radeon RX 5500 XT is still entirely unsupported by these utilities.
The Flash-Tool is required and is linked below. Start the command line window later while running “cmd” as the administrator. Otherwise, it won’t operate. Then navigate to the directory containing the new BIOS file and the flash tool. We must first unlock the ROM in order to flash at all. With the call parameter “-unlockrom” and the adapter number (here, the first graphics card discovered is, for example, “0,” this is accomplished as shown below).
The flashing process is then initiated by calling up the flash tool once more with the proper parameters. Attention! Flashing is done at your own risk and, if improperly done or interrupted during the process, could result in a bricked BIOS. Only a second, independently controlled graphics card will be helpful in this situation.
The computer needs to be restarted after flashing. The updated information in GPU-Z is already stunning. In this instance, I had the boost clock slightly raised. The value is now 2104 MHz rather than 1925 MHz. Realistically, the card can run at 2050 MHz with the proper cooling.
However, this is only the beginning, as everyone may still make some adjustments now that I’ve finally set new Wattman limit values.
Checking results and overclocking in the Wattman
Let us first look at the initial situation before the BIOS flash. 1250 mV and 2039 MHz were maximum possible with GPU tuning, the power limit was at maximum +50.
Now that the BIOS Flash has been completed, we can see Wattman with a bit more space. 1250 mV with a 60% power cap at 2121 MHz However, I would like to emphasize once more that this is not a replica scenario and simply serves as an example of what can be achievable provided you follow the software’s conditions of usage.
We ask that you refrain from submitting any requests to the editors regarding the use or functionality of this software while it is provided here in its current state. All readers are welcome to use the forum and the lively community for any input. As a website, we just serve as a liaison between the R.B.R.T. and our website’s visitors. Additionally, a unique installer is required to download the program, which is free and only accessible from this website.