Lags in Spielen und keine Ahnung warum

Hallo!

Zuerstmal ich bin älteres Semester
Ich habe seit kurzen einen neuen PC mit Windows 7. Ich bin zwar älter, spiele aber gerne, z.b. CS Global Offensive, WOW oder Battlefield.
Jetzt habe ich aber schon seit einiger Zeit immerwieder Lags in diesen Spielen, also nicht andauernd, sondern alle paar Sekunden stockt es und der Ping geht hoch auf 200 dann wieder 50 usw.

Ich habe mal das Tool LatencyMon drüberlaufen lassen mit dieser Auswertung:

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system seems to have difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. 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:05:27 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: WOLFGANG
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z97-K
CPU: GenuineIntel Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz
Logical processors: 4
Processor groups: 1
RAM: 7877 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3500,0 MHz
Measured CPU speed: 4087,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): 1424,229693
Average measured interrupt to process latency (µs): 1,392046

Highest measured interrupt to DPC latency (µs): 164,424217
Average measured interrupt to DPC latency (µs): 0,340319


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

Highest reported total ISR routine time (%): 0,013032
Driver with highest ISR total time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

Total time spent in ISRs (%) 0,019136

ISR count (execution time <250 µs): 379427
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): 354,9660
Driver with highest DPC routine execution time: ndis.sys - NDIS 6.20-Treiber, Microsoft Corporation

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

DPC count (execution time <250 µs): 1916325
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 5
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: avpui.exe

Total number of hard pagefaults 8212
Hard pagefault count of hardest hit process: 2292
Highest hard pagefault resolution time (µs): 504073,317429
Total time spent in hard pagefaults (%): 2,360582
Number of processes hit: 33


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 3,022559
CPU 0 ISR highest execution time (µs): 15,917429
CPU 0 ISR total execution time (s): 0,250730
CPU 0 ISR count: 379427
CPU 0 DPC highest execution time (µs): 313,623143
CPU 0 DPC total execution time (s): 1,314264
CPU 0 DPC count: 1838881
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,773918
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): 252,988857
CPU 1 DPC total execution time (s): 0,088212
CPU 1 DPC count: 16594
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,587251
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): 222,947429
CPU 2 DPC total execution time (s): 0,108568
CPU 2 DPC count: 37818
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,833160
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): 354,9660
CPU 3 DPC total execution time (s): 0,088823
CPU 3 DPC count: 23037
_________________________________________________________________________________________________________


Hat einer einen Plan, was da los ist?
Ich habe eben das Bios und die IntelHD Treiber aktualisiert.
Einer meinte, irgendwas ist mit den ATAPI.SYS Aber was ist das?

Grüße

Wolfgang

 

Du kannst mal den Ram überprüfen mit memtest86+. Das gibt es auf den LinuxMint-ISOs als auch auf der UBCD.
https://www.ultimatebootcd.com/download.html