Имя пользователя:
Пароль:  
Помощь | Регистрация | Забыли пароль?  

Показать сообщение отдельно

Новый участник


Сообщения: 6
Благодарности: 0

Профиль | Сайт | Отправить PM | Цитировать


Отчет из latencyMon
Цитата:
ONCLUSION
____________________________________________________________________________________________________ _____
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 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:01:27 (h:mm:ss) on all processors.


____________________________________________________________________________________________________ _____
SYSTEM INFORMATION
____________________________________________________________________________________________________ _____
Computer name: GONDAR-ПК
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: G41MT-S2, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Pentium(R) Dual-Core CPU E6600 @ 3.06GHz
Logical processors: 2
Processor groups: 1
RAM: 4094 MB total


____________________________________________________________________________________________________ _____
CPU SPEED
____________________________________________________________________________________________________ _____
Reported CPU speed: 3066,0 MHz
Measured CPU speed: 2501,0 MHz (approx.)

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): 14346,947914
Average measured interrupt to process latency (µs): 3,675346

Highest measured interrupt to DPC latency (µs): 220,378095
Average measured interrupt to DPC latency (µs): 0,920126


____________________________________________________________________________________________________ _____
MEASURED SMI, IPI AND CPU STALLS
____________________________________________________________________________________________________ _____
The SMI, IPI and CPU stalls value represents the highest measured interval that a CPU did not respond while having its maskable interrupts disabled.

Highest measured SMI or CPU stall (µs) 7,012030


____________________________________________________________________________________________________ _____
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): 110,709067
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

Total time spent in ISRs (%) 0,322228

ISR count (execution time <250 µs): 146971
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): 147,725701
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 320.00 , NVIDIA Corporation

Highest reported total DPC routine time (%): 0,290932
Driver with highest DPC total execution time: USBPORT.SYS - Драйвер порта USB 1.1 и 2.0, Microsoft Corporation

Total time spent in DPCs (%) 0,980602

DPC count (execution time <250 µs): 447578
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µs): 0
DPC count (execution time >=4000 µs): 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: firefox.exe

Total number of hard pagefaults 16
Hard pagefault count of hardest hit process: 15
Highest hard pagefault resolution time (µs): 22962,740705
Total time spent in hard pagefaults (%): 0,013278
Number of processes hit: 2


____________________________________________________________________________________________________ _____
PER CPU DATA
____________________________________________________________________________________________________ _____
CPU 0 Interrupt cycle time (s): 1,754581
CPU 0 ISR highest execution time (µs): 110,709067
CPU 0 ISR total execution time (s): 0,311458
CPU 0 ISR count: 116898
CPU 0 DPC highest execution time (µs): 147,725701
CPU 0 DPC total execution time (s): 1,097973
CPU 0 DPC count: 413850
____________________________________________________________________________________________________ _____
CPU 1 Interrupt cycle time (s): 1,224394
CPU 1 ISR highest execution time (µs): 69,495108
CPU 1 ISR total execution time (s): 0,249837
CPU 1 ISR count: 30073
CPU 1 DPC highest execution time (µs): 146,326810
CPU 1 DPC total execution time (s): 0,610158
CPU 1 DPC count: 33728
____________________________________________________________________________________________________ _____
http://saveimg.ru/show-image.php?id=...5fecd6046db36c
http://saveimg.ru/show-image.php?id=...02dc0c66dbc6a5

Насчет журнала, замечена лишь 1- на ошибка
"//./root/CIMV2 SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99 0x80041003"

так- же замечен новый лаг, курсор после лага меняется на произвольный!

Отправлено: 21:45, 05-05-2013 | #3