Привет, у меня тоже самое, ничего не помогло, скорее всего проблема по аппаратной части, помогла лишь сборка нового ПК, старый как резервный и архив использую
Как привести в норму показатели LatencyMon? (1 онлайн
- Автор темы Lsw
- Дата начала
подключен через LAN, рылся в сетевом адаптере, его настройках хотел отключить "параметр пробуждение пакетом Magic", которого там не оказалось. Он есть только в настройках WLAN. Отключил, перезагуризил фпс минимум 50, средний 60 где-то. Системные прерывания 0% когда были 100%. И кстати запустил танки там всё отлично, проблема только с варзоном была. Но как по мне фпс общий снизился. Раньше чаще показывало 70 фпс сейчас либо в домах либо на некоторых локациях. Хз даже, может кажется
Добавлено:
Но суть именно что они пропали. Это главное, теперь не грузят проц в 100%
Решение
#1 Find the audiosrv and audioendpointbuilder services (start taskman in admin mode, go to services tab, locate said services by description)
#2 Right click and "go to process"/"go to detail" (windows 10)
#3 Change the affinity (meaning what core the process runs on) to something other than cores 0 or 1 if you have a 4 or more core system.
It works because ACPI.sys and wdf01000.sys tend to run on cores 0 and 1. You put the audio stuff on cores 2 or 3 (etc.)
You leave your audio service free from interruption on other cores.
Попробовал, да намного лучше, но всеравно acpi.sys вылазит
#1 Find the audiosrv and audioendpointbuilder services (start taskman in admin mode, go to services tab, locate said services by description)
#2 Right click and "go to process"/"go to detail" (windows 10)
#3 Change the affinity (meaning what core the process runs on) to something other than cores 0 or 1 if you have a 4 or more core system.
It works because ACPI.sys and wdf01000.sys tend to run on cores 0 and 1. You put the audio stuff on cores 2 or 3 (etc.)
You leave your audio service free from interruption on other cores.
Попробовал, да намного лучше, но всеравно acpi.sys вылазит
Последнее редактирование:
друзья, давно мучаюсь с этими системными прерываниями, прямо не знаю что делать, недавно узнал о latencymon и вот что она мне показала, помогите пожалуйста разобраться что тут нужно сделать чтобы решить проблему? гуглёж особо ни к чему не привёл
_________________________________________________________________________________________________________
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:03:27 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: EYERIP
OS version: Windows 10, 10.0, version 2009, build: 19042 (x64)
Hardware: G7 7790, Dell Inc.
CPU: GenuineIntel Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Logical processors: 6
Processor groups: 1
RAM: 16196 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2592 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): 1451,50
Average measured interrupt to process latency (µs): 8,513664
Highest measured interrupt to DPC latency (µs): 1448,10
Average measured interrupt to DPC latency (µs): 4,938366
_________________________________________________________________________________________________________
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): 192,325617
Driver with highest ISR routine execution time: ACPI.sys - ACPI драйвер для NT, Microsoft Corporation
Highest reported total ISR routine time (%): 0,023051
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,027296
ISR count (execution time <250 µs): 29487
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): 1946,844907
Driver with highest DPC routine execution time: ACPI.sys - ACPI драйвер для NT, Microsoft Corporation
Highest reported total DPC routine time (%): 0,013651
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,050453
DPC count (execution time <250 µs): 108150
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 143
DPC count (execution time 1000-2000 µs): 54
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 1771
Hard pagefault count of hardest hit process: 1183
Number of processes hit: 14
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 2,645235
CPU 0 ISR highest execution time (µs): 192,325617
CPU 0 ISR total execution time (s): 0,336649
CPU 0 ISR count: 29291
CPU 0 DPC highest execution time (µs): 1946,844907
CPU 0 DPC total execution time (s): 0,575790
CPU 0 DPC count: 97110
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,429532
CPU 1 ISR highest execution time (µs): 191,649691
CPU 1 ISR total execution time (s): 0,002550
CPU 1 ISR count: 196
CPU 1 DPC highest execution time (µs): 398,532407
CPU 1 DPC total execution time (s): 0,022381
CPU 1 DPC count: 5042
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,430290
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): 118,912809
CPU 2 DPC total execution time (s): 0,011141
CPU 2 DPC count: 2796
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,333171
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): 130,601080
CPU 3 DPC total execution time (s): 0,005470
CPU 3 DPC count: 1125
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0,392558
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): 125,006173
CPU 4 DPC total execution time (s): 0,005251
CPU 4 DPC count: 1091
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0,424883
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): 123,671296
CPU 5 DPC total execution time (s): 0,006929
CPU 5 DPC count: 1183
_________________________________________________________________________________________________________
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:03:27 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: EYERIP
OS version: Windows 10, 10.0, version 2009, build: 19042 (x64)
Hardware: G7 7790, Dell Inc.
CPU: GenuineIntel Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Logical processors: 6
Processor groups: 1
RAM: 16196 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2592 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): 1451,50
Average measured interrupt to process latency (µs): 8,513664
Highest measured interrupt to DPC latency (µs): 1448,10
Average measured interrupt to DPC latency (µs): 4,938366
_________________________________________________________________________________________________________
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): 192,325617
Driver with highest ISR routine execution time: ACPI.sys - ACPI драйвер для NT, Microsoft Corporation
Highest reported total ISR routine time (%): 0,023051
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,027296
ISR count (execution time <250 µs): 29487
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): 1946,844907
Driver with highest DPC routine execution time: ACPI.sys - ACPI драйвер для NT, Microsoft Corporation
Highest reported total DPC routine time (%): 0,013651
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,050453
DPC count (execution time <250 µs): 108150
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 143
DPC count (execution time 1000-2000 µs): 54
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 1771
Hard pagefault count of hardest hit process: 1183
Number of processes hit: 14
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 2,645235
CPU 0 ISR highest execution time (µs): 192,325617
CPU 0 ISR total execution time (s): 0,336649
CPU 0 ISR count: 29291
CPU 0 DPC highest execution time (µs): 1946,844907
CPU 0 DPC total execution time (s): 0,575790
CPU 0 DPC count: 97110
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,429532
CPU 1 ISR highest execution time (µs): 191,649691
CPU 1 ISR total execution time (s): 0,002550
CPU 1 ISR count: 196
CPU 1 DPC highest execution time (µs): 398,532407
CPU 1 DPC total execution time (s): 0,022381
CPU 1 DPC count: 5042
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,430290
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): 118,912809
CPU 2 DPC total execution time (s): 0,011141
CPU 2 DPC count: 2796
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,333171
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): 130,601080
CPU 3 DPC total execution time (s): 0,005470
CPU 3 DPC count: 1125
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0,392558
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): 125,006173
CPU 4 DPC total execution time (s): 0,005251
CPU 4 DPC count: 1091
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0,424883
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): 123,671296
CPU 5 DPC total execution time (s): 0,006929
CPU 5 DPC count: 1183
_________________________________________________________________________________________________________