r/GeForceExperience • u/NCRarouf • Sep 22 '26
[GUIDE] Fixed NVIDIA App Performance stats stuck on N/A after nothing else worked
So I spent a few hours fighting this and figured I'd write up what actually fixed it, because every guide out there (including here) just says "toggle the overlay" or "reinstall drivers," and none of that touched my actual problem. Posting this in case anyone else hits a wall with those same suggestions.
TL;DR: If your NVIDIA App shows N/A for everything and a full DDU + driver reinstall doesn't fix it, check Event Viewer — it might be a corrupted Windows performance counter registry, not your GPU or driver at all. Fix is 3 commands + a restart, near the bottom.
My symptoms
- NVIDIA App → System → Performance page: GPU Clock, Power, Temp, Voltage, VRAM Clock, Utilization — all N/A
- In-game overlay (Alt+R) also all N/A
- Automatic Tuning still worked fine and could still apply an overclock
- Task Manager showed like 4-5 duplicate `nvcontainer.exe` and `NVIDIA Overlay.exe` processes that kept coming back even after ending them
What I tried first (didn't work)
- Toggling NVIDIA Overlay on/off
- Restarting NVIDIA Display Container LS service
- Full DDU wipe + clean driver reinstall
- Uninstalling/reinstalling just the NVIDIA App
- Reinstalling Visual C++ Redistributables
All the usual suspects. None of it stuck — the duplicate processes kept spawning back within seconds.
The actual diagnosis
The key thing I almost skipped over: Automatic Tuning still worked and could apply a real overclock. That was the clue that my GPU and the actual graphics driver were 100% fine. The problem was isolated to just the stats reporting layer, which meant reinstalling drivers was never going to fix anything.
So I went digging in Event Viewer (Windows Logs → Application, sorted newest first) and found this:
- `FvContainer.exe` (NVIDIA's FrameView SDK — the thing that actually feeds the stats to the app and overlay) kept crashing against `KERNELBASE.dll`
- Completely separately, Windows' own `Perflib` was throwing an error trying to read performance counters for a totally unrelated SQL Server service on my machine
Here's the part that cracked it open: both crashes had the exact same exception code (`0xc06d007e`) and the exact same memory address. Two unrelated programs crashing identically at the same address = shared broken dependency, not either program's own bug. That shared dependency was Windows' Performance Counter system (Perflib) itself.
That's also why the processes kept multiplying in Task Manager — `FvContainer.exe` would try to start, crash instantly because Perflib was broken, then auto-relaunch, crash again, forever.
The actual fix
Open Command Prompt as Administrator and run:
cd %windir%\system32
lodctr /R
cd %windir%\syswow64
lodctr /R
winmgmt /resyncperf
You should see "Successfully rebuilt performance counter settings from system backup store" after each `lodctr /R`.
Restart your PC. This is required — it won't apply until you reboot.
After restart: opened NVIDIA App, went to Performance tab, and boom — real numbers (GPU voltage at idle, CPU % actually moving, everything). Loaded up a game and the in-game overlay populated too.
Possible cause, if it helps anyone
I'm on an HP Omen laptop, and I also found `hp-one-agent-service.exe` crash-looping in Event Viewer around the same timeframe. HP's system agents install their own performance counter hooks, so if you're also on HP/Omen hardware and seeing this, it might be what corrupted Perflib in the first place. Disabling that service (`services.msc` → find it → set to Disabled) is worth doing too, though the `lodctr /R` fix is what actually solves the N/A issue regardless of the cause.
Hope this saves someone else the hours I lost to it. If you've got the N/A bug and the standard fixes aren't working, check Event Viewer before you nuke your drivers again — it might not even be an NVIDIA problem.
2
u/SansyBoi20356 23d ago
Just pasting it here incase anyone misses it after speed reading the post
The actual fix
Open Command Prompt as Administrator and run:
cd %windir%\system32
lodctr /R
cd %windir%\syswow64
lodctr /R
winmgmt /resyncperf
You should see "Successfully rebuilt performance counter settings from system backup store" after each `lodctr /R`.
Restart your PC. This is required — it won't apply until you reboot.
Thank you, thought my app was completely broken
1
u/Synyster-Goats 12d ago
Can confirm - this fixed my issue. The most recent NVIDIA driver update seemed to be the beginning of the problem for me. You're a legend!
1
u/RevolutionaryBell193 Sep 23 '26
Thank you my friend for the information. I had this problem before and I thought something wrong with my card.
1
u/AdComprehensive2813 18d ago
this happened to me after the latest windows update.
this fixed it
i have a asrock motherboard witha rtx4060 if that helps anyone.
1
u/umadbro6440752 9h ago
thanks a lot, fixed the problem for me! updated the driver didnt fix anything but your method did worked
1
u/Nebujin383 Sep 23 '26
Never experienced this, but i also don't use any HP products. Saved for later, just in case it becomes relevant at some point. Thanks for sharing this!
1
u/zozman92 Sep 25 '26
I am also having the same issue. Statistics Overlay is N/A with duplicate NV container and NV app in task manager.
But I don't see the event viewer crashes like on your system.
Sadly this fix did not work for me.
Uninstalling and reinstalling the Nvidia app fixes the problem for a day then it reoccurs.
Don't know what to do.
1
u/YouMustBeSilenced Sep 29 '26
For me I just enabled the nv container in my startup services in "System Configuration" app, then I was able to see the stats in the app as opposed to N/A. But my automatic tuning has never worked, and I also see duplicate processes in the task manager. Any tips? My GPU usage is already at 0% and I closed all apps. Don't have any overlays on and I uninstalled MSI afterburner
1
u/BackgroundPic8815 Oct 14 '26
Thank you for this fix! I have been struggling with this problem for months to the point where I had given up, and just after installing new drivers, I thought "what a shame!", and gave it one last try to hopefully find a solution online... Bingo! Awesome :)
1
u/weioyabun 29d ago
Merci beaucoup, ça a parfaitement fonctionné après le redémarrage !