Hello guys, hoping you're doing fine.

Today I want to share something that may affect your cards (?

I have released 3 tools:

1. A way to modify VBIOSes, so you can increase power limit, voltage, NVVDD offsets, MSVDD offsets (Blackwell 2.0), OCPs, fan channels, power per fan, core offsets more than 1000, VRAM offsets more than 3000, lower power limits (below 400W on a RTX 5090), lower clocks, etc. But as you know, these can't be flashed directly on the cards because falcon, right?
2. A custom VBIOS loader on Windows, that patches the registry file related to that GPU, it resets it and it's applied on every reboot. This does not change the real VBIOS on your card, but it just loads a copy via a patch and it let you use any modification!
3. A custom VBIOS loader on Fedora, that patches the GSP firmware start on memory, builds a separate boot entry and then rebuilds automatically with kernel updates. This does not change the real VBIOS either.

What are the requirements?

• Windows:
  • Windows 10 or 11, 64-bit.
  • NVIDIA driver 616.56 or newer (status shows the version).
  • A payload file for that exact GPU model (same PCI device ID).
• Linux:
  • A working NVIDIA 615.x driver or newer with the open kernel modules; nvidia-smi must list your GPUs.
  • The unpatched source of the open kernel modules for the exact installed version, for example: git clone --depth 1 --branch 615.78.08 https://github.com/NVIDIA/open-gpu-kernel-modules
  • Python 3.11 or newer, the headers for the running kernel (kernel-devel on Fedora), make, dracut, grub2-editenv and mokutil. With DNF5, also libdnf5-plugin-actions.
  • GRUB with GRUB_DEFAULT=saved and GRUB_ENABLE_BLSCFG=true (Fedora's defaults).
  • Secure Boot off, or your own module signing key: pass --signing-key and --signing-certificate to prepare.

You need to first get a copy of your VBIOS, you can do it with GPU-Z on Windows, or with nvflash on Linux.

Note that you can't modify EVERYTHING for the VBIOS, since it's still on research of what can be modified, what not and which rails are exposed. Also for example, VRAM timings can be modified (not on these tools) but they aren't applied, since the card reads it physically from the flash hardware.

So, some example pics!

First, some VBIOS editor example, for a RTX 5090 VBIOS, a RTX 4090 VBIOS, and a RTX 3090 VBIOS.

Then, the VBIOS loader on Windows looks like this:

Then you can choose a VBIOS, for example I will select a 671W VBIOS for the 4090.

And press OK/Accept, and a quick GPU restart after (no windows reboot), it works!

And it works just fine!

PS C:\Users\User> nvidia-smi -i 0 -pl 671

Power limit for GPU 00000000:05:00.0 was set to 671.00 W from 550.00 W.

All done.

On the other hand for Linux, the UI looks very similar, and steps are similar, but you can also guide yourself on the github repo!

You can edit the values you modified on MSI Afterburner, mvolt+ (recommended) on Windows. On Linux you can use LACT.

Tested GPUs that I own, and it works:

• RTX 6000 PRO MaxQ: Unlocked voltage (stock 0.9V) to 1.1V, power from 325W to 600W, core offset to be able to do +2000Mhz, VRAM to be able up to +6000Mhz (it depends of your luck), and some OCPs.
• RTX 5090: PL from 600W to 800W, core offset to be able to do +2000Mhz, VRAM to be able up to +6000Mhz.
• RTX 5080: PL from 360W to 500W, core offset to be able to do +2000Mhz, VRAM to be able up to +6000Mhz.
• RTX 5070Ti: PL up to 450W, core offset to be able to do +2000Mhz, VRAM to be able up to +6000Mhz.
• RTX 4000 PRO SFF: PL from 70W to 105W, core offset to be able to do +2000Mhz, VRAM to be able up to +7000Mhz, unlocked voltage from 0.85V to 1.1V.
• RTX 5070: PL from 250 to 350W, core offset to be able to do +2000Mhz, VRAM to be able up to +6000Mhz.
• RTX 5060Ti: PL from 185W to 300W, core offset to be able to do +2000Mhz, VRAM to be able up to +6000Mhz.
• RTX 4090: PL up to 700W, core offset to be able to do +2000Mhz, VRAM to be able up to +6000Mhz.
• RTX 2000 Ada: PL from 70W to 105W, unlocked voltage up to 1.1V.
• RTX A2000 (Ampere): PL from 70W to 105W, unlocked voltage up to 1.1V.

Tested GPUs that I don't own, by other users:

• RTX 6000 PRO Workstation Edition
• RTX 5090
• RTX 5080 Laptop
• RTX 4070
• RTX 3060

For now, I can't seem to be able to edit Ada laptop variants (RTX 40 laptop series). Laptop Blackwell series (RTX 50 laptop series) can edit some parts of the VBIOS, but not all of them. Laptop Ampere series (RTX 30 laptop series) can edit almost everything.

And finally, the links are:

VBIOS Editor (Linux and Windows): https://github.com/Panchovix/nvidia-vbios-vix-editor

Custom VBIOS loader (Windows): https://github.com/Panchovix/nvidia-windows-vbios-vix-loader

Custom VBIOS loader (Linux): https://github.com/Panchovix/nvidia-linux-vbios-vix-loader

Everything is open source, so you can check the code to see if there are applicable fixes and such.

So if you guys can try, please let me know! If you find crashes on the vbios editor, or a specific GPU has info you can't edit and may be feasible to do so, you can raise an issue on github and I will check it out.

Warning: You use these software entirely at your own risk. Any modification you make with it, anything derived from it or from its output, and any damage that results, is solely your responsibility.

Then, the VBIOS loader on Windows looks like this:

MSI RTX 3080 Ti Ventus 3X Deshroud Mod — 2x Arctic P12 Pro PST, 14°C Lower GPU Temps and Almost Silent!
I finally completed a deshroud mod on my MSI RTX 3080 Ti Ventus 3X, replacing the three stock GPU fans with 2x Arctic P12 Pro PST 120mm fans.
The results have honestly exceeded my expectations!
Before vs. after
Measurement
Stock fans
2x Arctic P12 Pro PST
GPU temperature
80°C
66°C
GPU hotspot
90°C
74°C
VRAM temperature
92°C
86°C
Fan speed
~2000 RPM
~2000 RPM
Noise
Noticeably loud
Almost inaudible
Testing
The new results were recorded during a 10-minute FurMark test at 1440p, averaging around 160 FPS.
That’s a 14°C drop in GPU temperature, a 16°C drop in hotspot temperature, and a 6°C drop in VRAM temperature.
The biggest surprise is the noise reduction. The stock fans were loud even around 2000 RPM, while the two Arctic fans are practically inaudible at the same approximate speed in my setup.
Both 120mm fans fit the heatsink surprisingly well. My goal was to reduce noise while improving cooling, and so far, the results have been excellent.
I’ll continue monitoring temperatures during longer gaming sessions to see how the setup performs over time.
Build details
GPU: MSI RTX 3080 Ti Ventus 3X
Fans: 2x Arctic P12 Pro PST 120mm
Test: FurMark, 1440p, 10 minutes
Fan speed: Approximately 2000 RPM
Has anyone else done a deshroud mod on a Ventus 3X? I’d love to hear about your fan choices, fan curves, and long-term results!
Note: These are my own results. Ambient temperature, case airflow, and test conditions can affect temperatures, so comparisons may vary.

Doing this while reducing tdp is awesome

NVIDIA Streamline SDK 2.14.16 is now available for all developers:

Bug Fixes & Stability Improvements

https://github.com/NVIDIA-RTX/Streamline/releases/tag/v2.14.16

https://github.com/NVIDIA/DLSS/tree/main/lib/Windows_x86_64/rel - dll files for games.

Just wanted to share some appreciation for how durable this old Lenovo Y50-70 beast is. The screen has taken a beating, the touchpad is completely worn out from years of heavy use, and I've opened it up countless times to clean the fans—yet this legendary GTX 960M still boots up and refuses to give up!

​Seeing the mind-blowing new Spark tech, massive AI leaps, and modern RTX advancements being pushed today honestly feels like looking at alien technology compared to this old warrior. It’s wild how far hardware has come. Anyone else still holding onto an ancient GPU that simply refuses to die.

Hi everyone,
I’m considering switching from MSI Afterburner to Mvolt for undervolting my RTX 4080 Super.
I mainly use the voltage curve editor and I’d like to know if mVolt is a better alternative to Afterburner, especially regarding stability and compatibility with RTX 4000 series GPU.

The reason I’m considering switching is that I’ve been having a frustrating issue with Afterburner.
My undervolt profile is set to 2655 MHz at 950 mV, but after every Windows boot, Afterburner lowers the frequency below my saved value, so I have to manually reapply the profile.

I’ve already tried launching Afterburner through Windows Task Scheduler with a delayed startup, but the issue persists.

Is mVolt reliable and stable on RTX 4000 series GPUs, particularly the 4080 Super?

Is its curve editor better or more consistent than Afterburner?

Does mVolt have similar issues with undervolt profiles changing after reboot?

Would you recommend switching, or sticking with Afterburner?
Thanks

Hey guys, wanted to share some real-world benchmark data from a maintenance job I just finished:

The Results:

• CPU Temps: Dropped from 100°C down to ~80°C under heavy load (-20°C drop).
• GPU Score: Increased by +43% in synthetic benchmarks once throttling stopped.
• DaVinci Resolve 4K Export: Significantly faster render times and zero timeline lag.

I made a detailed teardown and benchmark video covering the whole process and thermal charts if anyone wants to see the step-by-step or exact numbers:

https://youtu.be/Jz4oQcztXEg?si=m3KcuOEcL9Cfj-SR

Looking for an open source frame work where I can use cursor along with open source / weight models with an agent swarm that has existing skills. Wasn’t sure if any one has run across any yet.

Is there an official webpage about the presets?

My 2060 super is starting to show its age and I want to upgrade to a 50 series. My goal is to push my current hardware as far as it can go before likely getting a new rig in 3-5 years.

Current build:
Motherboard: Asus Prime 450M-A
CPU: Ryzen 7 3700X
PSU: 850W
Monitors: 1080p, 60hz refresh (x2)
RAM: 32GB DDR 4
Current GPU to replace: 2060 super

I was previously recommended a 9060xt 16GB model, but AMD driver timeouts and other issues including crashes convinced me back to team green again. That thing was a pain in my butt.

Right now my options on the low end of my budget are the 5060 and 5060 ti 8GB models, with my stretch budget going up to the 5060 ti 16GB or 5070 12gb. I’m not sure if those are worth the price increase with my current CPU probably being a bottleneck though.

Anyone actually using NVIDIA ConnectX-8 SuperNICs in production yet? How's the real-world performance?

I´ve been considering this for a while now and it seems its not really worth it if you dont go at least to an RTX 5080.

Im not in the US so it is not that easy to sell the RTX 3090 for what it is worth now and Getting a RTX5080 is even more expensive than it should.

So, has any of you guys upgraded from an RTX 3090 to any Series 5000 GPU?

If you did, which GPU did you get and how much did your FPS in different scenarios improve?

I think im mainly trying to figure out if going to a 5070Ti or even 5070 or if it is worth it to sell a kidney to get a 5080.

Early recipe, still testing. ./start.sh serves NVIDIA's NVFP4 quant of Qwen3.8-Flash-Next over an OpenAI-compatible API on one DGX Spark (GB10).

Settings

• vLLM in eugr's Spark image, b12x kernels for GB10
• 262k context, FP8 KV cache
• Up to 8 parallel sessions
• MTP speculative decoding, 4 draft tokens
• PLE tables offloaded to disk
• Qwen3 reasoning + tool-call parsers

What's NVFP4? NVIDIA's 4-bit float format: every block of 16 weights shares an FP8 scale, plus one scale per tensor, so it holds up better than plain INT4. ModelOpt "mixed" keeps sensitive layers at higher precision. ~96 GB, native on Blackwell FP4 tensor cores.

Numbers (single stream), vs MiaAI-Lab's TensorFold INT4 recipe on the same GB10:

• 256k ctx: 1,881 vs 1,970 t/s prefill, 35 vs 38 t/s decode
• tool-eval-bench: 90/100 vs 85
• Structured output: 83% vs 40%
• Hard mode: 91% vs 74%
• Tool-call TTFT: 245 ms vs 526 ms
• TensorFold decodes faster up to 32k; FP4 holds ~35 t/s at every depth

Recipe: https://github.com/devopsfortunato/Qwen3.8-Flash-Next-FP4-Local-DGX-Spark

Credits: TensorFold recipe by MiaAI-Lab, plus NVIDIA, vLLM, and eugr for the Spark image.

Feedback welcome, especially if you've run it with concurrent sessions.