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

Status
Not open for further replies.
Ah you beat me to my post. That's not quite what we want. Try these steps instead:

Open regedit, navigate to that key I posted above, then right-click on the "PowerSettings" folder in the left side and select Export.
 
Just to clarify too, both your XP and W7 installs using high performance plans both have 500 dpc spikes? And are those spikes from Nvidia or other things?
 
not using xp at all. its a suggestion because xp will have less power saving settings than 7. nvidia spikes at 500 no matter what.
 
They should be identical since these are the hardcoded defaults. I used diffmerge on my W10 just now to be sure, and they were the same. Do CurrentControlSet.
 
w7 cap wim, no power under currentrolset but have entries under controlset001 and 002, but there is this key
Code:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Power\User
, you want that?
 
Oh I think I misread your post originally. You're not pulling it from your live install, but rather from the WIM? Either method will be fine, I think even if you deleted the power plans the defaults still remain in the tree. But yeah on the WIM I guess you have to use controlset001 then once Windows is actually installed, it copies the keys to currentcontrolset?

edit: We don't want anything in Power\User, only Power\PowerSettings
 
its from an unmodded(default) eol updated wim, guaranteed all defaults. i can export a deployed but later today.
 
Code:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Power\PowerSettings
 

Attachments

  • w7-export v2a.reg
    636 KB
  • w7-export v2a.bat.TXT
    283.7 KB
Last edited:
This is what I posted the other day already :p

Look at that folder I uploaded for Clanger, inside is a Power_IdleStates.reg and it has both these keys and sets them to 100% on the high performance power plan. It doesn't fully eliminate CPU downclocking though, which is why I didn't include them in V1.0 of my optimized image guide, because there are relevant companion keys that still need to be discovered in order to fully stop the downclocks.
Ok will delete the post, must have missed it
 
Major Update #3:

The wife let me get back on my PC after errands yesterday, and so I spent a full 12 straight hours testing all the stuff in this thread that I didn't have time to do initially when people posted suggestions, or that I had put off because I had already messed with that kind of stuff in years past while tweaking and knew it probably wouldn't be the solution. At this point I have over 100 hours total sunk into this thread, and I have now tried everything suggested here, as well as every suggestion on Google. The TLDR is none of it helped, and some of it made things worse, including higher DPC, freezes, crashes, and system bricking.

I started to write up a full summary of every single thing I tested and my conclusions, but it was a LOT of text, and I'm not sure it's useful since the end result is it didn't fix anything. I guess if enough people want to hear about it then I'll go ahead and do it just for people interesting in learning about things and/or want more ideas of stuff they can research/test on their own. But otherwise at this point in time I'm confident it's an issue Microsoft/Nvidia need to fix. While we may find a workaround at some point, it's not a solution, a solution needs to come from them.

Please, please, please, if you are following this thread go file a support ticket with Nvidia and link to the thread, and file a report with Microsoft as well. Be sure to include your LatencyMon screenshots showing the bad DPC. Be prepared to deal with a lot of bullcrap such as them telling you to do things you've already tried, such as updating your bios, doing stupid crap like running sfc, and so forth. But hang in there and keep pressuring them. Also, go to all of your favorite gaming/benchmarking websites and send the editors a mail, so that we can get news coverage on this. It's the only way to get it fixed, as that's how every other major performance issue has received proper attention, such as the latest W11 22H2 performance bug where Microsoft made a mistake and then tried to ignore all the user reports, until a bunch of people got on Twitter and kept pinging Nvidia about it, so then Nvidia told Microsoft to get their act together and it got hotfixed by both companies.

I won't be adding more info to this thread unless someone comes up with something totally new to try, and instead I'm going to go back to working on my optimization todo list because that stuff I know for a fact will continue to improve the overall DPC and performance of the machine, since back in July when I first posted about this problem I was having Nvidia spikes of 800, now I'm down to 500 by time I finished v1.0 of my optimized image, and no DPC issues when the Nvidia driver is uninstalled. So at this point I'm triaging my time management to focus on stuff that I know I can get progress from. If I stumble upon a workaround I'll update this thread.

Good luck guys, keep fighting the good fight.
 
Last edited:
15 pages and we are back to square one, zip zilch squat kadingus nada and FoL.
Worth(mebbe?) carrying on with power plan settings and looking at setting gpu speed to a constant so it doesnt have to ramp up.
 
...Worth(mebbe?) carrying on with power plan settings and looking at setting gpu speed to a constant so it doesnt have to ramp up.
Yeah that's on my todo list for sure, outside of this Nvidia issue. I think there's still a lot of improvements to be gained in power plans, since so much of it is undocumented, it's just time consuming since there's 142 keys and figuring out what the ~60ish CPU keys do is difficult to say the least.
 
having a clean unmodded xp hipo plan for comparison would be helpfull.
Absolutely, if you or anyone else has an XP SP3 export of the Power\PowerSettings tree, that would go a long way in helping me figure it all out, in conjunction with comparing it to your W7 tree and my W10 tree.
 
Status
Not open for further replies.
Back
Top