[Petya V4sechkin]

начались проблемы

Запуск восстановления системы

[love_fist911]

Восстановление ничего не дало (кроме поломанной лицензии на одном приложении), откатил обратно.
Драйверы переустановил (на видеокарту и аудиокарту) — без изменений.
Есть еще варианты?
____
На данный момент интересует именно звук, графика вроде бы, в порядке.

[Petya V4sechkin]

некие шумо-скрипо-хрипы, примерно такие же, какие появляются при переполнении буфера(или что там) аудиочипа, упала производительность

Во время глюка сделайте отчет LatencyMon и скриншоты вкладки Drivers с сортировкой по ISR и DPC.

Перед использованием прочитайте документацию. Для завершения мониторинга нажать кнопку Stop. После зайти на все вкладки (Stats, Processes и Drivers) и посмотреть результаты. На вкладке Stats скопировать отчет целиком (в текстовом виде). На вкладке Processes задать сортировку по столбцу Pagefaults. На вкладке Drivers - по столбцам ISR и DPC.

некоторые приложения вообще вылетают после черного экрана

Приведите ошибки из журнала событий -> Журналы Windows -> в разделах Приложение и Система (правой кнопкой мыши -> Копировать -> Копировать сведения как текст).

[love_fist911]

скриншоты вкладки Drivers »

ISR и DPC

Stats:

читать дальше »

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


____________________________________________________________________________________________________ _____
SYSTEM INFORMATION
____________________________________________________________________________________________________ _____
Computer name: NOTEBOOK
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: TWH, Quanta
CPU: GenuineIntel Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz
Logical processors: 4
Processor groups: 1
RAM: 4043 MB total


____________________________________________________________________________________________________ _____
CPU SPEED
____________________________________________________________________________________________________ _____
Reported CPU speed: 2395.0 MHz
Measured CPU speed: 1842.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): 11248.908999
Average measured interrupt to process latency (µs): 830.666007

Highest measured interrupt to DPC latency (µs): 11245.915562
Average measured interrupt to DPC latency (µs): 827.168908


____________________________________________________________________________________________________ _____
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) 9.407945


____________________________________________________________________________________________________ _____
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): 140.242171
Driver with highest ISR routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation

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

Total time spent in ISRs (%) 0.214819

ISR count (execution time <250 µs): 39234
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): 10927.858038
Driver with highest DPC routine execution time: ndis.sys - Драйвер NDIS 6.30, Microsoft Corporation

Highest reported total DPC routine time (%): 10.057597
Driver with highest DPC total execution time: ndis.sys - Драйвер NDIS 6.30, Microsoft Corporation

Total time spent in DPCs (%) 10.328443

DPC count (execution time <250 µs): 57091
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: metroll.exe

Total number of hard pagefaults 612
Hard pagefault count of hardest hit process: 587
Highest hard pagefault resolution time (µs): 657750.727349
Total time spent in hard pagefaults (%): 10.734297
Number of processes hit: 3


____________________________________________________________________________________________________ _____
PER CPU DATA
____________________________________________________________________________________________________ _____
CPU 0 Interrupt cycle time (s): 13.044246
CPU 0 ISR highest execution time (µs): 140.242171
CPU 0 ISR total execution time (s): 0.275905
CPU 0 ISR count: 39234
CPU 0 DPC highest execution time (µs): 10927.858038
CPU 0 DPC total execution time (s): 13.212849
CPU 0 DPC count: 45352
____________________________________________________________________________________________________ _____
CPU 1 Interrupt cycle time (s): 0.134812
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): 120.080167
CPU 1 DPC total execution time (s): 0.006487
CPU 1 DPC count: 1535
____________________________________________________________________________________________________ _____
CPU 2 Interrupt cycle time (s): 0.218881
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): 110.369937
CPU 2 DPC total execution time (s): 0.044819
CPU 2 DPC count: 10878
____________________________________________________________________________________________________ _____
CPU 3 Interrupt cycle time (s): 0.095468
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): 32.228810
CPU 3 DPC total execution time (s): 0.001284
CPU 3 DPC count: 609
____________________________________________________________________________________________________ _____

Processes


Относительно вылетов — система не регистрировала никаких ошибок, видимо, они обрабатывались внутренне, у меня есть подозрения, переустановка драйвера графики исправила проблему с DirectX — сейчас все нормально, либо они были случайны.

[Petya V4sechkin]

love_fist911, наибольшая загрузка у ndis.sys - причина в сетевых компонентах (какая-то программа слишком интенсивно использует сеть).

Попробуйте рекомендации
Как определить, является проблема системной или вызвана сторонним приложением/службой

[love_fist911]

причина в сетевых компонентах »

А как это связано с проблемами аудио?

[Petya V4sechkin]

love_fist911, в двух словах: операции Interrupts (ISR) и Deferred procedure calls (DPC) имеют более высокий приоритет, чем воспроизведение звука.
Такое довольно часто случается:

• Потрескивает звук (хрипит) в Windows 7
• Щелкает, потрескивает звук в Windows 7

[love_fist911]

Отключил Вай-Фай подключение (сам модуль был отключен по Fn+F2, но подключение остается «включенным»): Панель управления → Сеть и Интернет → Сетевые подключения — Беспроводная сеть(ПКМ) — Отключить.
Трещать перестало. Интересно-интересно.
Провел эксперимент: При включенном подключении(в Сетевых подключениях), но выключенном модуле(Fn+F2), действительно трещит. При включенном модуле — не трещит. При отключенном модуле и подключении — тоже. Такие дела.