Jump to content

I’ve been plagued by flickering screens and been unable to playback video or work in DaVinci Resolve at all without everything freezing, stuttering and bugging out (often accompanied by a windows log mentioning nvlddmkm, but not every time). 
 

For months now, I’ve been waiting for the Nvidia drivers to deal with this and solve it. All while commentators on the issues on YouTube keep talking back and forth about how it’s fixed and then it’s not fixed and now it’s hotfixed but not really and there’s no clear indication on when the issues are actually fixed.

 

The issues seem to relate to some combo of Windows 11 updates, together with the Nvidia updates, together with some relation to the BIOS. But who knows? It seems everyone, including the companies themselves seem to be just shooting in the dark on this issue. 
 

I’ve been holding my Windows 11 updates (24H2) from updating ever since I first encountered this issue by updating to it and the new Nividia drivers back in January. But even reverting back to what’s supposed to work, the issues persist (though not in the same intensity), even if I did clean installs of everything. So even trying to stay away from the recent BS these companies push out by reverting back doesn’t work if you ever touched the new updates.

 

And it seems that many have these issues, but it’s still not talked about enough. I can’t work with my computer anymore and new games are a coin toss if they work or not. The recent “The Alters” seems to work but some parts flickers a lot and after closing down, the OS starts to bug out requiring a restart.

 

So when is all this going to get fixed? And when will people figure out exactly what the damn problem is instead of just guessing?
 

Linus group should definitely make an investigation video into this. It’s for worse than whatever pricing the 5060 has and how bad Nvidia is with the new cards or whatever the trending topic is. If the 40-cards can’t even work anymore due to these drivers, then we need this problem to be more visible and pressure Nvidia to fix it. Who cares about the 50-cards when we have more people with 40-cards and these issues.

Link to post
Share on other sites

Not to say there isn't any problem, the thing is for most people in most things it is fine. I use regularly use Resolve on two systems, older and newer. Always latest Nvidia driver, no problems at all with Resolve or games. It sucks if you have the combination of hardware, OS, software, drivers and who knows what else that means you have problems, but it isn't everyone.

Gaming system: R7 7800X3D, Asus ROG Strix B650E-F Gaming Wifi, Thermalright Phantom Spirit 120 SE ARGB, Corsair Vengeance 2x 32GB 6000C30, MSI Ventus 3x OC RTX 5070 Ti, MSI MPG A850G, Fractal Design North, Samsung 990 Pro 2TB, Alienware AW3225QF (32" 240 Hz OLED)
Productivity system: i9-7980XE, Asus X299 TUF mark 2, Noctua D15, 64GB ram (mixed), RTX 4070 FE, NZXT E850, GameMax Abyss, Samsung 980 Pro 2TB, iiyama ProLite XU2793QSU-B6 (27" 1440p 100 Hz)
Gaming laptop: Lenovo Legion 5, 5800H, RTX 3070, Kingston DDR4 3200C22 2x16GB 2Rx8, Kingston Fury Renegade 1TB + Crucial P1 1TB SSD, 165 Hz IPS 1080p G-Sync Compatible

Link to post
Share on other sites

My4070 laptop has really old drivers and zero issues (around version 550, can't check right now). Also my 5070 desktop has 572.83 drivers and little to no issues, ie yeah there are issues but with older drivers it can mostly be "fixed".

The direction tells you... the direction

-Scott Manley, 2021

 

Softwares used:

Corsair Link (Anime Edition) 

MSI Afterburner 

OpenRGB

Lively Wallpaper 

OBS Studio

Shutter Encoder

Avidemux

FSResizer

Audacity 

VLC

WMP

GIMP

HWiNFO64

Paint

3D Paint

GitHub Desktop 

Superposition 

Prime95

Aida64

GPUZ

CPUZ

Generic Logviewer

 

 

 

Link to post
Share on other sites

1 hour ago, Glazarus said:

The issues seem to relate to some combo of Windows 11 updates

Unlikely cause newer NV drivers also show massive issues on my very old (22h2 iirc) windows 10 install. 

 

 

1 hour ago, Glazarus said:

And when will people figure out exactly what the damn problem is instead of just guessing?

While this is speculation it seems pretty obvious the culprit is the new "app" in combination with support for newer framegen implementations, cause it all literally started when the new app was released and the old "geforce experience" was "deprecated"...

 

Ie it may never be fixed, see AMD drivers since they sold/deprecated"ATi" ... they never worked right since... ("AMD driver has crashed"... again and again...)

The direction tells you... the direction

-Scott Manley, 2021

 

Softwares used:

Corsair Link (Anime Edition) 

MSI Afterburner 

OpenRGB

Lively Wallpaper 

OBS Studio

Shutter Encoder

Avidemux

FSResizer

Audacity 

VLC

WMP

GIMP

HWiNFO64

Paint

3D Paint

GitHub Desktop 

Superposition 

Prime95

Aida64

GPUZ

CPUZ

Generic Logviewer

 

 

 

Link to post
Share on other sites

Go back to 560 or before and its fine. 

 

Make sure to ddu the driver.

 

Its a mess and i have to deal with it a lot with architecture firms atm. Gpo policies deployed to prevent any auto update and all. Its a mess but older drivers are solid still

Link to post
Share on other sites

2 hours ago, Glazarus said:

.

not sure if this helps but on my latest rollback from 566.36 it borked and i ddu'd into the newest drivers and everything works perfectly (for now), make sure to ddu, treat before and after 566 as completely different drivers.

5950x 1.33v 5.05 4.5 88C 195w ll R20 12k ll drp4 ll x570 dark hero ll gskill 4x8gb 3666 14-14-14-32-320-24-2T (zen trfc)  1.45v 45C 1.15v soc ll 6950xt gaming x trio 325w 60C ll samsung 970 500gb nvme os ll sandisk 4tb ssd ll 6x nf12/14 ippc fans ll tt gt10 case ll evga g2 1300w ll w10 pro ll 34GN850B ll AW3423DW

 

9900k 1.36v 5.1avx 4.9ring 85C 195w (daily) 1.02v 4.3ghz 80w 50C R20 temps score=5500 ll D15 ll Z390 taichi ult 1.60 bios ll gskill 4x8gb 14-14-14-30-280-20 ddr3666bdie 1.45v 45C 1.22sa/1.18 io  ll EVGA 30 non90 tie ftw3 1920//10000 0.85v 300w 71C ll  6x nf14 ippc 2000rpm ll 500gb nvme 970 evo ll l sandisk 4tb sata ssd +4tb exssd backup ll 2x 500gb samsung 970 evo raid 0 llCorsair graphite 780T ll EVGA P2 1200w ll w10p ll NEC PA241w ll pa32ucg-k

 

prebuilt 5800 stock ll 2x8gb ddr4 cl17 3466 ll oem 3080 0.85v 1890//10000 290w 74C ll 27gl850b ll pa272w ll w11

 

Link to post
Share on other sites

58 minutes ago, jaslion said:

Go back to 560 or before and its fine. 

 

11 minutes ago, xg32 said:

not sure if this helps but on my latest rollback from 566.36


As I mentioned, reverting back doesn’t help, it only mitigates the worst of it in games and web videos, but Resolve always fail. I can’t even use it for editing audio files.  
 

And I’m always using DDU, it doesn’t matter.

 

1 hour ago, Mark Kaine said:

While this is speculation it seems pretty obvious the culprit is the new "app" in combination with support for newer framegen implementations, cause it all literally started when the new app was released and the old "geforce experience" was "deprecated"...

 

Ie it may never be fixed, see AMD drivers since they sold/deprecated"ATi" ... they never worked right since... ("AMD driver has crashed"... again and again...)


Yes, that’s a theory I also had, but reverting that as well doesn’t help.

 

Since Resolve and Chrome uses hardware acceleration, people have suggested turning that off, but that makes the whole point of using Resolve pointless. However, it does hint at something relating to the errors.

 

What I’ve discovered in games is that the flickering often happen when using in-game menus or cut scenes or things that are more related to graphical elements. It may be that it’s about how such graphics render and that there’s an error on how the CPU, BIOS and GPU handle frames of such elements.
 

That there’s been so much focus on AI enhanced features that it has affected handling of graphical elements to trigger TLD type errors or similar, causing the GPU to lag out.

 

The main problem is however that Nvidia, Microsoft and motherboard manufacturers seem to not speak to each other to solve this. They need to prioritize this error since they’re about to tank Nvidia as the reliable choice for professionals. Game devs and people working in that industry rely on Nvidia as the stable work horse for their work, so it’s vital that they gain back the trust here. If I didn’t have a MacBook as a backup for working with Resolve, I would have had to buy an entirely new workstation because I cannot spend months trying to figure something out that Nvidia and Microsoft doesn’t seem to prioritize at all. 
 

I even had my processor replaced to avoid the Intel problems as a source for these issues and the problems just carried over into that change.
 

Link to post
Share on other sites

If you're looking for stability in productivity apps, have you tried switching to the Studio drivers? Those are supposed to be more stable, and while they lack optimizations for newer games, so tend to come with a minor performance hit, you can still game with them.

Link to post
Share on other sites

2 hours ago, Glazarus said:

As I mentioned, reverting back doesn’t help, it only mitigates the worst of it in games and web videos, but Resolve always fail.

Yeah, but tbf they said before 560,which is also my experience as said (it's a custom Asus driver even and the GPU works great!)... Gotta try until you find the right one as dumb as it sounds (so around 500 to 556 maybe) I agree with the rest of your post but as for now we gotta use those workarounds, also as suggested studio drivers in general should be more stable.

 

 

Otherwise there may be an actual issue with your hw or sw,  because afaik resolve works - except some hw/sw combinations apparently.

The direction tells you... the direction

-Scott Manley, 2021

 

Softwares used:

Corsair Link (Anime Edition) 

MSI Afterburner 

OpenRGB

Lively Wallpaper 

OBS Studio

Shutter Encoder

Avidemux

FSResizer

Audacity 

VLC

WMP

GIMP

HWiNFO64

Paint

3D Paint

GitHub Desktop 

Superposition 

Prime95

Aida64

GPUZ

CPUZ

Generic Logviewer

 

 

 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×