Will Msi Live Update 6 Do Bios Flashing?

*** Under Construction Concluding update: 21/02/17 ***

Updated 23/03/17:-

i) added AlKappaccino testing information of OC'ing

Notation:- As of Fiji bios editor v1.two all mods well-nigh users may crave can exist done. The manual mods are still in OP for those that wish to know how the editor was adult on mods I tested. They are as well there so others may develop a mod and share it.

Note:- Whatever stock ROM even with a UEFI/GOP module within it, is technically non-UEFI once modified. There is a bios signature inside Legacy ROM section, which is a hash of the hashes of protected tables within ROM. As the mods we do are within the protected tables and nosotros can't update the signature in Legacy ROM to reverberate the changes it will fail UEFI checks, thus you demand CSM support enabled in motherboard bios to apply a modded ROM. The only solution to allow custom UEFI ROM with CSM = Off, is to apply a custom UEFI/GOP module in ROM. This solution was provided by Lordkag of Fernando'south Win-RAID Forum. The update tool is located in advisable heading beneath.

Brand fill-in of original bios on video card, for each switch position.

Edit copies of your original bios, so you ever have original unedited bios to use if things go bad.

Do not flash both bios positions equally so at least you'll have choice to boot from other if something goes wrong.

Do non take HWiNFO, GPU-Z, MSI AB, TriXX, etc running in the groundwork when flashing ROM to card.

Alert: Using this guide to edit your bios volition void your warranty (if bill of fare has one). This guide is provided assuming a user knows implications of what they are doing. I have no responsibleness for damage from using this information. All efforts are being made to double check data simply at that place possibly errors.

Quote:

Originally Posted by AlKappaccino

Greetings,

late to this political party, but anyways. I started to oc my Fury 10 again, after I went back to stock when ReLive came live and now I desire to share some OC results with you.

I use OPs custom BIOS and changed MVDDC back to stock ane.300V. My carte du jour at stock runs VID on DPM7 with 1.187V which I inverse to i.231V. I used the already set up +25mV offset simply decreased VID of DPM0-DPM6 appropriately to match stock values again. And so DPM0-half dozen is stock and DPM7 is around 1.256V nether usage.

Cadre Clock on 1140mhz at 1.256V runs stable so far, running multiple stress tests. OC in percent = +8%

HBM can run stock with -25mV but for 545mhz, ane.300V is necessary Going higher results in memory error. OC in percentage = +viii%

GPU gets around 48-50°C, VDDC Temp become as high as 65°C and MVDDC is around 49°C. Logged with HWiNFO64.
I use a pretty ambitious cooling bend though, running one,900rpm about of the time, which is an acceptable noise level for me.

And earlier I forget, my HW is: Windows 10, AMD ReLive 17.3.1, Radeon Fury X, Xeon E3-1231v3, [email protected] of DDR3 ram

So I ran a few benches to run across the functioning departure betwixt stock, core oc, HBM oc and both overclocked. I ran each test three times and used the average of those for the diagrams.

So first of, Valley benchmark with Ultra Preset. Min and Max FPS is not that important. 0,1/1/99-percentile would be much better, but I wanted to keep information technology simple. Allow'due south talk about avg. FPS so.
We tin can encounter, that HBM oc just already gives u.s. a boost of around +12%. Core OC gives us a boost of +15%. OCing both, results in literally the aforementioned, even a chip less. Even though the card maintained their max clock speeds, some kind of throttling seems to take place.

[/IMG]

Next up, 3D Mark. In Burn down Strikes Loftier Operation exam, HBM oc gives +2%, core and both oced requite around +8% operation heave. Once again Core gives you more performance per % of oc, but oc on both tends to be even a tidbit worse than ocing merely the core.

Heading over to 3D Marks Time Spy benchmark, we see a very interesting outcome. HBM oc now gives u.s. -ane.7% performance in overall score, on graphics it's withing margin of error. Core oc nonetheless increases our performance by around +5%. Again, OC on botch results the same.

On Deus Ex: Flesh Divided (DX:MD) I used the built in criterion on DX12, combined with a custom preset (Ultra with tweaks) I gear up for my game. Nosotros can now see, that HBM oc does naught and even the 8% core clock increase gives us only four,viii% FPS increase. I was curious whether the increased HBM clock really does zilch, so I as well measured the frametimes using OCAT/PresentMon with those results:

While definitely not the all-time frametimes, we see that HBM oc performs exactly equally stock. Only core clock increase results in a ameliorate avg. consequence simply oc on both give the states the shortest spikes and overall all-time timings. Which is interesting, considering the reported FPS is the aforementioned.

Conclusion: While not the virtually comprehensive benchmark, I get a similar pattern throughout each test and I try to extend that when I got fourth dimension. HBM oc does literally cipher at all, with the exception of Valley benchmark. Increasing the core clock results in minor operation increases, but you lot're very limited on how far yous can push the carte du jour. A typical combination of both, seems to run the card into some kind of throttling (The clockspeeds stayed at max though). We can often meet a slight decreased performance, even though information technology should be always slightly college at minimum. But temps are okay, so are the used voltages. Every bit of now, it seems that you gain null from HBM OC, but it may vary in different applications. I'll effort to look further into this.

Oh and yeah, here are some AIDA64 screen I took. Ane is full stock (1050/500), the other full oc (1140/545):

Fury 10 3DMark 13 Mega bench (FS / FSE / FSU over 250+ runs) by gupsterg

AtomBIOS

AtomBios is the ROM on card.

Quote:

AtomBios info

Cantlet is basically a byte code scripting language used to write little scripts to handle bones card initialization tasks (asic init, setting engine/memory clocks, modesetting).

In that location are two sets of tables in Atom: command tables (basically scripts that execute certain functionality) and information tables (structs that shop lath/system specific information (type and number of connectors/encoders used on the board, power states, ddc lines, panel info, etc.).

The command tables are versioned and there are specific structs defined for the inputs to the command tables. These are all divers in atombios.h and ObjectID.h. Command tables tin also call other command tables and look up data in information tables.

Extract from, another useful folio to view.

AtomDis (AtomBios parser) installation and usage in Ubuntu

1. Used this guide to install VM of Ubuntu , I used Ubuntu 32bit version.

2. Click Files icon in launcher bar , you lot will now be in your user dwelling directory. Right click a empty department and select Open up Terminal

*** Commands in terminal window are case sensitive ***

3. Install git , blazon command sudo apt-get install git

4. Clone the AtomDis files , type command git clone git://people.freedesktop.org/~mhopf/AtomDis

5. Now compile the downloaded AtomDis files, type command make

6. To see supported commands for atomdis blazon command ./atomdis

7. Yous tin brand atomdis output data to txt by adding >filename.txt , for example gaining tables of a bios.

./atomdis yourbiosfilename l >bios_tables.txt

Another method I utilise is selecting and copying created tables list in terminal window and the pasting it into PasteBIN. I tin then share this paste or view information technology in windows whilst Ubuntu running in VM, I also use googledrive as I quick method of transferring files between windows & Ubuntu VM.

AtomBiosReader for Windows by @kizwan

Creates tables for a ROM like AtomDis in Linux, in the created tables lists y'all will find "Command Tables" and "Data Tables". Pretty much all edits nosotros will be doing are"Data Tables".

Extract from created tables list for a ROM:-

Lawmaking:

Code:

                  000f:   a0da  Len 02b4  Rev 07:01  (PowerPlayInfo)

Each tabular array gets a hexadecimal number in the listing, in above case PowerPlay is 000f.

After that we encounter the beginning location for PowerPlay in the ROM = a0da , if we pick "Search" then select "Goto" from menu bar in HxD (hex editor) and type that outset location the cursor will go there.

Subsequently that we see length in hexadecimal of the PowerPlay table in the ROM, 02B4 . If we pick "Edit" so "Select cake" from menu bar in HxD and enter the offset location a0da and the length 02B4 the whole PowerPlay volition be selected out of ROM.

ATOMBIOSReader.zip 74k .aught file

ATiFlash

Run control prompt in ambassador mode to flash; it can take longer than DOS version to cease flash on previous gen cards, so do expect. Below is screenie of completed wink message.

Link:-

Saving ROM

1. Download ATiFlash zip, place all files in directory where you will run ATiFlash.

two. Run command prompt as administrator, navigate to where ATiFlash is on your organisation, mine is in C:\Users\XPS

iii. To relieve ROM enter atiflash -s 0 romname.rom , in one case complete you can flip bios switch to save other position bios.

Notation:- Check saved ROM is 256KB, also GPU-Z at present does support fill-in of ROM for Republic of the fiji islands.

Flashing ROM

1. Download ATiFlash zip, identify all files in directory where you will run ATiFlash.

two. Run command prompt as ambassador, navigate to where ATiFlash is on your system, mine is in C:\Users\XPS

3. To flash enter atiflash -p 0 romname.rom , practise look for message on screen "Restart Organization To Consummate VBIOS Update."

Forcing a flash of ROM with different SSID / DeviceID

1. Download ATiFlash zip, place all files in directory where y'all will run ATiFlash.

2. Run command prompt equally administrator, navigate to where ATiFlash is on your system, mine is in C:\Users\XPS

3. To flash enter atiflash -p 0 romname.rom -f , do wait for message on screen "Restart Organization To Complete VBIOS Update."

Notes:- Practice non have HWiNFO , GPU-Z, MSI AB, etc running in the background when flashing card. If your system is OC'd (ie CPU) make sure it is stable or I would advise flash at stock. If you lot have not fixed checksum yous volition run into an mistake same as below image.

ATiFlash.nil 185k .zippo file

Set shortcut backdrop so information technology runs as administrator.

Subsequently a ROM is flashed successfully yous will run into bulletin shown below.

Be enlightened yous may notation the AtiWinFlash progress bar showing "Not Responding" momentarily when flashing a modded ROM, this is normal behavior, the flash volition complete successfully.

AtiWinFlash.zip 1200k .zip file

Notes:- Do not take HWiNFO , GPU-Z, MSI AB, etc running in the background when flashing card. If your system is OC'd (ie CPU) make sure it is stable or I would advise wink at stock.

Having issues after a flash like clocks, etc non being correct?

1st pace reset drivers to default, so far I have not needed to reinstall drivers for a bios mod to take as default.

Next if yous accept profiles and settings saved in MSI AB / GPU Tweak / TriXX , etc you may demand to either delete the settings files for those apps or uninstall them without keeping profiles, etc and then reinstall. I'd likewise make sure install folders for those apps are empty / deleted later on uninstall prior to reinstalling. Looking at Asus graphics card support pages GPU Tweak II uninstaller does not remove everything so they have a special uninstaller on their site.

Another matter that has come to lite is it'due south all-time to not fix "Extend Official Overclocking Limits" in MSI AB prior to a wink of ROM, every bit clocks,etc perchance wrong after flash.

Fiji Bios Editor past @DDSZ

How to edit GPU Core voltage

Concepts

The 3 methods of voltage modification that can be used past united states.

i) The PowerPlay can exist modified for VID for a DPM, DPM is a GPU state, this has a clock and voltage associated with it, manually prepare or "auto calculate".

two) A GPU core voltage offset through the voltage command bit, this furnishings all DPM states, may they be manually set or "auto calculate".

iii) A combination of the 2 above methods.

Manually setting VID for a DPM

Right click paradigm below and open in new tab to meet large version.

Increasing VID for a DPM based on an OC in OS via SW

Case:- In paradigm heading Manually setting VID for a DPM the example card has DPM 7 as 1212mV on stock ROM. So if information technology required +56mV in MSI AB/Trixx, etc to attain a GPU clock OC of 1145MHz and we wish to set that OC in ROM you lot would edit:-

i) DPM 7 GPU clock from 1050 to 1145.
ii) DPM 7 VID from 1212mV to 1268mV (ie 1212mV+56mV=1268mV)

Note:- Setting more than than 1300mV volition make windows BSOD just before logon, so if your card has 1 ROM position be careful you don't set more than than 1300mV for a DPM. The only way to gain more than 1300mV is to use a ROM which has a GPU core voltage offset. Simply manufactory ROMs which take this so far is Sapphire Fury Nitro, for other cards use my ROM packs in heading further down OP.

SVI2 Compliant Voltages

The below image has SVI2 compliant voltages table, which tin can exist used when manually setting VID per DPM in Fiji bios editor. Right click image below and open in new tab to run across large version.

Editing GPU Core voltage kickoff

See heading My Fiji VDDC/MVDDC start ROM packs and finding voltage beginning in ROM until farther update here.

Gaining VID per DPM information and i2cdump for voltage command chip (IR3567B)

Registers dump via AiDA64 will produce VID per DPM, I used AIDA64 Extreme v5.60.3700.

Annotation: In menu > view > status bar must be enabled to meet card shown in video for registers dump.

When we have 2 or more than GPU in a arrangement then only i cards VID per DPM is shown neatly in registers dump. You lot'll find headings within dump:-

[ ATI GPU #[GPU No] @ mem [variable text] ]

And so beneath that is the registers for that card.

So let'due south say GPU one was shown with nice neat VID per DPM in registers dump, then head over to registers below heading for GPU 2. Then you'll annotation:-

[SCLK DPM0 / MinVddc = 0.90000 5]
[SCLK DPM0 / SclkFreq = 300 MHz]

then on.

Here is

to ref, I do make a mistake at one point

Currently on my carte du jour AiDA64 is non giving i2cdump, and so I added -i2cdump command switch to MSI Afterburning to get info of IR3567B voltage controller scrap. In the install dir of MSI Afterburner you lot will find I2CDUMP.TXT with dumped info.

Example of how your shortcut belongings for "Target" box should exist:-

"C:\Program Files (x86)\MSI Afterburning\MSIAfterburner.exe" -i2cdump

Note: the infinite between " -

To aid thread if members can attach the 2x created TXTs, I would appreciate it

(delight practise exam at stock).

Top window registers dump via AiDA64, well-nigh finish is VID. Lower window i2cdump via MSI AB, bus 6 id xxx is where on my ref PCB Fury IR3567B responded.

How to edit GPU Frequency per DPM

In Fiji Bios editor is PowerPlay tab, here you can fix GPU frequency per DPM, DPM 0 = lowest state DPM7 = highest state.

Correct click below image and open up in new tab to see big version.

Annotation: Forgot to state in the to a higher place prototype if GPU clock is decreased and VID is fix as "auto calculate" you lot volition see decreased VID.

In PowerPlay is a section which sets GPU frequency per DPM, DPM 0 = everyman state DPM7 = highest state.

What yous run across in the notepad window:-

i) take hex values do endian conversion (the switching of hex values)

2) catechumen HEX to DEC

3) knock of the 00 to brand value to MHz

To set a new value of GPU frequency for a DPM practise the reverse of above, fix checksum and wink. Be aware that changing a frequency will mean ROM will recalculate a new EVV VID for that DPM(view logs below).

Note:- The maximum VID I've seen so far on my Fury Tri-Ten has been ane.250V for GPU clocks above 1000MHz.

How to edit cooling profile in ROM

Right click below paradigm and open in new tab to see bigger size.

In that location are two modes of fan control, standard aka look up table (LUT) and avant-garde aka fuzzy logic (FL).

Hither is screenie of Overdrive department for FL (stock method) and LUT.

In PowerPlay about lower section is cooling profile (correct click paradigm and open in new tab to see at best res).

Annotation:- set up checksum before flashing ROM

LUT enable mode works but sticks to one PWM rather than the 3, so currently until I find a way for it to work only use FL mode or custom curves via MSI AB, etc. It peradventure commuter issue or something else.

Due to few question about the mod I've added epitome beneath hopefully explaining what this mod does.

The values I modded to improve cooling profile on Fury Tri-X (air cooled) also work the same way on Fury X (AIO).

Extra cooling profile information for avant-garde transmission modders

How to edit OverDrive Limits in PowerPlay

Notation: From Fiji bios editor v1.2 OverDrive limit tin can be modified using it, this department has been kept here to show how the manual mod is done, so users volition learn more about ROM and share mods they develop.

Near the top of PowerPlay is OverDrive Limits.

Case Memory clock limit:-

50 C3 00 00 , switch the HEX values = 00 00 C3 50 , catechumen to DEC = 50000 , trim 00 to make MHz = 500

To set 525MHz, add 00 to the finish of value 52500 , convert to HEX 00 00 CD 14 , switch HEX values = 14 CD 00 00 .

Overwrite original values in PowerPlay using hex editor and save ROM, open ROM in Fiji Bios editor and resave to fix checksum and flash.

If we upward RAM frequency in PowerPlay (ie HBM clock) and don't increase OverDrive RAM Limit, HBM/RAM performance is non limited.

Note one: When we enhance RAM OverDrive Limit in PowerPlay higher than set HBM clock in PowerPlay you lot will not crave "Extend Official Overclocking Limits" to exist selected in MSI AB to be able to increase HBM clock. You will besides encounter a slider in OverDrive page to exist able to modify HBM clock.

Note 2:- If you modify HBM clock in ROM college than OverDrive Limit for RAM y'all will not be able to change GPU clocks via software (ie MSI AB, this was tested with default settings in driver/MSI AB). Yous volition see a HBM slider in OverDrive page but it can not be moved.

Annotation iii: If we wish to mod ROM to be like "factory ROM" but take increased HBM clock in PowerPlay then match RAM OverDrive Limit to it. Then in OverDrive folio of commuter you will have no slider for HBM clock aligning and you volition need to enable "Extend Official Overclocking Limits" in MSI AB to increment HBM clock via software.

So in stock ROM RAM freq. 500MHz OD RAM Limit 500MHz = no RAM slider.

So in ROM RAM freq. 500MHz OD RAM Limit 525MHz = moveable RAM slider.

So in ROM RAM freq. 525MHz OD RAM Limit 500MHz = RAM section appearing merely no slider.

And so in ROM RAM freq. 525MHz OD RAM Limit 525MHz = no RAM section in OD.

How to edit Maximum ASIC Temperature

In PowerPlay near lower department is PowerLimit section within that is Maximum ASIC Temperature (right click image and open in new tab to meet at best res).

Note:- fix checksum earlier flashing ROM

How to edit PowerLimit

In that location are 3 values that can be edited, screenshots only show PowerPlay table; the values shown are most the end of this table.

Alarm: Anyone implementing this modernistic needs to be aware you will see no upped % for "PowerLimit" in CCC / MSI AB / TriXX / etc. The new values will become new starting point of "PowerLimit" (ie 0%). When you increase these 3 values in bios and add 50% "PowerLimit" via an OC app you lot will be going higher than stock settings.

Note: PowerLimit relates to GPU not total board ability usage. So you volition see higher readings for A/W in HWiNFO for VRM than what you set in PowerLimit as other circuitry and "electric elements" are not part of PowerLimit.

The 3 values that tin can exist edited are:-

TDP: "Change TDP limit based on client's thermal solution"

TDC: "PowerTune limit for maximum thermally sustainable electric current by VDDC regulator that can be supplied"

Maximum Power Commitment Limit (MPDL): "This power limit is the total chip ability that we need to stay inside in order to not violate the PCIe rail/connector power delivery"

TDC

For this knowledge of phases on VRM and spec of components is necessary. Best source is hello res PCB images and and then google for tech spec pdfs on mosfets. The ref PCB Fury / X are 6 phase VRM, IMO 400A is max depending on load / temps, temps greatly effect what VRM can output without running into an issue.

Simple explanation regarding VRM

The VRM takes the 12v and steps it downwardly to lower voltage for GPU,etc to use, the VRM converts the higher voltage, lower electric current supply to a low voltage, high current supply.

MPDL relates to what power tin can be delivered to menu from mobo slot/PCI-Eastward plugs.

So a viii+6 config card 300W MAX , 8+8 = 375W , etc simply behave in mind warning in reddish higher up.

My "safe" advise would exist:-

a) to accept stock values of TDP / TDC / MPDL and add aforementioned % to each just taking into context VRM for TDC and PCI-East connector config for MPDL.

b) test what PL you crave and set up in ROM only that amount, this fashion if yous wanna test a new OC to run across if information technology throttle you can e'er use MSI AB to add together a pocket-sized amount of PL.

Just as a side note I never run Furmark / Kombuster / OCCT on my GPUs.

Further info
Quote:

Originally Posted past The Stilt

Hawaii or Fiji based cards don't draw anywhere near the maximum allowed past the specification (i.eastward 66W) from the PCI-Eastward slot. They depict the power for the GPU VRM from the PCI-E power connectors and the power drawn from the PCI-East omnibus itself only feeds VDDCI VRM and the display interfaces (on Hawaii) and MVDDC and display interfaces on Republic of the fiji islands.

Below is data from THG for Fury Tri-Ten, Fury X and Nano. Viewers of data be enlightened:-

a) high leakage fleck would be more than describe, we accept no idea if these are high/average/low leakage GPU samples.
b) I would use the average figures rather than max, without going into particular the max figures are instantaneous draw figures which occur for a very minute time flow but tin occur frequently depending upon "factors".

At present to expand on what the PCI-E plugs can provide, what I have placed college up in this section is PCI-E SIG information simply the hardware limits of PCI-E plugs are college. Most PSU are half-dozen+ii so the 6 pivot plug does have 3x 12V.

Using GOPupd tool to update/add UEFI/GOP module so custom Fiji ROM will work with CSM=Off

Credit to Lordkag of Fernando's Win-RAID Forum for this app and custom UEFI/GOP module.

i) Download GOPupd v1.9.five with custom AMD UEFI/GOP module. If you require the original GOPupd tool visit Fernado's Win-RAID forum via this link to right thread.

two) save your ROM to update with GOPupd using GPU-Z or AtiFlash or use your already modified ROM and view video below.

Notes:

i) You lot will see a bulletin announced as beneath, this is non an outcome, if you see a differing bulletin delight post in thread.

Code:

                  Data after ROM and not part of EFI! Please report information technology!    Recovering actress information at the aforementioned offset 0x38000.

two) the custom UEFI/GOP module in VBios will allow CSM=Off and Fast boot= On, merely will not allow Secure boot = On, reason beingness the signature in UEFI/GOP can not be updated past united states of america AFAIK.

How to edit ROM for data/command table length changes

My Republic of the fiji islands VDDC/MVDDC offset ROM packs and finding voltage offset in ROM

At the time of this post there are no mill ROMs with VDDC & MVDDC in ROM (Nitro does from manufactory have VDDC only offset). And then attached are ROMs I made

, no farther support or edits will be done to them by me, any yous require them to exist learn from thread and make it and so

After flashing it is recommended to ability down PC fully and up to reinitialize voltage command flake (IR3567B) with the new offset data in ROM.

The Fury Tri-X ROMs are stock factory ROMs with:-

i) VDDC & MVDDC offsets added.
two) VDDC & MVDDC offsets added plus 400MHz timings placed in 500MHz & 600MHz straps.

The Fury Nitro ROMs are stock factory ROMs with:-

i) MVDDC first added.
two) MVDDC offset added plus 400MHz timings placed in 500MHz & 600MHz straps.

Thus user volition need to run @TX12's unlock tool to gain SP and to practise any other mods they require.

The Fury Ten , Nano and Radeon Pro Duo ROMs are stock factory ROMs with:-

i) VDDC & MVDDC offsets added.
ii) VDDC & MVDDC offsets added plus 400MHz timings placed in 500MHz & 600MHz straps.

Then user will need to do whatsoever other mods they require.

Note: VDDC & MVDDC ROMs have +25mV VDDC but -25mV MVDDC, so you lot should see i.275V in HWiNFO. Just the Fury Nitro VDDC & MVDDC ROMs have +18.75mV VDDC (equally they have this from factory) but -25mV MVDDC. To make MVDDC stock or higher user will need to edit ROM, this is and then user is taking steps to increase voltage.

Note: Fifty-fifty though the modded ROMs are based on UEFI ROMs, this has been disabled in ROM (ie the modded ROMs are Not-UEFI). The reason being I/nosotros are unable to update a "signature" in the ROM, which when "pure UEFI" fashion is enabled on a motherboard, the legacy ROM department due to modification and no "signature" update to reflect this, fails check. So you will need CSM support enabled in motherboard bios. The only way to have above ROM (or your own modded ROMs) working with CSM = Off is to employ Lordkag's GOPupd Tool to insert a custom UEFI/GOP module in to video card ROM.

Note: Be aware these ROMs have stock factory VMAX limit as one.48125V for loop 1 (GPU) loop two (HBM). So even if yous add +300mV commencement to GPU and your EVV VID is 1.250V you will not go over one.48125V. If you manually set your DPM 7 every bit 1.3V and add +300mV offset to GPU you will still not go over 1.48125V. Every bit we are talking VID, due to LLC (LoadLine Scale) you lot will non see 1.48125V VDDC and by that I do not advise it is rubber to employ such high VID/VDDC. The HBM voltage has also same voltage limit, I did not increase or decrease this from stock ROM setting.

Fury_Tri-X_ROM_Pack.zip 814k .goose egg file

Naught SHA-i hash: c651697a051d1e371fa807aec5ace9f1b9340055

Fury_Nitro_ROM_Pack.naught link to my GD
Zip SHA-1 hash: FD175957C689425462D6E9C5171DB10AF6FE3FC7

Fury_X_ROM_Pack.nix 205k .nada file

Nada Sha-1 hash: 7e863dc6ae1bcbf807d588486bedae6d788cdae3

Nano_ROM_Pack.zip 202k .zip file

Nix SHA-ane hash: fe1a9f6928b5def287a6896bf7c6054b93e8642f

Radeon_Pro_Duo_ROM_Pack.zilch 377k .zip file

Aught SHA-1 hash: de2e556eb97c0180bfb81ec97ec8fcdf4a0e0b2e

Alarm: Using these ROMs will void your warranty (if card has one). These are provided assuming a user knows implications of what they are doing. I accept no responsibility for damage from using these ROMs.

Below is an image of VoltageObjectInfo from voltage offset ROM to illustrate how to change it with in ROM.

Hither is a

showing how to use windows calculator for above purpose.

I suggest users experimenting with increased MVDDC to modernistic the cooling profile so HBM is cooler. As Fiji has gen 1 HBM I would assume it may not really tolerate increased MVDDC for lengthy periods, but I don't know for certain. So exercise caution if you value not killing the bill of fare.

Note: You can search for the GPU core/HBM voltage offsets in a ROM by using the find command in a hex editor merely I highly recommend using the tables lists with each ROM to do this edit and then y'all know yous are in the right expanse of ROM.

Note: Adding the hex values:-

i) 8D 00 xx 00 (20 denoting get-go value) for GPU core voltage kickoff.
2) 8E 00 20 00 (twenty cogent offset value) for HBM voltage commencement.

to another ROM'southward VoltageObjectInfo is non recommended, reason beingness adding these values also requires farther edits to ROM, which I have not listed here

but easily doable if yous learn ROM mod which is point of placing transmission mods in OP

Note: For Radeon Pro Duo every bit there is chief and slave ROM you will need to edit each equally required.

Adding VDDC Offset to Fury X ROM

Note: This guide is for where IR3567B is used on PCB as Voltage Control Chip.

Link to

Attached is guide.txt seen in linked video.

guide.txt 3k .txt file

GoogleDoc link to IR3567B registers I'thousand aware of. The procedure shown in the video tin can be used to add registers which may not exist in the VoltageObjectInfo of your ROM.

Note: Use above GoogleDoc information with caution every bit potential for killing bill of fare.

FAQ

What is EVV?

EVV = Electronic Variable Voltage, this is the default method of VID setting in ROM. This is based on LeakageID and default GPU clock plus other GPU properties. A VID per DPM volition be calculated and set automatically.

In stock ROM PowerPlay nosotros see EVV pointers per DPM, to calculate the pointer you need to add together the guild (2-viii) to 0xFF00 or 65280:

- DPM0 (manually stock-still voltage)
- DPM1 (2nd DPM) = 0xFF02 (65282)
- DPM2 (3rd DPM) = 0xFF03 (65283)
- DPM3 (4th DPM) = 0xFF04 (65284)
- DPM4 (5th DPM) = 0xFF05 (65285)
- DPM5 (6th DPM) = 0xFF06 (65286)
- DPM6 (seventh DPM) = 0xFF07 (65287)
- DPM7 (8th DPM) = 0xFF08 (65288)

Then the DPM VID pointers we see they increment by 1 to denote the next level of DPM EVV VID.

What is DPM?

DPM = Dynamic Power Management , when we hash out this it is basically states the bios has for the GPU, at that place are 8 in ROM (but in that location are more than, read AMD PowerTune PDFs on web). DPM 0 is lowest and DPM 7 is highest, "PowerTune" tech uses these states to manage the GPU for various reasons.

What's the difference betwixt VID and VDDC?

VID is the voltage that the GPU requests from voltage regulator, VDDC is the real monitored GPU voltage. Why VID and VDDC will likewise vary is due to LoadLine calibration, the difference between VID and VDDC due to LLC is termed as VDROOP. VDROOP is groovy, read this linked commodity and apply information technology in the sense of the GPU.

This is why we gain VID information per DPM as VDDC tin can exist lower than VID. Please view this

carefully as well. I have attached the registers dump showing VID per DPM and HML with the VDDC from per DPM testing beneath.

Fury_X_GPU-Z_Render_test.cipher 11k .nix file

As well nosotros must note due to "PowerTune" tech and different apps load GPU differently we will see unlike VDDC for same VID and clocks. You lot tin can test this by say running 3DM FS and monitoring VDDC in MSI AB and and so comparing with a run of Unigine Valley or Heaven.

Does HBM clock in steps?

Simple answer Aye and I was a skeptic about this only information technology is true, for longer answer view this post.

OCP Limit / VRM Temperature Limit Info

Users may notice in HWiNFO VRM amp readings higher than OCP limits in IR3567B, AFAIK this is non due to an error in HWiNFO just down to how the driver reports this data to it. I have lowered OCP on my card to test if card does shutdown when OCP limit is reached.