У меня есть ноутбук Toshiba Satellite L-50, который изначально имел Windows 8.1, после того, как я обновил его до Windows 10, все эти проблемы со звуком начались. Я думаю, что это может быть связано с устаревшими драйверами, которые TOSHIBA обновил для Win 8.1 в 2013 или 2015 году.
Я обновил драйверы только вручную с помощью файлов .inf в диспетчере устройств.
Вот как это звучит: https://clyp.it/ks3xzdrc
Всякий раз, когда я открыл 20 вкладок в Chrome, в том числе 3 вкладки YouTube или более, воспроизводящие аудио +, я открывал некоторые видеоигры и проигрыватель MusicBee, когда я начинаю воспроизводить один из этих аудиоисточников, мой звук начинает трещать, невозможно что-либо слушать , Он исчезает, когда я открываю панель DTS Sound и выключаю улучшения. И это происходит при использовании высокопроизводительного плана питания. Но я не могу не использовать DTS, потому что без него звук очень низкого качества, сухой, без басов, ничего, просто звук…
Технические характеристики:
- 16 ГБ ОЗУ
- NVIDIA 740M
- IDT High Definition Audio
- Intel Quad Core i7-4700MQ
Я также сделал тесты 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 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 1:01:08 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: COMPUTER
OS version: Windows 10 , 10.0, build: 14393 (x64)
Hardware: SATELLITE L50-A-19N, TOSHIBA, VG10S
CPU: GenuineIntel Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
Logical processors: 8
Processor groups: 1
RAM: 16295 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2394 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): 6163.758486
Average measured interrupt to process latency (µs): 4.369088
Highest measured interrupt to DPC latency (µs): 6159.909611
Average measured interrupt to DPC latency (µs): 1.666508
_________________________________________________________________________________________________________
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): 235.162907
Driver with highest ISR routine execution time: ACPI.sys - ACPI Driver for NT, Microsoft Corporation
Highest reported total ISR routine time (%): 0.038663
Driver with highest ISR total time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation
Total time spent in ISRs (%) 0.047170
ISR count (execution time <250 µs): 1661229
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): 2976.676692
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation
Highest reported total DPC routine time (%): 0.112158
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in DPCs (%) 0.321216
DPC count (execution time <250 µs): 21177175
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 630
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µs): 1
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: musicbee.exe
Total number of hard pagefaults 27965
Hard pagefault count of hardest hit process: 8938
Highest hard pagefault resolution time (µs): 300129.554720
Total time spent in hard pagefaults (%): 0.224020
Number of processes hit: 36
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 194.016463
CPU 0 ISR highest execution time (µs): 235.162907
CPU 0 ISR total execution time (s): 12.342339
CPU 0 ISR count: 1432981
CPU 0 DPC highest execution time (µs): 951.070175
CPU 0 DPC total execution time (s): 66.085713
CPU 0 DPC count: 18380959
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 84.449878
CPU 1 ISR highest execution time (µs): 145.335840
CPU 1 ISR total execution time (s): 1.003215
CPU 1 ISR count: 124387
CPU 1 DPC highest execution time (µs): 475.623225
CPU 1 DPC total execution time (s): 7.401236
CPU 1 DPC count: 791592
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 56.717142
CPU 2 ISR highest execution time (µs): 109.807018
CPU 2 ISR total execution time (s): 0.400784
CPU 2 ISR count: 83558
CPU 2 DPC highest execution time (µs): 371.132832
CPU 2 DPC total execution time (s): 5.814637
CPU 2 DPC count: 478759
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 61.666263
CPU 3 ISR highest execution time (µs): 131.147870
CPU 3 ISR total execution time (s): 0.091189
CPU 3 ISR count: 19320
CPU 3 DPC highest execution time (µs): 181.157895
CPU 3 DPC total execution time (s): 0.956490
CPU 3 DPC count: 143280
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 54.360507
CPU 4 ISR highest execution time (µs): 76.472431
CPU 4 ISR total execution time (s): 0.005396
CPU 4 ISR count: 949
CPU 4 DPC highest execution time (µs): 337.111111
CPU 4 DPC total execution time (s): 4.540029
CPU 4 DPC count: 426125
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 62.874138
CPU 5 ISR highest execution time (µs): 8.441103
CPU 5 ISR total execution time (s): 0.000171
CPU 5 ISR count: 34
CPU 5 DPC highest execution time (µs): 152.748538
CPU 5 DPC total execution time (s): 1.113091
CPU 5 DPC count: 177993
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 53.750462
CPU 6 ISR highest execution time (µs): 0.0
CPU 6 ISR total execution time (s): 0.0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 2976.676692
CPU 6 DPC total execution time (s): 6.636305
CPU 6 DPC count: 567945
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 61.751746
CPU 7 ISR highest execution time (µs): 0.0
CPU 7 ISR total execution time (s): 0.0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 153.434837
CPU 7 DPC total execution time (s): 1.719763
CPU 7 DPC count: 211153
_________________________________________________________________________________________________________