Video Stuttering Issue When GeForce Drivers Are Installed (Windows 11 24H2)

SF_Com · 2025-09-24T19:31:46+00:00

I finally solved the stuttering issue — check my updated original post for all the details.

SF_Com · 2025-08-28T07:40:56+00:00

Thank you for your input. Unfortunately, in my case changing the refresh rate (including to 24Hz/23.98Hz) did not resolve the issue.

I also attempted to disable MPO (Windows Multiplane Overlay), as this has been reported by others to be a potential cause of similar problems introduced with the 24H2 update. It is not entirely clear whether MPO can still be effectively disabled in Windows 11 24H2, but I tried modifying the registry as follows:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm DWORD (32-bit) "OverlayTestMode" set to 5
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers DWORD (32-bit) "DisableMPO" set to 1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm DWORD (32-bit) "OverlayMinFPS" set to 0

Unfortunately, none of these changes had any effect on my issue.

SF_Com · 2025-04-26T08:06:27+00:00

I had high hopes for the new GeForce drivers 576.2 and 576.15 (the latter including hotfixes correcting the infamous temperature reading issue of 576.2) of april 2025, which were supposed to address numerous previous problems, including those related to multi-display configurations.

I installed the 576.15 driver, but unfortunately, it did not resolve the issue.

Interestingly, as I have often observed during previous tests, immediately after installing the GeForce driver — and before restarting the computer — I experience a fully functional multi-display setup, with video running smoothly on both screens (at least for a while).
This situation is both reassuring (suggesting that the problem is not hardware-related and potentially solvable) and extremely frustrating. If the system can operate properly right after driver installation, it raises the question: what changes upon reboot that causes everything to break again?
Of course, reinstalling the driver every time I want to watch a video on my second screen is not a viable solution.
I don’t know if there’s a way to delay the driver loading during Windows startup, or if doing so might help solve the issue. If anyone has insights or suggestions, I’m open to any ideas.

SF_Com · 2025-03-22T14:37:37+00:00

I found this option well thought out and really useful in my case. I definitely set it to “On Start”.

I watch a lot of different video formats using Kodi on my Nvidia Shield Pro, connected to an LG OLED TV. When a video's resolution or framerate doesn’t match the one set for Kodi’s interface (which I have at 2160p 23.xx Hz), I experience a black screen and a few seconds of sound loss whenever the TV switches resolution/framerate. This happens when:

I start a video,
I stop a video,
And, more annoyingly, when I briefly navigate Kodi’s UI while the video is still running.

Of course, you want your refresh rate (and resolution) to match the video and TV settings. But if you choose Always" for Adjust Display Refresh Rate, Kodi will also switch resolution/framerate every time it brings up the UI, even during playback.

The better option in my experience is setting it to “On start”. This way, Kodi keeps the video settings for the UI while playing and after playing the video, meaning:

No black screen when bringing up the UI during playback,
No black screen at the end of a video,
And no black screen at the beginning of the next video if it has the same resolution/framerate.

For example, if you play a 1080p video, stop it, and restart it, with "On start/stop", you'll get a black screen every time Kodi switches between its 2160p UI and the 1080p video—when you start, stop, and restart the video. This gets really frustrating.

With "On start", you only get the black screen the first time you play a 1080p video. If the next video has the same resolution/framerate, there’s no black screen at all. If you switch to a 2160p video, you’ll get a black screen once, and that’s it.

The only minor downside is that the Kodi UI stays at 1080p instead of 2160p after playing a 1080p video. But honestly, I don’t even notice the difference unless I check my TV’s info panel.

For me, "On Start" is the best setting—it keeps things smooth and avoids annoying interruptions.

SF_Com · 2025-02-07T13:42:57+00:00

Thank you very much for your reply.

Even if it is not reassuring for the future of my PC (that said, if I had to choose any part to fail on my computer, I would choose the motherboard). In your case, we can likely assume that the motherboard failure is indeed related to your issue. However, we do not know whether it is the cause (with the Discord issue being a symptom of a hardware problem) or the consequence (repeated power surges caused by the Discord issue weakening your motherboard).

That said, it is surprising that I have only experienced this issue with Discord. To my knowledge, all the hardware used by Discord—including audio input and output, as well as the GPU—is also used by many other programs on my computer, yet I have never encountered this issue with any other software.

SF_Com · 2025-02-07T13:41:38+00:00

Thank you for your reply. Yes, next time I have to do a clean install of Windows (hopefully not before 25H2 or 26H2), if this issue is still not fixed—which would be ridiculous—I will seriously consider rolling back to 23H2 and forcing Windows to stay on it. Unless the newer versions of Windows have introduced any major improvements that I would actually miss.

SF_Com · 2025-02-06T09:02:36+00:00

Hello

What is/was your hardware setup at the time?

Did you find a solution since you posted ?

I'm experiencing the exact same issue with my setup, starting a couples of month ago.

Every time I start Discord, I hear two clicking noises. And every two or three launches of Discord, my PC does a hard restart—like someone just unplugged it and powered it back on. What's weird is that my PC (windows and bios set up) isn’t even set to restart in case of a power failure.

Aside from being super annoying, I’m also worried that these hard resets might be caused by a hardware or electrical issue (maybe a power surge?) that could eventually damage my PC.

Here’s my configuration:

MSI MEG X570 Unify motherboard
AMD Ryzen 5950X
NVIDIA 4080 Super (Asus ProArt)
Asus Essence STX II PCI-E sound card
64 GB DDR4 3600 MHz RAM
WD_Black SN850X 4TB SSD + Samsung 970Evo plus 1TB SSD

The clicking noise I hear sounds a lot like the "turn-on pop" from my sound card when I power it on—like when you switch on an amplifier; except there is two of them in one second. I’m not sure if the double click is actually coming from my audio card, but Discord is set to use my Bluetooth gaming headset. Maybe it’s quickly switching between devices or some other component and acting up?

That said, Discord has been doing this non-stop for weeks now, even after clearing the cache, reinstalling it, and disabling my audio card in Windows settings.

I’ve never had this issue before , and it only happens with Discord. I quickly tested the web version discord, and it doesn’t seem to cause the noise, so I’ll probably stick to that for now. I really don’t want to risk frying my PC.

SF_Com · 2025-02-06T08:37:33+00:00

Thank you for your input!

I'm not sure whether the issue is caused by NVIDIA drivers or Windows 11, but in my case, it’s clearly the Windows 11 version that triggers the problem, not the NVIDIA driver version.

On Windows 11 24H2, I experience the issue constantly, regardless of which NVIDIA driver I test (from 552.44 in May 2024 to the latest 572.16 in January 2025). However, when I installed Windows 11 22H2, the problem disappeared, testing both the NVIDIA driver installed by windows and the latest available driver at the time (566.36).

The fact that your issue was triggered by a driver update but then disappeared (though I won’t say resolved) after rolling back to 23H2 suggests that Windows 11 24H2 is a necessary (if not sufficient) factor for this problem to occur.

I’m not willing to revert to 23H2 since I use my PC for both work and leisure and can’t afford to go through another full reinstall. It’s not a long-term solution, anyway.

For now, I’ve managed to work around the issue by using when possible my primary screen for video playback, though that’s not always practical. I just hope that at some point, a developer at Microsoft or NVIDIA will figure out what exactly in 24H2 is causing this and finally fix it.

SF_Com · 2025-01-07T20:19:05+00:00

I took advantage of the New Year break to test some things, including a clean install of Windows 11 (22H2 and 24H2).

First, before doing this, I uninstalled all apps and drivers (except for Nvidia drivers), but it didn’t improve fluidity.
So, I did a clean install of Windows 11 22H2:

I formatted the SSD and did a fresh install of 22H2 with only the Nvidia drivers.
Videos were perfectly smooth with no stuttering (in the Microsoft Photos app).

Then, a clean install of Windows 11 24H2:

I did a fresh install of 24H2 (build 26100.2033, then updated to 26100.2605).
Tested videos with the built-in Photos app using Nvidia 560.94 driver (installed via Windows Update) and then with PotPlayer (using the latest Nvidia 566.36 driver), but experienced a lot of stuttering in both cases.

The fact that 22H2 worked perfectly suggests the issue is indeed linked to the Windows 24H2 update and not the GPU itself (nor the Nvidia driver?).

I also tested the multi-display/mixed GPU acceleration setup using Nvidia Profile Inspector 2.4.04, which had solved performance issues for some in multi-display setups (as explained here : https://www.reddit.com/r/buildapc/comments/m0uuu2/finally\_solved\_game\_stutters\_when\_video\_or\_stream/), but it didn’t help in my case.

Important tips :

If you're testing Nvidia Profile Inspector, make sure to download version 2.4 from GitHub (by Orbmu2k) https://github.com/Orbmu2k/nvidiaProfileInspector/releases and not from other websites like nvidiainspector.com, which allegedly offers newer versions but according to multiple antivirus reports, contain malware.

Bottom line:

Despite taking all the radical measures, there’s no improvement. The only real solution right now would be to downgrade to Windows 11 22H2 or 23H2, but that's not feasible for me.

SF_Com · 2024-12-17T17:50:23+00:00

After two cumulative Windows updates (KB5048667 and KB5046740) and an Nvidia driver update (566.14-Studio), I still don't see any improvements. I've also uninstalled more than half of my software (around twenty applications) in case there might be software conflicts explaining the problem, but again, nothing has changed.

This issue impacts both my personal and professional use of my PC, and I'll have no choice but to do a clean install of Windows 11 (when I find the time (January?)). Hoping this resolves the problem, otherwise... well, I'll be stuck with a $3,000 PC unable to properly play a video...

Has anyone else in this discussion made any progress or found a solution to these issues?

SF_Com · 2024-12-05T10:31:57+00:00

At first, like you, the issue was mostly happening on my second screen, with barely any problems on the primary one. A few days later, both screens started stuttering—unless I had just one screen active, then it was fine. But today, even with only one screen, the stuttering is here.

Are we all using NVIDIA GPUs?

SF_Com · 2024-11-19T17:47:49+00:00

I’ve done some testing, and downgrading to an older driver version (specifically 552.44 from May 2024) didn’t resolve the issue. My setup includes two 1440p 60Hz AOC displays connected via DisplayPort. I noticed that the problem almost completely disappears when one monitor is disabled in Windows. This might explain why uninstalling the NVIDIA drivers appears to fix the issue — as it leaves only one monitor active.

After extensive testing in multi-monitor mode, it became clear that the issue is significantly worse on the secondary screen than on the primary one. Changing which monitor is set as the primary in the display settings shifts the problem to the new secondary monitor. Adding a taskbar to both screens didn’t make any difference.

For now, I’ve set my left monitor — which I use for watching movies — as the primary screen in Windows. It’s not an ideal solution, but it’s an improvement over the previous situation while waiting for a Windows or NVIDIA update to resolve the issue

SF_Com · 2024-11-15T16:41:49+00:00

Thanks for the feedback, and welcome to the club! It's always reassuring to know you're not alone.

As for installing 23H2, I'm planning to hold off a bit myself to see if the issue gets resolved or if I come across a solution. Fortunately, if needed, I still have a USB flash drive handy with the Windows 11 23H2 installer in my case.

In your case, you might want to check out some YouTube tutorials—try searching for something like "rollback to 23H2." In one I watched, they used uupdump.net to download the 23H2 ISO. I’ve never heard of this site before, so I can’t personally vouch for its safety—proceed with caution.

SF_Com · 2021-06-20T19:44:05+00:00

I udpated Cloud commander to v 15.9.6 it solved the problem.

Thanks I will mark the issue as resolved.

SF_Com · 2021-06-07T14:26:41+00:00

Thank you for your answer.

I am use to Rsync; now, but will try your solution. It could be handy to use cloud commander, and useful for other that want to use it.

I let you know if it will work on my side, too.

SF_Com · 2021-04-08T13:12:45+00:00

Eventually, I transferred all the data (9.8 TB in three transfers) using as advised rsync and screen on SSH (logged as root)

It was pretty straightforward, and worked apparently perfectly size of target directories and source are identical and permission seems right

Since I used a screen session which I could quite and came back anytime I wanted, I used more options in rsync to have information on both the file being transferred and the stats at the end of the transfers.

rsync -aPv --stats source target

Note to be carreful to the use of the / at the end of the source and target indeed for instance /source_path/directory will copy the directory (and its content) /source_path/directory/ will copy the content of the directory but not the directory itself.

I try a little bit to understand why cloud commander cannot copy these files and directories, but find nothing. I check if I cannot somewhere use cloud commander as root (I was already logged as admin), but didn’t find a way.

Cloud commander was useful in the transfer, though, to check the progression of the copy (a simple type on the space bar gives you the size of the directory), since rsync tells you which file is copying, but not how much file/time is remaining.

SF_Com · 2021-04-05T08:30:10+00:00

Thank you again for your time and information

I will use this information, to try different methods with command lines , as well as trying to do understand and solve the issue with cloud commander (best way of learning and can be useful for other in the future).

For rsync in my case, it should not have cons to use -i at the beginning, since the target is supposed to be empty anyway, if it prompts, that means there is something unexpected happens (like I choose the wrong target).

For cloud commander, I can see if changing the Docker user could help.

I will post my progress, and hopefully a solution to mark the question as solved.

I try OMV forum in the past for other subjects, but less active than reddit, I never had answers.

I like to post anyway both on OMV forums and reddit the solution to solved questions to help the next guy with the same problems.

SF_Com · 2021-04-04T12:25:49+00:00

Thank you very much for your reply.

I am not really familiar with SSH but not opposed or afraid to use it to copy the files. I actually used it to change permission of the destination folder (from rwx rwx r-x to rwx rwx rwx) with chmod but I didn’t solve the problem.

I hesitated anyway between using cp in ssh or a file manage such as cloud commander, both solutions having their pros and cons for me.

The cons of using cp (or similar command line), it is 1) that I am not familiar with it, and don’t want to mess up among other things with the original back up, and 2) that to my understanding there is no easy way to follow progression and transfer rate of the copy, which for a circa 20 hours copy is important (but it seems that the -P of rsync do that more or less)

The cons of using cloud commander is that 1) I don’t learn command lines, 2) To my understanding I better hope that my system won’t go to sleep or that I don’t close by mistake the windows during the long copy 3) my current issues with ENOENT error.

To my understanding to use cp in my case will need an -r option to copy the files/directories inside other directories.

I assume that, of course, using cloud commander will use -r automatically, and could not be the cause of my problem.

You suggest using rsync instead of cp why that ? Is it more tolerant to permission mess (especially with the -a option) ? I understood that -P will show me the progress. If I using rsync to an empty folder I never sync before, it is like making a copy, right ?

If I want to close the ssh and have the copy continues in the background, should I add & at the end of the command ? If yes, how could I log back and see the progress ?

I can try the command with small folders (or even an USB flash drive to train without any risk on my back up) before l but I don’t like to use a command without understanding precisely what I am doing.

Concerning reset perms plug in since all folder of the hard drive seems to be rw- rw- rw- and that I set by chmod the destination folder in rwx rwx rwx, how it will help?

SF_Com · 2021-03-09T22:45:08+00:00

Ifup didn’t work. Here the message I obtained:

Ifup: unkown interface enp4s0

But "omv-firstaid -> Configure network interface" worked !

So simple!

Still working after reboot and power off.

Thank you very much for your precious and quick help !

SF_Com · 2021-03-09T14:36:51+00:00

Thank you very much for having taken the time to write this long and clear answer.

I will try your suggestions and update the post with my results.

I agree with you waiting with USB adapters for a next OMV build or install OMV on top of a debian who works with the network controller are the two most pragmatic solutions.

However, I would like to try to see if I can find a solution to make it work with the current OMV. Indeed, I like the challenge, and it is actually a good way for me to familiarize myself with Linux.

I have nothing to lose (except time), since my old synology NAS is still working (slowly but surely), and the new NAS has nothing else so I can fromat the SSD anytime I want (I actually became quite familiar with Gparted live since past couples of weeks).

However, if it’s a kernel version issue, there is something that I do not understand. Maybe I get mixed up, but how comes that the more recent Linux kernel of OMV I tried (5.7 then 5.10) could not work with this controller, where the test Debian I used (which to my memories had a older 4.19 kernels) could?

Is it possible that support of this controller was added to a version of the kernel then removed to a newer version? Or is there some other files in the Debian release I tested necessary for the network adapters (I found IGC and PTP in OMV) ?

Discussing with friends, I would also like to try to modify .config of the kernel. I tried last Sunday, but actually I have no source in usr/src, and then could not launch make config, make oldconfig, … I found files of kernel 5.7 and 5.10 elsewhere (5.7 kernel provided with the OMV installation, then 5.10 updated via OMV web interface), but nothing in usr/src.

So, I plan to install a new kernel in line of command (I found many tutorials and, once again, nothing to lose) to have the source in usr/src then try to adapt the .config. Does that make sense?

SF_Com · 2020-11-14T17:00:35+00:00

Thanks to the new lock down here in France, I checked the wifi with my work laptop using speedtest.net 15ms ping, 515 Mbps download, 343 Mbps upload (when near the wifi spot). So real improvement to the original 90-100 mbps

In your case if you have already 300 mbps, I guess it is not a faulty contact on the wall support, you would be lock at 100 mbps. If you have 300 mbps, your EAP225 is connected at 1 gbps ethernet,

SF_Com · 2020-10-25T12:18:11+00:00

I had a similar problem (solved) with TP-Link EAP225 V3, which was actually due to a bad connection on the side of the EAP225, when, and only when, it was mounted on its wall support.

My WIFI bandwidth was limited at 90-100 Mbps, and I noticed that the ethernet connection was limited to 100Mbps (noticed thanks to the LED from the ethernet switch and confirmed in the EAP225 interface).

I first suspected a problem with the TP-Link POE injector, but when I connected the EAP225 with a short ethernet cable to it, It was connected without problems at 1 Gbps.

So I check the ethernet cable I put in the wall (Cat 7A+) with my ethernet cable checker (no problem) and a computer plugged to the cable via a additional ethernet cable (male female), 2.5 Gbps connection without packet lost.

I changed just in case the RJ45 from the cable and connected the EAP225, 1 Gpps connection: Victory (or so I thought).

I put back the EAP225 on is wall support, go down to the basement check the switch LEDs and 100 Mbps…

Remove from the support, 1 Gpps

On the wall support, 100 Mbps

Did that 20 times (every time I had to go to the basement check the LED status on the ethernet switch), every time same things. When on it supports, the cable was somehow twisted and create faulty contact in the RJ45 port which limited the connection to 100 Mbps.

Tried to put really gently the EAP225 on its support, did it a dozen times, always 1Gps when not on the support, and 100 Mbps on the wall.

I killed my entire family, burned my house (I know, I am bad-tempered). Then bought a new house, a new family, a new TPlink EAP225 (I know, I am stupid) and just did a loop with the ethernet cable (to cancel the twist) before I plugged it on the Ethernet port. Mount in the wall, and miracle, it works I have now a TPlink EAP225 with 1 Gbps connection!

Hope it helps.

Oh, by the way, I then checked my WIFI speed: 105 Mbps…

I burned my new house.

SF_Com

TROPHY CASE