All equipment in my testing is my own, none is given to me or provided to me by a company. I choose combo of HW based on my needs and budget.
I am just an owner, no professional qualification or job in field of discussion.
I am just an owner, no professional qualification or job in field of discussion.
Last updates:
15/03/25 - Flashing ASRock RX 7900 XTX Aqua OC VBIOS using AMDVBFlash section updated.
01/03/25 - If flash fails or wish to use a differing VBIOS section added.
-=XFX=- RX 7900 XT/XTX Merc Owners Club -=Force=-
I saw several posts in the main [OFFICIAL] AMD Radeon RX 7900 XTX/XT Owner's Club of XFX Merc RX 7900 XT/XTX owners. I thought to myself let's start an owners club
.The Stilt's pearls on RDNA 3
i) ASIC Quality (LeakageID) and SMU determined GPU clock OC, link. Also see this post, it is The Stilt, link and this post..
ii) Powerlimits of various cards, link.
iii) Here is some testing on RDNA2, much is valid for RDNA3. One key thing is right at end of post, say as example XTX is 1150mV. SMU will not do a V/F based on needing more than 1150mV.
ii) Powerlimits of various cards, link.
iii) Here is some testing on RDNA2, much is valid for RDNA3. One key thing is right at end of post, say as example XTX is 1150mV. SMU will not do a V/F based on needing more than 1150mV.
RDNA3 GPU Voltage
GPU Voltage in driver panel/Wattman/MCT is applying an offset on VGFX.
We are not setting x voltage. This is to allow SMU to continue to set voltage as needed based on various factors.
See this AMD KB, link.
Below graphs are from 3DM TS run on Nitro and Merc. Even though the Nitro (red line) is set at 1037mV (-123mV offset) and the Merc (green line) is set at 1125mV (-25mV offset) the VGFX on average is only 43mV difference.
![Image]()
Data ZIP for above run, generic log viewer allows seeing HWI CSV as graphs, there is CFG file included for it.
This is The Stilt's profile on reddit, link. Serveral posts on RDNA2, it's the same for RDNA3.
Link.
![Rectangle Parallel Slope Font Circle]()
We are not setting x voltage. This is to allow SMU to continue to set voltage as needed based on various factors.
See this AMD KB, link.
Below graphs are from 3DM TS run on Nitro and Merc. Even though the Nitro (red line) is set at 1037mV (-123mV offset) and the Merc (green line) is set at 1125mV (-25mV offset) the VGFX on average is only 43mV difference.
Data ZIP for above run, generic log viewer allows seeing HWI CSV as graphs, there is CFG file included for it.
This is The Stilt's profile on reddit, link. Serveral posts on RDNA2, it's the same for RDNA3.
Link.
Link.
Next here is data from RedF (posted here), the graph has 3 lines, 1150mV results in 0mV offset, 1050mV results in -100mV, 1000mV results in -150mV.
RedF produced below voltage frequency curve for his Merx XTX, ASIC Quality (LeakageID) 43.0%, Auto OC GPU 3126MHz with 22.12.2 an 3080 with 23.1.1.
RedF System Specs:-
CPU: AMD Ryzen 5800X3D / Cooling: Heatkiller IV Pro 360+280 / RAM: 32GB Trident Z B-D @4000 1,54V 16-16-16-32 / MoBo: Gigabyte X570S Aorus Master / Gfx: XFX 7900XTX MERC / SSD: 2*960GB Corsair MP510 1x Samsung PM9A1 M.2 / PSU: Seasonic Prime PX 1KW / OS: Win11 / Case: Modded Silent Base 601
Driver used v23.1.2.
RedF System Specs:-
CPU: AMD Ryzen 5800X3D / Cooling: Heatkiller IV Pro 360+280 / RAM: 32GB Trident Z B-D @4000 1,54V 16-16-16-32 / MoBo: Gigabyte X570S Aorus Master / Gfx: XFX 7900XTX MERC / SSD: 2*960GB Corsair MP510 1x Samsung PM9A1 M.2 / PSU: Seasonic Prime PX 1KW / OS: Win11 / Case: Modded Silent Base 601
Driver used v23.1.2.
Link to post in thread.
![World Biome Sky Landscape Screenshot]()
Monitoring data taken from GPU-Z at 0.1 sec polling interval, link to post by RedF.
Monitoring data taken from GPU-Z at 0.1 sec polling interval, link to post by RedF.
RDNA2/3 ASIC Quality (LeakageID)
This is The Stilt, he posts reviews on linked site, articles section.
RDNA3 employs AVFS, most advanced method to get best from silicon within limits set.
ASIC Quality as shown in GPU-Z and HWINFO is based on LeakageID, see this post.
I have been in discussions with The Stilt and Martin Malik (Mumak) concerning ASIC Quality (LeakageID).
The problem is no one outside of AMD knows how to take the LeakageID and convert it to amps. Amps is the correct denotion for LeakageID. As stated by The Stilt the LeakageID is amps, so lower value is lower leakage. It has been and currently expressed as %. As this is only solution fitting without knowledge from AMD.
To determine which sample of a card is better than another, use GFXCLKFmax as given by driver panel "Overclock GPU". Don't use LeakageID. I have had 5x XTX samples, 4x AIB, 1x MBA. Ranging from 36% to 54%, the 54% was actually best result and held through press to v23.1.2.
This link has screen data from rig with Merc XTX 42.3% vs Nitro+ XTX 46.0% vs Nitro+ XTX 54.0%. Clearly the Merc sample is giving best perf due to lower AQ (ie lower leakage) and has best max power. Do look at GFXCLKmax in MCT besides other info in screenies to show different samples, link to ZIP of 3DM results files for those runs. Also some test data posted here.
GPU voltage can only really be compared using data from monitoring. See relevant section in OP for more info.
AMD's "ASIC Quality" has nothing to do with direct quality and is not comparable between different chip variants, let alone circuit designs.
That value is a holdover from the days when DVFS-based power management would draw a circuit's constant voltage within certain limits based on its leakage current ("ASIC Quality").
A higher ASIC Quality means a higher leakage current, and it is not a desired feature, especially in today's circuits.
You can get a better idea of the quality of the circuit when you compare the "Max Frequency" standard value on the AMD Software Performance tab (Overdrive) of different cards (as the average of a couple of boots, with standard settings) >= RDNA2 cards.
That value is a holdover from the days when DVFS-based power management would draw a circuit's constant voltage within certain limits based on its leakage current ("ASIC Quality").
A higher ASIC Quality means a higher leakage current, and it is not a desired feature, especially in today's circuits.
You can get a better idea of the quality of the circuit when you compare the "Max Frequency" standard value on the AMD Software Performance tab (Overdrive) of different cards (as the average of a couple of boots, with standard settings) >= RDNA2 cards.
RDNA3 employs AVFS, most advanced method to get best from silicon within limits set.
ASIC Quality as shown in GPU-Z and HWINFO is based on LeakageID, see this post.
To the fact that I was once doing the implementation in question for both softwares that support value reading (GPU-Z and HWiNFO).
And similarly complained about the way GPU-Z "describes" that value, because it leaves the flip side of that higher "ASIC Quality" unreported from the description.
Higher "ASIC Quality" circuits always draw a higher amount of current at the same voltage. Unless the low voltage is an absolute value for some reason or there is something in the circuit that prevents using higher voltages, then lower "ASIC Quality" circuits are in many cases a smarter choice, because they run cooler due to their lower leakage current.
No "ASIC Quality" value actually even exists, instead the value shown to the consumer is calculated from the "LeakageID" parameter. The value in question is in amperes .
E: And as I said before, with RDNA2 and newer circuits it is absolutely useless to look at any other value than the maximum clock shown in AMD Software's Overdrive.
This is the GFXCLKFmax value, which is the value determined by AVFS circuit-wise based on many variables. Along with the fixed property of the circuit itself (e.g. the leakage current), it also includes the environment variables used by the closed AVFS and therefore it is calibrated at every init (practically at boot).
And similarly complained about the way GPU-Z "describes" that value, because it leaves the flip side of that higher "ASIC Quality" unreported from the description.
Higher "ASIC Quality" circuits always draw a higher amount of current at the same voltage. Unless the low voltage is an absolute value for some reason or there is something in the circuit that prevents using higher voltages, then lower "ASIC Quality" circuits are in many cases a smarter choice, because they run cooler due to their lower leakage current.
No "ASIC Quality" value actually even exists, instead the value shown to the consumer is calculated from the "LeakageID" parameter. The value in question is in amperes
.E: And as I said before, with RDNA2 and newer circuits it is absolutely useless to look at any other value than the maximum clock shown in AMD Software's Overdrive.
This is the GFXCLKFmax value, which is the value determined by AVFS circuit-wise based on many variables. Along with the fixed property of the circuit itself (e.g. the leakage current), it also includes the environment variables used by the closed AVFS and therefore it is calibrated at every init (practically at boot).
I have been in discussions with The Stilt and Martin Malik (Mumak) concerning ASIC Quality (LeakageID).
The problem is no one outside of AMD knows how to take the LeakageID and convert it to amps. Amps is the correct denotion for LeakageID. As stated by The Stilt the LeakageID is amps, so lower value is lower leakage. It has been and currently expressed as %. As this is only solution fitting without knowledge from AMD.
To determine which sample of a card is better than another, use GFXCLKFmax as given by driver panel "Overclock GPU". Don't use LeakageID. I have had 5x XTX samples, 4x AIB, 1x MBA. Ranging from 36% to 54%, the 54% was actually best result and held through press to v23.1.2.
This link has screen data from rig with Merc XTX 42.3% vs Nitro+ XTX 46.0% vs Nitro+ XTX 54.0%. Clearly the Merc sample is giving best perf due to lower AQ (ie lower leakage) and has best max power. Do look at GFXCLKmax in MCT besides other info in screenies to show different samples, link to ZIP of 3DM results files for those runs. Also some test data posted here.
5800X3D (BR 2422 PGS)
ASUS ROG Crosshair VIII Dark Hero
Crucial Ballistix Sport LT 2x16GB (BLS2K16G4D32AESB)
2x WD Black SN770 2TB NVMe
2x Samsung 870 EVO 4TB SATA
EVGA G6 850W (Seasonic Focus Gold platform), using all stock factory modular cables.
Be Quiet Dark Base Pro 900, front door removed and mesh mod done, top panel stock mesh had plastic removed to improve airflow.
Cooling:-
Bykski A-Ryzen-ThV2-X CPU block (Arctic Cooling MX-4)
2x Magicool 360 Slim G2 radiator EK-XRES 140 Revo D5 PWM
EK ZMT (OD 5/8", ID 3/8"), Barrow fittings
Coolant Mayhems XT-1 clear concentrate ~20% mix with distilled water
Top radiator as exhaust, 3x Arctic Cooling F12 PWM (push only)
Front rad as intake, 6x Arctic Cooling F12 PWM (push/pull only)
Case rear fan, Be Quiet Silent Wings 3 1000RPM (set to 100%)
Case RAM fan Be Quiet Silent Wings 3 1000RPM (set to 100%)
ASUS ROG Crosshair VIII Dark Hero
Crucial Ballistix Sport LT 2x16GB (BLS2K16G4D32AESB)
2x WD Black SN770 2TB NVMe
2x Samsung 870 EVO 4TB SATA
EVGA G6 850W (Seasonic Focus Gold platform), using all stock factory modular cables.
Be Quiet Dark Base Pro 900, front door removed and mesh mod done, top panel stock mesh had plastic removed to improve airflow.
Cooling:-
Bykski A-Ryzen-ThV2-X CPU block (Arctic Cooling MX-4)
2x Magicool 360 Slim G2 radiator EK-XRES 140 Revo D5 PWM
EK ZMT (OD 5/8", ID 3/8"), Barrow fittings
Coolant Mayhems XT-1 clear concentrate ~20% mix with distilled water
Top radiator as exhaust, 3x Arctic Cooling F12 PWM (push only)
Front rad as intake, 6x Arctic Cooling F12 PWM (push/pull only)
Case rear fan, Be Quiet Silent Wings 3 1000RPM (set to 100%)
Case RAM fan Be Quiet Silent Wings 3 1000RPM (set to 100%)
GPU voltage can only really be compared using data from monitoring. See relevant section in OP for more info.
Merc XTX V/F Curve (VB 009 & 010) provided by RedF.
RedF produced below voltage frequency curve for his Merx XTX on VBIOS 009 and 010, ASIC Quality (LeakageID) 43.0%, Auto OC GPU 3126MHz with 22.12.2 an 3080 with 23.1.1.
RedF System Specs:-
CPU: AMD Ryzen 5800X3D / Cooling: Heatkiller IV Pro 360+280 / RAM: 32GB Trident Z B-D @4000 1,54V 16-16-16-32 / MoBo: Gigabyte X570S Aorus Master / Gfx: XFX 7900XTX MERC / SSD: 2*960GB Corsair MP510 1x Samsung PM9A1 M.2 / PSU: Seasonic Prime PX 1KW / OS: Win11 / Case: Modded Silent Base 601
Driver used v23.1.2.
RedF System Specs:-
CPU: AMD Ryzen 5800X3D / Cooling: Heatkiller IV Pro 360+280 / RAM: 32GB Trident Z B-D @4000 1,54V 16-16-16-32 / MoBo: Gigabyte X570S Aorus Master / Gfx: XFX 7900XTX MERC / SSD: 2*960GB Corsair MP510 1x Samsung PM9A1 M.2 / PSU: Seasonic Prime PX 1KW / OS: Win11 / Case: Modded Silent Base 601
Driver used v23.1.2.
Link to post in thread.
![World Biome Sky Landscape Screenshot]()
Monitoring data taken from GPU-Z at 0.1 sec polling interval, link to post by RedF.
Monitoring data taken from GPU-Z at 0.1 sec polling interval, link to post by RedF.
RDNA3 SOC Voltage and Clocks
RX Vega was when I first encountered SOC clock, what we found at the time was SOC clock needed to be above HBM clock, otherwise any gain from HBM clock increase was capped.
On RDNA3 the SOC clock raises as we increase MEMCLK.
Between MEMCLK 2500MHz to 2762MHz SOCCLK will be targeted as 1285MHz. 2764MHz to 2824MHz (not tested higher) SOCCLK will be targeted as 1500MHz.
VSOC increases as MEMCLK increases plus say when SOCCLK target notches up.
Currently not checked, but it maybe VBIOS setting base level for VSOC or SMU profile silicon and apply.
Below tests were at MEMCLK 2500MHz, 2764MHz, 2772MHz, 2800MHz and 2824MHz.
On RDNA3 the SOC clock raises as we increase MEMCLK.
Between MEMCLK 2500MHz to 2762MHz SOCCLK will be targeted as 1285MHz. 2764MHz to 2824MHz (not tested higher) SOCCLK will be targeted as 1500MHz.
VSOC increases as MEMCLK increases plus say when SOCCLK target notches up.
Currently not checked, but it maybe VBIOS setting base level for VSOC or SMU profile silicon and apply.
Same test, MBA XTX, same MEMCLK results in same SOCCLK, VSOC is min 0.954 aver 0.961 max 0.975.
![Product Rectangle Font Screenshot Parallel]()
Below tests were at MEMCLK 2500MHz, 2764MHz, 2772MHz, 2800MHz and 2824MHz.
HWI polling rate: 300ms
MemtestCL (The Stilt Mod) 2x instances, set to 8192MB, 25 iterations
MEMCLK: 2500MHz SOCCLK: 1285MHz VSOC(ave.): 0.941V
Wall meter plug read, total rig, ~30W screen, idle ~103W, max 425W
![Font Line Screenshot Parallel Pattern]()
MEMCLK: 2764MHz SOCCLK: 1500MHz VSOC(ave.): 1.023V
Wall meter plug read, total rig, ~30W screen, idle ~103W, max 449W
![Font Line Screenshot Parallel Pattern]()
MEMCLK: 2772MHz SOCCLK: 1500MHz VSOC(ave.): 1.025V
Wall meter plug read, total rig, ~30W screen, idle ~103W, max 450W
![Font Line Screenshot Parallel Pattern]()
MEMCLK: 2804MHz SOCCLK: 1500MHz VSOC(ave.): 1.036V
Wall meter plug read, total rig, ~30W screen, idle ~103W, max 456W
![Font Line Screenshot Parallel Pattern]()
MEMCLK: 2824MHz SOCCLK: 1500MHz VSOC(ave.): 1.041V
Wall meter plug read, total rig, ~30W screen, idle ~103W, max 455W
![Font Line Screenshot Parallel Pattern]()
MemtestCL (The Stilt Mod) 2x instances, set to 8192MB, 25 iterations
MEMCLK: 2500MHz SOCCLK: 1285MHz VSOC(ave.): 0.941V
Wall meter plug read, total rig, ~30W screen, idle ~103W, max 425W
MEMCLK: 2764MHz SOCCLK: 1500MHz VSOC(ave.): 1.023V
Wall meter plug read, total rig, ~30W screen, idle ~103W, max 449W
MEMCLK: 2772MHz SOCCLK: 1500MHz VSOC(ave.): 1.025V
Wall meter plug read, total rig, ~30W screen, idle ~103W, max 450W
MEMCLK: 2804MHz SOCCLK: 1500MHz VSOC(ave.): 1.036V
Wall meter plug read, total rig, ~30W screen, idle ~103W, max 456W
MEMCLK: 2824MHz SOCCLK: 1500MHz VSOC(ave.): 1.041V
Wall meter plug read, total rig, ~30W screen, idle ~103W, max 455W
GPU Front End Clock and GPU Front End Clock (effective)
This article my author of HWINFO is on CPU, but same principle, link.
Driver panel "Undervolt GPU"
What driver states as "Undervolt GPU" isn't based on profiling silicon in use.
For XT it is 1075mV
For XTX it is 1125mV
This has been verfied by user shares on various cards.
For XT it is 1075mV
For XTX it is 1125mV
This has been verfied by user shares on various cards.
Driver panel "Overclock GPU"
What driver states as "Overclock GPU" is based on various parameters as stated by The Stilt (see links above). This will vary even on same drivers, same card, per test for each POST of card.
You are likely to see different clocks also when drivers change and SMU FW is changed. SMU profiles GPU, so when FW changes AMD may make various parameter changes which will change determination, boost behaviour, etc.
When doing "Overclock GPU" via driver panel, if you monitor using HWINFO, you will see test is done with 10% PL increase.
![Colorfulness Black Font Rectangle Screenshot]()
Default performance tuning tab
![Black Font Computer Screenshot Software]()
You are likely to see different clocks also when drivers change and SMU FW is changed. SMU profiles GPU, so when FW changes AMD may make various parameter changes which will change determination, boost behaviour, etc.
When doing "Overclock GPU" via driver panel, if you monitor using HWINFO, you will see test is done with 10% PL increase.
Default performance tuning tab
Driver panel "Overclock VRAM"
All 5x XTX samples I have had, 4x AIB (1x Merc, 2x Nitro+ & 1x Red Devil) and 1x MBA have all shown 2650MHz. I do not think profiling is done by driver, but a preset value by driver is shown, just like "Undervolt GPU".
GPU SMU FW
The GPU SMU FW is updated via driver. Other updates of GPU FW can also be done via driver.
In the past I have seen VRM config being changed via driver. For example reference RX 480, a shift of power usage from PCI-E slot to PCI-E plugs was necessary as VBIOS had been set incorrectly. Link to thread, see further in thread when driver fixes issue.
SMU FW can tweak GPU behind the scenes. One way of observing quickly is "Overclock GPU" result in driver panel. Older FW seems to boost more, but so far haven't noticed performance loss in like tests.
In the past I have seen VRM config being changed via driver. For example reference RX 480, a shift of power usage from PCI-E slot to PCI-E plugs was necessary as VBIOS had been set incorrectly. Link to thread, see further in thread when driver fixes issue.
SMU FW can tweak GPU behind the scenes. One way of observing quickly is "Overclock GPU" result in driver panel. Older FW seems to boost more, but so far haven't noticed performance loss in like tests.
| Driver Version | SMU FW Version used |
| Press release driver | v0.78.71 |
| v22.12.1 | v0.78.73 |
| v22.12.2 | v0.78.75 |
| v23.1.1 | v0.78.76 |
| v23.1.2 | v0.78.76 |
| v23.2.1 | v0.78.76 |
| v23.2.2 | v0.78.77 |
| v23.1.1 | v0.78.79 |
My OC tips for Navi31 daily use, stability testing and bench
In OP is a section where it states SMU FW within a driver, you can see in HWINFO where you see A.Q. It is likely driver includes other FW as well, for example IMC perhaps, no idea though.
AVFS is crazy good on newer drivers (posting as of v23.3.1). I am no longer bothering with manual OC/UV. Lose stabilty and not much performance from my sample's bench results.
Daily use using OC VB, -10% PL, VRAM 2728MHz. When need extra perf, go 0% PL, VRAM 2728MHz, max perf +15% PL, VRAM 2728MHz.
This is ZIP for all 3 profiles, will create result table soon.
MemtestCL is a lighter load on GPU IMC/VRAM, Memtest Vulkan heavier, ~100% loading. So if my card does ~2800MHz VRAM MHz (UCLK) then it's about ~2700MHz on Memtest Vulkan. Daily use I'd go with Memtest Vulkan tested MHz. I don't think either fail on unstable GPU profile, but I have noted at times higher set GPU can pass Memtest Vulkan with higher VRAM MHz.
If your card can do ~2764MHz VRAM, then at this point SOC MHz will be ~1500MHz vs ~1285MHz. As VRAM MHz rises SOC voltage does also. So you may find higher VRAM MHz stable vs slighly under it. So test range of VRAM MHz in my experience with cards I had.
For pure bench results go as high VRAM MHz as performance doesn't degrade.
For manual OC/UV, daily or bench, I found either setting GFXCLKmin/max with:-
i) 300MHz gap, results in ~150MHz gap in GPU-Z.
ii) 200MHz gap, results in ~150MHz gap in GPU-Z.
Yield good performance results, your experience may differ, so I'd say test and set as needed based on best performance yield. I couldn't see from looking at set profiles, if set gap, aided or harmed stability, so again I'd say test what works best for you.
Owned 5x XTX, MBA, Merc, Nitro+ and Red Devil. LeakageID as below.
MBA XTX 36.1%
Merc XTX 42.3%
Nitro+ XTX Sample 1 54.0% Sample 2 46.0%
Red Devil XTX 49.4%
Lower LeakageID (ASIC Quality) from silicon I had, gave more performance for set PL vs higher LeakageID (ASIC Quality) silicon.
Lower LeakageID (ASIC Quality) from silicon I had, had lower voltage vs higher LeakageID (ASIC Quality) silicon. My tested cards showed that lower LeakageID silicon had lower voltage and didn't UV as much as higher LeakageID. Your experience may differ, as also what SMU profiles silicon, for GFXCLKmax, dictates V/F, within usual limits.
It seems VB 010 may improve card performance, links to posts by RedF, link 1, link 2. Mine I have tried VB 009 with upto driver version v23.1.2 doesn't change performance vs 010. My XTX Merc out of box came with 010, 010 is what I use. So your experience may vary on differing VB.
Will add some, soon.
AVFS is crazy good on newer drivers (posting as of v23.3.1). I am no longer bothering with manual OC/UV. Lose stabilty and not much performance from my sample's bench results.
Daily use using OC VB, -10% PL, VRAM 2728MHz. When need extra perf, go 0% PL, VRAM 2728MHz, max perf +15% PL, VRAM 2728MHz.
This is ZIP for all 3 profiles, will create result table soon.
MemtestCL is a lighter load on GPU IMC/VRAM, Memtest Vulkan heavier, ~100% loading. So if my card does ~2800MHz VRAM MHz (UCLK) then it's about ~2700MHz on Memtest Vulkan. Daily use I'd go with Memtest Vulkan tested MHz. I don't think either fail on unstable GPU profile, but I have noted at times higher set GPU can pass Memtest Vulkan with higher VRAM MHz.
If your card can do ~2764MHz VRAM, then at this point SOC MHz will be ~1500MHz vs ~1285MHz. As VRAM MHz rises SOC voltage does also. So you may find higher VRAM MHz stable vs slighly under it. So test range of VRAM MHz in my experience with cards I had.
For pure bench results go as high VRAM MHz as performance doesn't degrade.
For manual OC/UV, daily or bench, I found either setting GFXCLKmin/max with:-
i) 300MHz gap, results in ~150MHz gap in GPU-Z.
ii) 200MHz gap, results in ~150MHz gap in GPU-Z.
Yield good performance results, your experience may differ, so I'd say test and set as needed based on best performance yield. I couldn't see from looking at set profiles, if set gap, aided or harmed stability, so again I'd say test what works best for you.
Owned 5x XTX, MBA, Merc, Nitro+ and Red Devil. LeakageID as below.
MBA XTX 36.1%
Merc XTX 42.3%
Nitro+ XTX Sample 1 54.0% Sample 2 46.0%
Red Devil XTX 49.4%
Lower LeakageID (ASIC Quality) from silicon I had, gave more performance for set PL vs higher LeakageID (ASIC Quality) silicon.
Lower LeakageID (ASIC Quality) from silicon I had, had lower voltage vs higher LeakageID (ASIC Quality) silicon. My tested cards showed that lower LeakageID silicon had lower voltage and didn't UV as much as higher LeakageID. Your experience may differ, as also what SMU profiles silicon, for GFXCLKmax, dictates V/F, within usual limits.
It seems VB 010 may improve card performance, links to posts by RedF, link 1, link 2. Mine I have tried VB 009 with upto driver version v23.1.2 doesn't change performance vs 010. My XTX Merc out of box came with 010, 010 is what I use. So your experience may vary on differing VB.
Will add some, soon.
AMDVBFLASH Information v5.0.567
Download link:- AMDVBFlash / ATI ATIFlash 5.0.567 Download
RX 7900 XTX Merc BIOS Version 022.001.002.010 download link (These files are from my Merc XTX, which came from factory with 010)
Flash under safe mode. Flash only a VBIOS position.
To flash use command: amdvbflash --flash biosfilename.rom --fa --fp --fv
On flashing you should recieve messages as in screenie below. The screenie is from when I downgraded my FW.
![Font Screenshot Computer program Software Computer]()
Options and other commands can be seen by using command: amdvbflash -h
If a VBIOS position gets incorrectly flashed and system won't POST. Then use other VBIOS position to POST system to safe mode. Before using AMD VBFLASH, whilst in OS, flip switch to VBIOS with incorrect flash, then initiate flashing again.
After flashing I would install a fresh driver, so flash VBIOS, then reboot to safe mode again, run DDU, reboot to OS, install fresh driver.
DDU will clear all previous driver settings and game profiles. If you want those, export via settings section of driver. Then you can restore quickly and easily.
![Font Screenshot Multimedia Software Multimedia software]()
GPU-Z may show previous VBIOS version, reflash VBIOS, as VBIOS on RX 7000 series has active/inactive partition.
RX 7900 XTX Merc BIOS Version 022.001.002.010 download link (These files are from my Merc XTX, which came from factory with 010)
Flash under safe mode. Flash only a VBIOS position.
To flash use command: amdvbflash --flash biosfilename.rom --fa --fp --fv
On flashing you should recieve messages as in screenie below. The screenie is from when I downgraded my FW.
Options and other commands can be seen by using command: amdvbflash -h
If a VBIOS position gets incorrectly flashed and system won't POST. Then use other VBIOS position to POST system to safe mode. Before using AMD VBFLASH, whilst in OS, flip switch to VBIOS with incorrect flash, then initiate flashing again.
After flashing I would install a fresh driver, so flash VBIOS, then reboot to safe mode again, run DDU, reboot to OS, install fresh driver.
DDU will clear all previous driver settings and game profiles. If you want those, export via settings section of driver. Then you can restore quickly and easily.
GPU-Z may show previous VBIOS version, reflash VBIOS, as VBIOS on RX 7000 series has active/inactive partition.
Flashing ASRock RX 7900 XTX Aqua OC VBIOS using AMDVBFlash
Warning:- There is potential for software flash to go wrong, you may need HW flash tool to recover VBIOS position.
Do not flash both VBIOS positions.
I would advise to do with no OC on system.
Responsibility is on you for using method and running into issues.
My total my system maximum wall plug meter power draw was ~716W, when 3DM TS was used. The figure included screen (~30W), my rig at time was 5700X3D, Crosshair VIII Dark Hero, 2x16GB RAM, 2x NVMe, 2x SATA SSD, 1x D5 pump, 9x 120mm fans, 2x 140mm fans.
PSUs are DC sided rated (ie components), so if wall plug meter shows ~716W, -30W for my screen, roughly -10% efficiency, means DC side power draw ~617W. I was using an EVGA G6 850W, I ran whole suite of 3DM benchmarks and that was max power draw I saw.
XFX XTX Magnetic can have 20ms spikes of 507W, W1zzard :-
Guide assumes one video card in system, disable AMD iGPU if you are using and re-enable after get Aqua XOC. I will update guide again for iGPU context.
If using this guide to flash XTX Nitro+ be aware you must not flash on software position of VBIOS switch.
![Electronic device Technology Wire Electronics Electrical cable]()
1. Download AMDVBFlash v5.0.567 from TPU. From AMDVBFlash v5.0.567 run AMDVBFlashDriverInstaller.exe
2. Download AMDVBFlash v5.0.616 modded version by Benik3, link, place in it's own folder, not with AMDVBFlash from TPU.
3. Download Aqua XTX OC VBIOS from TPU VBIOS DB. Place in folder where v5.0.616 modded version by Benik3 is.
4. Use Notepad and make config file to use with AMDVBFlash:-
ssid=0x5301
svid=0x1849
biospn=113-D70201-810010
biosversion=022.001.002.010.000001
devid=0x744C
Extension of file as .cfg, place file in folder where AMDVBFlash v5.0.616 modded version by Benik3 is.
5. Go to safe mode, easiest method is restart from start menu whilst holding down shift key. Will try to update these photos as turned out blurry, but they do the job.
6. Uninstall driver using DDU (link), in DDU use clean & restart.
7. Go to safe mode.
8. Where AMDVBFlash v5.0.616 modded version by Benik3 is, use command prompt with administrator privileges:-
amdvbflash -p [filename] --fa --fp --fv --config=[filename].cfg --debug-log-status=true
Note:
1. Debug log file default location is C:\Users\[username]\AppData\Roaming\AMD.
2. VBIOS file can be any extension, ie .bin, .rom, as long as you type correctly the details in command and it is valid VBIOS it will flash.
Run flash command 2 times.
9. Power system down, turn off power to PSU from wall plug or switch on rear of PSU, then post to OS/go to safe mode. Make sure --active and --inactive VBIOS partition match, if they do not repeat step 8 until they match. Command to check active/inactive VBIOS partition:-
![Text Font Screenshot Number Software]()
![Text Font Screenshot Number Software]()
10. Once in safe mode run ASRock Aqua XOC update, run it 2 times. Power down, turn off power to PSU from wall plug or switch on rear of PSU.
11. Go to standard OS. Uninstall AMDVBFlash driver using AMDVBFlashDriverInstaller.exe from AMDVBFlash v5.0.567. Install AMD GPU driver.
Due to how Aqua XOC VBIOS is and how GPU-Z shows VBIOS information, you will see differing version vs driver/HWINFO.
![Software Technology Number Screenshot Video Game Software]()
When you hover mouse over VBIOS version in GPU-Z you will see below info.
![Font Software Technology Screenshot Number]()
Reference below image at it will make sense why these differing versions are seen.
![Text White Font Screenshot Diagram]()
The correct power limits for Aqua XOC are in below spoiler.
![Software Font Technology Screenshot Number]()
![Software Font Technology Screenshot Number]()
Do not flash both VBIOS positions.
I would advise to do with no OC on system.
Responsibility is on you for using method and running into issues.
My total my system maximum wall plug meter power draw was ~716W, when 3DM TS was used. The figure included screen (~30W), my rig at time was 5700X3D, Crosshair VIII Dark Hero, 2x16GB RAM, 2x NVMe, 2x SATA SSD, 1x D5 pump, 9x 120mm fans, 2x 140mm fans.
PSUs are DC sided rated (ie components), so if wall plug meter shows ~716W, -30W for my screen, roughly -10% efficiency, means DC side power draw ~617W. I was using an EVGA G6 850W, I ran whole suite of 3DM benchmarks and that was max power draw I saw.
XFX XTX Magnetic can have 20ms spikes of 507W, W1zzard :-
So on Aqua XOC VBIOS be higher.
Guide assumes one video card in system, disable AMD iGPU if you are using and re-enable after get Aqua XOC. I will update guide again for iGPU context.
If using this guide to flash XTX Nitro+ be aware you must not flash on software position of VBIOS switch.
1. Download AMDVBFlash v5.0.567 from TPU. From AMDVBFlash v5.0.567 run AMDVBFlashDriverInstaller.exe
2. Download AMDVBFlash v5.0.616 modded version by Benik3, link, place in it's own folder, not with AMDVBFlash from TPU.
3. Download Aqua XTX OC VBIOS from TPU VBIOS DB. Place in folder where v5.0.616 modded version by Benik3 is.
4. Use Notepad and make config file to use with AMDVBFlash:-
ssid=0x5301
svid=0x1849
biospn=113-D70201-810010
biosversion=022.001.002.010.000001
devid=0x744C
Extension of file as .cfg, place file in folder where AMDVBFlash v5.0.616 modded version by Benik3 is.
5. Go to safe mode, easiest method is restart from start menu whilst holding down shift key. Will try to update these photos as turned out blurry, but they do the job.
6. Uninstall driver using DDU (link), in DDU use clean & restart.
7. Go to safe mode.
8. Where AMDVBFlash v5.0.616 modded version by Benik3 is, use command prompt with administrator privileges:-
amdvbflash -p [filename] --fa --fp --fv --config=[filename].cfg --debug-log-status=true
Note:
1. Debug log file default location is C:\Users\[username]\AppData\Roaming\AMD.
2. VBIOS file can be any extension, ie .bin, .rom, as long as you type correctly the details in command and it is valid VBIOS it will flash.
Run flash command 2 times.
9. Power system down, turn off power to PSU from wall plug or switch on rear of PSU, then post to OS/go to safe mode. Make sure --active and --inactive VBIOS partition match, if they do not repeat step 8 until they match. Command to check active/inactive VBIOS partition:-
10. Once in safe mode run ASRock Aqua XOC update, run it 2 times. Power down, turn off power to PSU from wall plug or switch on rear of PSU.
First check is AMD GPU driver, uninstall AMD GPU driver.
![Text Font Screenshot Number Software]()
Second check is Aqua OC SSID in active VBIOS partition of the VBIOS chip in use must be Aqua OC, flash Aqua OC VBIOS.
![Text Font Screenshot Number Software]()
Final check inactive VBIOS partition of the VBIOS chip in use must be Aqua OC, reflash Aqua OC VBIOS.
![Text Font Screenshot Number Software]()
Both VBIOS chips need not be Aqua OC from my experience, twice I have gone Aqua XOC and both times the other VBIOS chip on my card had Merc VBIOS.
Second check is Aqua OC SSID in active VBIOS partition of the VBIOS chip in use must be Aqua OC, flash Aqua OC VBIOS.
Final check inactive VBIOS partition of the VBIOS chip in use must be Aqua OC, reflash Aqua OC VBIOS.
Both VBIOS chips need not be Aqua OC from my experience, twice I have gone Aqua XOC and both times the other VBIOS chip on my card had Merc VBIOS.
11. Go to standard OS. Uninstall AMDVBFlash driver using AMDVBFlashDriverInstaller.exe from AMDVBFlash v5.0.567. Install AMD GPU driver.
Due to how Aqua XOC VBIOS is and how GPU-Z shows VBIOS information, you will see differing version vs driver/HWINFO.
When you hover mouse over VBIOS version in GPU-Z you will see below info.
Reference below image at it will make sense why these differing versions are seen.
The correct power limits for Aqua XOC are in below spoiler.
If flash fails or wish to use a differing VBIOS
If a flash fails, use AMDVBFlash v5.0.616 modded version by Benik3 (link) to revert card to a VBIOS you want.
POST system on working VBIOS position, change to failed/corrupt VBIOS position and flash.
If corrupt/failed flash VBIOS position is working do flash process using that VBIOS position.
To make a CFG to use, the file must have information of VBIOS file you wish to flash.
amdvbflash -p [filename] --fa --fp --fv --config=[filename].cfg --debug-log-status=true
Note:
1. Debug log file default location is C:\Users\[username]\AppData\Roaming\AMD.
2. VBIOS file can be any extension, ie .bin, .rom, as long as you type correctly the details in command and it is valid VBIOS it will flash.
3. Flash twice, then power down system fully, switch off power to PSU either from swicth on back of PSU or wall power plug.
After flash and power down/up of system check, active and inactive VBIOS partition match, repeat flash process if they do not.
![Text Font Screenshot Number Software]()
![Text Font Screenshot Number Software]()
If flash process fails too many times you get locked out from flashing using AMDVBFlash.
So power down, see if system can POST on the failed flash position. If it doesn't then just POST on working position and then change switch position to failed VBIOS position and flash.
When I had issue with going Aqua XOC direct, I flashed Merc OC VBIOS back on card. Then I went Aqua OC as stated in guide on OP and used ASRock tool to go XOC. Twice I have gone Aqua OC using TPU VBIOS linked in OP, then XOC using ASRock tool.
Merc XTX OC 010 VBIOS and CFG, link.
amdvbflash -p 0 merc.rom --fa --fp --fv --config=merc.cfg --debug-log-status=true
Do above twice, then power down system.
POST system on working VBIOS position, change to failed/corrupt VBIOS position and flash.
If corrupt/failed flash VBIOS position is working do flash process using that VBIOS position.
To make a CFG to use, the file must have information of VBIOS file you wish to flash.
Use notepad to make CFG to use with AMDVBFlash, save file with .CFG extension.
ssid=0x[Subsystem Vendor ID of VBIOS to flash]
svid=0x[Subsystem Vendor of VBIOS to flash]
biospn=[VBIOS P/N of VBIOS to flash]
biosversion=[VBIOS version of VBIOS to flash]
devid=0x744C
All 7900 series have same devid, may that be GRE, XT, XTX, it is always 744C.
![Text Screenshot Number Font Software]()
ssid=0x[Subsystem Vendor ID of VBIOS to flash]
svid=0x[Subsystem Vendor of VBIOS to flash]
biospn=[VBIOS P/N of VBIOS to flash]
biosversion=[VBIOS version of VBIOS to flash]
devid=0x744C
All 7900 series have same devid, may that be GRE, XT, XTX, it is always 744C.
amdvbflash -p [filename] --fa --fp --fv --config=[filename].cfg --debug-log-status=true
Note:
1. Debug log file default location is C:\Users\[username]\AppData\Roaming\AMD.
2. VBIOS file can be any extension, ie .bin, .rom, as long as you type correctly the details in command and it is valid VBIOS it will flash.
3. Flash twice, then power down system fully, switch off power to PSU either from swicth on back of PSU or wall power plug.
After flash and power down/up of system check, active and inactive VBIOS partition match, repeat flash process if they do not.
If flash process fails too many times you get locked out from flashing using AMDVBFlash.
So power down, see if system can POST on the failed flash position. If it doesn't then just POST on working position and then change switch position to failed VBIOS position and flash.
When I had issue with going Aqua XOC direct, I flashed Merc OC VBIOS back on card. Then I went Aqua OC as stated in guide on OP and used ASRock tool to go XOC. Twice I have gone Aqua OC using TPU VBIOS linked in OP, then XOC using ASRock tool.
Merc XTX OC 010 VBIOS and CFG, link.
amdvbflash -p 0 merc.rom --fa --fp --fv --config=merc.cfg --debug-log-status=true
Do above twice, then power down system.
Flashing ASRock RX 7900 XTX Aqua OC VBIOS using CH341a by Allium
Allium's flashing post link.
![Text Screenshot Font Number Software]()
Flash only one VBIOS chip.
VBIOS on front of card is VBIOS switch towards Display IO side.
VBIOS on rear of card is VBIOS switch towards PCI-E plugs.
Link to RedF post.
![Technology Machine Computer hardware Hardware Programmer Electronics]()
Flash ASRock Aqua VBIOS using HW flash tool, then you use ASRock tool to update to Aqua Extreme OC VBIOS.
XFX XTX Magnetic can have 20ms spikes of 507W, W1zzard :-
Flash only one VBIOS chip.
VBIOS on front of card is VBIOS switch towards Display IO side.
VBIOS on rear of card is VBIOS switch towards PCI-E plugs.
Link to RedF post.
Flash ASRock Aqua VBIOS using HW flash tool, then you use ASRock tool to update to Aqua Extreme OC VBIOS.
XFX XTX Magnetic can have 20ms spikes of 507W, W1zzard :-
So on Aqua XOC VBIOS be higher.
EVC - Hardware mod to "Raise the limits..." by Enzarch
R.B.R.T - MoreClockTool (Download link)
This allows you to do what Wattman does, more compact, clear and simple GUI. Some users found it more stable than Wattman for tweaking. Also read some posts, on various owners forums, where some XFX RX 7900 series card owners can't use Wattman to tune card, but MCT works.
R.B.R.T - MPT
Currently MPT doesn't function with RDNA3/Navi3x. Driver blocks SPPT. Various investigations by Hellm, Veii, myself, other R.B.R.T members, other owners and supporters have bore no fruit.
But please take the time to see this interview to PCW by AMD representative concerning RDNA3/Navi3x.
But please take the time to see this interview to PCW by AMD representative concerning RDNA3/Navi3x.
MemtestCL - The Stilt Mod (Download link)
This is an old program, home page link, Github link. When Navi2x came out I asked The Stilt if he could modify the program to allow greater than 4GB a instance, he did provide me an update. He used the most current OpenCL ICD build at the time, ~Nov 21. There is also this version which works better than original MemtestCL and allows greater than 4GB an instance.
It worked well on Navi2x IMO and also on Navi3x. It probably has some slight bugs, but I found it useful and have linked nonetheless.
You can not fully test all available VRAM, as some will be in use and some must be left free for OS, etc. I would test with 2 instances, for me 2 instances of 8192MB have worked well on several XTX cards I have owned.
Command usage:-
memtestcl xxxx yy
xxxx = set MB for testing
yy = number of iterations to run
For more commands-
It worked well on Navi2x IMO and also on Navi3x. It probably has some slight bugs, but I found it useful and have linked nonetheless.
You can not fully test all available VRAM, as some will be in use and some must be left free for OS, etc. I would test with 2 instances, for me 2 instances of 8192MB have worked well on several XTX cards I have owned.
Command usage:-
memtestcl xxxx yy
xxxx = set MB for testing
yy = number of iterations to run
For more commands-
Code:
-------------------------------------------------------------
| MemtestCL v1.00 |
| |
| Usage: memtestCL [flags] [MB GPU RAM to test] [# iters] |
| |
| Defaults: GPU 0, 128MB RAM, 50 test iterations |
| Amount of tested RAM will be rounded up to nearest 2MB |
-------------------------------------------------------------
Available flags:
--platform N ,-p N : run test on the Nth (from 0) OpenCL platform
--gpu N ,-g N : run test on the Nth (from 0) OpenCL device
on selected platform
--license ,-l : show license terms for this buildMemtest Vulkan by galkinvv
Link to thread with app, link to section in XFX Merc owners thread discussing Memtest Vulkan, will soon do guide here.
PCI SIG Power Info vs Hardware specification
75 watts from slot, 3x8pin 450W (150W+150W+150W), total 525W.
Actual HW for standard 8pin 288W (3x288W) or decent PSU are HCS terminal and 396W (3x396W) plus you have slot 75W based on PCI-SIG spec.
PCB/VRM Design
Below from XFX product page:-
12x VDDCR_GFX (Core)
3x VDD_SOC (SOC)
2x VDDCR_USR (Unknown)
2x VDD_MEM (VRAM)
1x VDDCI_MEM (VDDCI)
Total 20 phases
The XFX PCB is similar to reference PCB, but made longer with additional 8 pin connector vs MBA XTX. No USB-C display port, but an extra DP and also dual VBIOS.
Below is image comparing MBA XTX PCB to XFX Merc XTX PCB. IgorLAB marked VRM phases and the other 2 images are from TPU reviews.
![Image]()
Circuit board analysis on TPU review link. Due to complexity of Navi31, all PCBs are 14 layers, "2oz copper". All use same mosfet and controller, most use same chokes and only a few have a phase extra for GPU and or VRAM. All have more than capable VRM. Basically it is only the lack of FW/Powerlimit tweaking holding cards back.
There are more phases then stated by XFX.
12x VDDCR_GFX (Core)
3x VDD_SOC (SOC)
2x VDDCR_USR (Unknown)
2x VDD_MEM (VRAM)
1x VDDCI_MEM (VDDCI)
Total 20 phases
The XFX PCB is similar to reference PCB, but made longer with additional 8 pin connector vs MBA XTX. No USB-C display port, but an extra DP and also dual VBIOS.
Below is image comparing MBA XTX PCB to XFX Merc XTX PCB. IgorLAB marked VRM phases and the other 2 images are from TPU reviews.
Circuit board analysis on TPU review link. Due to complexity of Navi31, all PCBs are 14 layers, "2oz copper". All use same mosfet and controller, most use same chokes and only a few have a phase extra for GPU and or VRAM. All have more than capable VRM. Basically it is only the lack of FW/Powerlimit tweaking holding cards back.
RX 7900 Series Tier list based on PowerLimit
-= Full Unlock =-
Tier 1
GPU PPT Limit (Sustained): 290W (-10% to +15%)
GPU PPT Limit (Short): 348W (-10% to +15%)
GPU Core TDC Limit 281A
Merc, Other variants TBC
Tier 2
GPU PPT Limit (Sustained): xxxW (-10% to +15%)
GPU PPT Limit (Short): xxxW (-10% to +15%)
GPU Core TDC Limit xxxA
Other variants TBC
Tier 3
GPU PPT Limit (Sustained): xxxW (-10% to +15%)
GPU PPT Limit (Short): xxxW (-10% to +15%)
GPU Core TDC Limit xxxA
Other variants TBC
Tier 4
GPU PPT Limit (Sustained): 257W (-10% to +15%)
GPU PPT Limit (Short): 308W (-10% to +15%)
GPU Core TDC Limit 448A
MBA, GAMING TRIO CLASSIC
Notes:-
GPU Core TDC Limit I have not seen GPU reach, the other 2 limits are the greatest limiters.
Tier 1
GPU PPT Limit (Sustained): 290W (-10% to +15%)
GPU PPT Limit (Short): 348W (-10% to +15%)
GPU Core TDC Limit 281A
Merc, Other variants TBC
Tier 2
GPU PPT Limit (Sustained): xxxW (-10% to +15%)
GPU PPT Limit (Short): xxxW (-10% to +15%)
GPU Core TDC Limit xxxA
Other variants TBC
Tier 3
GPU PPT Limit (Sustained): xxxW (-10% to +15%)
GPU PPT Limit (Short): xxxW (-10% to +15%)
GPU Core TDC Limit xxxA
Other variants TBC
Tier 4
GPU PPT Limit (Sustained): 257W (-10% to +15%)
GPU PPT Limit (Short): 308W (-10% to +15%)
GPU Core TDC Limit 448A
MBA, GAMING TRIO CLASSIC
Notes:-
GPU Core TDC Limit I have not seen GPU reach, the other 2 limits are the greatest limiters.
GPU PPT Limit (Sustained): 400W (-10% to +15%)
GPU PPT Limit (Short): 480W (-10% to +15%)
GPU Core TDC Limit 448A
Aqua Extreme OC vBIOS (Boost Clock up to 2935MHz)
Tier 0
-= Full Unlock =-
Tier 1
GPU PPT Limit (Sustained): 339W (-10% to +15%)
GPU PPT Limit (Short): 406W (-10% to +15%)
GPU Core TDC Limit 328A
Aorus Elite, Aqua, Liquid Devil, Merc, Nitro+, Phantom, Taichi
Tier 2
GPU PPT Limit (Sustained): 315W (-10% to +15%)
GPU PPT Limit (Short): 378W (-10% to +15%)
GPU Core TDC Limit 303A
Red Devil, TUF,
Tier 3
GPU PPT Limit (Sustained): 303W (-10% to +15%)
GPU PPT Limit (Short): 363W (-10% to +15%)
GPU Core TDC Limit 290A
Gaming OC, Hellhound, Pulse,
Tier 4
GPU PPT Limit (Sustained): 291W (-10% to +15%)
GPU PPT Limit (Short): 349W (-10% to +15%)
GPU Core TDC Limit 448A
MBA, GAMING TRIO CLASSIC
Notes:-
GPU Core TDC Limit I have not seen GPU reach, the other 2 limits are the greatest limiters.
Aqua and Taichi are same PowerLimit as Aorus Elite and Nitro, due to their boost clocks. Owners shares confirm PowerLimit on Aorus Elite and Nitro.
Merc has boost clock 2615MHz on product page, but owners shares confirm it's same PowerLimit as Aorus Elite and Nitro.
Phantom confirmed via review on Newgg showing HWI, Tier 1 card.
GPU PPT Limit (Short): 480W (-10% to +15%)
GPU Core TDC Limit 448A
Aqua Extreme OC vBIOS (Boost Clock up to 2935MHz)
Tier 0
-= Full Unlock =-
Tier 1
GPU PPT Limit (Sustained): 339W (-10% to +15%)
GPU PPT Limit (Short): 406W (-10% to +15%)
GPU Core TDC Limit 328A
Aorus Elite, Aqua, Liquid Devil, Merc, Nitro+, Phantom, Taichi
Tier 2
GPU PPT Limit (Sustained): 315W (-10% to +15%)
GPU PPT Limit (Short): 378W (-10% to +15%)
GPU Core TDC Limit 303A
Red Devil, TUF,
Tier 3
GPU PPT Limit (Sustained): 303W (-10% to +15%)
GPU PPT Limit (Short): 363W (-10% to +15%)
GPU Core TDC Limit 290A
Gaming OC, Hellhound, Pulse,
Tier 4
GPU PPT Limit (Sustained): 291W (-10% to +15%)
GPU PPT Limit (Short): 349W (-10% to +15%)
GPU Core TDC Limit 448A
MBA, GAMING TRIO CLASSIC
Notes:-
GPU Core TDC Limit I have not seen GPU reach, the other 2 limits are the greatest limiters.
Aqua and Taichi are same PowerLimit as Aorus Elite and Nitro, due to their boost clocks. Owners shares confirm PowerLimit on Aorus Elite and Nitro.
Merc has boost clock 2615MHz on product page, but owners shares confirm it's same PowerLimit as Aorus Elite and Nitro.
Phantom confirmed via review on Newgg showing HWI, Tier 1 card.
FAQ
i) VBIOS switch position towards:-
a) Display IO is increased PowerLimit VBIOS on XT.
b) PCI-E power plugs is is increased PowerLimit VBIOS on XTX.
ii) Checking if Powerlimit has increased can be seem on HWINFO, see red outlined metrics in below screenie.
![Black Font Line Screenshot Parallel]()
![Black Font Line Screenshot Parallel]()
ii) Finding out ASIC Quality (LeakageID), open HWINFO without checking any checkboxes, left pane select Video Adapter, select GPU, right pane a section will show ASIC Quality.
iii) Finding out what SMU FW version in use with a installed driver, open HWINFO without checking any checkboxes, left pane select Video Adapter, select GPU, right pane a section will show SMU FW.
a) Display IO is increased PowerLimit VBIOS on XT.
b) PCI-E power plugs is is increased PowerLimit VBIOS on XTX.
ii) Checking if Powerlimit has increased can be seem on HWINFO, see red outlined metrics in below screenie.
ii) Finding out ASIC Quality (LeakageID), open HWINFO without checking any checkboxes, left pane select Video Adapter, select GPU, right pane a section will show ASIC Quality.
iii) Finding out what SMU FW version in use with a installed driver, open HWINFO without checking any checkboxes, left pane select Video Adapter, select GPU, right pane a section will show SMU FW.
General links
-= XFX Merc Owners rig photos link =-
OCN - [OFFICIAL] AMD Radeon RX 7900 XTX/XT Owner's Club
OCUK - The Radeon RX 7900 XT(X) Owners Thread.
Reddit - r/AMD
XFX RX 7000 Series - Product page
Generic Log Viewer for viewing HWINFO (and other apps) CSV as graphs. Video link on basics of using app.
DisplayDriverUninstaller this will remove all trace of driver, best practise to use when change drivers/cards, game profiles, settings all will be deleted.
Waterblocks
Alphacool Forum - New cooler for RX 7900XTX Merc 310!
Reports of issue with Alphacool block on XFX Merc, see this thread.
Alphacool Eisblock Aurora Acryl RX 7900XTX Merc 310 with backplate
![Text Font Number Screenshot Document]()
Alphacool Core RX 7900XTX Merc 310 mit Backplate
![Text Number Font Screenshot Document]()
Bykski A-XF7900XTX-X
![White Screenshot]()
Reports of issue with Alphacool block on XFX Merc, see this thread.
Alphacool Eisblock Aurora Acryl RX 7900XTX Merc 310 with backplate
Alphacool Core RX 7900XTX Merc 310 mit Backplate
Bykski A-XF7900XTX-X
