Was bewirkt ein Knacken und Knacken von Audio? (Toshiba Satellite Laptop; Hohe CPU)
854
rudolph
Ich habe ein Toshiba Satellite L-50-Laptop, das ursprünglich Windows 8.1 hatte, nachdem ich es auf Windows 10 aufgerüstet hatte, begannen alle diese Audioprobleme. Ich denke, es könnte von den veralteten Treibern verursacht werden, die TOSHIBA 2013 oder 2015 für Win 8.1 aktualisiert hat.
Ich habe Treiber nur manuell mit .inf-Dateien im Geräte-Manager aktualisiert.
Immer, wenn ich in Chrome 20 Registerkarten geöffnet habe, einschließlich 3 Youtube-Tabs oder mehr, die Audio abspielen, habe ich ein Videospiel geöffnet und den MusicBee-Player geöffnet. Wenn ich eine dieser Audioquellen wiedergebe, fängt mein Audio an zu knistern und es ist unmöglich, etwas zu hören . Es geht weg, wenn ich das DTS-Soundfenster öffne und die Verbesserungen ausschalte. Und dies geschieht während des Einsatzes von High Performance Power Plan. DTS kann ich jedoch nicht verwenden, denn ohne sie ist der Klang sehr minderwertig, trocken, kein Bass, nichts, nur einfacher Ton.
Specs:
16 GB RAM
NVIDIA 740M
IDT High Definition Audio
Intel Quad Core i7-4700MQ
Ich habe auch LatencyMon Tests gemacht und das sind die Ergebnisse:
_________________________________________________________________________________________________________ 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 _________________________________________________________________________________________________________
ndis.sys = netzwerkbezogener Treiber. Aktualisieren Sie daher alle Netzwerktreiber.
magicandre1981 vor 7 Jahren
0
1 Antwort auf die Frage
0
x_031
Dies ist in der Tat KEIN Hardwaredefekt, da Sie ein Upgrade auf ein anderes Windows-Betriebssystem durchgeführt haben und diese Probleme aufgetreten sind.
Wenn Sie Ihren Thread hier lesen, wird ich mich an eine Lösung für dieses Problem erinnern. Es ist Ihr Energieplan, der das Audio nicht seine Sache erledigen lässt.
Um dies zu beheben, wechseln Sie zu Systemsteuerung> Energieeinstellungen> Mindestprozessorstatus auf 100% . Beachten Sie, dass dies keine dauerhafte Korrektur ist. Es ist immer noch eine Problemumgehung, aber Sie können dies verwenden, bis sie bessere Treiber für Ihre Software herausgeben und mit Windows 10 kompatibel sind.