Unregelmäßigkeiten bei Audioausgabe

[Gkla]

Hi Leute,
irgendwie hab ich seit einer Woche was seltsames was die Audioausgabe anbelangt.
Egal ob Mp3, Flac, Video (avi, mkv), youtube, bei der Audiowiedergabe kommen relativ oft Unregelmäßigkeiten vor, sprich stocken, kurzes "einfrieren", das macht z.B. manchmal ein rrrr-Geräusch oder so, jedenfalls ist das neu, vorher lief alles wunderbar. Keine Ahnung wo das her kommt. Diese Sachen kommen total unregelmäßig vor, manchmal kommt bei 2-3 Songs garnix, dann beim nächsten kommen solche Sachen 4-5 mal vor. An den Liedern kann es aber nicht liegen, da ich es random getestet habe. Und wenn ich bei einem Song, wo solche kurzen Stocker vorkommen zurückzappe, dann kommt es oftmals kein zweites mal. Die Geräusche kommen dabei auch immer nur so ganz ganz kurz vor, 1 Sekunde oder so.
PS es macht keinen Unterschied ob ich es per Monitor-Lautsprecher oder per Headset Musik höre .
Es macht auch keinen Unterschied wie sehr der PC ausgelastet ist. Manchmal habe ich nur Firefox offen und nebenbei Musik an, selbst da, bei nur 2-3 Anwendungen kommen die Probleme vor.

Mein System:
AMD FX-8350 8x4,00 GHZ
Sapphire Radeon R9 290 Vapor-X OC 4GBRAM
Asus M5A97 Evo R2.0
GeIL DIMM-Speicher 16GB DDR3-1600
Arctic Freezer xtreme Rev 2.0
be quiet! Pure Power L8 CM 630 Watt
Samsung HD103SJ 1000 GB
WD10EZEX WD Blue 1000 GB
ST3320812AS 320 GB
Win 7 Ultimate 64-Bit

Wer hat einen Rat?

MfG

 

[arvan]

Hi,

mal versucht im BIOS Load Line Calibration auf Aus/Regular zu stellen?

 

[druckluft]

mal versucht im BIOS Load Line Calibration auf Aus/Regular zu stellen?

Was soll denn diese Option der Spannungsregelung für die CPU damit zu tun haben

@TE: Teste mal mit dem DPC Latency Checker oder Resplendence Latency Monitor ob Probleme auftreten

 

[Gkla]

Hab DPC Latency Checker mal eine halbe Stunden laufen lassen, bei den Problemen schlägt es halt rot aus. Absolute Maximum beträgt 70937 μs.
PS mir ist grad eingefallen, dass ich vor einer Woche einen neuen WLAN Stick gekauft habe, weil mein alter kaputt ging. Ich benutze jetzt den EDIMAX WLAN USB NANO STICK EW-7811UN.
Weiss aber nicht genau ob ich die Probleme schon vor dem Adpater Wechsel hatte, kann aber auch sein.
Obs da einen Zusammenhang gibt?
Hab noch nicht probiert ob die Probleme verschwinden wenn ich den Adapter abmache, werd ich aber nachher mal tun.

 

[druckluft]

Gut möglich, dass die Probleme vom WLAN Adapter verursacht werden. WLAN gehört bei DPC Problemen zu den üblichen Verdächtigen. Wenn die Probleme vorher nicht vorhanden waren, ist die Wahrscheinlichkeit umso größer.

Bei Werten der DPC Latenz um die 70000 kann man davon ausgehen, dass das auch auf Consumer Soundkarten hörbare Probleme macht (Aussetzer bzw kurze Loops des Audiopuffers). Falls die Probleme auch ohne WLAN bestehen bleiben, zeigt dir der Latency Monitor noch den verursachenden Treiber an (leider nicht mit 100% Aussagekraft). Das Problem läßt sich damit evtl weiter eingrenzen, eine noch genauere Analyse läßt sich mit dem Windows Performance Toolkit machen. Ich weiß nicht ob der User MagicAndre1981 hier noch aktiv ist, der kannte sich damit ziemlich gut aus...

 

[Gkla]

Nach 2 Stunden LatencyMon:

Spoiler

_________________________________________________________________________________________________________
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. Also one or more ISR routines that belong to a driver running in your system appear to be executing for too long. 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 2:10:47 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: ASUSTeK COMPUTER INC., M5A97 EVO R2.0
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor
Logical processors: 8
Processor groups: 1
RAM: 16283 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 4334 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): 71128,189827
Average measured interrupt to process latency (µs): 8,916683

Highest measured interrupt to DPC latency (µs): 71071,964250
Average measured interrupt to DPC latency (µs): 3,998280


_________________________________________________________________________________________________________
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): 3180,781726
Driver with highest ISR routine execution time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation

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

Total time spent in ISRs (%) 0,118831

ISR count (execution time <250 µs): 9682804
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 90
ISR count (execution time 1000-1999 µs): 85
ISR count (execution time 2000-3999 µs): 4
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): 74332,477388
Driver with highest DPC routine execution time: asstor64.sys - Asmedia 106x SATA Host Controller Driver, Asmedia Technology

Highest reported total DPC routine time (%): 0,206443
Driver with highest DPC total execution time: USBPORT.SYS - USB 1.1 & 2.0-Porttreiber, Microsoft Corporation

Total time spent in DPCs (%) 0,492435

DPC count (execution time <250 µs): 51901658
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 139
DPC count (execution time 1000-1999 µs): 13
DPC count (execution time 2000-3999 µs): 14
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 4276
Hard pagefault count of hardest hit process: 2661
Highest hard pagefault resolution time (µs): 116248,309183
Total time spent in hard pagefaults (%): 0,022205
Number of processes hit: 15


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 334,932470
CPU 0 ISR highest execution time (µs): 3180,781726
CPU 0 ISR total execution time (s): 63,974153
CPU 0 ISR count: 8007506
CPU 0 DPC highest execution time (µs): 71266,811029
CPU 0 DPC total execution time (s): 121,444572
CPU 0 DPC count: 42050745
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 372,25960
CPU 1 ISR highest execution time (µs): 89,245039
CPU 1 ISR total execution time (s): 1,141953
CPU 1 ISR count: 195495
CPU 1 DPC highest execution time (µs): 71141,073835
CPU 1 DPC total execution time (s): 19,112796
CPU 1 DPC count: 1056509
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 240,634182
CPU 2 ISR highest execution time (µs): 83,407245
CPU 2 ISR total execution time (s): 1,151341
CPU 2 ISR count: 182940
CPU 2 DPC highest execution time (µs): 74332,477388
CPU 2 DPC total execution time (s): 18,049261
CPU 2 DPC count: 1067461
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 213,037674
CPU 3 ISR highest execution time (µs): 82,574758
CPU 3 ISR total execution time (s): 1,098677
CPU 3 ISR count: 179613
CPU 3 DPC highest execution time (µs): 71141,815413
CPU 3 DPC total execution time (s): 17,747467
CPU 3 DPC count: 961170
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 357,636064
CPU 4 ISR highest execution time (µs): 104,445316
CPU 4 ISR total execution time (s): 1,117446
CPU 4 ISR count: 184399
CPU 4 DPC highest execution time (µs): 71129,051454
CPU 4 DPC total execution time (s): 28,467535
CPU 4 DPC count: 1585405
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 329,773275
CPU 5 ISR highest execution time (µs): 3073,759575
CPU 5 ISR total execution time (s): 1,116479
CPU 5 ISR count: 185526
CPU 5 DPC highest execution time (µs): 71159,662437
CPU 5 DPC total execution time (s): 20,915981
CPU 5 DPC count: 1005335
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 335,038343
CPU 6 ISR highest execution time (µs): 2072,254269
CPU 6 ISR total execution time (s): 1,466155
CPU 6 ISR count: 233546
CPU 6 DPC highest execution time (µs): 74183,118366
CPU 6 DPC total execution time (s): 27,602882
CPU 6 DPC count: 1341919
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 360,578580
CPU 7 ISR highest execution time (µs): 114,618366
CPU 7 ISR total execution time (s): 3,536668
CPU 7 ISR count: 513958
CPU 7 DPC highest execution time (µs): 71212,279649
CPU 7 DPC total execution time (s): 55,813455
CPU 7 DPC count: 2834518

Sollte es am WLAN Adapter liegen, kann man dagegen was tun oder muss da einfach ein neuer (teuerer) her?
Brauch grad noch das Internet, werd das aber definitiv mal testen ob der LatencyMon Test anders ausfällt wenn ich den Stick abmache.

 

[druckluft]

Also der Latency Monitor nennt als Verursacher den Treiber für den Asmedia SATA-Controller: 'asstor64.sys - Asmedia 106x SATA Host Controller Driver'

Muss aber nicht zwingend heißen, dass das der Verursacher ist. Ich würde jetzt folgendermaßen vorgehen:

- WLAN Stick abstecken und schauen ob es sich bessert.

- Falls am Asmedia SATA Port ein Device angeschlossen ist, würde ich das mal testweise entfernen und schauen ob sich was verändert. Du kannst auch im Gerätemanager den Treiber vorrübergehend deaktivieren. Falls hier Besserung eintritt, hilft eventuell ein Treiberupdate oder ein BIOS Update des Controllers. Falls es ein Onboard Controller ist, bitte das Update des Boardherstellers verwenden. Eventuell ist auch ein Downgrade auf eine bestimmte Treiber/BIOS Kombination nötig (vielleicht findest du bei Google was dazu). Zur Not kannst du den Controller auch komplett deaktiviert lassen (BIOS oder Gerätemanager).

 

[Gkla]

Hab WLAN Adapter abgemacht und den SATA Driver deinstalliert.

Spoiler

_________________________________________________________________________________________________________
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:11:40 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: ASUSTeK COMPUTER INC., M5A97 EVO R2.0
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor
Logical processors: 8
Processor groups: 1
RAM: 16283 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 4334 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): 4304,091545
Average measured interrupt to process latency (µs): 9,478560

Highest measured interrupt to DPC latency (µs): 189,229778
Average measured interrupt to DPC latency (µs): 3,335320


_________________________________________________________________________________________________________
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): 74,958699
Driver with highest ISR routine execution time: USBPORT.SYS - USB 1.1 & 2.0-Porttreiber, Microsoft Corporation

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

Total time spent in ISRs (%) 0,016997

ISR count (execution time <250 µs): 117111
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): 210,39940
Driver with highest DPC routine execution time: amd_sata.sys - AHCI 1.2 Device Driver, Advanced Micro Devices

Highest reported total DPC routine time (%): 0,012236
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,049602

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

Total number of hard pagefaults 2311
Hard pagefault count of hardest hit process: 1033
Highest hard pagefault resolution time (µs): 118128,475311
Total time spent in hard pagefaults (%): 0,332083
Number of processes hit: 17


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 5,062453
CPU 0 ISR highest execution time (µs): 60,483849
CPU 0 ISR total execution time (s): 0,636968
CPU 0 ISR count: 71911
CPU 0 DPC highest execution time (µs): 210,39940
CPU 0 DPC total execution time (s): 1,380410
CPU 0 DPC count: 404759
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 2,867234
CPU 1 ISR highest execution time (µs): 48,813336
CPU 1 ISR total execution time (s): 0,034785
CPU 1 ISR count: 5208
CPU 1 DPC highest execution time (µs): 209,025150
CPU 1 DPC total execution time (s): 0,212729
CPU 1 DPC count: 37448
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 2,453885
CPU 2 ISR highest execution time (µs): 46,985233
CPU 2 ISR total execution time (s): 0,040268
CPU 2 ISR count: 5354
CPU 2 DPC highest execution time (µs): 138,877250
CPU 2 DPC total execution time (s): 0,173680
CPU 2 DPC count: 21705
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2,132280
CPU 3 ISR highest execution time (µs): 43,710891
CPU 3 ISR total execution time (s): 0,034552
CPU 3 ISR count: 4997
CPU 3 DPC highest execution time (µs): 208,949008
CPU 3 DPC total execution time (s): 0,127885
CPU 3 DPC count: 16274
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 2,378437
CPU 4 ISR highest execution time (µs): 36,754038
CPU 4 ISR total execution time (s): 0,040713
CPU 4 ISR count: 5501
CPU 4 DPC highest execution time (µs): 208,789571
CPU 4 DPC total execution time (s): 0,168889
CPU 4 DPC count: 22303
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 2,216577
CPU 5 ISR highest execution time (µs): 35,973466
CPU 5 ISR total execution time (s): 0,036977
CPU 5 ISR count: 5368
CPU 5 DPC highest execution time (µs): 141,568989
CPU 5 DPC total execution time (s): 0,137444
CPU 5 DPC count: 17557
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 2,009122
CPU 6 ISR highest execution time (µs): 54,833641
CPU 6 ISR total execution time (s): 0,041647
CPU 6 ISR count: 5871
CPU 6 DPC highest execution time (µs): 208,891094
CPU 6 DPC total execution time (s): 0,172592
CPU 6 DPC count: 24337
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 2,619564
CPU 7 ISR highest execution time (µs): 74,958699
CPU 7 ISR total execution time (s): 0,087078
CPU 7 ISR count: 12901
CPU 7 DPC highest execution time (µs): 208,990309
CPU 7 DPC total execution time (s): 0,407494
CPU 7 DPC count: 45328

Habs nach 10 Minuten schon wieder ausgemacht weil es ja sicherlich nicht besser wird.
Hmmm, weitere Hinweise?
Echt seltsam, aber sagt mal ganz allgemein, wird das eher ein Hardware oder Software Problem sein?

 

[druckluft]

Im Prinzip kann es sowohl an der Hardware als auch an der Software liegen. Allermeistens ist jedoch letzteres wahrscheinlicher.

Da sich bei dir immerhin eine deutliche Verbesserung eingestellt hat, solltest du nochmal testen an welchem der beiden Treiber es lag. Also WLAN und SATA einzeln deaktivieren/aktivieren (so meinte ich das eigentlich in meinem vorherigen Post). Wenn du dann den Verursacher kennst, kannst du veruschen ob Updates das Problem lösen.

Auf jeden Fall sollten so wie es jetzt ist, keine Soundprobleme mehr auftreten bei Verwendung einer Consumer Soundkarte. Die Interrupt to Process Latency von ca. 4000us ist nicht schön aber auch nicht wirklich störend. An was das liegt, kannst du nur durch Try&Error (deaktivieren weiterer Geräte und Dienste, immer einzeln und dann testen) herausfinden oder mit dem Windows Performance Toolkit. Wenn du bei der Benutzung keine Einschränkung hast, würde ich es lassen. Ich glaube wenn sich zb beim Spielen die Frametimes um 4ms verschlechtern ist das nicht sooo dramatisch oder?

 

[Sound-Fuzzy]

Hab WLAN Adapter abgemacht und den SATA Driver deinstalliert.

Installier ihn mal sauber neu, den ohne passenden Treiber kann es auch Probleme geben.

Weitere Hinweise:
- CPU-OC rausnehmen (wird mit 4334MHz angezeigt)
- Smart-Werte der Platte checken
- WLAN an USB3.0-Port stecken

 

[druckluft]

Neuinstallation kann natürlich das Problem lösen, vor allem wenn dabei neue Treiberversionen installiert werden. Leider ist das nicht immer der Fall und dann hast du gleiche Problem wie vorher. Bevor ich den Aufwand einer Neuinstallation in Kauf nehmen würde (kann ja oft mehrere Tage in Anspruch nehmen), würde ich es mit Treiber und BIOS Updates probieren. War denn an dem SATA Controller überhaupt eine Disk angeschlossen? Wenn ja, dann solltest du die natürlich mal checken.
OC hingegen wird nicht das Problem sein, selbst wenn es instabil sein sollte sind solche Probleme dafür untypisch.

 

[Gkla]

Seltsam ich hab jetzt den WLAN Adapter einfach an einen anderen Port gehängt, seitdem hab ich die Audioprobleme nicht mehr. Latencymon schlägt zwar immer noch relativ oft aus, aber solange wie ich keine hörbaren Probleme mehr hab bin ich zufrieden