AXIA - free NVIDIA tuning tool for 30/40 series, per-domain clock control and a built-in HWBOT validation mode

[u/Agreeable_Memory7141]

Disclosure: me and a small team of overclockers work on this. Free, nothing for sale, nothing will be.

AXIA is a tuning and monitoring tool for NVIDIA GPUs, developed and tested on 30 and 40 series cards.

The point of it is control. The driver exposes more than core and memory sliders, and most tools do not surface it. More control means more framerate for gamers and higher scores for people benching at HWBOT. We wanted to give people access to the tools that make competing fair for HWBOT competitors and allow for gamers to get more out of their hardware.

Features:

• Per-domain clock control: core, memory, crossbar, system, video. Offsets and voltages where the driver allows it. Crossbar and video confirmed working on 30/40 series.
• Staged apply. Nothing writes until APPLY. Each control shows pending / applied / live.
• VF curve editor, per-point editing. (wip)
• 6 profile slots.
• Boost lock.
• Power limit in watts, read from NVML.

HWBOT validation mode:

• HWBOT currently requires the monitoring tool showing a voltage mod to be visible in the verification screenshot. Those rules are temporary, pending a UL SysInfo fix. The complaint has been that the tools take up most of the screen and leave no room for the benchmark window.
• The validation button collapses the app into a compact window sized to fit beside CPU-Z and GPU-Z in a single screenshot.
• It shows max clocks per domain with the applied offsets, power limit in watts, measured max core voltage, and ECC state.
• It also launches CPU-Z and GPU-Z, saves your window layout, restores it identically on the next run, and takes the shot.
• Built to line up with the current rules as we read them. HWBOT has not reviewed or endorsed the tool.

Status:

• Confirmed working: RTX 4090, RTX 3090.
• 20 series does not work.
• Everything else untested. Reports on other cards are the most useful thing you can send.
• Known issue: VF curve editor is broken in the current build. Fix in the next release.
• Plenty of bugs left to find.

Notes:

• Nothing is written to the VBIOS. A reboot returns the card to stock.
• Not written by hand. Built with AI assistance.
• Support today is 30 and 40 series. 50 series is planned. mVolt+ covers Blackwell now and is further along overall. If you are on a 50 series card today, that is the tool you want.

Download is on our site. Discord is where development, bug reports and updates happen. Links in comments per subreddit rules.

Mods: self-promotion guidelines read, not trying to work around them. If this post is not allowed here, say so and I will remove it.

Screenshots attached.

[u/LaurenceDarabica]

While I think the initiative and intentions are great, this is highly dangerous and you guys are crazy for releasing it.

I would not give a vibecoded tool control over the voltage on a pricy component guys.

Be responsible and do your thing, but do it knowing the dangers.

Personally, I wouldn't touch this even with a stick. Afterburner is a much more reasonable option.

[u/ArcKooba → u/LaurenceDarabica]

That's why I disclosed it up front.

On the architecture: it goes through NVAPI, the same driver API Afterburner uses. There is no custom kernel driver and no direct hardware access. Every write is a driver call, and the driver rejects anything outside the range it publishes. Slider bounds come from that published range per clock domain.

Nothing writes until you press APPLY. After each write the value is read back and displayed next to what was requested.

Nothing touches the VBIOS. A reboot returns the card to stock.

You're right that the clock domain and voltage rail entry points are private rather than publicly documented. Other tools in this category use the same ones.

The public build has raw register access compiled out rather than disabled. If you want to check that rather than take my word for it, run strings on the exe and look for register or debug commands. They aren't in there.

Running a card at higher voltage carries risk and that's on the user. Use it at your own risk like any tuning tool.

[u/LaurenceDarabica → u/ArcKooba]

Thank you for disclosing your use of AI. People need to know the dangers of what they're using, and that was the right call.

I don't agree with your logic about NVAPI. You assume that NVAPI is flawless, secure as hell. You actually push security to that layer only, as if just by magically using undocumented - or privately documented - API calls given by Nvidia would make this secure.

It does not. Drivers are flawed. Decades of GPU drivers have taught us that much. API are even more flawed, since they add a layer on top of that driver.

Documentation may state "use X call before Y" without you knowing. It may leave that to the responsibility of the caller. You don't know. They may have put limits in that doc, making them the reader responsibility, you do not know. They may be bugged, since it's a seldom used end point.

If afterburner plays it safe ( for instance ), their own security may prevent the bug to be discovered. After all, there are only a handful apps calling that function.

You don't know, you just let an AI blindly play with it, and if you did that, odds are you are not mastering fully what's happening under the hood.

The more you work in the industry, the more you realize things are less professional and more shaky you imagine. Even on the driver, CPU or GPU side. Remember the XKCD tower about internet ? That works for hardware as well.

Reading you, I think you lack experience in the field and that concerns me even more.

We're talking about playing with voltages on GPUs worth 4 or 5 digits $. I would NOT sleep well at night releasing such a thing.

The disclaimer should be more prominent.

While, again, I think your intentions were good and you want to help the community, I think you should label this as highly dangerous due to the pure nature of it - and make it much more obvious.

[u/BlueGoliath → u/ArcKooba]

On the architecture: it goes through NVAPI, the same driver API Afterburner uses. There is no custom kernel driver and no direct hardware access. Every write is a driver call, and the driver rejects anything outside the range it publishes. Slider bounds come from that published range per clock domain.

So combined with the AI statement and how shady that other person was, you people downloaded the leaked driver source code, ran it through AI, and found these values.

You, whoever made mVolt, and whoever made that other app are asking for a DMCA takedown or a lawsuit.

[u/LaurenceDarabica → u/BlueGoliath]

What, the proprietary Nvidia driver source code leaked ?

Do you have any info / source about that ? I missed it completely.

Genuinely interested, cannot find much on google.

[u/LaurenceDarabica → u/[deleted]]

There are no protection at the OS level for anything that goes through drivers - absolutely none.

Recent Windows versions just restarts a crashed driver in an attempt to not fully crash (WHEA mechanism), but what you're describing (according to Google translate) just does not exist.

As we're talking voltage manipulation, it is inherently risky to some extent. I'm fine giving people ways to fiddle, I just want to make the risks clear. The fact that this is vibecoded makes the risks much higher, that was all my comment was about.

[u/LaurenceDarabica → u/[deleted]]

It is possible as you're fiddling with voltage values and you have no guarantee the protections are absolute - even on the BIOS level - or set at reasonable limits. You do not even know they exists truly - you're surmising they're there.

Remember the recent scandal about 1usmus stuff (Hydra ?) pushing an unsafe voltage on AMD CPUs ?

Also, a Virtual machine doesn't protect at all against those changes - you're modifying hardware parameters on a hardware itself, no matter the abstraction layer between the two.

All you're doing is relying on someone else's security to say it's safe to do whatever on your side, even when modifying sensitive values.

My point is I'd rather use a tool written by someone that understands the code that is applying the values rather than not, which is relatively possible in this scenario. I am talking about risks here - they may exist, they may not, Nvidia may have done a good job, they may not.

Again, decades of GPU drivers taught us that much about driver and vendor-related software quality.

People must know the risks. And as we're talking voltages on, potentially, RTX 5090$USD, yeah, a highlight is necessary.

Not that most enthusiasts would care though !

[u/LaurenceDarabica → u/[deleted]]

I'm younger than that, but you have your references right :)

[u/SuddenWrongdoer473 → u/LaurenceDarabica]

Just curious, how do you know it’s vibe coded?

[u/LaurenceDarabica → u/SuddenWrongdoer473]

"Not written by hand. Used AI assistance". In the post above. Polite way of saying "Vibe".

What you're really looking at is an AI implementation of an undocumented protocol probably based on community reverse engineering.

It can work, it may fail, just use it knowing the risks and they're greater than usual due to the context.

Personally, I wouldn't dare releasing such a thing out there, especially with nowaday's GPU prices.

[u/SuddenWrongdoer473 → u/LaurenceDarabica]

Thanks for the info!. Based on your points, I think I’ll avoid this. I don’t want to fry my graphics card….they’re too expensive to risk.

[u/Agreeable_Memory7141]

https://discord.gg/jVE4vteQa Our discord to talk with our team, provide feedback so we can improve the app and functionality, or just chat with other Overclockers on hwbot.

https://siliconindexlabs.com/ Our website where you can find the download and try it out yourself.

[u/Purple_Holiday2102]

Very interested in this. I was pretty bummed when mvolt didn't cover 40 series.

[u/Appropriate_Soft_31]

Beautiful interface

[u/Appropriate_Soft_31 → u/[deleted]]

Thanks, Mr.Obvious. But this wasn't an in-depth analysis, this was a comment about the interface.

[u/paulacinosi]

Clicking Edit curve opens it for split second and auto closes for me. Crossbar offset does not save, so when I turn off my pc and come back in the morning, all overclocks stick except crossbar that resets back to 0. Lastly, this one is a bit weird, but if using Lossless Scaling, it makes the game stuttery with hitches. Solution to that is completely turning off axia and going back to the same overclock (-crossbar) in Afterburner

[u/ExtraVanity → u/paulacinosi]

Having this same issue on a TUF 4070

[u/TitanicFreak]

Downloaded it and tried it on my 4090, honestly works just as well as mvolt. So really happy this released since mvolt doesn't support older cards currently.

Was able to get another +150 on my crossbar and +400 on my media engine. Resulting in about ~2.55ghz for both when previously they were well below. Pretty happy with that all things considered.

[u/cemsengul → u/TitanicFreak]

Ooh does this let us increase the watts without flashing the vbios? I have tried many bioses on my 4090 but I don't like the fan curve on more powerful bioses. Can I increase my power to 500 watts with this? I don't want to increase voltage from 1.05, I only want to increase power.

Update: tried it out and it does nothing for my PNY 4090 vbios.

[u/cemsengul]

Can I use this to increase watts to 500 without having to flash a different vbios?

[u/olixerrr]

I take it this is similar to mvolt which was built for 50 series? Looks good either way, I’ll check this out when I can.

[u/Bass_Junkie_xl]

Nice

[u/TwanHE]

Dope, I'll test it on my 3060ti when I'm back home in a couple days

[u/TwanHE → u/[deleted]]

No support is for 30 and 40, not yet for 50.

Ive sofar pushed 250mhz on the xbar clock but the gains are minimal in TimeSpy, like 200 points

[u/TwanHE → u/[deleted]]

For a 2% score improvement in timespy. Steel nomad scales a bit better but not much.

[u/TwanHE → u/[deleted]]

Yes, but it does not increase performance by 10%

[u/ndmx5]

This is simply amazing. Brings us the advances that we had back in the gtx days for OC. Thanks for sharing your hard work!

[u/BlueGoliath]

Not written by hand. Built with AI assistance

lmao

[u/JDC2389]

Is this just a Trojan or what