Doing this while reducing tdp is awesome

Code: N6Cj9pxcWwv9SEB3bSaXpHNv

Claim through nvidia app.

instructions:

"Congratulations! With your recent purchase of a qualifying NVIDIA RTX50 series desktops, laptop or graphics card1, you’ve gained free access to CONTROL Resonant.

How to redeem:

Install your qualified graphics card. Update or install the latest version of the NVIDIA app. Open and log in to the NVIDIA app. Go to “REDEEM” Enter your bundle code from your qualifying bundle purchase. Follow the remaining instructions on screen.

Your CONTROL Resonant Bundle redemption code is: N6Cj9pxcWwv9SEB3bSaXpHNv"

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

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.

So I was reading some reviews of people comparing the 256GB Mac Studio vs 2 of the Nvidia spark workstations. They mentioned costs of between $10k and $15k and posted some numbers. A few guys mentioned a video that ran the two machines head to head on various models. One of the models was qwen flash which I have and can run. You guys may have seen my post a few weeks back about getting my 5090 working on my Mac. Well the thing that stuck out to me was that the Mac was quicker in some things but was much slower on prefill and multi user. That is specifically what my shim can accomplish so I ran some tests.

These are the numbers I got from the video:

┌────────────────────┬──────┬──────────┬──────────────┐
│                    │  Us  │ M5 Ultra │ 2× DGX Spark │
├────────────────────┼──────┼──────────┼──────────────┤
│ Single-user decode │ 68.4 │ 45       │ 38           │
├────────────────────┼──────┼──────────┼──────────────┤
│ 8 users, total     │ 155  │ 66–70    │ 120          │
├────────────────────┼──────┼──────────┼──────────────┤
│ 32k cold prefill   │ 27 s │ 26 s     │ 11.2 s       │
└────────────────────┴──────┴──────────┴──────────────┘

And these are numbers I get with llamacpp with my m4 128gb laptop and 5090

As you can see I'm still working on cold prefill but for a $6k investment for the M4 and the 5090 box you get better performance on the split system. The 5090 probably blows both systems out of the water on a smaller model that fits fully in the cards Vram too.

I don't have these other systems but these are the numbers I've found. feel free to correct me if my numbers are not what you are seeing in real world testing. If you want to test this yourself I'm updating the macuda project tonight with the changes that enabled these results. I've go the driver and shim working on 3060 and 5090. I haven't tested the 3060 on these latest features yet but it's shim work mostly so it should carry over.

edited 8 user to 155 from 133 after retest

Is RTX 3050 Processor still good for a budget friendly for architecture. Im really on a tight budget right now

This Hotfix driver looks to be specifically targeting a couple monitor related bugs.

Article: https://www.nvidia.com/en-us/geforce/forums/g-sync-pulsar/131/586047/qhd-360-pulsar-monitors-changelog/

Download Link: https://international.download.nvidia.com/Windows/617.70hf/617.70-desktop-notebook-win10-win11-64bit-international-dch.hf.exe

Reminders:

• Hotfix driver will not be available in NVIDIA App and needs to be downloaded from the link above.
• After installing the Hotfix driver, NVIDIA App may show some old driver date. This is normal as Hotfix driver does not exist in NVIDIA App database and it reverted to an old default changelog and dates.
• If you do not care about the fixes listed, this Hotfix driver is no different vs WHQL 617.42 Driver.
• These fixes will be incorporated into the next WHQL driver release

NVIDIA Driver forum thread is here: Link Here

Submit driver feedback directly to NVIDIA: Link Here

---------------------------------

From the Article:

We now have a hotfix driver for the two below bugs. These fixes will - for now - not be in main NVIDIA driver until we can do more extensive QA.

• QHD monitor running at 360 Hz may have occasional black flash during gameplay [4846825] 
• When gaming on a 360Hz G-SYNC Pulsar monitor, FPS may drop to 320FPS [6408986] 

NOTE: The hotfix driver fixes some, but not all cases of the black screen issue. We are working on finding a driver solution for the remaining cases. If you still encounter this, please use the workaround: Set Manage 3D Settings --> Power Management Mode to Prefer Maximum Performance . You do need to reboot after setting that for it to take effect.

For those who want to test out the new Frame Generation preset C with DLSS swapper / NVPI etc.. Instead of using the NVIDIA App override.

You can see which preset is active via the DLSS Dev overlay at the top of the screen.
(Enabled via Regedit or DLSS Swapper > settings > show onscreen indicator)

But unlike DLSS upscaling,
The DLSS Dev overlay doesnt list the preset letter in use for Frame Generation, instead look for the below variables that change based on the preset in use for confirmation:

Preset A: UIR = NA - Full
Preset B: UIR = ON - Full
Preset C: UIR = NA - Lite

(These variables are listed at the end of the FG bar)

NOTE:
You can technically get the Alt+R overlay working with accurate preset reporting whilst using NVPI / DLSS Swapper if you enabled 'DLSS-FG - enable DLL Override' in NVPI, BUT this defeats a bit of the purpose of using these tools as it will use the NVIDIA app .dll not the local game files one. Plus then your dependant on the nvidia app version not necessarily the latest avaliable etc etc.

Edit: fixed pic caption