Куратор(ы):
eLfiK
Автор | Сообщение | |||
---|---|---|---|---|
|
||||
Member Статус: Не в сети |
Обсуждение проблем ОС и оборудования: задержка реакции системы (latency), микроcтаттер, инпутлаг, фризы. Осуществлять мониторинг программой Latency Monitor нужно в течение 1 минуты, в состоянии простоя системы т.е. без дисковой, сетевой активности, и любой другой, с выключенным ав и приложениями в трее и автозагрузке, Презентация NVIDIA (на англ.) о проблемах статтеров, фризов и лагов (терминология, описание и причины возникновения) Последний раз редактировалось iG0Lka 07.02.2018 15:48, всего редактировалось 8 раз(а). |
Реклама | |
Партнер |
Phenomenum |
|
Member Статус: Не в сети |
yylseijfvlu0 Железо напиши, пожалуйста. Все, что есть. И ответь на все мои вопросы. |
Y0! |
|
Member Статус: Не в сети |
Привет. BIOS сброшен в дефолт, вручную не изменено ничего, версия 5851 (последняя от ASUS). Винда — десятка корпоративная 21H1 (не сборка) из образа с обновлениями от июня 2021, не изменены никакие настройки (разве что убрана галочка с повышенной точности указателя мыши), не удалено ничего, из драйверов установлен только графический 471.22 без geforce experience (чистая установка), никакие другие драйверы не ставил, так что стоит только то, что было встроено в винду. В предыдущий раз пробовал ставить все самые новые драйверы, но ничего это не исправило, потому сейчас поставил только видео. Показатели LatencyMon (снято во время работы CS:GO) какие-то слишком пугающие. Interrupt to user process latency Код: _________________________________________________________________________________________________________ _________________________________________________________________________________________________________ _________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________ Highest measured interrupt to process latency (µs): 2988,40 Highest measured interrupt to DPC latency (µs): 2985,0 _________________________________________________________________________________________________________ Highest ISR routine execution time (µs): 259,614807 Highest reported total ISR routine time (%): 0,266056 Total time spent in ISRs (%) 0,269609 ISR count (execution time <250 µs): 760454 _________________________________________________________________________________________________________ Highest DPC routine execution time (µs): 6000,838297 Highest reported total DPC routine time (%): 0,122476 Total time spent in DPCs (%) 0,189475 DPC count (execution time <250 µs): 1577122 _________________________________________________________________________________________________________ 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 _________________________________________________________________________________________________________ Interrupt to DPC latency Код: _________________________________________________________________________________________________________ _________________________________________________________________________________________________________ _________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________ Highest measured interrupt to DPC latency (µs): 4408,0 _________________________________________________________________________________________________________ Highest ISR routine execution time (µs): 263,462288 Highest reported total ISR routine time (%): 0,360598 Total time spent in ISRs (%) 0,365003 ISR count (execution time <250 µs): 707634 _________________________________________________________________________________________________________ Highest DPC routine execution time (µs): 6007,821876 Highest reported total DPC routine time (%): 0,170995 Total time spent in DPCs (%) 0,254326 DPC count (execution time <250 µs): 1458428 _________________________________________________________________________________________________________ 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 _________________________________________________________________________________________________________ Kernel timer latency Код: _________________________________________________________________________________________________________ _________________________________________________________________________________________________________ _________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________ Highest measured kernel timer latency (µs): 26668,10 _________________________________________________________________________________________________________ Highest ISR routine execution time (µs): 291,035903 Highest reported total ISR routine time (%): 0,363446 Total time spent in ISRs (%) 0,367381 ISR count (execution time <250 µs): 1001708 _________________________________________________________________________________________________________ Highest DPC routine execution time (µs): 5995,026997 Highest reported total DPC routine time (%): 0,174894 Total time spent in DPCs (%) 0,263101 DPC count (execution time <250 µs): 1984892 _________________________________________________________________________________________________________ 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 _________________________________________________________________________________________________________ |
Dimonas |
|
Member Статус: Не в сети |
Y0! писал(а): оказатели LatencyMon (снято во время работы CS:GO) какие-то слишком пугающие. Показатели надо снимать в простое. FAQ читал? |
Y0! |
|
Member Статус: Не в сети |
Dimonas так лучше?.. Вложение:
Вложение:
В msconfig была снята галочка с элементов автозагрузки, скрыты службы Майкрософт и отключены все прочие службы, сразу после загрузки рабочего стола был запущен последний LatencyMon. Проблема проявляется в микрофризах в CS:GO, BFV, некоторые из них, возможно, появляются перед проигрыванием любых внутриигровых звуков. Тестирование проводилось как с разнообразными твиками (которые могут помочь при первом запуске после их применения, но потом всё возвращается), так и на девственно чистой корпоративной десятке, драйверы — самые-самые новые, пробовал не ставить драйвер аудио, мыши, видеодрайвер всегда ставится без GeForce Experience, как в одиночку, так и в сочетании с комплектным HD аудиодрайвером, USBC и PhysX. Пробовал разные USB порты. Около года назад значительно уменьшить количество микрофризов помогала неустановка драйвера мыши, но сейчас и это ничего не меняет. |
Dimonas |
|
Member Статус: Не в сети |
Y0! писал(а): Проблема проявляется в микрофризах в CS:GO, BFV, некоторые из них, возможно, появляются перед проигрыванием любых внутриигровых звуков. По скринам трудно сказать в чем у тебя проблема. Драйверы мыши? Без них никак? И что за драйверы VMware в системе? Винда точно свежеустановлена? |
Y0! |
|
Member Статус: Не в сети |
Dimonas можно и без драйвера мыши, вот сейчас его нет, но это ничего к лучшему не меняет. Возможно, это аппаратная проблема — винда, на которую из дров я поставил только видео, а также Steam (для тестирования фризов), умудрилась упасть в BSOD 1000007e (ntfs.sys), когда Steam скачивал CS:GO. В системе два диска — 860 evo (винда и всё, что на неё установлено) и обычный винчестер 7200 об., первый вчера сканировал samsung magician’ом, второй — chkdsk /f /r, ошибок не найдено. |
Y0! |
|
Member Статус: Не в сети |
Вложение:
|
BOBKOC |
|
Member Статус: Не в сети |
так то криминала не видно, но можешь поэкспериментить с переводом в msi режим видюхи и аудио. ребутаться ток надо при каждом применении + проверять применилось ли |
Y0! |
|
Member Статус: Не в сети |
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, но фризы полностью не исчезают. После этих твиков может при первом запуске чувствоваться очень низкая задержка мыши, но это почему-то быстро пропадает и потом может случайным образом снова проявляться, закономерности не замечено. |
Dimonas |
|
Member Статус: Не в сети |
Y0! Таймеры и приоритеты прерываний можно не крутить было. По моим наблюдениям это мало что дает в играх. А вот с фризами системы в первую очередь надо проверять связку процессор-память. Попробовать обновить биос материнки до последней версии с новой AGESA, поставить XMP тайминги и CMD 2T для стабильности. Я лично наблюдал ситуацию, когда в CMD 1T все тесты памяти без ошибок, а в PUBG фризы были. Поставил CMD 2T и проблема ушла. |
Y0! |
|
Member Статус: Не в сети |
Dimonas BIOS, как указывал, самый новый. Пробовал ставить всё в авто и тогда ставится режим 2400 CL19, попробовал прописать то же, что прописывается в D.O.C.P., но с 2T вместо 1T. 2T применилось, но фризит по-прежнему. Сейчас прерывания не изменены, я просто написал то, что тестировал в недалёком прошлом. Интересно, как всё же выявить корень этой проблемы? |
OLD Hunter |
|
Member Статус: Не в сети |
А что за сборка ПК, БП вот это все, где? |
Y0! |
|
Member Статус: Не в сети |
Применил частично твики по мануалу — фиг что изменилось… OLD Hunter Привет, снова заполнил. Фиксы отключены. Фризы были с самого начала этой сборки (всё куплено с нуля, кроме мыши, это и помогло выявить первичную проблему, как тогда казалось — неустановка Synapse 2 сводила фризы до самого минимума, но непроизвольное нажатие боковых кнопок всякий раз заставляло вернуться к Synapse и терпеть; потом были попытки разогнать мой «отборный» B-die, о них я писал тут в соответствующей теме, фризов от такого разгона становилось только больше; какое-то время назад фризы мне надоели и я начал писать в техподдержку NVIDIA, на тот момент винда уже была обновлена до 21H1). Техподдержка NVIDIA расписалась в собственном бессилии что-либо продиагностировать — сказали проверить видеокарту в другом компьютере, посоветовали обратиться к разработчику игры (и не важно, что игр две и они вообще разные, как и их разработчики). Что ж, когда выброшу этот комп на помойку и куплю новый — может, исправлю фризы. |
OLD Hunter |
|
Member Статус: Не в сети |
Y0! Хм, тогда остается только в СЦ обратиться, железо же на гарантии еще? |
Y0! |
|
Member Статус: Не в сети |
OLD Hunter эта серия БП была в списке рекомендуемых тут в соответствующей теме, возможно, она и сейчас там. |
BOBKOC |
|
Member Статус: Не в сети |
Y0! писал(а): сказали & посоветовали а может те win11 установить ради эксперимента + там у Nvidia уже WDM3.0 при дровах 471.22+ |
Dimonas |
|
Member Статус: Не в сети |
Y0! |
OLD Hunter |
|
Member Статус: Не в сети |
Видео бы еще увидеть этих фризов, ну т.е с графиком фреймтайма. Ну у странно что они не во всех играх. На движке фростайбта они есть? Можно скачать что-то по типу бф3 или 4 , да любой бф, можно и более поздние, может и лиц есть. Там есть встроенный график производительности, там график и цпу и ГП, т.е можно точно определить откуда фриз — ЦП или ГП. |
Y0! |
|
Member Статус: Не в сети |
Вложение: Комментарий к файлу: Вот скриншоты с моим комментарием на ломаном английском (в архиве).
Я упомянул две игры, в которые я играл — CS:GO и BF5. В обеих — фризы. |
—
Кто сейчас на конференции |
Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 11 |
Вы не можете начинать темы Вы не можете отвечать на сообщения Вы не можете редактировать свои сообщения Вы не можете удалять свои сообщения Вы не можете добавлять вложения |
Лаборатория
Новости
17078
Views
16
Replies
11
Participants
Last post by
zGunBLADEz,
Is there any way i can reduce the latency ? Is this the normal latency ? Since my cpu doesn’t have integrated igpu. My gpu driver version 456.55 tried the latest driver but it cause it even more up to 10. Thanks
My system:
Ryzen 5 3600
Rtx 2060
B450 tomhawk max
512 gb transcend ssd
corsair cx650 bronze psu
16 gigs ram 3200 mhz
See less
See more
2
This spike is happening when the p-state changes. I wouldn’t worry about it as the same thing happens with my RTX 3090. P-state changes always have a DPC spike.
This spike is happening when the p-state changes. I wouldn’t worry about it as the same thing happens with my RTX 3090. P-state changes always have a DPC spike.
Yeah, this is only a problem if you want it to be one. However, if this is related to p-states, setting power management to prefer maximum performance should solve it, right?
This spike is happening when the p-state changes. I wouldn’t worry about it as the same thing happens with my RTX 3090. P-state changes always have a DPC spike.
I am not getting spikes tho. Like when i am using chrome playing video or playing cod mw my latency stays 1.2+
Nvidia has a problem with DPC latency every single launch of new GPUs as they update their drivers, break crap ton of things in process and fail to realize that driver latency matters and they bloat it up.
And yes alt+tab etc. makes this tools fairly useless as you need to see live values not just max, max often happens during changes of window focus, change of state, …
Thats normal. Been a issue since Maxwell drivers and they just dont care.
Is this an AMD only issue?
No issues on my Maximus 12 extreme and 3090.
See less
See more
1
Is this an AMD only issue?
No issues on my Maximus 12 extreme and 3090.View attachment 2463537
its probably more a per system scenario, i wouldnt doubt it. either that or we all put our tinfoil hats on, and say intel is paying off nvidia
also, to OP: i am doubting, in any real world scenario, that your going to notice that 1ms delay, if it was 4 or 5 you might.
Reactions:
1
Is this an AMD only issue?
No issues on my Maximus 12 extreme and 3090.View attachment 2463537
You ran it for a minute and did nothing. If he did the same thing his would look like yours. Now with LatencyMon running go open a Twitch stream in Google Chrome or a game and watch the spike happen. Post what yours looks like and I bet you it looks the same. P-state changes cause the spike. It is normal.
Bullshit.
I was running Heaven benchmark at the same time. I do not like nor appreciate when people accuse me of something I didn’t do.
Here. Take this and shove it. Sorry for knowing how to maintain my system correctly.View attachment 2463614
I have no trouble achieving low DPC latency on nvlddmkm either.
My power management is fully enabled in BIOS. These are 30+ minute runs. Even on balanced the numbers are not terrible either.
On balance mode
On Ultimate Performance
-
2.5 MB
Views: 105 -
2.5 MB
Views: 141
See less
See more
4
Disable sysmain service.. restart windows and try latencymon again
I have no trouble achieving low DPC latency on nvlddmkm either.
My power management is fully enabled in BIOS. These are 30+ minute runs. Even on balanced the numbers are not terrible either.On balance mode
View attachment 2463627
On Ultimate Performance
View attachment 2463628
Thank you.
It’s sad that some people think that just because someone has a problem, that everyone else must have a problem, and you literally have to record 30 minute videos of multiple games and benchmarks running at the same time to convince them it’s their system that’s at fault, not ours
Thank you.
It’s sad that some people think that just because someone has a problem, that everyone else must have a problem, and you literally have to record 30 minute videos of multiple games and benchmarks running at the same time to convince them it’s their system that’s at fault, not ours
You are a clown you still haven’t posted what I asked since I mentioned it was specific to the RTX 3090. You are confusing me with the OP. I do not have any latency issues as well.
Is there any way i can reduce the latency ? Is this the normal latency ? Since my cpu doesn’t have integrated igpu. My gpu driver version 456.55 tried the latest driver but it cause it even more up to 10. Thanks
My system:
Ryzen 5 3600
Rtx 2060
B450 tomhawk max
512 gb transcend ssd
corsair cx650 bronze psu
16 gigs ram 3200 mhzView attachment 2463490
View attachment 2463493
Disable sysmain service.. restart windows and try latencymon again
The DPC latency as far as I remember is a major problem for «real time» users such as audio engineers and why they may avoid Nvidia GPUs entirely, cherry pick an OS or entire platform.
Sometimes the DPC latency was so bad it can cause problems even for regular users.
All you can do is submit bug reports directly at Nvidia’s site and complain to the internet, trying to get attention and Nvidia noticing that it’s being talked negatively about for a reason and fix that reason.
Back when Pascal launched, I’ve had the high DPC too, everyone pretty much suffers from it with new NV GPUs or even just new generation/major update of NV drivers.
See less
See more
M12 extreme + 3090 strix oc and have this problem big time.
first it was acpi.sys breaking havoc and after stopping monitoring the EC sensors on the mb it resolved but nvlddmkm.sys dpc is still crazy high.
The DPC latency as far as I remember is a major problem for «real time» users such as audio engineers and why they may avoid Nvidia GPUs entirely, cherry pick an OS or entire platform.
Sometimes the DPC latency was so bad it can cause problems even for regular users.All you can do is submit bug reports directly at Nvidia’s site and complain to the internet, trying to get attention and Nvidia noticing that it’s being talked negatively about for a reason and fix that reason.
Back when Pascal launched, I’ve had the high DPC too, everyone pretty much suffers from it with new NV GPUs or even just new generation/major update of NV drivers.
it also affects frametimes ALOT…
- This is an older thread, you may not receive a response, and could
be reviving an old thread. Please consider creating a new thread.
Содержание
- Высокие задержки DPC в видеокартах NVIDIA GTX 10-х серий и метод решения этой проблемы
- реклама
- реклама
- реклама
- реклама
- Nvidia windows kernel mode driver dpc latency
- DPC Latency Caused by Nvidia Drivers
- NVIDIA Windows Kernel Module Driver high latency causing in game microstutter.
- nevermore15
- High DPC Latency (nvlddmkm.sys, dxgkrnl.sys, Wdf01000.sys, ACPI.sys)
- levider
Высокие задержки DPC в видеокартах NVIDIA GTX 10-х серий и метод решения этой проблемы
До сих пор еще, очень много пользователей имеют в своих компьютерах видеокарты Nvidia 10-ой серии GTX 1060, GTX 1070, GTX 1080. Их владельцы по причине массового безумства, называемого майнингом, так и не смогли их поменять на видеокарты 20 и 30 серии по известным причинам. Потому данная серия видеокарт на сегодняшний день является актуальной для пользователей. И я не являюсь исключением, у меня есть компьютер с видеокартой PALIT JETSTREAM GTX 1070.
реклама
Майнинг нас всех вынудил сделать шаг назад по поколениям комплектующих. В начале 2020 года я думал, что моя видеокарта доживает уже последние дни своей актуальности. А сейчас понимаю, что она полностью актуальна на сегодняшний день, в связи со сложившейся ситуацией на рынке видеокарт.
В этой статье хочу поделиться с читателями о том, как компания NVIDIA в очередной раз «села в лужу» с видеокартами 10-й серии, причем конкретно так села, и до сих пор так и не смогла устранить имеющиеся с ними проблемы. Видеокарты Nvidia 10 серии прославились фризами и подвисаниями в играх, несмотря на высокие значения FPS при этом. Разбираться с этим вопросом я стал после того, как сам столкнулся с такими проблемами на своей видеокарте GTX 1070. Причем изменение настроек в любых их вариантах проблему не решило, фризы никуда не исчезли. Единственная настройка в драйвере видеокарты (в панели управления NVIDIA), которая хотя бы несколько уменьшила фризы, это включение на «ультра» режима низкой задержки.
реклама
Ответ компании NVIDIA, что проблема решена..
реклама
Последующая жалоба в компанию NVIDIA о нерешенной проблеме.
Никакие программные ухищрения к устранению данной проблемы не привели. А драйвера начиная с версии 386.95 с хост-фиксом, это такая себе полумера, для отвода глаз, которая проблему окончательно так и не решила, и после выпуска этого драйвера жалобы так и не прекратились. У меня вообще сложилось впечатление, что компания NVIDIA специально, осознанно «завалила» этот параметр задержек, чтобы за счет его ухудшения улучшить другие, по которым оценивается производительность в синтетических тестах, таким образом, для значительного повышения FPS они и создали эту неправильную работу системных таймеров прерываний. И получается, что в тестах все прекрасно, а играть невозможно.
Данную проблему еще усугубляет «количество подготовленных кадров», опция этого параметра так же находится в панели управления NVIDIA. Подготовленные кадры, так сказать кадры, хранящиеся в запасе, необходимы для того, чтобы поступление их на рендеринг в видеокарту от центрального процессора было непрерывным, даже если центральный процессор «затупит», и не успеет подготовить очередной кадр в срок по какой-либо причине. Эта функция не позволяет видеокарте простаивать в момент отсутствия очередного кадра от центрального процессора, кадр берется из запаса. Так же эта функция повышает FPS (количество кадров в секунду), но она значительно увеличивает задержки DPC, и для уменьшения задержек необходимо эту функцию отключить, или свести к минимуму количество подготовленных кадров.
Приведу для примера измерение задержек в своем компьютере с помощью программы «LatencyMon». Она в режиме реального времени проводит измерение задержек, и в случае превышения задержек, в скобках указывает виновника.
реклама
В первом случае отключаю драйвер видеокарты NVIDIA путем отключения устройства «NVIDIA GeForce GTX 1070» в диспетчере устройств, видеокарта в этом случае будет работать без драйвера, и провожу измерение задержек.
И по результату измерений видно, что программа «LatencyMon» ничего касающегося видеокарты, как виновника больших задержек не указала. А указала сетевой драйвер (network driver interface specification).
Теперь включаю драйвер видеокарты NVIDIA путем включения устройства «NVIDIA GeForce GTX 1070» в диспетчере устройств, и провожу повторно измерение.
И теперь видно, что программа «LatencyMon» указала виновника в больших задержках, которые составляют 551 мкс. И это драйвер видеокарты NVIDIA версии 465.89.
Что бы хотелось посоветовать для уменьшения эффекта фризов в видеокартах NVIDIA GTX 10-х серий:
1. В настройках панели управления NVIDIA, в режиме управления электропитанием установить режим максимальной производительности.
2. В настройках панели управления NVIDIA, режим низкой задержки обязательно включить на «ультра».
3. В настройках панели управления NVIDIA, максимальное количество заранее подготовленных кадров установить на минимум.
Сталкивались ли вы с такой проблемой в видеокартах NVIDIA GTX 10-х серий? И как вы их решили? Пишите в комментариях.
Источник
Как уже не раз говорилось – не у всех и не всегда настройки из данного гайда дадут хорошие результаты в плане FPS, но в первую очередь он предназначен для уменьшения задержек с чем он должен справится у большинства.
Все тесты сделаны в чистой Windows (всё настроено и используется по-умолчанию), но с обновлёнными драйверами nVidia, а в качестве оппонента выступает та же Windows, но уже настроенная по гайду. Следует учитывать, что как и все тесты они не показывают полноты всей картины, разбежки между запусками это нормально, поэтому приведены средние результаты.
Версии используемые в тестах:
Благодаря nVidia тут замечательно видно, что основу моих задержек составляют именно её драйверы (к слову, на предыдущей версии результаты были получше), а борьба с этим отдельный вид искусства. Так же эти результаты не показывают идеальный вариант, а весьма наглядно демонстрируют что улучшилось и с чем еще предстоит бороться.
‼️ Рекомендуется после обновления драйверов nVidia смотреть с помощью LatencyMon не стало ли хуже и, весьма вероятно, имеет смысл откатить драйвер на предыдущую версию.
Результаты LatencyMon после настройки:
Результаты LatencyMon до настройки:
Результаты LatencyMon после настройки:
Результаты LatencyMon до настройки:
Для оценки можно придерживаться примерно таких оптимальных цифр в результатах статистики:
Если ваши значения не больше чем в два раза, то есть смысл для более детального решения проблемы – поиска проблемных устройств или драйверов (о чём будет ниже). Если же ваши значения больше на несколько порядков, то что-то в вашей системе явно не так.
Результаты LatencyMon после настройки:
Результаты LatencyMon до настройки:
На этой вкладке можно увидеть какие именно драйверы влияют на задержки и исходя из показателей искать решение.
Основной список системных драйверов:
Результаты LatencyMon после настройки:
Результаты LatencyMon до настройки:
Здесь можно более подробно посмотреть как распараллелены драйверы по ядрам и их загрузка.
В качестве дополнительной оптимизации так же можно попробовать перенести драйвер сетевого адаптера на другое ядро, но по-хорошему, кроме печальной или не очень статистики, с этим мы вряд ли можем что-то сделать не угробив в дальнейшем Windows.
Для облизывания на FPS мы будем использовать популярный синтетический стресс-тест FurMark [скачать] для оценки производительности в Open GL.
Результаты FurMark после настройки:
Результаты FurMark до настройки:
✨ Кроме того, не стоит пренебрегать такими решениями как MSI Afterburner и настройками в BIOS для увеличение производительности GPU и CPU. Поэтому результаты в играх при правильном подходе будут показывать еще больший прирост в производительности.
Источник
DPC Latency Caused by Nvidia Drivers
Processor | AMD Ryzen 3700X |
---|---|
Motherboard | Asus X570 TUF Gaming Plus |
Cooling | NZXT Kraken X62 |
Memory | G.Skill 2x8GB 3600CL16 |
Video Card(s) | Asus Strix RTX 2070 |
Storage | Samsung 850 SSD 500GB |
Display(s) | Acer Predator XB271HU |
Case | NZXT S340 Elite |
I dont edit audio, but I am after tweaking my system. I’ve used DPC Latency Checker to measure the systems latency and found it is most likely caused by the Nvidia drivers. Nvidia has addressed this in the past and claims it was fixed.
Setup: AMD 3700X set to 4.0Ghz constant, with C-States disabled. GPU RTX 2070 no OC. Fresh install o Windows 10 2004 build 19041.421, only Windows10 default drivers and Nvidia Driver 451.85 is installed. Tried also moded W10 with removed bloatware (Superlite edition). Also removed all possibly AMD, Intel, Nvidia by Windows installed drivers with Display Driver Uninstaller and installed Nvidia Driver only, without PhysX, HD Audio, Experience, USB-C.
When I disable the Nvidia Driver in Device Manager
The latency is a lot lower
I did not try older Nvidia drivers as I like the Max Frame Rate option in the newer driver versions. As I dont have to run Riva Tuner or any additional software to have a fixed max frame rate.
I’ve ruled out HPET On/Off tweaking as the latency result was reproducible when disabling the Nvidia driver.
Источник
NVIDIA Windows Kernel Module Driver high latency causing in game microstutter.
nevermore15
Active member
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.
Total time spent in ISRs (%) 0.007531
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.
Total time spent in DPCs (%) 0.848527
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
_________________________________________________________________________________________________________
Источник
High DPC Latency (nvlddmkm.sys, dxgkrnl.sys, Wdf01000.sys, ACPI.sys)
levider
Member
Hello guys
I have huge problem with high DPC latency on my Omen laptop
1. I reinstalled Nvidia drivers (now without PhysX, only main driver)
2. I tried to disable Device Manager > Battery > something called battery control to solve ACPI.sys problem. And it worked, but my second monitor doesn’t work :/
_________________________________________________________________________________________________________
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:02:42 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2496 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): 3244,301037
Average measured interrupt to process latency (µs): 13,158952
Highest measured interrupt to DPC latency (µs): 3236,506182
Average measured interrupt to DPC latency (µs): 3,636769
_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.
Total time spent in ISRs (%) 0,012927
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.
Total time spent in DPCs (%) 0,422731
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: latmon.exe
Total number of hard pagefaults 598
Hard pagefault count of hardest hit process: 422
Number of processes hit: 15
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 10,463318
CPU 0 ISR highest execution time (µs): 491,963942
CPU 0 ISR total execution time (s): 0,078858
CPU 0 ISR count: 6069
CPU 0 DPC highest execution time (µs): 2323,189904
CPU 0 DPC total execution time (s): 2,611212
CPU 0 DPC count: 278151
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 2,031970
CPU 1 ISR highest execution time (µs): 90,870994
CPU 1 ISR total execution time (s): 0,003447
CPU 1 ISR count: 637
CPU 1 DPC highest execution time (µs): 413,272436
CPU 1 DPC total execution time (s): 0,070354
CPU 1 DPC count: 3115
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 2,661673
CPU 2 ISR highest execution time (µs): 22,421474
CPU 2 ISR total execution time (s): 0,001042
CPU 2 ISR count: 242
CPU 2 DPC highest execution time (µs): 279,509615
CPU 2 DPC total execution time (s): 0,021926
CPU 2 DPC count: 1688
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2,487784
CPU 3 ISR highest execution time (µs): 3,746795
CPU 3 ISR total execution time (s): 0,000444
CPU 3 ISR count: 198
CPU 3 DPC highest execution time (µs): 409,529647
CPU 3 DPC total execution time (s): 0,036582
CPU 3 DPC count: 2471
_________________________________________________________________________________________________________
Driver file Description ISR count DPC count Highest execution (ms) Total execution (ms) Image base Image size Company Product Version Path
————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
Источник
Typically my computer averages somewhere in the low teen’s to low thirties according to Latencymon. However, I noticed recently that I’ve been getting massive spikes in latency related to dxgkrnl.sys and nvlddmkm.sys. My BIOS is updated to the most recent release and I’ve uninstalled all the useless bloatware that comes with Win 10 (Cortana, Game Bar etc..) Can anyone help me figure out what the issue is? Here’s the Latencymon breakdown from earlier today:
_________________________________________________________________________________________________________
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. Also one or more ISR 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 5:07:39 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: MY-PC
OS version: Windows 10 , 10.0, build: 18363 (x64)
Hardware: ASUSTeK COMPUTER INC., Z170-A
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Logical processors: 8
Processor groups: 1
RAM: 16322 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 4008 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.
WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.
_________________________________________________________________________________________________________
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): 2679.50
Average measured interrupt to process latency (µs): 2.151481
Highest measured interrupt to DPC latency (µs): 2675.0
Average measured interrupt to DPC latency (µs): 0.724937
_________________________________________________________________________________________________________
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): 1241.473802
Driver with highest ISR routine execution time: dxgkrnl.sys — DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0.001431
Driver with highest ISR total time: dxgkrnl.sys — DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0.001628
ISR count (execution time <250 µs): 111676
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 2824
ISR count (execution time 1000-1999 µs): 10
ISR count (execution time 2000-3999 µ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): 3467.046906
Driver with highest DPC routine execution time: nvlddmkm.sys — NVIDIA Windows Kernel Mode Driver, Version 445.87 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0.001196
Driver with highest DPC total execution time: iaStorA.sys — Intel(R) Rapid Storage Technology driver — x64, Intel Corporation
Total time spent in DPCs (%) 0.005295
DPC count (execution time <250 µs): 1519989
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 8426
DPC count (execution time 1000-1999 µs): 166
DPC count (execution time 2000-3999 µs): 37
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 36177
Hard pagefault count of hardest hit process: 20966
Number of processes hit: 28
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 226.784686
CPU 0 ISR highest execution time (µs): 1241.473802
CPU 0 ISR total execution time (s): 2.179280
CPU 0 ISR count: 113478
CPU 0 DPC highest execution time (µs): 3076.739521
CPU 0 DPC total execution time (s): 6.233969
CPU 0 DPC count: 1249865
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 240.373923
CPU 1 ISR highest execution time (µs): 882.187375
CPU 1 ISR total execution time (s): 0.224942
CPU 1 ISR count: 1032
CPU 1 DPC highest execution time (µs): 3467.046906
CPU 1 DPC total execution time (s): 1.214712
CPU 1 DPC count: 180483
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 200.412169
CPU 2 ISR highest execution time (µs): 0.0
CPU 2 ISR total execution time (s): 0.0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 624.690619
CPU 2 DPC total execution time (s): 0.118454
CPU 2 DPC count: 48920
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 216.404346
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): 606.038174
CPU 3 DPC total execution time (s): 0.032019
CPU 3 DPC count: 2455
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 200.096209
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): 419.529691
CPU 4 DPC total execution time (s): 0.061491
CPU 4 DPC count: 18421
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 242.843178
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): 454.436627
CPU 5 DPC total execution time (s): 0.027757
CPU 5 DPC count: 4247
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 210.318140
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): 796.492016
CPU 6 DPC total execution time (s): 0.066206
CPU 6 DPC count: 20103
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 236.110250
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): 620.879990
CPU 7 DPC total execution time (s): 0.065337
CPU 7 DPC count: 4124
_________________________________________________________________________________________________________
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.
Page 1 of 6
-
Hi, I’ve been having very high DPC latency caused by Nvidia drivers for the past 2 months. I’ve reinstalled, tried older drivers and scanned for virus but it did not help. I also updated my BIOs but it changed nothing.
Here is some stats from LatencyMoon, I will include the most important info so u dont have to read all day;
CONCLUSION
_________________________________________________________________________________________________________Highest measured interrupt to process latency (µs): 11617,008845
Average measured interrupt to process latency (µs): 2,918835Highest measured interrupt to DPC latency (µs): 145,766009
Average measured interrupt to DPC latency (µs): 0,714862Highest ISR routine execution time (µs): 137,432353
Driver with highest ISR routine execution time: dxgkrnl.sys — DirectX Graphics Kernel, Microsoft CorporationHighest DPC routine execution time (µs): 419,952941
Driver with highest DPC routine execution time: nvlddmkm.sys — NVIDIA Windows Kernel Mode Driver, Version 331.93 , NVIDIA CorporationHighest reported total DPC routine time (%): 0,315023
Driver with highest DPC total execution time: USBPORT.SYS — USB 1.1 & 2.0 portdrivrutin, Microsoft CorporationThats about it. I have an 660 twinfrozr 2gb, i5 3570k stock speed and 8 gb ram 1600mhz if this info helps
Any ideas on how to fix this driver problem and make the DPC normal is greatly appreciated, thanks.
-
Begin with disabling all devices that you dont use, like lan cards, audio cards, everything that isnt vital for system stability and you dont need, just disable it and see if that helps.
I know that torrent apps, and such can give very high dpc latency, so also make sure you dont have all these programs autorunning on system boot, disable all that ****, they dont need to be on when not used.
-
Yup, based on this.
And this.
The time don’t match, so it can be hard disk issues that I seen before.
-
mbk1969
Ancient Guru- Messages:
- 14,738
- Likes Received:
- 12,752
- GPU:
It is highest value, and it is less then millisecond.
If nevertheless you think that it is the problems root, you can try and switch your videocard to MSI mode
-
See if something is eating up you memory with standby cache data. I find its almost always the culprit when it comes to crazy slow downs in windows. Sysinternals rammap available from microsoft does a great job at this. And even allows you to clear standby, granted it is there for a reason, but windows notoriously mismanages its standby cache. Supposed to clear out and give priority to new tasks, but that assumes the apps you are using poll windows perf data correctly.
Be sure to view your error logs by creating a custom view log that catches all errors from all logs, not just the default error log.
You can also use the programs Autoruns from sysinternals to really get a look at stuff thats being launched on boot/login (pay special attention to «yellow» entries, since autoruns thinks the referenced files are missing, pink is things is isn’t familiar with or doesn’t have complete metadetails associated with it).
If there are consistencies in the timings of the problems make sure you check recently run stuff in scheduled tasks, since the new popular thing for programs is to put stuff in there, instead of the more known startup methods.
Make sure you do a full clean install of nvidia drivers, and make sure you are installing all chipset drivers with the /overall flag added to a shortcut for setup.exe.
Hope some of this helps
-
Make sure you do a full clean install of nvidia drivers, and make sure you are installing all chipset drivers with the /overall flag added to a shortcut for setup.exe.
Hope some of this helps[/QUOTE]
Where can I install all chipset drivers?
-
mbk1969
Ancient Guru- Messages:
- 14,738
- Likes Received:
- 12,752
- GPU:
-
extract the latest infinst_autol.zip Create a shortcut to the setup.exe file, and add the switch /overall to the end of the shortcuts path in properties.
https://downloadcenter.intel.com/Se…on+Utility&ProdId=816&LineId=1090&FamilyId=42
-
Latencymon 6.0? Kernal to latency timer? cause I noticed in 6.0 in Kernal to Latency Timer I get massive latency issue the moment I hit start. Probably has somthing to do with he took out measure SMIs and CPU stalls from main program which is checked by another separate program, but left the check box in the main program still.
If you not on using 6.0 I dont know, BTW the us reported by the nvidia drivers are normal us for there drivers,
-
Mda400
Maha Guru- Messages:
- 1,058
- Likes Received:
- 185
- GPU:
Is OP using Win8 or 8.1? Interrupts are handled differently from Windows 7 and before and you may not be getting accurate readings.
At least that’s the case for DPC Latency Checker. Best to keep HPET on in BIOS/UEFI if you had disabled it before, use bcdedit /set useplatformclock true to enable HPET to be the primary hardware timer in Windows, and use bcdedit /set disabledynamictick true (if on Win8 or 8.1) in admin. command prompt.
Oh, and run this program at all times to use the lowest/fastest clock resolution your CPU supports (which should halve DPC from the current 1ms resolution and may increase fps).
Last edited: Dec 13, 2013
-
mr1hm
Active Member- Messages:
- 97
- Likes Received:
- 2
- GPU:
hmm, it seemed like with it off in the BIOS, BF4 ran a bit smoother and much more responsively on windows 8 pro for me.
also im just curious if leaving it enabled helps SLI at all?
thanks.
-
Mda400
Maha Guru- Messages:
- 1,058
- Likes Received:
- 185
- GPU:
HPET in general, is a much tighter and faster clock timer than past timers. Just make sure you use the useplatformclock command, otherwise you will be mixing HPET and other timers in windows which can cancel out the benefits.
If you want, google WinTestTimer 1.1 to find out if Windows is successfully using HPET as the primary timer (query platform clock should be something like 14.xx or 25.xx etc. anything like 6.xx or 3.xx and you are mixing timers).
Since I edited my post above, that Timer Resolution program does more for FPS than any other tweaks i’ve used because the author (credits: Lucas Hale :thumbup has found out that Windows does not use the tightest CPU clock resolution by default. If the CPU can resolve interrupts in half the time, then it gets work done faster thus resulting in some faster performance.
Last edited: Dec 13, 2013
-
mr1hm
Active Member- Messages:
- 97
- Likes Received:
- 2
- GPU:
ahh i see, thanks for the info so just to confirm, i’d have to ensure BOTH «useplatformclock» and «disabledynamictick» are set to true for HPET to be the only timer, correct?
also, would i have to be using HPET in order to use the TimerResolution program? i seem to be having a hard time finding a download for it as well
-
Mda400
Maha Guru- Messages:
- 1,058
- Likes Received:
- 185
- GPU:
useplatformclock is for making HPET the primary timer. disabledynamictick is for further DPC issues similar to the power saving function of core parking (ONLY if you’re running Windows 8/8.1).
Download the free Timer Resolution program (version 1.2) as even though it says WinXP support and only 1ms low resolution, it still works on all modern OSes including Win8/8.1 and provides lower than 1ms (I think its his way of tricking the end user into buying the paid version for better functionality). Lucas doesn’t like direct linking to his files so I just linked to the website (sorry for confusion. Its the blue link in the table).
I recommend keeping Timer Resolution running at all times as it doesn’t make the system unstable and could benefit other small tasks, but you’ll have to find a program to minimize it to taskbar if you are annoyed with its always-showing presence.
Last edited: Dec 13, 2013
-
mr1hm
Active Member- Messages:
- 97
- Likes Received:
- 2
- GPU:
so i re-enabled HPET in the BIOS and set the bcdedit commands to true as well as download the timer resolution program.
it gave me the same responsive feeling as HPET disabled and possibly increased my average FPS in BF4. pretty stoked about this as i don’t really like disabling things that generally run fine enabled with other programs.
thanks!
-
Mda400
Maha Guru- Messages:
- 1,058
- Likes Received:
- 185
- GPU:
No problem, man. I was just as amazed about the improvement it gave me when I found out about these tweaks. :nerd:
Does it still stutter for you though? Even though I don’t own the game yet, I hear issues with stutter and resource usage. Sounds like a history with the BF series though with its large scale gameplay.
-
Im using win7 ult + latencymon v6, and the problem I have is that when I play Counter strike Global Offensive and im getting shot or shooting it feels Laggy/ Choppy / Stuttery despite 120+ fps 120hz good ping.
I used the bcdedit /set useplatformclock true command but it changed nothing.
Last edited: Dec 14, 2013
-
mbk1969
Ancient Guru- Messages:
- 14,738
- Likes Received:
- 12,752
- GPU:
With your CPU and on Win7 you don`t need ‘useplatformclock true’. Win7 should select the best of high performance counters at the rig.
-
okay. I just noticed there was a warning sign on USB devices in Device manager, it said drivers were missing, but when I use windows solution wich tries to install drivers, my whole PC just completley freezes.
Maybe this has something to do with the high DPC latency.
-
HPET is a older timer. I wouldn’t use it. Invariable TSC isa newer timer, which your CPU supports. Like mbk1969 said, do not use the platform true command. Let Windows pick the timer.
And you can try disabling dynamicticks, cause it will lower DPC latency. But for me, when I disable it, I get stuttering/hitching in BF4. When I turn dynamicticks back on, it goes away. It sounds weird but I know at least one other person who experienced the same thing, which he posted about in that huge DPC latency thread.
Page 1 of 6
Share This Page