Nvidia windows kernel mode driver dpc latency

Sysnative Forums

  • Microsoft Support & Malware Removal

  • Windows 10

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

NVIDIA Windows Kernel Module Driver high latency causing in game microstutter.

  • Thread starter
    Thread starter

    nevermore15

  • Start date
    Start date

Joined
Feb 20, 2021
Posts
29




  • #1

Hi there, I’ve been having issues for around 4 months where all my videogames stutter and micro stutter to some degree. It’s been really frustrating and I hope that one of y’all can help. I’ve tried countless guides and I’ve even gone to Microcenter to have the techs look at it just for them to tell me that there’s nothing that they can do. I used latency mon and I’ve attatched the results. Sorry if something in my post is wrong. I’m not too experienced with this stuff. It seems that its mostly the NVIDIA Kernel Driver during gaming, and the Network driver interface specification during normal use. Please let me know if I need to post more information I just want to get this over with.

Specs: ASUS ROG B450F Gaming II
Zotac RTX 3070
Ryzen 3600x
16gb corsair vengeance white 3200mhz
500gb Nvme m.2 WD black
2tb WD Hard Drive
750 watt PSU

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:02:14 (h:mm:ss) on all processors.

_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-ITVKR7D
OS version: Windows 10, 10.0, version 2009, build: 19042 (x64)
Hardware: System Product Name, System manufacturer
CPU: AuthenticAMD AMD Ryzen 5 3600X 6-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 16294 MB total

_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 380 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes
the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 796.10
Average measured interrupt to process latency (µs): 7.373617

Highest measured interrupt to DPC latency (µs): 791.90
Average measured interrupt to DPC latency (µs): 3.786315

_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 117.050
Driver with highest ISR routine execution time: HDAudBus.sys — High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0.005037
Driver with highest ISR total time: Wdf01000.sys — Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0.007531

ISR count (execution time <250 µs): 105312
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0

_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 947.220
Driver with highest DPC routine execution time: nvlddmkm.sys — NVIDIA Windows Kernel Mode Driver, Version 461.40 , NVIDIA Corporation

Highest reported total DPC routine time (%): 0.556803
Driver with highest DPC total execution time: ndis.sys — Network Driver Interface Specification (NDIS), Microsoft Corporation

Total time spent in DPCs (%) 0.848527

DPC count (execution time <250 µs): 481015
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 12199
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0

_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires
reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see
which programs were hit.

Process with highest pagefault count: msmpeng.exe

Total number of hard pagefaults 3006
Hard pagefault count of hardest hit process: 1077
Number of processes hit: 58

_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 13.877046
CPU 0 ISR highest execution time (µs): 94.790
CPU 0 ISR total execution time (s): 0.001418
CPU 0 ISR count: 439
CPU 0 DPC highest execution time (µs): 947.220
CPU 0 DPC total execution time (s): 5.532492
CPU 0 DPC count: 155462
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 10.036351
CPU 1 ISR highest execution time (µs): 80.410
CPU 1 ISR total execution time (s): 0.001399
CPU 1 ISR count: 1022
CPU 1 DPC highest execution time (µs): 883.020
CPU 1 DPC total execution time (s): 3.329040
CPU 1 DPC count: 112728
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 8.029588
CPU 2 ISR highest execution time (µs): 85.170
CPU 2 ISR total execution time (s): 0.008390
CPU 2 ISR count: 2299
CPU 2 DPC highest execution time (µs): 914.610
CPU 2 DPC total execution time (s): 2.778771
CPU 2 DPC count: 67206
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2.713610
CPU 3 ISR highest execution time (µs): 103.330
CPU 3 ISR total execution time (s): 0.018220
CPU 3 ISR count: 17726
CPU 3 DPC highest execution time (µs): 572.630
CPU 3 DPC total execution time (s): 0.736754
CPU 3 DPC count: 32188
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 2.126310
CPU 4 ISR highest execution time (µs): 106.160
CPU 4 ISR total execution time (s): 0.030711
CPU 4 ISR count: 17578
CPU 4 DPC highest execution time (µs): 490.790
CPU 4 DPC total execution time (s): 0.564582
CPU 4 DPC count: 28795
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 1.290346
CPU 5 ISR highest execution time (µs): 117.050
CPU 5 ISR total execution time (s): 0.019130
CPU 5 ISR count: 10471
CPU 5 DPC highest execution time (µs): 196.340
CPU 5 DPC total execution time (s): 0.268027
CPU 5 DPC count: 16862
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 0.817404
CPU 6 ISR highest execution time (µs): 108.40
CPU 6 ISR total execution time (s): 0.009544
CPU 6 ISR count: 2585
CPU 6 DPC highest execution time (µs): 164.870
CPU 6 DPC total execution time (s): 0.087005
CPU 6 DPC count: 12797
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 0.760451
CPU 7 ISR highest execution time (µs): 8.870
CPU 7 ISR total execution time (s): 0.000302
CPU 7 ISR count: 52
CPU 7 DPC highest execution time (µs): 110.340
CPU 7 DPC total execution time (s): 0.026813
CPU 7 DPC count: 6535
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 0.979627
CPU 8 ISR highest execution time (µs): 102.610
CPU 8 ISR total execution time (s): 0.020786
CPU 8 ISR count: 37079
CPU 8 DPC highest execution time (µs): 123.650
CPU 8 DPC total execution time (s): 0.064216
CPU 8 DPC count: 14415
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 0.803844
CPU 9 ISR highest execution time (µs): 5.090
CPU 9 ISR total execution time (s): 0.001536
CPU 9 ISR count: 2253
CPU 9 DPC highest execution time (µs): 162.520
CPU 9 DPC total execution time (s): 0.049710
CPU 9 DPC count: 9496
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 0.950035
CPU 10 ISR highest execution time (µs): 93.940
CPU 10 ISR total execution time (s): 0.003605
CPU 10 ISR count: 4844
CPU 10 DPC highest execution time (µs): 128.990
CPU 10 DPC total execution time (s): 0.091793
CPU 10 DPC count: 18429
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 1.026593
CPU 11 ISR highest execution time (µs): 108.970
CPU 11 ISR total execution time (s): 0.006137
CPU 11 ISR count: 8964
CPU 11 DPC highest execution time (µs): 132.330
CPU 11 DPC total execution time (s): 0.124589
CPU 11 DPC count: 18301
_________________________________________________________________________________________________________

Joined
May 23, 2012
Posts
2,943
Location

Colorado


Joined
Feb 20, 2021
Posts
29




  • #3

Hi there, I’m trying to do the step where you set the paths and stuff, but even after I’ve gone into the path option and set the location for the SDK, the commands in admin enabled command prompt still don’t work.

Heres what it says.
C:\WINDOWS\system32>xperf -on DiagEasy

C:\WINDOWS\system32>xperf -d «%userprofile%\Desktop\trace.etl»
xperf: error: Merge ETL: The system cannot find the path specified. (0x3).

And I’ve attatched a screenshot of what I did for the first step of setting the location.

Attachments

Joined
May 23, 2012
Posts
2,943
Location

Colorado




  • #4

I will try to take a look this weekend to determine the issues. It seems the latest Windows version and SDK may have resulted in changes that require us to update our instructions.

Joined
Feb 20, 2021
Posts
29




  • #5

Alright thanks for helping me out I appreciate it a lot.

Joined
Feb 20, 2021
Posts
29




  • #6

Hey there, sorry to bother but is there a fix to the instructions yet?

Joined
May 23, 2012
Posts
2,943
Location

Colorado




  • #7

Hey there, sorry to bother but is there a fix to the instructions yet?

Sorry about the delay; I ended up having my first ICU/hospital stay of my life this weekend but should be headed home today. I will see if I can get someone else to get you interim instructions until I can take a closer look later this week and update the overall instructions.

Joined
Feb 20, 2021
Posts
29




  • #8

I am so sorry to hear that. Please feel better soon and take it easy.




  • #9

I uninstalled all kits I had, then I followed carefully the instructions to reinstall the performance toolkit.
Instructions are correct, using xperf.

Alternative commands, because it seems xperf is almost deprecated, COULD be (experimenting new commands — you must use only one of them):

wpr -start audio.verbose
wpr -start video.verbose
wpr -start network.verbose

A combination of them:

wpr -start audio.verbose -start video.verbose -start audio.verbose

To stop the trace (use only one command; the appropriate one in base of the one you have chosen previously):

wpr -stop "%userprofile%\desktop\WPR-audio-trace.etl"
wpr -stop "%userprofile%\desktop\WPR-video-trace.etl"
wpr -stop "%userprofile%\desktop\WPR-network-trace.etl"
wpr -stop "%userprofile%\desktop\WPR-audio-video-network-trace.etl"

Joined
Feb 20, 2021
Posts
29




  • #10

Ok cool, I ended up getting everything working as it should be. Thank y’all for helping me with the steps.

Speccy Link

Google Drive Link to trace.etl and SysnativeFileCollectionApp.zip

  • Write a brief description of your problem.
    You can also include the steps you tried.

Constant microstuttering in every single thing I do. The ufotest online stutters, games all microstutter, videos microstutter, dragging windows, basically everything. I’ve tried reinstalling multiple times and actually replacing RAM, GPU, and MOBO. Started around 5-6 months ago.

  • OS ? (Windows 10, 8.1, 8, 7, Vista)

Win 10 Education

  • x86 (32bit) or x64 (64bit)?

x64

  • What was original installed OS on system?

Windows 10 Default

  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?

Installed it myself and got a key from my school.

  • Age of system? (hardware)

I’ve switched out a lot of parts so its different than what it was in like 2016. I’d say average age of parts is newer than 1 year.

  • Age of OS installation?

2 weeks

  • Have you re-installed the OS?

Yes, multiple times to try to fix the stutter issue.

  • System Manufacturer?

Custom built by me.

  • Laptop or Desktop?

Desktop

  • MotherBoard — (if NOT a laptop)

ROG STRIX B450-F GAMING II

  • CPU

Ryzen 3600x

  • RAM (brand, EXACT model, what slots are you using?)

Corsair Vengeance RGB Pro 16GB (2x8GB) DDR4 3200MHz C16 LED Desktop Memory — White, DIMM A2 B2

  • Video Card

Zotac RTX 3070 OC

  • Power Supply — brand & wattage (if laptop, skip this one)

Corsair CX Series 750 Watt (2017) 80 Plus Bronze Certified Non-Modular Power Supply (CP-9020123-NA) (Closest one I could find. I can’t find documentation for the PSU lol. If its really important I will take it out of my case and find the actual product number)

  • Is driver verifier enabled or disabled?

I don’t believe so. I’ve never actually ran or used it.

  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)

Only Windows Defender

  • Are you using proxy, vpn, ipfilters or similar software?

Yes I’m using Windscribe.

  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)

No I am not.

  • Are you currently under/overclocking? Are there overclocking software installed on your system?

No everything is running stock. I’m running MSI afterburner for frametime monitoring, Asus Armory, and NZXT CAM.

Joined
May 23, 2012
Posts
2,943
Location

Colorado




  • #11

Instructions are correct, using xperf.

One issue with the instructions that I found is that %userprofile%\Desktop does not exist on my system. I suspect they made the public desktop folder everyone’s desktop folder with a recent Windows upgrade, and/or the file storage aspect of it was moved into OneDrive for users who chose to use OneDrive as a backup solution.

Joined
Feb 20, 2021
Posts
29




  • #12

Hi there, is anyone able to look over the issues I’m having with my computer? I’ve also done RAM and Storage Tests and they all turned out fine. Thanks in advance.

Joined
May 23, 2012
Posts
2,943
Location

Colorado




  • #13

After analyzing your trace, I am seeing an issue between your network and display card drivers. Before focusing on those, I want to make sure your foundation is set up correctly since that can lead to issues with devices and their drivers working cleanly. Do you have the latest chipset drivers for your motherboard?

AMD Chipset Driver V2.11.26.106 For Windows 10 64-bit.

Joined
Feb 20, 2021
Posts
29




  • #14

Yep Everything is up to date in terms of chipset drivers. I also ended up looking over the stuff myself and replacing my network adapter. Theres no issue in terms of the ndis.sys drivers now.

Joined
May 23, 2012
Posts
2,943
Location

Colorado




  • #15

Yep Everything is up to date in terms of chipset drivers. I also ended up looking over the stuff myself and replacing my network adapter. Theres no issue in terms of the ndis.sys drivers now.

Nice investigating. Are you still seeing issues with the Nvidia causing stuttering? Have you tried different drivers to see if any provide more stable framerates?

It’s rarer than it used to be, but you may also want to contact AMD/Nvidia to see if they know of any conflict between the hardware setup with your motherboard and display card. Even if there are no conflicts, they may be able to point you to other possible solutions.

You also mentioned this started approximately four months ago. Were there any software or hardware updates that you recall performing before the issues began?

Joined
Feb 20, 2021
Posts
29




  • #16

No i dont quite remember anything weird happening. I have been in talks with nvidia but so far theyve just said to try the card in another PC which is what im working on right now. Ive tried all the drivers that have been released for the 3070, but so far no dice. Do you think it might be a hardware issue with the card itself? Ill keep trying to think of any issues before the stuttering started. Maybe one would be that the 5700xt drivers kept making my warzone stuttering but then it got fixed.

Joined
May 23, 2012
Posts
2,943
Location

Colorado




  • #17

Yeah, a bad card could cause any number of issues. A bit out of the ordinary in my experience for what you are describing, though. Usually cards work until they fully fail. Overheating/throttling is more likely to cause stuttering. Is there much dust in the system? Has there ever been a lot of dust caked on any components?

Dust can damage or degrade contacts and/or circuitry. Just FYI, never use a vacuum to clean dust from computers. The static a vacuum builds up can also damage peripherals. Compressed air at low pressure is safest for clearing dust.

Joined
Feb 20, 2021
Posts
29




  • #18

No ive always kept things really clean inside my PC and stayed away from vaping near it. To clean it I always use compressed air. I may wait for the next NVIDIA driver update to see if it fixes anything, but if it doesnt, do you think I should try RMAing the card?

Joined
May 23, 2012
Posts
2,943
Location

Colorado




  • #19

I think it depends on what happens with your troubleshooting through Nvidia. Have you tried removing the GPU and running off the motherboard HDMI?

EDIT:

You may also find the following of interest: RTX 3070 Stutter

Last edited:

Joined
Feb 20, 2021
Posts
29




  • #20

Thanks for the link :) I will definitely take a look.
I haven’t tried taking out the GPU and running HDMI from mobo, but I don’t think I can do that with my Ryzen CPU. I’ll give it a try when I can as I’m away from my Rig for the week.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

  • Microsoft Support & Malware Removal

  • Windows 10

Куратор(ы):  

eLfiK   

Автор Сообщение
 

Добавлено: 12.10.2016 12:14 

[профиль]

Member

Статус: Не в сети
Регистрация: 12.10.2016

1. Ликбез по прерываниям.

Все прерывания делятся по следующим приоритетам:
1 место — работает на уровне кольцо -2
прерывания SMI (system management interrupt — прерывание системного управления), которое возникает:
-по сигналу от чипсета или периферии на материнской плате
-программный SMI, посланный системным ПО через порт ввода-вывода
-запись по адресу ввода-вывода, для которого микропрограммно установлена необходимость активации SMM.
2 место — гипервизор, который работает в кольце -1
3 место — ядро операционной системы — работает в кольце 0
4 место — пользовательский уровень — работает в кольце 3

2. Ссылки.

https://forums.guru3d.com/threads/windows-line-based-vs-message-signaled-based-interrupts-msi-tool.378044/
https://www.ixbt.com/live/sw/umenshaem-latentnost-vvoda-v-windows-10-11.html
https://www.ixbt.com/live/sw/ispravlenie-sistemnogo-taymera-hpet-v-novyh-versiyah-windows.html

3. Борьба с прерываниями.

https://github.com/denis-g/windows10-latency-optimization

Позднее дополню каждый раздел.
Все проблемы у нас связаны с тем, что windows относится к операционным системам с вытесняющей многозадачностью.
Вытесняющая многозадачность требует обработки системного прерывания от аппаратного таймера. По истечении кванта времени, отведённого процессу, происходит прерывание и вызывается планировщик процессов. Частота вызова планировщика критична: слишком частый его вызов будет расходовать процессорное время впустую.
Единственное, что мы можем изменить — это увеличить время кванта и поменять соотношение квантов времени на активную задачу и задачи в фоне, за это отвечает параметр в реестре
Win32PrioritySeparation
По умолчанию
0х26 квант 18:6 = Оптимальный вариант
При этом само время кванта зависит от системного таймера.
При системном таймера 15.625 мс оно будет больше, чем при 1.0 мс.
Высчитывается время системного таймера * тики.

SMI-прерывания зависят от BIOS/UEFI и оборудования.
Отключаем все лишнее, отключаем энергосохранение, скорость вентиляторов фиксируем, это все, что мы можем сделать.
В нашем плане энергосохранения выбрать оценка для поднятия частоты вместо 15 мс максимум 5000 мс.
Есть программа Intel SMI Latency Checker
Для гипервизора — отключаем поддержку виртуальных машин в биосе.

Про прерывания на уровне ядра и пользователя в windows.

В Windows применяется:
— для x86 — 32 уровня IRQL от 0 до 31 (в скобках указано числовое значение):
High (31)
Power fail (30)
IPI (29)
Clock (28)
Profile (27)
Диапазон аппаратных прерываний, называемых Devices IRQL, или DIRQL (от 26 до 3) или ISR
DPC/DISPATCH (2)
APC (1)
PASSIVE (0)
Это означает, например, что планировщик (работающий на уровне DPC/DISPATCH) может быть прерван аппаратными прерываниями, межпроцессорными прерываниями (IPI) и т. д., но не может быть прерван асинхронными процедурами (APC) и обычными потоками, работающими на уровне PASSIVE. Межпроцессорные прерывания IPI могут быть прерваны сбоем электропитания (прерывание на уровне Power fail), но не могут быть прерваны обычными аппаратными прерываниями от устройств и т. д.
— для х64
16 уровней IRQL (от 0 до 15)
High/Profile (15)
Interprocessor interrupt/Power (14)
Clock (13)
Synch (12)
Device n (11)
………
Device 1 (3)
Dispatch/DPC (2)
APC (1)
Passive/Low (0)

При этом:
hardware interrupts 3-15 (3-31)
software interrupts 1-2 (1-2)
normal thread execution 0 (0)

Наш пользовательский процесс может иметь следующие приоритеты:
Idle — 4
Below Normal — 6
Normal -8
Above Normal -10
High -13
Real-Time -24
Внутри процесса мы можем задать приоритет для его потоков:
Idle дает итоговый приоритет процесса с потоком 1, кроме real-time, там он его просто снизит до фиксированной 16
Lowest -2
Below Normal -1
Normal 0
Above Normal +1
Highest +2
Time Critical +7

Итоговый приоритет потока — это сумма приоритетов процесса и потока.
31 — максимум
Real-Time — от 16 до 31.
При этом даже максимальный 31 приоритет не лает нам возможности подняться выше уровня Passive/Low(0), поэтому любое прерывание на нашем ядре прервет нашу программу.

Программы для оценки прерываний:

ETW xperf WPA — родной софт от microsoft
Latency monitor https://www.resplendence.com/latencymon
DPC latency https://www.wagnardsoft.com/forums/viewtopic.php?t=5265

Настройка прерываний

https://www.wagnardsoft.com/content/Download-Intelligent-standby-list-cleaner-ISLC-1034
https://www.techpowerup.com/download/microsoft-interrupt-affinity-tool/
http://www.mediafire.com/file/ewpy1p0rr132thk/MSI_util_v3.zip
http://www.mediafire.com/file/2kkkvko7e75opce/MSI_util_v2.zip
https://github.com/spddl/GoInterruptPolicy

Борьба с прерываниями.
Бороться надо двумя путями.
Первый путь — уменьшить само количество прерываний=их частоту.
Частота прерываний за 1 секунду до 10000 считается еще неплохой.
Второй путь — уменьшить длительность прерываний.
Есть еще третий путь — освободить от прерываний нужные нам ядра.

Первое и самое главное.
Установка максимально облегченной и очищенной системы.
Если хватит windows 10, то лучше ставить ее.
23H2 лучше, чем 24Н2.
Отключить динамический таймер.
Поднять, а не снизить время для системного таймера до 15,625 мс!
Если снизим до 0.5 мс, то увеличим количество прерываний.
Но тут вступает в действие многозадачность винды.
1/4 времени отдается фоновым процессам.
Минимум — это 6 тиков.
Полностью вырубить все фоновые процессы на винде мы не сможем.
Для 120 кадров нам нужно иметь перерыв не больше 1/120=8.(3) мс.
Поэтому подходит время для системного таймера только
0.5 мс или 1 мс , так как 2 мс уже много (2 мс*6=12 мс).

Отключить VSYNC.
Включить тройную буферизацию если процессор успевает рендерить, то компенсирует воемя двух кадров: 2*1000 мс / частоту кадров в Гц
Краткий список исследований по психофизиологии:
Watson (1986): Задержки <5 мс незаметны.
Kelly (1979): Порог фликера <2 мс.
Burr & Ross (1982): 10% кадра = 100мс/частоту кадров (при движении).
Clayton (2018): 1–2% кадров= 1000мс*процент пропуска кадров (10–20 мс/с) незаметно.
Carrasco (2011): <5–10 мс при внимании.
Hoffman et al. (2017): <3 мс с размытием.
Swafford et al. (2016): <4 мс, 2% (20 мс) при редких фризах (реже 1 раза в секунду).
Digital Foundry (2025): 0.125 фриза/с=0.125*1000мс/частоту кадров Гц) заметно при частых повторениях.

Для 120 Гц:
1982-0.833мс
2025-1.042мс

Снизить частоту опроса мыши до 125Гц.

Главные правила для таймеров:
Таймеры используются для времени (QPC) и для системных прерываний=тиков.

useplatformclock disables TSC and uses the platform source clock instead (HPET or PMT). PMT is used when HPET is disabled in BIOS.
useplatformtick disables TSC tick and uses the platform source tick instead (RTC).
Does disabledynamictick work when useplatformtick is used?
No, it does not do anything since RTC is not a dynamic tick counter.

При этом возможны разные комбинации таймеров.

TSC + TSC without desync:
bcdedit /deletevalue useplatformclock — bcdedit /deletevalue useplatformtick
(make sure HPET is enabled in BIOS)
TSC + RTC:
bcdedit /deletevalue useplatformclock — bcdedit /set useplatformtick Yes
HPET + RTC:
bcdedit /set useplatformclock Yes — bcdedit /set useplatformtick Yes
(make sure HPET is enabled in BIOS)
PMT + RTC:
bcdedit /set useplatformclock Yes — bcdedit /set useplatformtick Yes
(make sure HPET is disabled in BIOS)
Частота HPET 14.318180 MHz, в 4 раза выше частоты ACPI PM Timer.
RTC устаревший тайминг с частотой от 2-х до 8192 Гц.
Использует кварц 32.768 KHz
HPET требует больше времени на вызов, чем TSC или PM Timer, но это важно только для системных прерываний.
HPET и PM timer находятся в южном мосте.
TSC в процессоре.
Поэтому вполне допустима комбинация HPET (для времени QPC)+TSC (для тиков).

bcdedit /set useplatformtick no (отключаем RTC и включаем TSC для тиков)
bcdedit /set useplatformclock no (отключаем HPET и включаем TSC для времени QPC)
bcdedit /set disabledynamictick yes (отключаем динамическое изменение частоты системного таймера — влияет только на тики)
bcdedit /set tscsyncpolicy Enhanced (включаем улучшенную синхронизацию TSC-таймера)
HPET не следует отключать в биосе и в диспетчере устройств.
Посмотреть текущую конфигурацию можно с помощью команды
bcdedit /enum

Обсуждение проблем ОС и оборудования: задержка реакции системы (latency), микроcтаттер, инпутлаг, фризы.

Перед тем как задавать вопросы, просьба прочитать FAQ

Осуществлять мониторинг программой Latency Monitor нужно в течение 1 минуты, в состоянии простоя системы т.е. без дисковой, сетевой активности, и любой другой, с выключенным ав и приложениями в трее и автозагрузке,
не раньше чем через 2 минуты после загрузки системы.
Не двигаем мышку и не используем клавиатуру в момент измерений. Потом остановка и скриншот.

Презентация NVIDIA (на англ.) о проблемах статтеров, фризов и лагов (терминология, описание и причины возникновения)

Последний раз редактировалось anta777 05.05.2025 22:50, всего редактировалось 34 раз(а).
Начну редактировать первое сообщение и возьмусь за эту тему.
Реклама

Партнер
 
Phenomenum

Member

Статус: Не в сети
Регистрация: 23.06.2019
Фото: 0

yylseijfvlu0 Железо напиши, пожалуйста. Все, что есть. И ответь на все мои вопросы.


_________________
R9 7900X+Thermalright FS 140 / ASUS Rog Strix X670E-A / G.Skill Trident 6200 CL30 / RX 7900 XTX Sapphire Nitro+ / Thermaltake Toughpower PF1 1050W / Fractal Meshify 2

 
Y0!

Member

Статус: Не в сети
Регистрация: 02.06.2012
Откуда: Стольный Град

Привет. BIOS сброшен в дефолт, вручную не изменено ничего, версия 5851 (последняя от ASUS). Винда — десятка корпоративная 21H1 (не сборка) из образа с обновлениями от июня 2021, не изменены никакие настройки (разве что убрана галочка с повышенной точности указателя мыши), не удалено ничего, из драйверов установлен только графический 471.22 без geforce experience (чистая установка), никакие другие драйверы не ставил, так что стоит только то, что было встроено в винду. В предыдущий раз пробовал ставить все самые новые драйверы, но ничего это не исправило, потому сейчас поставил только видео.

Показатели LatencyMon (снято во время работы CS:GO) какие-то слишком пугающие.

Interrupt to user process latency

Код:

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for  0:09:30  (h:mm:ss) on all processors.

_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:                                        DESKTOP
OS version:                                           Windows 10, 10.0, version 2009, build: 19043 (x64)
Hardware:                                             System Product Name, System manufacturer
CPU:                                                  AuthenticAMD AMD Ryzen 5 3600 6-Core Processor
Logical processors:                                   12
Processor groups:                                     1
RAM:                                                  16291 MB total

_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed:                                   3593 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs):   2988,40
Average measured interrupt to process latency (µs):   6,137626

Highest measured interrupt to DPC latency (µs):       2985,0
Average measured interrupt to DPC latency (µs):       2,247735

_________________________________________________________________________________________________________
 REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs):              259,614807
Driver with highest ISR routine execution time:       dxgkrnl.sys — DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%):          0,266056
Driver with highest ISR total time:                   dxgkrnl.sys — DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%)                          0,269609

ISR count (execution time <250 µs):                   760454
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-1000 µs):               1
ISR count (execution time 1000-2000 µs):              0
ISR count (execution time 2000-4000 µs):              0
ISR count (execution time >=4000 µs):                 0

_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs):              6000,838297
Driver with highest DPC routine execution time:       nvlddmkm.sys — NVIDIA Windows Kernel Mode Driver, Version 471.22 , NVIDIA Corporation

Highest reported total DPC routine time (%):          0,122476
Driver with highest DPC total execution time:         dxgkrnl.sys — DirectX Graphics Kernel, Microsoft Corporation

Total time spent in DPCs (%)                          0,189475

DPC count (execution time <250 µs):                   1577122
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-10000 µs):              344
DPC count (execution time 1000-2000 µs):              4
DPC count (execution time 2000-4000 µs):              6
DPC count (execution time >=4000 µs):                 1

_________________________________________________________________________________________________________
 REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count:                 steamservice.exe

Total number of hard pagefaults                       877
Hard pagefault count of hardest hit process:          805
Number of processes hit:                              8

_________________________________________________________________________________________________________
 PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s):                       38,451351
CPU 0 ISR highest execution time (µs):                259,614807
CPU 0 ISR total execution time (s):                   18,279776
CPU 0 ISR count:                                      691529
CPU 0 DPC highest execution time (µs):                6000,838297
CPU 0 DPC total execution time (s):                   12,032065
CPU 0 DPC count:                                      1472796
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s):                       6,884179
CPU 1 ISR highest execution time (µs):                16,592263
CPU 1 ISR total execution time (s):                   0,155579
CPU 1 ISR count:                                      48252
CPU 1 DPC highest execution time (µs):                824,523240
CPU 1 DPC total execution time (s):                   0,729091
CPU 1 DPC count:                                      59349
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s):                       2,220725
CPU 2 ISR highest execution time (µs):                13,406067
CPU 2 ISR total execution time (s):                   0,028150
CPU 2 ISR count:                                      4913
CPU 2 DPC highest execution time (µs):                313,188979
CPU 2 DPC total execution time (s):                   0,089587
CPU 2 DPC count:                                      25214
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s):                       1,610403
CPU 3 ISR highest execution time (µs):                0,0
CPU 3 ISR total execution time (s):                   0,0
CPU 3 ISR count:                                      0
CPU 3 DPC highest execution time (µs):                17,163373
CPU 3 DPC total execution time (s):                   0,000296
CPU 3 DPC count:                                      142
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s):                       1,527826
CPU 4 ISR highest execution time (µs):                0,0
CPU 4 ISR total execution time (s):                   0,0
CPU 4 ISR count:                                      0
CPU 4 DPC highest execution time (µs):                579,917618
CPU 4 DPC total execution time (s):                   0,009728
CPU 4 DPC count:                                      2192
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s):                       1,607180
CPU 5 ISR highest execution time (µs):                0,0
CPU 5 ISR total execution time (s):                   0,0
CPU 5 ISR count:                                      0
CPU 5 DPC highest execution time (µs):                508,789313
CPU 5 DPC total execution time (s):                   0,017095
CPU 5 DPC count:                                      2621
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s):                       1,979623
CPU 6 ISR highest execution time (µs):                0,0
CPU 6 ISR total execution time (s):                   0,0
CPU 6 ISR count:                                      0
CPU 6 DPC highest execution time (µs):                753,074311
CPU 6 DPC total execution time (s):                   0,040096
CPU 6 DPC count:                                      5067
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s):                       2,340813
CPU 7 ISR highest execution time (µs):                0,0
CPU 7 ISR total execution time (s):                   0,0
CPU 7 ISR count:                                      0
CPU 7 DPC highest execution time (µs):                517,406067
CPU 7 DPC total execution time (s):                   0,021066
CPU 7 DPC count:                                      2800
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s):                       1,546256
CPU 8 ISR highest execution time (µs):                3,807403
CPU 8 ISR total execution time (s):                   0,007763
CPU 8 ISR count:                                      14448
CPU 8 DPC highest execution time (µs):                244,996382
CPU 8 DPC total execution time (s):                   0,025174
CPU 8 DPC count:                                      4790
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s):                       0,864185
CPU 9 ISR highest execution time (µs):                1,532981
CPU 9 ISR total execution time (s):                   0,000061
CPU 9 ISR count:                                      94
CPU 9 DPC highest execution time (µs):                277,720011
CPU 9 DPC total execution time (s):                   0,001383
CPU 9 DPC count:                                      224
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s):                       1,208279
CPU 10 ISR highest execution time (µs):                1,482883
CPU 10 ISR total execution time (s):                   0,000387
CPU 10 ISR count:                                      652
CPU 10 DPC highest execution time (µs):                40,148066
CPU 10 DPC total execution time (s):                   0,014352
CPU 10 DPC count:                                      2110
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s):                       0,703498
CPU 11 ISR highest execution time (µs):                2,424715
CPU 11 ISR total execution time (s):                   0,000355
CPU 11 ISR count:                                      567
CPU 11 DPC highest execution time (µs):                347,345394
CPU 11 DPC total execution time (s):                   0,001808
CPU 11 DPC count:                                      172
_________________________________________________________________________________________________________

Interrupt to DPC latency

Код:

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for  0:06:34  (h:mm:ss) on all processors.

_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:                                        DESKTOP
OS version:                                           Windows 10, 10.0, version 2009, build: 19043 (x64)
Hardware:                                             System Product Name, System manufacturer
CPU:                                                  AuthenticAMD AMD Ryzen 5 3600 6-Core Processor
Logical processors:                                   12
Processor groups:                                     1
RAM:                                                  16291 MB total

_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed:                                   3593 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

_________________________________________________________________________________________________________
MEASURED INTERRUPT TO DPC LATENCIES
_________________________________________________________________________________________________________
The interrupt to DPC latency reflects the measured interval in which a DPC could execute in response to a hardware request from the moment the interrupt service routine started execution.

Highest measured interrupt to DPC latency (µs):       4408,0
Average measured interrupt to DPC latency (µs):       6,476717

_________________________________________________________________________________________________________
 REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs):              263,462288
Driver with highest ISR routine execution time:       dxgkrnl.sys — DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%):          0,360598
Driver with highest ISR total time:                   dxgkrnl.sys — DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%)                          0,365003

ISR count (execution time <250 µs):                   707634
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-1000 µs):               1
ISR count (execution time 1000-2000 µs):              0
ISR count (execution time 2000-4000 µs):              0
ISR count (execution time >=4000 µs):                 0

_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs):              6007,821876
Driver with highest DPC routine execution time:       nvlddmkm.sys — NVIDIA Windows Kernel Mode Driver, Version 471.22 , NVIDIA Corporation

Highest reported total DPC routine time (%):          0,170995
Driver with highest DPC total execution time:         dxgkrnl.sys — DirectX Graphics Kernel, Microsoft Corporation

Total time spent in DPCs (%)                          0,254326

DPC count (execution time <250 µs):                   1458428
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-10000 µs):              14
DPC count (execution time 1000-2000 µs):              2
DPC count (execution time 2000-4000 µs):              8
DPC count (execution time >=4000 µs):                 1

_________________________________________________________________________________________________________
 REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count:                 steam.exe

Total number of hard pagefaults                       41
Hard pagefault count of hardest hit process:          24
Number of processes hit:                              8

_________________________________________________________________________________________________________
 PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s):                       33,435017
CPU 0 ISR highest execution time (µs):                263,462288
CPU 0 ISR total execution time (s):                   17,104340
CPU 0 ISR count:                                      645813
CPU 0 DPC highest execution time (µs):                6007,821876
CPU 0 DPC total execution time (s):                   11,276489
CPU 0 DPC count:                                      1370566
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s):                       5,235574
CPU 1 ISR highest execution time (µs):                18,876705
CPU 1 ISR total execution time (s):                   0,106878
CPU 1 ISR count:                                      38474
CPU 1 DPC highest execution time (µs):                72,060117
CPU 1 DPC total execution time (s):                   0,581709
CPU 1 DPC count:                                      45277
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s):                       1,737066
CPU 2 ISR highest execution time (µs):                15,930977
CPU 2 ISR total execution time (s):                   0,044337
CPU 2 ISR count:                                      7726
CPU 2 DPC highest execution time (µs):                115,865294
CPU 2 DPC total execution time (s):                   0,096183
CPU 2 DPC count:                                      27193
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s):                       0,367461
CPU 3 ISR highest execution time (µs):                0,0
CPU 3 ISR total execution time (s):                   0,0
CPU 3 ISR count:                                      0
CPU 3 DPC highest execution time (µs):                14,518230
CPU 3 DPC total execution time (s):                   0,000315
CPU 3 DPC count:                                      140
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s):                       0,557523
CPU 4 ISR highest execution time (µs):                0,0
CPU 4 ISR total execution time (s):                   0,0
CPU 4 ISR count:                                      0
CPU 4 DPC highest execution time (µs):                34,617311
CPU 4 DPC total execution time (s):                   0,006094
CPU 4 DPC count:                                      1430
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s):                       0,618667
CPU 5 ISR highest execution time (µs):                0,0
CPU 5 ISR total execution time (s):                   0,0
CPU 5 ISR count:                                      0
CPU 5 DPC highest execution time (µs):                44,266073
CPU 5 DPC total execution time (s):                   0,015105
CPU 5 DPC count:                                      3859
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s):                       0,839017
CPU 6 ISR highest execution time (µs):                0,0
CPU 6 ISR total execution time (s):                   0,0
CPU 6 ISR count:                                      0
CPU 6 DPC highest execution time (µs):                62,33120
CPU 6 DPC total execution time (s):                   0,013302
CPU 6 DPC count:                                      2630
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s):                       0,817085
CPU 7 ISR highest execution time (µs):                0,0
CPU 7 ISR total execution time (s):                   0,0
CPU 7 ISR count:                                      0
CPU 7 DPC highest execution time (µs):                173,236849
CPU 7 DPC total execution time (s):                   0,004677
CPU 7 DPC count:                                      1145
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s):                       1,148899
CPU 8 ISR highest execution time (µs):                4,107988
CPU 8 ISR total execution time (s):                   0,008135
CPU 8 ISR count:                                      14865
CPU 8 DPC highest execution time (µs):                36,781520
CPU 8 DPC total execution time (s):                   0,023901
CPU 8 DPC count:                                      4449
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s):                       0,344745
CPU 9 ISR highest execution time (µs):                1,883663
CPU 9 ISR total execution time (s):                   0,000067
CPU 9 ISR count:                                      98
CPU 9 DPC highest execution time (µs):                34,597272
CPU 9 DPC total execution time (s):                   0,000486
CPU 9 DPC count:                                      110
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s):                       0,890416
CPU 10 ISR highest execution time (µs):                1,633176
CPU 10 ISR total execution time (s):                   0,000279
CPU 10 ISR count:                                      426
CPU 10 DPC highest execution time (µs):                70,186474
CPU 10 DPC total execution time (s):                   0,010631
CPU 10 DPC count:                                      1604
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s):                       0,350580
CPU 11 ISR highest execution time (µs):                2,284442
CPU 11 ISR total execution time (s):                   0,000155
CPU 11 ISR count:                                      233
CPU 11 DPC highest execution time (µs):                41,971611
CPU 11 DPC total execution time (s):                   0,000385
CPU 11 DPC count:                                      50
_________________________________________________________________________________________________________

Kernel timer latency

Код:

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for  0:09:07  (h:mm:ss) on all processors.

_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:                                        DESKTOP
OS version:                                           Windows 10, 10.0, version 2009, build: 19043 (x64)
Hardware:                                             System Product Name, System manufacturer
CPU:                                                  AuthenticAMD AMD Ryzen 5 3600 6-Core Processor
Logical processors:                                   12
Processor groups:                                     1
RAM:                                                  16291 MB total

_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed:                                   3593 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

_________________________________________________________________________________________________________
MEASURED KERNEL TIMER LATENCIES
_________________________________________________________________________________________________________
This value represents the maximum measured latency of a perodically scheduled kernel timer.

Highest measured kernel timer latency (µs):           26668,10

_________________________________________________________________________________________________________
 REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs):              291,035903
Driver with highest ISR routine execution time:       dxgkrnl.sys — DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%):          0,363446
Driver with highest ISR total time:                   dxgkrnl.sys — DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%)                          0,367381

ISR count (execution time <250 µs):                   1001708
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-1000 µs):               1
ISR count (execution time 1000-2000 µs):              0
ISR count (execution time 2000-4000 µs):              0
ISR count (execution time >=4000 µs):                 0

_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs):              5995,026997
Driver with highest DPC routine execution time:       nvlddmkm.sys — NVIDIA Windows Kernel Mode Driver, Version 471.22 , NVIDIA Corporation

Highest reported total DPC routine time (%):          0,174894
Driver with highest DPC total execution time:         dxgkrnl.sys — DirectX Graphics Kernel, Microsoft Corporation

Total time spent in DPCs (%)                          0,263101

DPC count (execution time <250 µs):                   1984892
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-10000 µs):              14
DPC count (execution time 1000-2000 µs):              4
DPC count (execution time 2000-4000 µs):              3
DPC count (execution time >=4000 µs):                 1

_________________________________________________________________________________________________________
 REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count:                 steam.exe

Total number of hard pagefaults                       50
Hard pagefault count of hardest hit process:          20
Number of processes hit:                              9

_________________________________________________________________________________________________________
 PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s):                       46,798506
CPU 0 ISR highest execution time (µs):                291,035903
CPU 0 ISR total execution time (s):                   23,924929
CPU 0 ISR count:                                      913618
CPU 0 DPC highest execution time (µs):                5995,026997
CPU 0 DPC total execution time (s):                   16,304354
CPU 0 DPC count:                                      1880811
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s):                       4,344870
CPU 1 ISR highest execution time (µs):                15,930977
CPU 1 ISR total execution time (s):                   0,153774
CPU 1 ISR count:                                      55133
CPU 1 DPC highest execution time (µs):                84,654606
CPU 1 DPC total execution time (s):                   0,764802
CPU 1 DPC count:                                      54910
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s):                       1,425927
CPU 2 ISR highest execution time (µs):                18,035068
CPU 2 ISR total execution time (s):                   0,044101
CPU 2 ISR count:                                      7436
CPU 2 DPC highest execution time (µs):                1746,425828
CPU 2 DPC total execution time (s):                   0,043998
CPU 2 DPC count:                                      13056
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s):                       0,242992
CPU 3 ISR highest execution time (µs):                0,0
CPU 3 ISR total execution time (s):                   0,0
CPU 3 ISR count:                                      0
CPU 3 DPC highest execution time (µs):                41,200111
CPU 3 DPC total execution time (s):                   0,000458
CPU 3 DPC count:                                      149
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s):                       3,112988
CPU 4 ISR highest execution time (µs):                0,0
CPU 4 ISR total execution time (s):                   0,0
CPU 4 ISR count:                                      0
CPU 4 DPC highest execution time (µs):                271,968828
CPU 4 DPC total execution time (s):                   0,083474
CPU 4 DPC count:                                      18617
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s):                       0,438464
CPU 5 ISR highest execution time (µs):                0,0
CPU 5 ISR total execution time (s):                   0,0
CPU 5 ISR count:                                      0
CPU 5 DPC highest execution time (µs):                40,538825
CPU 5 DPC total execution time (s):                   0,006527
CPU 5 DPC count:                                      1764
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s):                       0,909581
CPU 6 ISR highest execution time (µs):                0,0
CPU 6 ISR total execution time (s):                   0,0
CPU 6 ISR count:                                      0
CPU 6 DPC highest execution time (µs):                64,836070
CPU 6 DPC total execution time (s):                   0,018659
CPU 6 DPC count:                                      3792
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s):                       0,850489
CPU 7 ISR highest execution time (µs):                0,0
CPU 7 ISR total execution time (s):                   0,0
CPU 7 ISR count:                                      0
CPU 7 DPC highest execution time (µs):                30,689674
CPU 7 DPC total execution time (s):                   0,010344
CPU 7 DPC count:                                      2447
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s):                       1,271218
CPU 8 ISR highest execution time (µs):                1,923741
CPU 8 ISR total execution time (s):                   0,013477
CPU 8 ISR count:                                      24484
CPU 8 DPC highest execution time (µs):                47,893126
CPU 8 DPC total execution time (s):                   0,037713
CPU 8 DPC count:                                      7029
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s):                       0,181491
CPU 9 ISR highest execution time (µs):                1,362650
CPU 9 ISR total execution time (s):                   0,000082
CPU 9 ISR count:                                      112
CPU 9 DPC highest execution time (µs):                33,615363
CPU 9 DPC total execution time (s):                   0,000376
CPU 9 DPC count:                                      92
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s):                       0,931541
CPU 10 ISR highest execution time (µs):                1,392708
CPU 10 ISR total execution time (s):                   0,000415
CPU 10 ISR count:                                      652
CPU 10 DPC highest execution time (µs):                32,202616
CPU 10 DPC total execution time (s):                   0,014306
CPU 10 DPC count:                                      2140
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s):                       0,230668
CPU 11 ISR highest execution time (µs):                1,603117
CPU 11 ISR total execution time (s):                   0,000184
CPU 11 ISR count:                                      274
CPU 11 DPC highest execution time (µs):                33,665461
CPU 11 DPC total execution time (s):                   0,000695
CPU 11 DPC count:                                      107
_________________________________________________________________________________________________________


_________________
4-ех фаз хватает, что бы разогнать !!!8-ми ядерный!!! райзен до 3.8-3.9
Lopos, 13.10.2017

 
Dimonas

Member

Статус: Не в сети
Регистрация: 01.05.2005
Откуда: Краснодар

Y0! писал(а):

оказатели LatencyMon (снято во время работы CS:GO) какие-то слишком пугающие.

Показатели надо снимать в простое. FAQ читал?

 
Y0!

Member

Статус: Не в сети
Регистрация: 02.06.2012
Откуда: Стольный Град

Dimonas так лучше?..

Вложение:

Main.jpg

Main.jpg [ 190.69 КБ | Просмотров: 4159 ]

Вложение:

Drivers.jpg

Drivers.jpg [ 553.31 КБ | Просмотров: 4159 ]

В msconfig была снята галочка с элементов автозагрузки, скрыты службы Майкрософт и отключены все прочие службы, сразу после загрузки рабочего стола был запущен последний LatencyMon.

Проблема проявляется в микрофризах в CS:GO, BFV, некоторые из них, возможно, появляются перед проигрыванием любых внутриигровых звуков.
Также обычно движение прицела ощущается с небольшой, но задержкой, а в худших случаях — не на те расстояния, на которые ожидалось.

Тестирование проводилось как с разнообразными твиками (которые могут помочь при первом запуске после их применения, но потом всё возвращается), так и на девственно чистой корпоративной десятке, драйверы — самые-самые новые, пробовал не ставить драйвер аудио, мыши, видеодрайвер всегда ставится без GeForce Experience, как в одиночку, так и в сочетании с комплектным HD аудиодрайвером, USBC и PhysX. Пробовал разные USB порты. Около года назад значительно уменьшить количество микрофризов помогала неустановка драйвера мыши, но сейчас и это ничего не меняет.


_________________
4-ех фаз хватает, что бы разогнать !!!8-ми ядерный!!! райзен до 3.8-3.9
Lopos, 13.10.2017

 
Dimonas

Member

Статус: Не в сети
Регистрация: 01.05.2005
Откуда: Краснодар

Y0! писал(а):

Проблема проявляется в микрофризах в CS:GO, BFV, некоторые из них, возможно, появляются перед проигрыванием любых внутриигровых звуков.

По скринам трудно сказать в чем у тебя проблема. Драйверы мыши? Без них никак? И что за драйверы VMware в системе? Винда точно свежеустановлена?

 
Y0!

Member

Статус: Не в сети
Регистрация: 02.06.2012
Откуда: Стольный Град

Dimonas можно и без драйвера мыши, вот сейчас его нет, но это ничего к лучшему не меняет.
VMware — виртуалка, поставил только после различных тестирований задержек и графиков времени кадра, такая же картина даже если поставить только винду, голый видеодрайвер и Steam.
Винда установлена вчера, естественно сейчас на неё установлено немного приложений, потому что главное я выяснил — комп (микро)фризит даже при самом минимуме установленного ПО и независимо от настроек — есть вся телеметрия и виндовый антивирус, или они отключены.

Возможно, это аппаратная проблема — винда, на которую из дров я поставил только видео, а также Steam (для тестирования фризов), умудрилась упасть в BSOD 1000007e (ntfs.sys), когда Steam скачивал CS:GO. В системе два диска — 860 evo (винда и всё, что на неё установлено) и обычный винчестер 7200 об., первый вчера сканировал samsung magician’ом, второй — chkdsk /f /r, ошибок не найдено.


_________________
4-ех фаз хватает, что бы разогнать !!!8-ми ядерный!!! райзен до 3.8-3.9
Lopos, 13.10.2017

 
Y0!

Member

Статус: Не в сети
Регистрация: 02.06.2012
Откуда: Стольный Град

Вложение:

.jpg [ 150.02 КБ | Просмотров: 4125 ]


_________________
4-ех фаз хватает, что бы разогнать !!!8-ми ядерный!!! райзен до 3.8-3.9
Lopos, 13.10.2017

 
BOBKOC

Advanced member

Статус: Не в сети
Регистрация: 30.03.2017
Откуда: Москва/Вешняки
Фото: 11

так то криминала не видно, но можешь поэкспериментить с переводом в msi режим видюхи и аудио. ребутаться ток надо при каждом применении + проверять применилось ли

 
Y0!

Member

Статус: Не в сети
Регистрация: 02.06.2012
Откуда: Стольный Град

BOBKOC один из твиков заключался в том, чтобы всё перевести в msi и назначить высокий приоритет всему, кроме AMD PSP и сетевухи. Также прерывания видеокарты вешал на последние два потока. Также менял настройки HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile (SystemResponsiveness dword:00000000, Scheduling Category & SFIO Priority — high, Priority dword:00000006) и HKLM\SYSTEM\ControlSet001\Control\PriorityControl (Win32PrioritySeparation dword:00000006). Также ставил системный таймер в 0,5 мс и ставил автоочищение standby list (программой ISLC). Всё это вместе могло добавить до 9% средних fps в CS:GO, но фризы полностью не исчезают. После этих твиков может при первом запуске чувствоваться очень низкая задержка мыши, но это почему-то быстро пропадает и потом может случайным образом снова проявляться, закономерности не замечено.
Поддержка NVIDIA посоветовала полностью отключить энергосбережение PCI Express в плане питания в винде и активировать Hardware-acceletated GPU scheduling, но,естественно, это помогло не больше, чем выставление по их же совету ультранизкой задержки в видеодрайвере.
Ручное снижение таймингов оперативки и повышение её частоты только добавляло фризов, при чём Testmem5 с профилем anta777heavy и тест 1usmus DRAM Calculator не находили ошибок.
Не знаю, чего этому компьютеру не хватает.


_________________
4-ех фаз хватает, что бы разогнать !!!8-ми ядерный!!! райзен до 3.8-3.9
Lopos, 13.10.2017

 
Dimonas

Member

Статус: Не в сети
Регистрация: 01.05.2005
Откуда: Краснодар

Y0! Таймеры и приоритеты прерываний можно не крутить было. По моим наблюдениям это мало что дает в играх. А вот с фризами системы в первую очередь надо проверять связку процессор-память. Попробовать обновить биос материнки до последней версии с новой AGESA, поставить XMP тайминги и CMD 2T для стабильности. Я лично наблюдал ситуацию, когда в CMD 1T все тесты памяти без ошибок, а в PUBG фризы были. Поставил CMD 2T и проблема ушла.

 
Y0!

Member

Статус: Не в сети
Регистрация: 02.06.2012
Откуда: Стольный Град

Dimonas BIOS, как указывал, самый новый. Пробовал ставить всё в авто и тогда ставится режим 2400 CL19, попробовал прописать то же, что прописывается в D.O.C.P., но с 2T вместо 1T. 2T применилось, но фризит по-прежнему. Сейчас прерывания не изменены, я просто написал то, что тестировал в недалёком прошлом.
Всё-таки любопытная ситуация, после некоторых изменений при первом запуске Steam курсор просто супер контролируемый, но при последующих запусках он такое же непонятное Г как и всегда, будто софт подстраивается под новые настройки, чтобы работать так же плохо. Когда я меняю Multimedia — SystemProfile и системный таймер, происходит то же самое, и так же только при первом запуске после применения новых настроек, потом же всё, как обычно, хреново.

Интересно, как всё же выявить корень этой проблемы?


_________________
4-ех фаз хватает, что бы разогнать !!!8-ми ядерный!!! райзен до 3.8-3.9
Lopos, 13.10.2017

 
OLD Hunter

Member

Статус: Не в сети
Регистрация: 14.06.2009
Откуда: Омск

А что за сборка ПК, БП вот это все, где?
С чего началось, само по себе или после обновы какой то железки или всего компа? Фиксы от мельдония спектра пробовал отключать? Иногда это даёт эффект на некоторых сборках.

 
Y0!

Member

Статус: Не в сети
Регистрация: 02.06.2012
Откуда: Стольный Град

Применил частично твики по мануалу — фиг что изменилось…

OLD Hunter

Привет, снова заполнил. Фиксы отключены. Фризы были с самого начала этой сборки (всё куплено с нуля, кроме мыши, это и помогло выявить первичную проблему, как тогда казалось — неустановка Synapse 2 сводила фризы до самого минимума, но непроизвольное нажатие боковых кнопок всякий раз заставляло вернуться к Synapse и терпеть; потом были попытки разогнать мой «отборный» B-die, о них я писал тут в соответствующей теме, фризов от такого разгона становилось только больше; какое-то время назад фризы мне надоели и я начал писать в техподдержку NVIDIA, на тот момент винда уже была обновлена до 21H1).
Может быть, десятка всему виной, год назад пробовал ставить семёрку с кустарными USB3 драйверами (официальных-то нет) и мышь на семёрке, конечно, чувствуется просто прекрасно, но на тот момент я неудачно прошил BIOS и ловил BSOD за BSOD’ом с такими кодами, о которых раньше и не слышал, потому вернулся на десятку, снова прошил BIOS уже вроде без той проблемы и так с тех пор был на той же десятке, не знаю, когда точно началось то, что у меня сейчас. Не исключаю, что всё-таки какая-то железка выёживается — возможно, сама оперативка или контроллер памяти в проце, либо мои игры с BIOS таки оставили в ROM что-то лишнее, что уже не перезаписывается или перезаписывается неправильно (иронично, что шил BIOS из-под DOS при помощи frashrom как раз чтобы при прошивке BIOS не возникло ошибок вроде оставшихся от прошлого BIOS скрытых настроек), но об этом я самостоятельно уже не узнаю.

Техподдержка NVIDIA расписалась в собственном бессилии что-либо продиагностировать — сказали проверить видеокарту в другом компьютере, посоветовали обратиться к разработчику игры (и не важно, что игр две и они вообще разные, как и их разработчики). Что ж, когда выброшу этот комп на помойку и куплю новый — может, исправлю фризы.


_________________
4-ех фаз хватает, что бы разогнать !!!8-ми ядерный!!! райзен до 3.8-3.9
Lopos, 13.10.2017

 
OLD Hunter

Member

Статус: Не в сети
Регистрация: 14.06.2009
Откуда: Омск

Y0! Хм, тогда остается только в СЦ обратиться, железо же на гарантии еще?
Скорее всего какая-то несовместимость с МП или же что-то с БП, что менее вероятно. БП другой не проверялся?

 
Y0!

Member

Статус: Не в сети
Регистрация: 02.06.2012
Откуда: Стольный Град

OLD Hunter эта серия БП была в списке рекомендуемых тут в соответствующей теме, возможно, она и сейчас там.
Если неисправность нельзя обнаружить программно — подозреваю, что я просто зря просижу без компа несколько недель и мне вернут его с вердиктом «неисправность не обнаружена». Да и было бы спокойнее отдать только одну реально неисправную железку, а не весь комп — не знаю, что они на этом компе будут делать, может, станут майнить или специально повредят, чтобы снять всё с гарантии, тут барыги живут по принципу «не обманешь — не проживёшь».


_________________
4-ех фаз хватает, что бы разогнать !!!8-ми ядерный!!! райзен до 3.8-3.9
Lopos, 13.10.2017

 
BOBKOC

Advanced member

Статус: Не в сети
Регистрация: 30.03.2017
Откуда: Москва/Вешняки
Фото: 11

Y0! писал(а):

сказали & посоветовали

а может те win11 установить ради эксперимента + там у Nvidia уже WDM3.0 при дровах 471.22+

 
Dimonas

Member

Статус: Не в сети
Регистрация: 01.05.2005
Откуда: Краснодар

Y0!
Попробуй отключить максимально всё устройства в биосе и периферию. Даже звук и сетевую отключи на время теста. Проблема с фризами также останется?

 
OLD Hunter

Member

Статус: Не в сети
Регистрация: 14.06.2009
Откуда: Омск

Видео бы еще увидеть этих фризов, ну т.е с графиком фреймтайма. Ну у странно что они не во всех играх. На движке фростайбта они есть? Можно скачать что-то по типу бф3 или 4 , да любой бф, можно и более поздние, может и лиц есть. Там есть встроенный график производительности, там график и цпу и ГП, т.е можно точно определить откуда фриз — ЦП или ГП.

 
Y0!

Member

Статус: Не в сети
Регистрация: 02.06.2012
Откуда: Стольный Град

Вложение:

Комментарий к файлу: Вот скриншоты с моим комментарием на ломаном английском (в архиве).

.zip [3.06 МБ]

Скачиваний: 100

Я упомянул две игры, в которые я играл — CS:GO и BF5. В обеих — фризы.
Особенность происходящего в CS:GO в том, что фриз проявляется даже при нажатии на кнопки слева на начальном экране игры — на шестерёнку настроек, на знак вопроизведения (Play), и при смене изображения с начального на изображение окна настроек или окна поиска игры появляется заметный фриз, даже график фреймтайма не нужен, чтобы его видеть. То есть, минимум часть этих фризов — от появления нового изображения на экране взамен или поверх предыдущего (также фриз может случиться после нажатия на вызов консоли или вызов окна покупки оружия).
Я об этом написал в ТП стима, в ответ получил «мы не занимаемся проблемами производительности, чините свой комп» и эта говорящая кукла закрыла мой тикет, ТП nvidia отморозилась после того как я процитировал им этот ответ ТП стима и снабдил это комментарием, что первый уровень поддержки действует по методичке, когда она заканчивается — вся «поддержка» тоже заканчивается и единственная цель первого уровня ТП — не пустить проблему на уровень выше, где её могли бы решить (это был камень и в огород ТП nvidia, потому что своими домохозяечными ответами они уже просто достали).
Установил LTSC. У меня несколько аккаунтов Steam, после логина в часть из них фриз при открытии окон настроек и поиска игры в CS:GO не проявлялся, но после логина в один из следующих аккаунтов он снова стал появляться. Теперь буду ставить семёрку и там попробую попользоваться только одним аккаунтом стима (тем, на котором фриза временно не было).


_________________
4-ех фаз хватает, что бы разогнать !!!8-ми ядерный!!! райзен до 3.8-3.9
Lopos, 13.10.2017

Кто сейчас на конференции

Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 4

Вы не можете начинать темы
Вы не можете отвечать на сообщения
Вы не можете редактировать свои сообщения
Вы не можете удалять свои сообщения
Вы не можете добавлять вложения

High Latency on NVIDIA Windows Kernel Mode Driver

Discus and support High Latency on NVIDIA Windows Kernel Mode Driver in XBoX on Consoles to solve the problem; Hi, recently my PC has started to run games very poorly. This happened out of no where and ive tried everything I could think of. Usually I run GTA5…
Discussion in ‘XBoX on Consoles’ started by carlemil101, Dec 14, 2022.

  1. High Latency on NVIDIA Windows Kernel Mode Driver

    Hi, recently my PC has started to run games very poorly. This happened out of no where and ive tried everything I could think of. Usually I run GTA5 with 200+ fps but now its running 30-50 fps. This is happening in other games too. I cannot find the problem that is causing this. Ive tried running LatencyMon to see if could find the problem through there.
    I found that my «NVIDIA Windows Kernel Mode Driver» (nvlddmkm.sys) is running on a very high execution time (μs).

    Theres not a lot of help to find on the internet about this problem, atleast not anything that seemed to help me out.

    All of this happened after I updated to Windows 11. Ive now gone back to Window 10 but the issue is stille there

    Ive put the report text below

    _________________________________________________________________________________________________________

    CONCLUSION

    _________________________________________________________________________________________________________

    Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.

    LatencyMon has been analyzing your system for 0:02:02 (h:mm:ss) on all processors.

    _________________________________________________________________________________________________________

    SYSTEM INFORMATION

    _________________________________________________________________________________________________________

    Computer name: FONDK-NKE9KVSQ5

    OS version: Windows 10, 10.0, version 2009, build: 19045 (x64)

    Hardware: Z590 AORUS PRO AX, Gigabyte Technology Co., Ltd.

    BIOS: F7

    CPU: GenuineIntel Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz

    Logical processors: 16

    Processor groups: 1

    Processor group size: 16

    RAM: 16253 MB total

    _________________________________________________________________________________________________________

    CPU SPEED

    _________________________________________________________________________________________________________

    Reported CPU speed (WMI): 2904 MHz

    Reported CPU speed (registry): 2904 MHz

    Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

    _________________________________________________________________________________________________________

    MEASURED INTERRUPT TO USER PROCESS LATENCIES

    _________________________________________________________________________________________________________

    The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

    Highest measured interrupt to process latency (µs): 1410,30

    Average measured interrupt to process latency (µs): 8,136864

    Highest measured interrupt to DPC latency (µs): 1406,0

    Average measured interrupt to DPC latency (µs): 4,045040

    _________________________________________________________________________________________________________

    REPORTED ISRs

    _________________________________________________________________________________________________________

    Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

    Highest ISR routine execution time (µs): 164,584022

    Driver with highest ISR routine execution time: HDAudBus.sys — High Definition Audio Bus Driver, Microsoft Corporation

    Highest reported total ISR routine time (%): 0,004148

    Driver with highest ISR total time: HDAudBus.sys — High Definition Audio Bus Driver, Microsoft Corporation

    Total time spent in ISRs (%) 0,006008

    ISR count (execution time <250 µs): 55553

    ISR count (execution time 250-500 µs): 0

    ISR count (execution time 500-1000 µs): 0

    ISR count (execution time 1000-2000 µs): 0

    ISR count (execution time 2000-4000 µs): 0

    ISR count (execution time >=4000 µs): 0

    _________________________________________________________________________________________________________

    REPORTED DPCs

    _________________________________________________________________________________________________________

    DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

    Highest DPC routine execution time (µs): 1925,447314

    Driver with highest DPC routine execution time: nvlddmkm.sys — NVIDIA Windows Kernel Mode Driver, Version 527.56 , NVIDIA Corporation

    Highest reported total DPC routine time (%): 0,037301

    Driver with highest DPC total execution time: dxgkrnl.sys — DirectX Graphics Kernel, Microsoft Corporation

    Total time spent in DPCs (%) 0,141679

    DPC count (execution time <250 µs): 222293

    DPC count (execution time 250-500 µs): 0

    DPC count (execution time 500-10000 µs): 287

    DPC count (execution time 1000-2000 µs): 19

    DPC count (execution time 2000-4000 µs): 0

    DPC count (execution time >=4000 µs): 0

    _________________________________________________________________________________________________________

    REPORTED HARD PAGEFAULTS

    _________________________________________________________________________________________________________

    Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

    NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

    Process with highest pagefault count: msmpeng.exe

    Total number of hard pagefaults 76

    Hard pagefault count of hardest hit process: 42

    Number of processes hit: 10

    _________________________________________________________________________________________________________

    PER CPU DATA

    _________________________________________________________________________________________________________

    CPU 0 Interrupt cycle time (s): 9,122847

    CPU 0 ISR highest execution time (µs): 0,0

    CPU 0 ISR total execution time (s): 0,0

    CPU 0 ISR count: 0

    CPU 0 DPC highest execution time (µs): 1925,447314

    CPU 0 DPC total execution time (s): 2,067431

    CPU 0 DPC count: 178191

    _________________________________________________________________________________________________________

    CPU 1 Interrupt cycle time (s): 4,219907

    CPU 1 ISR highest execution time (µs): 164,584022

    CPU 1 ISR total execution time (s): 0,096688

    CPU 1 ISR count: 29134

    CPU 1 DPC highest execution time (µs): 387,669421

    CPU 1 DPC total execution time (s): 0,628755

    CPU 1 DPC count: 31048

    _________________________________________________________________________________________________________

    CPU 2 Interrupt cycle time (s): 1,428248

    CPU 2 ISR highest execution time (µs): 38,253444

    CPU 2 ISR total execution time (s): 0,004287

    CPU 2 ISR count: 1053

    CPU 2 DPC highest execution time (µs): 82,067493

    CPU 2 DPC total execution time (s): 0,030597

    CPU 2 DPC count: 2532

    _________________________________________________________________________________________________________

    CPU 3 Interrupt cycle time (s): 1,152199

    CPU 3 ISR highest execution time (µs): 0,0

    CPU 3 ISR total execution time (s): 0,0

    CPU 3 ISR count: 0

    CPU 3 DPC highest execution time (µs): 94,108815

    CPU 3 DPC total execution time (s): 0,003213

    CPU 3 DPC count: 662

    _________________________________________________________________________________________________________

    CPU 4 Interrupt cycle time (s): 1,237972

    CPU 4 ISR highest execution time (µs): 0,0

    CPU 4 ISR total execution time (s): 0,0

    CPU 4 ISR count: 0

    CPU 4 DPC highest execution time (µs): 78,214532

    CPU 4 DPC total execution time (s): 0,001330

    CPU 4 DPC count: 294

    _________________________________________________________________________________________________________

    CPU 5 Interrupt cycle time (s): 1,271155

    CPU 5 ISR highest execution time (µs): 0,0

    CPU 5 ISR total execution time (s): 0,0

    CPU 5 ISR count: 0

    CPU 5 DPC highest execution time (µs): 44,763085

    CPU 5 DPC total execution time (s): 0,001020

    CPU 5 DPC count: 296

    _________________________________________________________________________________________________________

    CPU 6 Interrupt cycle time (s): 1,547226

    CPU 6 ISR highest execution time (µs): 0,0

    CPU 6 ISR total execution time (s): 0,0

    CPU 6 ISR count: 0

    CPU 6 DPC highest execution time (µs): 95,733127

    CPU 6 DPC total execution time (s): 0,001341

    CPU 6 DPC count: 384

    _________________________________________________________________________________________________________

    CPU 7 Interrupt cycle time (s): 1,659259

    CPU 7 ISR highest execution time (µs): 0,0

    CPU 7 ISR total execution time (s): 0,0

    CPU 7 ISR count: 0

    CPU 7 DPC highest execution time (µs): 53,157025

    CPU 7 DPC total execution time (s): 0,003204

    CPU 7 DPC count: 936

    _________________________________________________________________________________________________________

    CPU 8 Interrupt cycle time (s): 1,973909

    CPU 8 ISR highest execution time (µs): 0,0

    CPU 8 ISR total execution time (s): 0,0

    CPU 8 ISR count: 0

    CPU 8 DPC highest execution time (µs): 79,880510

    CPU 8 DPC total execution time (s): 0,001380

    CPU 8 DPC count: 375

    _________________________________________________________________________________________________________

    CPU 9 Interrupt cycle time (s): 1,605381

    CPU 9 ISR highest execution time (µs): 0,0

    CPU 9 ISR total execution time (s): 0,0

    CPU 9 ISR count: 0

    CPU 9 DPC highest execution time (µs): 68,033058

    CPU 9 DPC total execution time (s): 0,006563

    CPU 9 DPC count: 1376

    _________________________________________________________________________________________________________

    CPU 10 Interrupt cycle time (s): 0,652097

    CPU 10 ISR highest execution time (µs): 0,0

    CPU 10 ISR total execution time (s): 0,0

    CPU 10 ISR count: 0

    CPU 10 DPC highest execution time (µs): 42,731749

    CPU 10 DPC total execution time (s): 0,000606

    CPU 10 DPC count: 243

    _________________________________________________________________________________________________________

    CPU 11 Interrupt cycle time (s): 0,659201

    CPU 11 ISR highest execution time (µs): 0,0

    CPU 11 ISR total execution time (s): 0,0

    CPU 11 ISR count: 0

    CPU 11 DPC highest execution time (µs): 36,504132

    CPU 11 DPC total execution time (s): 0,000719

    CPU 11 DPC count: 241

    _________________________________________________________________________________________________________

    CPU 12 Interrupt cycle time (s): 1,763088

    CPU 12 ISR highest execution time (µs): 44,046832

    CPU 12 ISR total execution time (s): 0,016640

    CPU 12 ISR count: 25366

    CPU 12 DPC highest execution time (µs): 80,166667

    CPU 12 DPC total execution time (s): 0,009128

    CPU 12 DPC count: 2615

    _________________________________________________________________________________________________________

    CPU 13 Interrupt cycle time (s): 1,520604

    CPU 13 ISR highest execution time (µs): 0,0

    CPU 13 ISR total execution time (s): 0,0

    CPU 13 ISR count: 0

    CPU 13 DPC highest execution time (µs): 67,975895

    CPU 13 DPC total execution time (s): 0,003542

    CPU 13 DPC count: 774

    _________________________________________________________________________________________________________

    CPU 14 Interrupt cycle time (s): 0,968114

    CPU 14 ISR highest execution time (µs): 0,0

    CPU 14 ISR total execution time (s): 0,0

    CPU 14 ISR count: 0

    CPU 14 DPC highest execution time (µs): 73,191116

    CPU 14 DPC total execution time (s): 0,007072

    CPU 14 DPC count: 1444

    _________________________________________________________________________________________________________

    CPU 15 Interrupt cycle time (s): 0,958771

    CPU 15 ISR highest execution time (µs): 0,0

    CPU 15 ISR total execution time (s): 0,0

    CPU 15 ISR count: 0

    CPU 15 DPC highest execution time (µs): 77,886364

    CPU 15 DPC total execution time (s): 0,007476

    CPU 15 DPC count: 1188

    :)

  2. High Latency on NVIDIA Windows Kernel Mode Driver

    hi i contacted my pc provider and they fixed it for me, the cpu cooler didnt work and the cpu was overheating

  3. High Latency on NVIDIA Windows Kernel Mode Driver

    1. download the updated chipset drivers from intel for windows 11

    2. use ddu in safe mode to remove the graphics driver and redownload the latest version and install, then restart the pc.

  4. High Latency on NVIDIA Windows Kernel Mode Driver

    You need to contact Nvidia or your hardware partner that made your card with these issues, they are the ones who can solve it.

  5. High Latency on NVIDIA Windows Kernel Mode Driver

    Display Driver Uninstaller Download version 18.0.5.9 (guru3d.com)

    The site above is the one you want

    it will completely remove all of the nvidia drivers and fully flush it out then you can install it from scratch.

  6. High Latency on NVIDIA Windows Kernel Mode Driver

    Can you tell me what DDU is?

Thema:

High Latency on NVIDIA Windows Kernel Mode Driver

  1. High Latency on NVIDIA Windows Kernel Mode Driver — Similar Threads — High Latency NVIDIA

  2. I have tested latency of Xbox series controller on two different laptops (one high end and…

    in XboX Insiders

    I have tested latency of Xbox series controller on two different laptops (one high end and…: I have tested latency of Xbox series controller on two different laptops (one high end and other one is 10 years old). Why am I not getting the Microsoft advertised latency which is 4 ms for wired…
  3. High Latency to Xbox Live (Routing Issue on Microsoft’s Network)

    in XBoX on Windows

    High Latency to Xbox Live (Routing Issue on Microsoft’s Network): Issue:
    I am experiencing consistently high latency (193-341ms) to Xbox Live servers, even though my internet connection is otherwise stable. This is making multiplayer gaming unplayable due to lag…
  4. Why is my xbox latency so high and what is the solution?

    in XBoX on Consoles

    Why is my xbox latency so high and what is the solution?: High latency on xbox. I bought fastest speed internet plan with isp and it didnt resolve the issue. I swapped old outdated modem for fastest newest modem from my isp and the latency is still at a…
  5. How do I fix high latency when everything else is really good and running well when the…

    in XBoX on Consoles

    How do I fix high latency when everything else is really good and running well when the…: My xbox has been having connection issues for a while now and I have tried a lot of stuff to fix it and it isn’t wifi cause my connection for upload speed and everything else is really good but…
  6. HIGH LATENCY WAS 173 BUT I CAN’T GET PASSED 148 MS ITS DRIVE ME CRAZY

    in XBoX on Consoles

    HIGH LATENCY WAS 173 BUT I CAN’T GET PASSED 148 MS ITS DRIVE ME CRAZY: Hi people GAZ HERE CAN ANY ONE please help or forward the bad news …and I’ll have to try start dealing with it…I know I’m not going to have xbox 1 run the same as xbox x. ….. as I have had…
  7. My latency is extremely high in I’m trying to fix it

    in XBoX on Consoles

    My latency is extremely high in I’m trying to fix it: I’m trying to get my latency to drop bro it’s not working for some reason

    f121275a-60c0-4280-91ae-a514021a76a1

  8. Need help fixing high latency on wired connection.

    in XBoX on Consoles

    Need help fixing high latency on wired connection.: I have an Xbox Series S on wired internet connection, with a download speed of 300 MB and upload of 75 MB. My latency in Xbox Network statistics and in Halo Infinite is of 100-140 ms. It’s…
  9. Very high latency can u please help me

    in XBoX on Consoles

    Very high latency can u please help me: have very hi latency on Xbox series s I ran a network test on test network speed & statistics and I’m getting a latency of 202 I believe that is causing me delay and lag on nba 2k24 can u please…
  10. Latency Variation’s and high ping despite seemingly good internet

    in XBoX on Consoles

    Latency Variation’s and high ping despite seemingly good internet: Hello, I recently have encountered issue where I have very high latency variation across all games. It happened seemingly overnight and have tried all sorts of things to resolve the issue. I tried…

Note: This post summarizes the entire thread so you do not have to read over 700 replies!

UPDATE (AUGUST 11TH, 2023)
You are probably reading this because you used LatencyMon and it revealed an issue in the Nvidia graphics driver. Everything you need to know is contained in this post, so keep reading. This thread started as an IRQ conflict, but evolved as we learned more, and eventually resulted in the discovery of several bugs causing high latency, which reveals itself in the form of stutters, freezes, crashing, and audio problems.

After months of research and testing, this thread prompted Nvidia and Microsoft to finally acknowledge these issues, which have plagued gamers and audio enthusiasts for many years. This thread also resulted in the creation of a guide that helps people optimize their computers for lower latency. It is important that we make a distinction here because half of these Deferred Procedure Call (DPC) issues are due to Nvidia and Microsoft bugs, while the other half come from computers that need optimizing.

The purpose of this thread was to identify the cause of the malfunctioning nvlddmkm.sys driver and find a tweak to mitigate it. While there were no reliable fixes discovered, Nvidia later added it to their open issues tracker, so we then waited for their response. Several updates were released to fix various bugs, and then an update specifically for the 3xxx series (Ampere architecture) was included because those cards had additional issues that were making the latency even worse. These fixes are included in drivers dated July 18th, 2023 or newer, and while legacy cards still receive security updates, it is unlikely they will get any other fixes, such as those related to DPC latency.

Other problems affecting Nvidia were bugs in the Desktop Window Manager (DWM) and Timeout Detection and Recovery (TDR) features. Microsoft has several preview fixes (link1, link2, link3, link4) for these, but it may be a while before they are available to everyone, and additional updates might be needed after the public has a chance to provide feedback. If the updates are finalized in time, they will be included in the ISO images (link5, link6) that Microsoft posts near the end of each year, and the best advice would be to do a clean install of Windows using those updated builds, and the latest Nvidia driver. Only Windows 10 and 11 will be receiving these updates.

For all other DPC issues, solutions have existed forever in the form of tweaking a computer for more performance. The Gaming Lounge (link7) has a huge list of important information regarding this. The takeaway here is to optimize, which means learning how to cleanly install the operating system, properly installing drivers and firmware, adjusting the BIOS for low latency, and using NTLite to slim down Windows.

Hopefully the Nvidia driver will be fully resolved by the start of 2024, but if the issues persist then all we can do is encourage everyone to submit support tickets to Nvidia and the Microsoft Feedback Hub, contact computer and gaming sites to have them write articles about it, and go to social media to continually remind these companies of the problem until it is addressed.

ORIGINAL POST (JULY 15TH, 2022)

LatencyMon reveals that nvlddmkm.sys (Nvidia Graphics driver kernel) has DPC latency spikes up to 800 microseconds fairly frequently. This is an extremely common issue that can be found all over Google, but I have not come across any solutions, except for a nonsensical one.

According to a post at LinusTechTips forum (link) this is happening because the graphics card is sharing an IRQ with a problematic device. On my computer, msinfo32.exe says the graphics card is sharing IRQ 16 with a motherboard USB host controller.

The solution is to force the IRQ to be reassigned, but the steps are extremely clunky. There has to be a better way than this? I already have an idea in mind that I will test tomorrow, where I will go into my BIOS and disable USB ports until I find the ones tied to this controller, and then move hardware around and reinstall Windows. This seems better than doing the steps listed in the solution, but may not help.

  1. Hi there, im currently having huge issues with DPC Latency on my computer making it almost impossible to play games without my sound cracking and poping and the game running slow

    ive downloaded the tool DPC Latency Checker and i run it 100% of the time im on my pc to monitor the issue and see if anything i do fixs it, my typical DPC latency when i have no problems is anywhere between 90 and 100 however, when the problem starts it shoots to over 20000 here is a picture of when the problem hits

    As you can see, it just skyrockets, now this red latency can last anywhere between 30 seconds and 30 minutes before returning back to normal green, it happens randomly more so when im playing games (call of duty modern warfare 2 for example) it also makes the game im playing stutter like i have 1 FPS, when it returns back to green my sound issue is gone and my game runs perfectly

    Im not the best with computers so disabling devices and stuff is new to me and im not sure which ones are safe to disable and which are not (except for System and Computer) i have the latest graphics and sound drivers and ive even tryed the default Windows 7 ones and 3 different Nvidia ones from the website and they changed nothing

    Somebody suggested i download the tool Latencymon so i did, i ran it when my dpc latency was not spiking and it reported no problems, however when the dpc latency spiked it reported the same problem over and over

    Also, the rest of the results it recorded whilst i had high dpc latency

    One or more DPC routines that execute on behalf of drivers running in your system appear to be causing serious problems making your system unsuitable for processing real time audio. You are likely to experience audio dropouts, clicks and pops.
    Time running: 0:04:59

    Highest DPC routine execution time (µs): 28821
    Responsible driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 260.99 , NVIDIA Corporation)
    DPC count (execution time <500 µs): 17351502
    DPC count (execution time 500-999 µs): 0
    DPC count (execution time 1000-1999 µs): 0
    DPC count (execution time 2000-3999 µs): 0
    DPC count (execution time >=4000 µs): 29

    Highest ISR routine execution time (µs): 79
    Responsible driver: dxgkrnl.sys (DirectX Graphics Kernel, Microsoft Corporation)
    ISR count (execution time <250 µs): 16799994
    ISR count (execution time 250-499 µs): 0
    ISR count (execution time 500-999 µs): 0
    ISR count (execution time 1000-1999 µs): 0
    ISR count (execution time >=2000 µs): 0

    Highest pagefault resolution time (µs): 171192
    Hard pagefault count (total): 100152
    Number of processes hit: 24
    Pagefault count of hardest hit process: 82207
    Process with highest pagefault count: MsMpEng.exe (PID: 920)

    NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

    Note: all execution times are calculated based on a CPU clock speed of 4011 MHz. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

    This is beyond me whats causing it but its got to the point where i simply cannot put up with it anymore and i need to find a fix any help you guys can give me would be greatly appreciated as its making gaming extremely hard to do

    System Specification
    — Power Supply: Corsair TX 650W ATX SLi Compliant Power Supply
    — CPU: Intel Core i7 950 3.06GHz Overclocked to 4.00GHz
    — Motherboard: Gigabyte EX58A-UD3R Intel X58 (Socket 1366) PCI-Express DDR3 Motherboard
    — Cooler: Prolimatech Megahalems Rev B CPU Cooler with Sharkoon Silent Eagle 2000rpm 120mm Fan
    — RAM: Corsair XMS3 6GB (3x2GB) DDR3 PC3-12800C8 (1600MHz) Tri-Channel
    — Hard Drive: Seagate Barracuda 7200.12 1TB SATA-II 32MB Cache
    — Graphics Card: NVIDIA GeForce GTX 460
    — Sound: Realtek ALC889 7.1 Channel Sound (On-Board)
    — Optical Drive: LG DVD+/-RW SATA Drive
    — Windows 7 64-Bit

  2. Your drivers are ALL up to date? Chipset, Sound, NIC, Mouse, DirectX, Windows Update and any low level drivers updated (AV etc)?

  3. Im not sure where to download the chipset and NIC drivers (sorry im not very good at this stuff) but i do have everything else

    NIC: Realtek PCIe GBE Family Controller
    Chipset: Intel X58

  4. Hey thanks for finding those for me, the realtek one just takes me to the main page however

    When i go to install the chipset drivers it tells me i have a newer version and do i wish to install the older one, does this mean i do not need to update or shall i just install the older ones?

    Thanks

  5. Just got 3 new things come up in the LAtencymon monitor tab..sigh i dont even know what to do anymore it appears it isnt just a nvidia driver

    USBPORT.SYS USB 1.1 & 2.0 Port Driver
    dxgkrnl.sys DirectX Graphics Kernel
    ataport.SYS ATAPI Driver extension

  6. i havent have realtec installed for while, but can u try disable any features like «virtual 7.1» or similar if there is and then try again to start app and see if it spikes

    sry for grammar

  7. I dont have anything called that or similar

  8. set 2 speakers only, thats what i ment

  9. Didnt make a difference :|

  10. Carfax
    Ancient Guru

    Messages:
    4,792
    Likes Received:
    2,137
    GPU:

    Make sure you’re running the latest BIOS for your motherboard, and that CIE power management is disabled in the BIOS, EIST, plus any other power saving options. Sometime these settings can cause the DPC latency to spike, so just try fiddling with them.

    I see you also have a Gigabyte motherboard, so make sure that Easytune and Dynamic Energy saver etc is disabled as these are definitely known to cause problems.

    Also, make sure HPET (High precision event timer) is enabled in the BIOS. Sometimes disabling HPET can also lower DPC latency big time as well, so just test it out.

    Last edited: Nov 15, 2010

Share This Page

Понравилась статья? Поделить с друзьями:
0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии
  • Windows 10 format exfat
  • Что значит windows 7 oem marker present in firmware
  • Windows 10 язык для каждого окна
  • Antimalware service executable грузит память windows 10 решение проблемы
  • Как сейчас поставить windows