Short freeze/stutter watching videos/playing games in W7

chunkylover42

Reputable
Jan 23, 2015
2
0
4,510
Built a brand new PC late last year, and getting alot of half-second freezes watching videos or playing games.
It could be that I'm only noticing it due to the sound looping, and could be happening all the time.
I've reinstalled the video and audio drivers many times to no avail. I'm thinking it might be a 3rd party driver. I ran latencymon and get some atrocious results. Results below.

Here's my specs
Operating System
Microsoft Windows 7 Ultimate 64-bit SP1
CPU
Intel Core i5 3550 @ 3.30GHz 45 °C
Ivy Bridge 22nm Technology
RAM
8.00 GB Dual-Channel DDR3 @ 611MHz (9-9-9-24)
Motherboard
ASUSTeK COMPUTER INC. P8H77-M (LGA1155) 30 °C
Graphics
ASUS VH222H (1920x1080@59Hz)
NVIDIA GeForce GTX 970
Hard Drives
932GB Western Digital WDC WD10EZEX-08M2NA0 ATA Device (SATA) 34 °C
224GB OCZ-AGILITY3 ATA Device (SSD) 30 °C
Optical Drives
PLDS DVD-RW DH16ABSH ATA Device
MZMX IBK1M7S9 SCSI CdRom Device
Audio
Realtek High Definition Audio


Here's my latencymon results


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


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: FUCK-PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: ASUSTeK COMPUTER INC., P8H77-M
CPU: GenuineIntel Intel(R) Core(TM) i5-3550 CPU @ 3.30GHz
Logical processors: 4
Processor groups: 1
RAM: 8136 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3299.0 MHz
Measured CPU speed: 290.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.

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): 77898.800881
Average measured interrupt to process latency (µs): 8.864629

Highest measured interrupt to DPC latency (µs): 76154.255998
Average measured interrupt to DPC latency (µs): 3.215111


_________________________________________________________________________________________________________
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): 264.446499
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0.105252
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0.172021

ISR count (execution time <250 µs): 705968
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 1
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): 10525.208548
Driver with highest DPC routine execution time: ndis.sys - NDIS 6.20 driver, Microsoft Corporation

Highest reported total DPC routine time (%): 0.148702
Driver with highest DPC total execution time:

Total time spent in DPCs (%) 0.410847

DPC count (execution time <250 µs): 3091565
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 6
DPC count (execution time 1000-1999 µs): 5
DPC count (execution time 2000-3999 µs): 118
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: avastsvc.exe

Total number of hard pagefaults 1195
Hard pagefault count of hardest hit process: 675
Highest hard pagefault resolution time (µs): 75655.742952
Total time spent in hard pagefaults (%): 0.163633
Number of processes hit: 18


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 17.940307
CPU 0 ISR highest execution time (µs): 264.446499
CPU 0 ISR total execution time (s): 3.132983
CPU 0 ISR count: 705969
CPU 0 DPC highest execution time (µs): 10525.208548
CPU 0 DPC total execution time (s): 6.886742
CPU 0 DPC count: 2975977
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 2.484357
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): 2318.875417
CPU 1 DPC total execution time (s): 0.223903
CPU 1 DPC count: 26687
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 7.724421
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): 2402.789936
CPU 2 DPC total execution time (s): 0.180307
CPU 2 DPC count: 36562
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 5.292729
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): 2290.831464
CPU 3 DPC total execution time (s): 0.191728
CPU 3 DPC count: 52473
_________________________________________________________________________________________________________
 

ThomasLeong

Honorable
May 27, 2013
305
1
10,960
Discovery is going to be a long, long process. Quickest route is to re-install Windows and motherboard drivers. If you have cloned it or set a Restore Point early in your setup BEFORE installing applications software, that would be a starting point.

Test to ensure problem is solved at this start point. Then, one by one install your other software. Test video runs after every install. At some juncture you should find the culprit which is causing the problem (could be codec clashes or a video filter over-ride or ???). Then google for a solution, else discard that software.

Thomas Leong