Overclock.net › Forums › Graphics Cards › NVIDIA › NVIDIA Drivers and Overclocking Software › Ongoing Pascal latency problems - Hotfix doesn't work for everyone.
New Posts  All Forums:Forum Nav:

Ongoing Pascal latency problems - Hotfix doesn't work for everyone. - Page 30

post #291 of 1679
Quote:
Originally Posted by jprovido View Post



is this bad? it's saying it IS having problems

Even at max Load I'd say it's bad, if that's Idle you got it worse than me.
post #292 of 1679
Quote:
Originally Posted by mark_thaddeus View Post

Has anyone tried going to Nvidia Control Panel then under Adjust Image Settings with preview tick on --- Use my preference emphasizing: PERFORMANCE

This cut my latency spikes to about a third. Also use latencymon instead of dpc latency checker, it's more accurate.

I didn't bother to read through the entire thread so apologies if this has been mentioned and tried. biggrin.gif


There are other steps to reduce / eliminate latency (at least for win 7)

https://www.native-instruments.com/forum/threads/solved-dropouts-cracks-pops-on-windows-7-and-nvidia-gfx-card.126080/


To disable the PowerMizer, here's what you have to do:

(You may want to back up your registry first)

1.Open up Regedit and go to

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\********\0000\
The *'s will be random numbers. There will be a few of them, pick the "0000" folder with the most keys in it.

2.Create the 4 Powermizer keys (these will all be DWORD):

PerfLevelSrc
PowerMizerEnable
PowermizerLevel
PowermizerLevelAC

3.Change the values (double click on them) to:

PerfLevelSrc 3322
PowerMizerEnable 0
PowermizerLevel 1
PowermizerLevelAC 1

4.Reboot and Powermizer will be disabled!


This reduced latency to 0.2-0.3 ms!

Powermizer is a laptop thing. How does that affect desktop GPUs?
post #293 of 1679
Quote:
Originally Posted by Dargonplay View Post

Even at max Load I'd say it's bad, if that's Idle you got it worse than me.

I've been hearing sudden "cracks/pop" listening to music/spotify once in a while but aside from that everything is perfect

edit:

at full load it says "no problem" with latencymon. I'm only having latency problems at idle
Edited by jprovido - 7/15/16 at 9:35pm
post #294 of 1679
Quote:
Originally Posted by jprovido View Post

I've been hearing sudden "cracks/pop" listening to music/spotify once in a while but aside from that everything is perfect

Yes, if those are idle readings then you will have audio problems and worse game stuttering.

I updated the OP so people can easily understand their readings with LatencyMon.
post #295 of 1679
Quote:
Originally Posted by Dargonplay View Post

Yes, if those are idle readings then you will have audio problems and worse game stuttering.

I updated the OP so people can easily understand their readings with LatencyMon.

tried heaven running in the background with latencymon. It says no problem at full load.

edit:

nvm after a few more minutes it showed the same message. it's better at full load though compared to idle
Edited by jprovido - 7/15/16 at 9:39pm
post #296 of 1679
Quote:
Originally Posted by jprovido View Post

tried heaven running in the background with latencymon. It says no problem at full load.

edit:

nvm after a few more minutes it showed the same message. it's better at full load tho

Update your post with a screenshot please, I've been hearing people say their DPC latency decrease on load when they have this issue with Pascal.
post #297 of 1679
So much misinformation in this thread doh.gif

Over 100uS current Interrupt to DPC latency is BAD. In fact, over 50uS is not good either. Though it is certainly not unacceptable.

This is how a system should be at idle:
LatencyMon Idle Usage!

Remember, a 1000Hz mouse relies on your system being able to process the input every 1ms, aka every 1000uS.

If you have regular levels above about 100uS or that bounce all over the place and get spikes you're going to be introducing jitter and stutters not only on your mouse movement's update rate but jitter and stutter on your on your audio and video rendering and presentation chain.

Then end result is a massive degradation in system FLUIDITY (kind of like what using vsync does but with your mouse and audio).

It will make tracking targets harder and screw up your aim. You may realistically not NOTICE it happening, but it IS still happening, and once you fix it you will then notice how it ISN'T happening. smile.gif

The same issues is described here where other factors negatively influence a mouse's polling rate, except the cause here is primarily from something else:
http://www.blurbusters.com/faq/mouse-guide/


I've made a few half-assed guides on lowering overall Interrupt (DPC/ISR) latency. Including those 500uS+ spikes from Nvidia drivers..
Some of it is in this thread. It's incomplete as hell though: http://forums.guru3d.com/showthread.php?s=05b8aa692c06608317d3a63235d17495&t=406260

You may not be able to get rid of them entirely, but you can certainly reduce their frequency significantly! biggrin.gif I may only get a spike every few minutes now.

My average idle DPC latency is 2uS

Work towards this idle usage:



I also don't need to disable TONS of power saving features and idle at 200watts to do this, I idle at 46w and have most power saving features enabled actually. You should disable C1E for sure though, and experiment with disabling C6/C7 states. Use the high performance power profile and set processor minimum frequency to 100% in power options. If your system is configured correctly you will have 0.1 to 0.7w idle power increase from doing that. thumb.gif
I recommend keeping Nvidia power usage at optimized (NOT adaptive) instead of max performance, in all my testing it works flawlessly at lowering idle power usage without causing problems during load like balanced does. It's as if Nvidia knows what they're doing. tongue.gif

Depending on your system and mouse's performance, your polling rate might be all over the place, varying wildly from 400-1600Hz and causing major spikes. You can test your mouse's performance with Mouse Movement Recorder in the MarkC Mouse Fix:

If anyone needs help or advice on optimizing DPC latency let me know, I spend about 30 hours a week on teamviewer helping people for fun. smile.gif

EDIT About DPC latency under load! I understand that is important too. However, if you've lowered the idle DPC latency to the absolute minimum your system can physically achieve, you have already done 95% of what you can do to lower the load DPC latency to IT'S minimum. smile.gif
Edited by cookieboyeli - 10/16/16 at 5:43pm
post #298 of 1679
Wait you have a few half-assed guides too?? You mean to tell me r0ach isn't the only one making these guides? bigeyedsmiley.png
post #299 of 1679
There are many placebowill kings here at ocn. biggrin.gif
post #300 of 1679
Quote:
Originally Posted by magnek View Post

Wait you have a few half-assed guides too?? You mean to tell me r0ach isn't the only one making these guides? bigeyedsmiley.png
R0ach has "a bit" of a problem with the placebo effect. redface.gif I don't.

He is right about disabling system components that are not in use though, like the 1394 controller and on board audio if you don't use it etc.

As for the HPET, the answer is always in debate because there is LITERALLY NO CORRECT ANSWER! It depends on your motherboard's implementation of the feature and your OS. As a general rule if your system is low end or older than Nalhelm I'd recommend disabling it in bios and/or device manger, if not, let it stay enabled. Running this as admin will delete preferences for or against HPET, thus letting your choices in the hardware to enable/disable and the software running decide what to do:
Code:
bcdedit /deletevalue useplatformclock
HPET isn't the only clocksource available on your system. Another timer called TSC exists and in many cases beats HPET by a factor of 100x, but that may be only when multiple processes running on different cores are calling it...

Here is a snippet of information I found on it: https://www.quora.com/Linux-Kernel-What-are-the-advantages-and-disadvantages-of-TSC-and-HPET-as-a-clocksource


So again, there is no yes or no answer. The best way to find the answer is to simply mess with it and test. smile.gif I find that a lot quicker than arguing about it!

My findings are it NEEDS to be disabled on my old Athlon II X4 machine, and hurts nothing at all being enabled on my Z97 Haswell. (Still testing this though)


I'm simply optimizing for all system performance, some of the stuff in the guide isn't going to help DPC latency at all, but it should still be done.

Updated my post to include the guide. Rereading it a few months later there is actually a few things I now disagree with! biggrin.gif Like Perfmonitor2 being useful. I don't think it is anymore and I've stopped using it. Process Explorer is much better for that task.
Edited by cookieboyeli - 7/15/16 at 11:22pm
New Posts  All Forums:Forum Nav:
  Return Home
Overclock.net › Forums › Graphics Cards › NVIDIA › NVIDIA Drivers and Overclocking Software › Ongoing Pascal latency problems - Hotfix doesn't work for everyone.