[Petya V4sechkin]

Dirty Move Beats, сделайте лог Kernrate во время тормоза.

Также во время тормоза выложите отчёт LatencyMon и скриншоты вкладки Drivers с сортировкой по ISR и DPC. Перед использованием LatencyMon прочитайте документацию (для завершения мониторинга не забудьте нажать кнопку Stop).

[Dirty Move Beats]

сделайте лог Kernrate во время тормоза. »

это происходит на доли секунд буквально

[Dirty Move Beats]

____________________________________________________________________________________________________ _____
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:05:39 (h:mm:ss) on all processors.


____________________________________________________________________________________________________ _____
SYSTEM INFORMATION
____________________________________________________________________________________________________ _____
Computer name: DIRTYMOVEBEATS
OS version: Windows 10 , 10.0, build: 14393 (x64)
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z97M-PLUS
CPU: GenuineIntel Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
Logical processors: 4
Processor groups: 1
RAM: 7367 MB total


____________________________________________________________________________________________________ _____
CPU SPEED
____________________________________________________________________________________________________ _____
Reported CPU speed: 3506 MHz
Measured CPU speed: 1 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.

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): 270,450402
Average measured interrupt to process latency (µs): 1,214463

Highest measured interrupt to DPC latency (µs): 268,698024
Average measured interrupt to DPC latency (µs): 0,415946


____________________________________________________________________________________________________ _____
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): 13,833714
Driver with highest ISR routine execution time: USBPORT.SYS - Драйвер порта USB 1.1 и 2.0, Microsoft Corporation

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

Total time spent in ISRs (%) 0,004173

ISR count (execution time <250 µs): 13736
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): 308,751569
Driver with highest DPC routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation

Highest reported total DPC routine time (%): 0,010595
Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.

Total time spent in DPCs (%) 0,078452

DPC count (execution time <250 µs): 709792
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 3
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: svchost.exe

Total number of hard pagefaults 6729
Hard pagefault count of hardest hit process: 1676
Highest hard pagefault resolution time (µs): 204373,712778
Total time spent in hard pagefaults (%): 1,502941
Number of processes hit: 23


____________________________________________________________________________________________________ _____
PER CPU DATA
____________________________________________________________________________________________________ _____
CPU 0 Interrupt cycle time (s): 1,710025
CPU 0 ISR highest execution time (µs): 13,833714
CPU 0 ISR total execution time (s): 0,056377
CPU 0 ISR count: 13691
CPU 0 DPC highest execution time (µs): 308,751569
CPU 0 DPC total execution time (s): 0,955703
CPU 0 DPC count: 645652
____________________________________________________________________________________________________ _____
CPU 1 Interrupt cycle time (s): 0,262882
CPU 1 ISR highest execution time (µs): 7,392470
CPU 1 ISR total execution time (s): 0,000222
CPU 1 ISR count: 43
CPU 1 DPC highest execution time (µs): 84,408443
CPU 1 DPC total execution time (s): 0,03680
CPU 1 DPC count: 22206
____________________________________________________________________________________________________ _____
CPU 2 Interrupt cycle time (s): 0,255260
CPU 2 ISR highest execution time (µs): 5,394467
CPU 2 ISR total execution time (s): 0,000011
CPU 2 ISR count: 2
CPU 2 DPC highest execution time (µs): 53,656874
CPU 2 DPC total execution time (s): 0,034175
CPU 2 DPC count: 19920
____________________________________________________________________________________________________ _____
CPU 3 Interrupt cycle time (s): 0,250035
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): 48,551341
CPU 3 DPC total execution time (s): 0,037477
CPU 3 DPC count: 22017
____________________________________________________________________________________________________ _____

[Dirty Move Beats]

Полагаю, что это проблема с самой системой, отключил абсолютно все устройства, но проблема не решилась, картина не меняется, пробовал ставить драйвер более старой версии, включал в BIOS Intel xHCI (USB 3,0), но ничего не меняется, видимо 10ка все еще сырая или просто косячная система, что не удивляет, но расстраивает.

Сейчас буду ставить 7ку, скину скрин этих же программ уже в ней, для сравнения.

[mwz]

скину скрин этих же программ уже в ней, для сравнения »

Если можно — сразу заберите его под тэг [spoiler], а то простынки великоваты.

[severagent007]

можно попробовать отключить bcdedit /set disabledynamictick yes
а затем проверить и попробовать выставить таймер винды на 0.5 программой Resolution Timer...
восстановить bcdedit /set disabledynamictick no
и bootice-ом удалить из загрузки эту строчку после ребута. На 10 таймер энергосберегающим сделали, у меня тоже 1000 в простое, еще можно пробовать выс производительность в элпитании, хотя врядли.

[Dirty Move Beats]

Поставил 7ку, официальный образ, удалив и форматировав все разделы, установил драйверы с официального сайта, поставил обновления, отключил службы, которые не используются, настроил электропитание, все вроде бы неплохо, но рывки мыши остались, правда не такие сильные, как в 10ке, но они есть, заглянул в DPC Latency Cheker, показания изменились сильно по сравнению с 10кой, сохранились лишь редкие скачки до 3000-5000, я не могу понять, с чем они связаны, они произвольны, вот скрин:

Скрытый текст

Вот отчет LatencyMon:

Скрытый текст

____________________________________________________________________________________________________ _____
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 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:33:30 (h:mm:ss) on all processors.


____________________________________________________________________________________________________ _____
SYSTEM INFORMATION
____________________________________________________________________________________________________ _____
Computer name: DIRTYMOVEBEATS
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z97M-PLUS
CPU: GenuineIntel Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
Logical processors: 4
Processor groups: 1
RAM: 7111 MB total


____________________________________________________________________________________________________ _____
CPU SPEED
____________________________________________________________________________________________________ _____
Reported CPU speed: 3506 MHz
Measured CPU speed: 1 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.

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): 7988,693806
Average measured interrupt to process latency (µs): 1,531232

Highest measured interrupt to DPC latency (µs): 4983,405199
Average measured interrupt to DPC latency (µs): 0,459314


____________________________________________________________________________________________________ _____
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): 11,774957
Driver with highest ISR routine execution time: ACPI.sys - ACPI драйвер для NT, Microsoft Corporation

Highest reported total ISR routine time (%): 0,003572
Driver with highest ISR total time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation

Total time spent in ISRs (%) 0,004055

ISR count (execution time <250 µs): 2010054
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): 234,230747
Driver with highest DPC routine execution time: raspppoe.sys - RAS PPPoE mini-port/call-manager driver, Microsoft Corporation

Highest reported total DPC routine time (%): 0,427228
Driver with highest DPC total execution time: iusb3xhc.sys - Intel(R) USB 3.0 eXtensible Host Controller Driver, Intel Corporation

Total time spent in DPCs (%) 0,742762

DPC count (execution time <250 µs): 16935139
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 10966
Hard pagefault count of hardest hit process: 3440
Highest hard pagefault resolution time (µs): 429403,963206
Total time spent in hard pagefaults (%): 0,123909
Number of processes hit: 17


____________________________________________________________________________________________________ _____
PER CPU DATA
____________________________________________________________________________________________________ _____
CPU 0 Interrupt cycle time (s): 48,578309
CPU 0 ISR highest execution time (µs): 11,774957
CPU 0 ISR total execution time (s): 0,326173
CPU 0 ISR count: 2010054
CPU 0 DPC highest execution time (µs): 234,230747
CPU 0 DPC total execution time (s): 41,869069
CPU 0 DPC count: 15523649
____________________________________________________________________________________________________ _____
CPU 1 Interrupt cycle time (s): 22,948777
CPU 1 ISR highest execution time (µs): 0,0
CPU 1 ISR total execution time (s): 0,0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 182,530519
CPU 1 DPC total execution time (s): 17,161177
CPU 1 DPC count: 1194396
____________________________________________________________________________________________________ _____
CPU 2 Interrupt cycle time (s): 4,637767
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): 95,087849
CPU 2 DPC total execution time (s): 0,249535
CPU 2 DPC count: 85729
____________________________________________________________________________________________________ _____
CPU 3 Interrupt cycle time (s): 4,877175
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): 70,960924
CPU 3 DPC total execution time (s): 0,464095
CPU 3 DPC count: 131365
____________________________________________________________________________________________________ _____

DPC Count:

Скрытый текст

ISR Count:

Скрытый текст

Диспетчер задач:

Скрытый текст

Версия BIOS стоит последняя, пробовал сбрасывать, переустанавливал драйверы, но проблемы остались, отключал все устройства из разъемов, но эти скачки и рывки мыши остаются, хотя со звуком в 7ке лучше, чем в 10ке, трески и щелчки я пока не слышал.

В чем же проблема и как ее можно побороть?

[Dirty Move Beats]

Ну еще заметил, что звук иногда прерывается и есть треск, к тому же, теряется соединение с ИБП, он тоже соединен по USB.

[Dirty Move Beats]

Проблема решена заменой системной платы.