Jump to content

They put out both a new windows update and nvidia driver and the issue is now kinda worse? it happens way more often, but instead of being black for like 2-3 seconds like before, my screen just flickers. the error is still listed as an open issue, but not sure if that is exactly the same thing or not. either way, this is a pain.

image.thumb.png.708946b924ac10df6b0bd4732108d21c.png

Link to post
Share on other sites

  • 2 weeks later...
1 hour ago, Bjoolz said:

If you have remove the bad storage and used DDU/reinstalled the OS, the next suspect is the GPU itself. 

yeah, had a bad hdd, replaced that with an ssd, issue is still there. DDU wiping and trying drivers didnt work either. currently backing everything up for a fresh windows install. praying its not the gpu but it is what it is i suppose.

Link to post
Share on other sites

  • 1 month later...

I have this issue too with RTX4090 combined with a Intel i9 13th gen. 

So far, all the "solutions" are basically just equivalent to "have you tried to turn it off and on again". Even the normal solution to do a full clean install of the Nvidia drivers with DDU just fixes it somewhat and then the problem returns. 

So far, it feels like this is primarily due to Windows 11 being stupid. Maybe some permission restrictions on files that need to access the system fully, but some nutjob at Microsoft programmed Windows to be stupid about it. 

There is no fix to this it seems, no one really seem to understand it or look at the core problem. This problem have existed since as far back as 2011 when searching for answers and still it persist.

People who experience this problem seem to go through every possible thing they can; getting a new GPU, getting the entire system reinstalled, clean install of nvidia drivers, changing registry, changing the voltage on the card, changing nvidia settings, changing windows to not download anything stupid and so on. 

There's no point in trying anymore since everyone is just hipfiring solutions and no one at Nvidia or Microsoft or anywhere else seems to look at why the freakin nvlddmkm file keeps failing like this. 

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

×