LatnecyMon

Dabei seit
März 2018
Beiträge
7
#1
Hi,

ich habe seit einiger Zeit kurze lags bei Computerspielen.

Ich habe verschiedene Treiberversionen ausprobiert. Windows 7 neu aufgesetzt, eine neue Festplatte benutzt und meine onboard Soundkarte bzw. eine Soundkarte PCI-E Soundkarte und habe immernoch die selben Probleme.
Ein BIOS Ubdate habe ich auch schon gemacht.
Ich habe das Internet schon durchstöbert, aber finde keine Lösung.
Nun hoffe ich das hier mir jemand helfen kann.

Vielen Dank schon mal :)


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


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: BVB-PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: ASRock, H87 Pro4
CPU: GenuineIntel Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
Logical processors: 4
Processor groups: 1
RAM: 8111 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3199 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): 4821,456007
Average measured interrupt to process latency (µs): 5,561685

Highest measured interrupt to DPC latency (µs): 608,163474
Average measured interrupt to DPC latency (µs): 1,646163


_________________________________________________________________________________________________________
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): 37,947171
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0,033604
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Total time spent in ISRs (%) 0,063317

ISR count (execution time <250 µs): 1281964
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): 454,146921
Driver with highest DPC routine execution time: tcpip.sys - TCP/IP-Treiber, Microsoft Corporation

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

DPC count (execution time <250 µs): 6569774
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 38
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 2102
Hard pagefault count of hardest hit process: 1139
Highest hard pagefault resolution time (µs): 556021,292904
Total time spent in hard pagefaults (%): 0,389435
Number of processes hit: 19


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 30,991548
CPU 0 ISR highest execution time (µs): 37,947171
CPU 0 ISR total execution time (s): 2,714840
CPU 0 ISR count: 1281964
CPU 0 DPC highest execution time (µs): 442,473273
CPU 0 DPC total execution time (s): 12,768011
CPU 0 DPC count: 6371252
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 22,976235
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): 454,146921
CPU 1 DPC total execution time (s): 0,282971
CPU 1 DPC count: 47359
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 19,094375
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): 420,575180
CPU 2 DPC total execution time (s): 0,336488
CPU 2 DPC count: 57499
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 16,966520
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): 409,713035
CPU 3 DPC total execution time (s): 0,431599
CPU 3 DPC count: 93702
_________________________________________________________________________________________________________
Ergänzung ()

Ich habe nochmal einen längeren Test gemacht.

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


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: BVB-PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: ASRock, H87 Pro4
CPU: GenuineIntel Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
Logical processors: 4
Processor groups: 1
RAM: 8111 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3199 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): 6831,916419
Average measured interrupt to process latency (µs): 5,672095

Highest measured interrupt to DPC latency (µs): 1011,791970
Average measured interrupt to DPC latency (µs): 1,706219


_________________________________________________________________________________________________________
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): 40,553298
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0,032780
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Total time spent in ISRs (%) 0,061657

ISR count (execution time <250 µs): 2921004
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): 1152,870272
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation

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

DPC count (execution time <250 µs): 14444251
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 82
DPC count (execution time 1000-1999 µs): 1
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 3839
Hard pagefault count of hardest hit process: 2273
Highest hard pagefault resolution time (µs): 299691,695842
Total time spent in hard pagefaults (%): 0,115725
Number of processes hit: 13


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 63,522233
CPU 0 ISR highest execution time (µs): 40,553298
CPU 0 ISR total execution time (s): 6,022201
CPU 0 ISR count: 2921004
CPU 0 DPC highest execution time (µs): 1152,870272
CPU 0 DPC total execution time (s): 24,024111
CPU 0 DPC count: 14003227
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 51,347795
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): 483,666146
CPU 1 DPC total execution time (s): 0,641640
CPU 1 DPC count: 105342
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 41,378956
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): 221,429197
CPU 2 DPC total execution time (s): 0,721808
CPU 2 DPC count: 127547
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 37,302529
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): 592,195061
CPU 3 DPC total execution time (s): 0,937940
CPU 3 DPC count: 208218
_________________________________________________________________________________________________________ LatencyMon.png
 

Z_E_R_O

Lt. Junior Grade
Dabei seit
Feb. 2006
Beiträge
300
#2
Hast du noch Audio Ein/-Ausgänge, die nicht direkt von deinem Mainboard kommen z.B. ein Frontpanel? Ich hatte ein altes Frontpanel wo mein Headset angeschlossen war, das hat Latenzen verursacht. Wenn ich es nicht benutze sind die Latenzen zwar weg, aber bei einigen Spielen hab ich trotzdem noch solche Lags. Es muss also nicht daran liegen.
 

Gerstenmalz

Newbie
Ersteller dieses Themas
Dabei seit
März 2018
Beiträge
7
#4
Nein ich habe kein Frontpanel und habe dies im BIOS auch deaktiviert.
Temperaturen sind normal.
Welche Stromsparfunktionen?
edit: Habe im BIOS soweit es möglich ist alles Stromsparfunktionen deaktiviert. Hilft leider auch nicht.
Und was meinst du mit Treiber reihenfolge?
Ergänzung ()

Hatte jetzt gerade nen BluesScreen

Problemsignatur:
Problemereignisname: BlueScreen
Betriebsystemversion: 6.1.7601.2.1.0.256.48
Gebietsschema-ID: 1031

Zusatzinformationen zum Problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002EC0B1A
BCP3: 0000000000000000
BCP4: 000000001545D260
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Dateien, die bei der Beschreibung des Problems hilfreich sind:
C:\Windows\Minidump\030818-18844-01.dmp
C:\Users\BVB\AppData\Local\Temp\WER-36239-0.sysdata.xml
 
Zuletzt bearbeitet:
Top