Теперь Кью работает в режиме чтения

Мы сохранили весь контент, но добавить что-то новое уже нельзя

Высокий DPC в Latency mon у драйвера Hdaudbus.sys,что делать?

_________________________________________________________________________________________________________

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. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. 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:14:00 (h:mm:ss) on all processors.

_________________________________________________________________________________________________________

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: Igor

OS version: Windows 7 Service Pack 1 , 6.1, build: 7601 (x64)

Hardware: ASUSTeK Computer INC., P7P55D LE

CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz

Logical processors: 4

Processor groups: 1

RAM: 8190 MB total

_________________________________________________________________________________________________________

CPU SPEED

_________________________________________________________________________________________________________

Reported CPU speed: 2808 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): 19706,764407

Average measured interrupt to process latency (µs): 7,083537

Highest measured interrupt to DPC latency (µs): 4019,016383

Average measured interrupt to DPC latency (µs): 1,690507

_________________________________________________________________________________________________________

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): 170,497863

Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0,114206

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

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

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

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

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): 3429,035613

Driver with highest DPC routine execution time: tcpip.sys - Драйвер TCP/IP, Microsoft Corporation

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

Driver with highest DPC total execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Total time spent in DPCs (%) 0,775252

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

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

DPC count (execution time 500-999 µs): 210

DPC count (execution time 1000-1999 µs): 16

DPC count (execution time 2000-3999 µs): 5

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: chrome.exe

Total number of hard pagefaults 49113

Hard pagefault count of hardest hit process: 11582

Number of processes hit: 70

_________________________________________________________________________________________________________

PER CPU DATA

_________________________________________________________________________________________________________

CPU 0 Interrupt cycle time (s): 20,452604

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

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

CPU 0 ISR count: 619965

CPU 0 DPC highest execution time (µs): 3429,035613

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

CPU 0 DPC count: 2920575

_________________________________________________________________________________________________________

CPU 1 Interrupt cycle time (s): 40,158639

CPU 1 ISR highest execution time (µs): 170,497863

CPU 1 ISR total execution time (s): 2,790422

CPU 1 ISR count: 156778

CPU 1 DPC highest execution time (µs): 791,252137

CPU 1 DPC total execution time (s): 1,815163

CPU 1 DPC count: 176598

_________________________________________________________________________________________________________

CPU 2 Interrupt cycle time (s): 49,194752

CPU 2 ISR highest execution time (µs): 44,419872

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

CPU 2 ISR count: 802

CPU 2 DPC highest execution time (µs): 430,601852

CPU 2 DPC total execution time (s): 15,193276

CPU 2 DPC count: 3094038

_________________________________________________________________________________________________________

CPU 3 Interrupt cycle time (s): 18,589217

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

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

CPU 3 ISR count: 41713

CPU 3 DPC highest execution time (µs): 1410,285256

CPU 3 DPC total execution time (s): 2,595526

CPU 3 DPC count: 213448

_________________________________________________________________________________________________________

Компьютеры
drivemines
  ·   · 1,9 K