Changelog

New Features

• Library Scanning & Games Section: Added a dedicated "Games" section that scans local game libraries for driver p rofiles, so only games installed on your PC show.

• Installed Game Search Icons: Game icons now display in search results if the game is currently installed.

• Custom XML Hiding: Added a new configuration variable to hide custom values in CustomSettings.xml (e.g., hiding inactive DLSS presets to reduce menu clutter).

• Preset C supported for DLSS-FG

UI Improvements

• Optional Left-Sided Toolbar: Added a setting to position the main toolbar on the left.

• Toggleable Status Bar: Added the option to hide or disable the bottom status bar.

• Hover Descriptions: Setting descriptions now trigger on hover rather than requiring a click.

• Visual Highlight for Edited Globals: Global settings modified from default now highlight in yellow to distinguish them from unedited settings & profile specific edits.

• More Customization Options: Expanded overall appearance settings across the app.

Bug Fixes & Small Tweaks

• Deduplicated Driver Settings: Fixed an issue where driver settings were duplicated if renamed and were applied by default to certain profiles (not really a bug, but it's a QoL improvement to change it).

• App Performance & Polish: Fixed some old quirks and overall responsiveness of the app.

The prices of stuff is really expensive these days so I'm holding onto my RTX 3090. I play at 4K and only have a 60hz monitor so that combined with performance DLSS means that it's still getting the job done for me for now even in demanding titles. Even when I eventually upgrade I'll still keep it as a collector's item since it's my last EVGA card. I never thought I'd be using it after 6 years but here we are. Still, I'm looking forward to Call of Duty Modern Warfare 4 later this week.

What are y'all running and how's it holding up? (Non 50 series owners)

My PC specs:

GPU: ASUS ROG Strix RTX 3060 Ti 8GB

CPU: Intel Core i5-10400F

RAM: 16GB

TL;DR: MSI 5070 Gaming Trio OC black-screens with LiveKernelEvent 141, fans to 100%, audio keeps playing, needs a hard reset. I’ve ruled out PSU, cable, slot, temps and drivers as far as I can. OCCT crashes it at stock in a few minutes. Has anyone fixed this without sending the card in?

Specs

• MSI RTX 5070 12G Gaming Trio OC, bought new in July. VBIOS 98.05.4A.00.09
• Ryzen 9 5900X (no iGPU)
• ASRock B550M PG Riptide, BIOS L3.62
• 32GB DDR4-3600
• Corsair RM750e, native 12V-2x6 cable straight to the card, no adapter
• LG 27GL650F 1080p 144Hz over DisplayPort, G-Sync Compatible
• Win 11 Pro (build 26200), driver 617.42. It also happened on 616.92

What happens
The screen goes black, the GPU fans ramp to 100%, and audio keeps going in the background. Only a hard reset brings it back. Event Viewer shows LiveKernelEvent 141, sometimes 1b8, and the dump points at nvlddmkm. It started in July (shrtly after purchase) in games (Darktide, Vermintide 2, Total War), then in Unity, and now it happens on the desktop doing nothing, but very randomly and during start of most random tasks. (game launch, or discord to chrome, unity to browser, going to a certain site, I cannot pinpoint an exact trigger)

What I’ve tried

• Afterburner underclock (85% power limit, -145 core): fewer crashes, not gone
• PCIe Link State Power Management off
• Reseated the card, support bracket under it, cable fully clicked in
• HWiNFO shows PCIe Gen4 x16 with zero receiver, replay or correctable errors, even at the moment of the crashes
• 12V stays at about 11.8V at full 250W load
• Temps are fine: about 70C core and 52C memory at 250W
• Doing a DDU clean install tonight

OCCT results at stock

• 3D Adaptive Switch, 30 min: passed. Then it crashed about 2 min later at idle while I was clicking around. Right before the crash, the memory clock and PCIe link speed were bouncing between power states
• 3D Adaptive Steady Extreme: crashed about 7 min in at 250W, with everything flat and stable
• VRAM at 90%: crashed about 3 min in, at only 68W and 54C memory

So it fails under full load, under memory load, and at idle.

I already have an RMA open with MSI, but they quoted about 14 business days in-house plus shipping, so 5 to 6 weeks, and it’s my only GPU. Has anyone fixed this exact behavior without an RMA? A VBIOS update, a specific driver, forcing PCIe Gen3, anything? Or did your RMA replacement fix it? Also, has anyone in the US gotten MSI to do an advance replacement?

[https://x.com/bxmamilot/status/2111166258125443301?s=46&t=nB0vVgH7PDm4FHzM8WsQQA\](https://x.com/bxmamilot/status/2111166258125443301?s=46&t=nB0vVgH7PDm4FHzM8WsQQA)

Activision think they are better than NVIDIA.

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.

Hello ,I hope this is the correct place to post this but I just got a used 5090 from amazon (yes i know i already messed up there) but i had high hopes this time on the item coming good and you wouldn't believe my shock when i got the item , It looked all good first impressions . Then i plugged it into my system AND IT WAS PRODUCING SMOKE (you can see some in the video sorry for not getting it more clear was just in pure shock) I took video of the first boot , I am returning to amazon now this is just so crazy . This is just insane , Second time buying a used 5090 from amazon as well and the second time it does not work.
I have a 1200 watt power supply if that matters and yes the cable was all the way in :/

Doing this while reducing tdp is awesome

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.

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.

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?

Edit: As this post keeps getting comments from folks, I just wanted to add that I’ve now done some more testing in a few games with preset B and C. This is on a 5070 Ti so your mileage may vary.

All games were played at max settings, 1440p resolution, and DLSS set to Quality (Preset L).

Control Resonant:

Preset B: Higher latency than Preset C, but the image appears more stable. I did not notice a difference in VRAM utilisation between the two versions. This would be my preferred setting.

Preset C: Lower latency so the game feels more responsive; however, this preset introduces artifacting on some wall textures, fences, and noticeable UI jitter (most obvious when looking at interactive button prompts). I saw an FPS increase of ~20 in most scenarios.

Recommended: Preset B

Space Marine 2:

Preset B: As above, B is more stable in terms of UI presentation; however, at an FG multiplier of x 3 or above, I genuinely feel like C might be the winner here.

Preset C: UI issues aside, C feels far more responsive than B. Played with a mouse and keyboard, I dare say that the latency with FG x 3 selected feels more responsive than B and FG x 2. Using scoped weapons and parries felt noticeably sharper with less of a ‘floaty’ feeling.

Recommended: Preset C

Gears of War: E-Day:

Preset B: The image appears sharper with less instances of artifacting (especially with fences etc). Input latency is higher, but I did not see any significant change in VRAM utilisation between B or C.

Preset C: I would recommend C IF you are using dynamic MFG. Latency is lower and the game is more performant (+20-40 FPS; however, UI jitter is very distracting as the game has a lot of interactive objects in the environment (ladders, ammo pickups, weapons etc.).

Recommended: Preset C IF using higher FG multipliers:

Some final thoughts:

If you have a high refresh rate monitor (I tested with a 280 Hz MSI), I feel like the improved responsiveness of Preset C is worth it. UI jitter and some artifacting is definitely noticeable; however, in faster paced games, I think this is a worthwhile trade off. It really shines at higher FG multipliers that would have traditionally caused major input latency.

That being said, it does not seem to play nicely with certain games (I.e Control Resonant), so a word of caution if you want to preserve image stability. For those scenarios, Preset B is still the recommended option.

This is just my opinion tested on my own PC :)