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

Status
Not open for further replies.
Maybe this is one of the great unknowns seeing that we are not the only ones trying to actually isolate and see what is the pure specific cause of it.

The only thing i can honestly think of is either a) stop overclocking, (it aint good for your hardware anyway) , b) do whatever you can to minimalise it, be it reg fixes or whatever and unfortunately, until the experts ( not looking at microsoft and nvidia, don't think they can spell expert ) fix it, or c ) try and put up with it for as long as you can ( i know, there is a global cost crisis going on and not everyone can go buying whole new systems ) . I do feel sorry for those who are having the issue and are losing faith in their beloved systems, but it isnt the hardwares fault ( i hope ) , and it isnt yours.

Maybe we keep this open so if eventually something miraculous happens, it can be a shining light for all who need it
 
Taosd said:
( i know, there is a global cost crisis going on and not everyone can go buying whole new systems )
Click to expand...
To be fair, I've just completed my brand new PC build. My previous one wasn't outdated by any means (Z490 + 10900K) but I felt like upgrading because I really liked the latest improvements that finally after a quite long time are real generational upgrades. My previous build didn't have any latency issues, this one is just terrible. So building a new system could just as easily get you into this horrible game as out of it.
 
Clanger said:
i dont think there is an answer for this, how many forums is this problem on? i mean if forums havnt found the answer by now they never will.
when ive tried something and it looks like ive got an improvement then bam it spikes back over 500 again.
Click to expand...
There are answers, it's just that there isn't a global answer that works for everyone affected. Especially if you look through forums what you'll notice is that everybody who reports their issue fixed always points to a different fix that worked out for them. Not to mention how many different flavors are to this issue as well depending on what's the major cause of the latency issues. I think we just need to accept that for the computer hardware and software manufacturers, latency became one of the abandoned hostages they simply don't care about freeing for now.
 
Last edited:
Taosd said:
Maybe this is one of the great unknowns seeing that we are not the only ones trying to actually isolate and see what is the pure specific cause of it.

The only thing i can honestly think of is either a) stop overclocking, (it aint good for your hardware anyway) , b) do whatever you can to minimalise it, be it reg fixes or whatever and unfortunately, until the experts ( not looking at microsoft and nvidia, don't think they can spell expert ) fix it, or c ) try and put up with it for as long as you can ( i know, there is a global cost crisis going on and not everyone can go buying whole new systems ) . I do feel sorry for those who are having the issue and are losing faith in their beloved systems, but it isnt the hardwares fault ( i hope ) , and it isnt yours.

Maybe we keep this open so if eventually something miraculous happens, it can be a shining light for all who need it
Click to expand...
Overclocking...... can't stop won't stop. It's how my computer still has great life in it and if done properly it will work for a long time. It's been overclocked for over 5 years and still plugging away

To someone not experienced in it yes it can ruin your parts.
 
We shouldn't get too discouraged at the slow progress, this is just a very complicated bug and we can all be quite proud of ourselves once a solution is reached, because we'll have solved something that Google hasn't been capable of in many years. I'm sure Nvidia must do *some* sort of DPC testing, even if it's just Bob the peon engineer who checks drivers to make sure they don't crash machines. The hard part for employees like Bob is getting someone in a position of power to acknowledge and then address it (been there done that).

I don't believe in the theory that because nobody else has found a fix that we can't find one here. I've disproven these sentiments in my own tweaking many times now. This bug is tough, and I think the solution for this particular bug is to keep working at it until we draw the attention of someone that has clout in the industry. If for example, AnandTech, LinusTechTips, or any other big tech site goes through this thread and writes an article, then all the other sites will regurgitate it, drawing Microsoft/Nvidia's attention in the process (historically this is how many bugs like these are fixed). I'd also recommend contacting some YouTubers, such as Chris Titus who is the one responsible for how popular the NTLite GamerOS thread has been, since he promoted it on his channel.

WORKS IN PROGRESS
Currently I've been trying to figure out why the interrupt tool doesn't work reliably. I talk about that in my recent posts for anyone that missed it. The TLDR is Microsoft discontinued this tool many years ago and I think that's why it's not working reliably and results cannot be replicated, because the operating system changed in how it handles this stuff. My GPU for example ignores any mask I set.

The other thing I worked on recently was trying qou's post. It seems like a lot of people didn't realize what he posted, but he's saying he fixed the issue, and even provided screenshots as well as his tweaks. Now I just need to figure out *which* of his 1,000+ tweaks is responsible for it. I already tried applying his entire .reg file, and no change in DPC, so that's not it, which means the fix has to be in NTLite from his XML preset. This part I could *really* use help on, because it takes a long time to check this since processing big presets like these are time consuming and this isn't the only project I'm working on at the moment too, so it's a juggling act of time management each day.

What may be faster than using quo's preset by itself, is to use NTLite's built-in presets to compare with. What I'd like to do for example, is take a W10 21H2 default ISO and then create 4 images using the 4 built-in NTLite presets, and then see which one(s) have fixed DPC, and diffmerge compare those XML files to eliminate all of the common components, leaving only the possible culprits behind. Then it would be much faster to test the remaining components until the offender is discovered. But, again this is stuff I could use help on, since it's so time consuming to process images, copy it all to a USB, reinstall Windows, etcetera. Before anyone inquires, a VM is not recommended, as Windows behaves much differently in a VM than it does on a real install.

I still want to pursue some of my own ideas too, but I haven't had time since I've been spending all my freetime working on the suggestions in this thread. Power plans are what I'm most interested in personally, as well as properly turning off more background activity of the operating system through the registry.

I haven't touched standbylist cleaner yet, but I have put lots of testing and research into timer resolutions and also HPET stuff, but I don't want to play with timer/HPET stuff anymore right now, as they are too greatly misunderstood and it warrants a whole thread of its own.

To summarize, if there's anyone that wants to help, but isn't sure how, you could contribute to a potential solution by looking into the xml preset stuff I talk about in the spoiler. I want to give up on this bug, but at this point my curiosity has piqued so high I just need to know what is responsible for the issue so I can sleep at night.
 
Titus is a member i think. yeah and you are right, the more its talked about the more nvidia/ms will get their s--t together and fix these things once and for fikken all.
 
Made a clean 21H2 Home image using qou's preset, but without the reg file. Can't get past Windows Setup, while the keyboard works if you press shift+F10 and can type in the command prompt, it won't let you type a name into the create a user screen. Ease of access is nuked so you can't use on-screen keyboard, can't talk to Cortana either. I don't really have time to troubleshoot 1,000 tweaks and removals to figure out the cause. So unless someone else wants to try, or can identify the cause of this, I'm moving on and leaving this potential solution behind.
 
Last edited:
Hellbovine said:
Made a clean 21H2 Home image using qou's preset, but without the reg file. Can't get past Windows Setup, while the keyboard works if you press shift+F10 and can type in the command prompt, it won't let you type a name into the create a user screen. Ease of access is nuked so you can't use on-screen keyboard, can't talk to Cortana either. I don't really have time to troubleshoot 1,000 tweaks and removals to figure out the cause. So unless someone else wants to try, or can identify the cause of this, I'm moving on and leaving this potential solution behind.
Click to expand...
I never encountered it since I'm using the unattended section to create a user.
 
qou said:
I never encountered it since I'm using the unattended section to create a user.
Click to expand...
I imported the preset as-is and didn't change anything, so the unattend stuff was still there. But, it could be that it's because you used ltsc and I'm using Home maybe? I can try to download an ltsc image later and try again. I don't have a license key for it, but that shouldn't be a problem to get it installed for simple testing. I haven't spent a lot of time importing people's presets, so I just don't know how to troubleshoot them yet.
 
Last edited:
Try to remove the user and create a new one, I edited the user section since it used a password, maybe it's what caused the typing issue.
 
Hi, i experience the same issues and the results of LatencyMon finally brought me to this Forum.
I guess i tried pretty much anything possible. Finally i were about to buy a new audio interface and reinstall my OS.

But then i remembered that the problems eventually started after updating my NVIDIA display driver.
So i downgraded to an older driver (4.72.84), which fixed it immediately.

Besides that, the only other thing that introduced a noticeable improvement was this:
https://www.ntlite.com/community/in...iver-nvlddmkm-sys-dpc-latency.2924/post-31425
That registry hack removed the massive spikes for me, and the overall DPC values came down a bit.
 
NetAndif said:
Hi, i experience the same issues and the results of LatencyMon finally brought me to this Forum.
I guess i tried pretty much anything possible. Finally i were about to buy a new audio interface and reinstall my OS.

But then i remembered that the problems eventually started after updating my NVIDIA display driver.
So i downgraded to an older driver (4.72.84), which fixed it immediately.

Besides that, the only other thing that introduced a noticeable improvement was this:
https://www.ntlite.com/community/in...iver-nvlddmkm-sys-dpc-latency.2924/post-31425
That registry hack removed the massive spikes for me, and the overall DPC values came down a bit.
Click to expand...
I've also had success with an old Nvidia driver - the registry hack did nothing for me, though. I'm still having occasional high spikes although they're no longer present as audio popping/crackling. Nvidia still produces the highest spikes but I get some crazy ones that are not related to any drivers seemingly. So in medical terms, the symptoms are currently treated but this is far from being solved.
 
Well, i have narrowed it down to driver version 516.94, which introduces the issue.
With version 512.95, everything is alright.
So did anyone already post this in the NVIDIA forums?
 
Last edited:
NetAndif said:
Well, i have narrowed it down to driver version 516.94, which introduces the issue.
With version 512.95, everything is alright.
So did anyone already post this in the NVIDIA forums?
Click to expand...
Reddit is where I see if I should upgrade drivers or not. They have good testing there showing gains or losses
 
Status
Not open for further replies.
Back
Top