Discussion: NVIDIA Display Driver (nvlddmkm.sys) DPC Latency

Status
Not open for further replies.
Just to clarify though, did you run LatencyMon when the audio driver was uninstalled. What I mean is uninstall it, do not install any audio driver at all, and run the test. Do the problems disappear? There has to be a reason you're mentioning audio drivers, and that's what I'm trying to dial in on.
 
Hellbovine said:
Just to clarify though, did you run LatencyMon when the audio driver was uninstalled. What I mean is uninstall it, do not install any audio driver at all, and run the test. Do the problems disappear? There has to be a reason you're mentioning audio drivers, and that's what I'm trying to dial in on.
Click to expand...
Nope, the problem doesn't go away. As I wrote above, it goes away only when the graphics card driver is disabled. But, earlier, the ISR and DPC indicators at wdf01000.sys and nvlddmkm.sys they grew up when the audio driver was somehow involved. Right now, I've turned off everything that an audio driver can use, and ISR and DPC are growing exponentially
 
Ok I see. Yeah you are probably in the same situation that most of us are in. No issues until the Nvidia driver gets installed, and then suddenly things go haywire. All we can do is keep trying to find a fix, and sharing information until one of us figures it out.
 
Hellbovine said:
Ok I see. Yeah you are probably in the same situation that most of us are in. No issues until the Nvidia driver gets installed, and then suddenly things go haywire. All we can do is keep trying to find a fix, and sharing information until one of us figures it out.
Click to expand...

just been reading on another site, a post made back in 2021, someone was having pretty much the same issues. swapped the nvid card for an rx 470 ....and quote " I managed to find some time to switch in a rx 470 into my system. The stuttering is still there but it isn't because of the Nvidia drivers this time. Also the wdf0100.sys drivers are freaking out."

I think to my recollection, it is the first i've seen where it removes the nvidia driver completely from the equation. i may be wrong tho.
 
Oh, I forgot to mention it. The sound crunch appears even when you click on the sound icon on the taskbar. Or when trying to adjust the volume with the slider
 
When I first got started on this I had spent a full week just reading through forum after forum of these posts. The only thing that was always consistant between all of them was Nvidia graphics cards plus Windows 10 or W11. A lot of people didn't share their Windows versions and so I couldn't make any helpful judgements about that part of the equation unfortunately. I can say that according to Google's advanced searching for timestamps the issue is almost non-existant before the year 2015, which is when W10 first released. Then it started to appear and progressively worsened as time went on.
 
Hellbovine said:
When I first got started on this I had spent a full week just reading through forum after forum of these posts. And the only thing that was always consistant between all of them was Nvidia graphics cards plus Windows 10 or W11. A lot of people didn't share their Windows versions and so I couldn't make any helpful judgements about that part the equation. I can however say that according to Google's advanced searching looking for timestamps the issue is almost non-existant before the year 2015, which is when W10 first released. Then it started to appear and progressively appeared more and more often as time went on.
Click to expand...

give me a few days i know i got my rx 470 lying around somewhere, i can have a look, see if it is still here, give it a once over,see if it still works and do the lat test and post the results if that will help further.
 
Taosd said:
give me a few days i know i got my rx 470 lying around somewhere, i can have a look, see if it is still here, give it a once over,see if it still works and do the lat test and post the results if that will help further.
Click to expand...
I knew I was forgetting something important in that last reply. The other big thing I saw too, was that the hardware didn't matter. It ran the entire gamut, from 15 year old stuff to bleeding edge thousands of dollars machines. Even in this thread we have the whole range already now too. And the interesting takeaway there is that some of these graphics cards stopped being supported at different times and only receive security updates now, so they really aren't on the "latest" Nvidia driver anymore, and yet they are all having the same issue.
 
Last edited:
Hellbovine said:
some of these graphics cards stopped being supported at different times and only receive security updates now, so they really aren't on the "latest" Nvidia driver anymore, and yet they are all having the same issue.
Click to expand...
w7 x64 eol, gt710 driver 473.81(latest, 474.06 wont install). i repeat, nvidia either dont know how to fix it or they dont care. or its a mixture of both.
Fancy buying an electric car powered by nvidia? duck fat.
 
Last edited:
Hellbovine said:
I just knew I should have taken the time to Google this and investigate it before trying, but I decided against my better judgement and instead I quickly reviewed the keys and applied it. My system is now bricked.

Please delete this reg file for now so that nobody else accidentally ruins their Windows, until this can get sorted out. Mods if you are online please do this now so that we don't have other victims since this is time sensitive.

I don't think ZEFIR001 meant to harm anyone, as I have seen a few of these keys already and tried them out, individually, and it looked like this set of keys wouldn't be problematic, but this is just a great reminder of why we need to thoroughly research and test stuff before publishing it online.

...I'll be offline for a few days as I work on getting my info recovered.
Click to expand...
Hello again Hellbovine. Sorry for throwing you into troubles with my .reg . I never expected it to brick entire windows, since it only affects nvidia driver and usually when nvidia driver is broken or missing it shows code 43 on gpu in device manage. The windows should've load normally but without gpu driver if something goes wrong.
It looks like certain dwords deadly incompatible with some nvidia drivers. But applying them helped me and i no longer have the issue on 441.41 driver.
I read somewhere what source of spikes could be P-states managment by the driver,so i found a full list of Registry keys accessed under the nvlddmkm (Nvidia Display) service/driver path and start experimenting with especially ones that affect power managment.

Please let me know if you need them,i can post entire list of keys.
Just dont want to be banned if someone system is broken again.
 
ZEFIR001 said:
dont want to be banned if someone system is broken again.
Click to expand...
Not banned but politely encouraged to in the future add warnings that "this file may break a system, you use it at your own risk" or similar :)
Testing is what we do and bricked systems are part and parcel of that, we find what works and warn when something doesnt.
I saved the reg file incase i had to restore it and i have a test install that i dont care if it gets bricked.
 
My results after i fixed the issue.
Somehow my wdf01000 disappeared and no longer gives ISR counts xD
But ntoskrnl.exe came back even knowing i fixed it long time ago.
0:00 - Reboot and launch latencymon
01:00 - opened chrome,browsed some yt videos and refreshed tabs 5-8 times
01:40 - launched steam
02:00 - closed steam
02:05 - launched steam again and launched PUBG
02:05 - 13:00 - played PUBG on deathmatch
13:25 - closed the game
13:40 - closed steam
14:00 turned off latencymon
What tweaks i did the day i fixed nvlddmkm issue:
1. Came into HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PriorityControl
and created high interrupt priority dword for my GPU IRQ, in my case its IRQ54=1
2. Updated AMD chipset drivers and disabled PSP.11 right after that in device manager
3. Spread all interrupts using Microsoft Interrupt Affinity Tool - Changed my GPU mask from Core 4 to Core 6 since its less busy. Then i took all other devices except network adapter/usb/audio card in Microsoft Interrupt Affinity Tool and set them on Core 8 since its not busy at all.
4. Rebooted and still had nvlddmkm spike issue.
5. Found nvlddmkm windows breaking .reg keys and applied some of them.

Rebooted left latencymon for 1 min - opened chrome and steam,surprised no more nvlddmkm.
Left latencymon for 2h and keep using system for web surfing,no more nvlddmkm spikes.
 

Attachments

  • results.txt
    9.3 KB
  • Untitled.png
    Untitled.png
    40 KB
  • Untitled2.png
    Untitled2.png
    56.7 KB
Judging by my recent tests and the complete shutdown of absolutely any energy-saving functions that just came to my hand. My only problem remains only wdf01000.
 
ZEFIR001 said:
:cool: Dont be so mad. We can contact and ill try to help you for free. Of course if you dont mind i can accidentally destroy your entire windows haha.
Click to expand...
Dude, I'm so tired of all this that I'm going to throw my computer out the window soon. So I will be only glad if someone helps me.
 
Today me and glxxmybxy tried to fix his wdf01000 and nvlddmkm issues on his system but unfortunatelly didnt get to the great results.
First of all he use official windows build with a lot of things done wrong like using online microsoft account with windows hello services and other useless services enabled. He have a lot of different software installed like NZXT controll center etc. We tried to install 441.41 driver on his rtx 3090 but no success,even with INF modding it gives error 43. He tried to apply my deadly dword tweak on 527 driver and it didnt change anything.
We checked the IRQ conficts and other things,everything was setup fine,but his wdf01000 gives not thousands but millions of ISR's. So now im starting to think what 3rd party devices and usb peripherals could really impact wdf01000 and nvlddmkm like Hellbovine said.
In conclusion :
I did recommend him to clean install NTLITE windows build 22h2 by FR33THY and start installing drivers manually one by one.
We'll see how it goes,anyway every day we get closer and closer to solving this,step by step.
 
Status
Not open for further replies.
Back
Top