[SOLVED] Audio/Video Stutter (Audio makes a "glitchy" sound); Mouse Freezes During Stutter. High DPC Latency. FIX: using a cabled network (got Ethernet cable)

friedrice

Member
Joined
Mar 13, 2020
Posts
14
Hey guys, I've had this problem since September of last year. The title basically describes my situation. I moved in with my girlfriend last year, and due to not having a truck, I moved my things slowly having my PC the first to go. My car has stiff springs so I thought this is a hardware issue, which it still might be, but the parts that I think would be affected (RAM and GPU) are both fine. At first it was just the audio and video having the stutters. I had my PC hooked up to the TV and thought it could have just been the TV, but the problem persisted when I had my desk and peripherals. I noticed the mouse also being affected when I was playing games and my mouse would not be in the position I expected it to be; it lagged behind.

For what I've done, I have done a clean install of Windows 10, new RAM, ran on Intel Graphics, updated all my drivers, updated my BIOS, but the problem is still here.

I've seen other posts on this forum about similar issues, but most are tailored for their specs. Any help will be greatly appreciated!

My Specs:
Intel i5-6600K
MSI GTX 1070
8GB Viper DDR4 Memory (Later swapped with Kingston HyperX 8GB)
MSI Z170A Gaming M7 Motherboard
120GB Kingston SSD
1TB Seagate Barracuda HDD
500GB Western Digital HDD
Razer NAGA Trinity Mouse
Corsair K70 Keyboard
 
I ran LatencyMon for almost an hour on idle.

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


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-086QR17
OS version: Windows 10 , 10.0, build: 18363 (x64)
Hardware: MS-7976, MSI, Z170A GAMING M7 (MS-7976)
CPU: GenuineIntel Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
Logical processors: 4
Processor groups: 1
RAM: 8153 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3504 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.

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

Highest measured interrupt to DPC latency (µs): 1756.90
Average measured interrupt to DPC latency (µs): 0.529031


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

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

Total time spent in ISRs (%) 0.021728

ISR count (execution time <250 µs): 186863
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): 86319.986301
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Highest reported total DPC routine time (%): 0.700964
Driver with highest DPC total execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Total time spent in DPCs (%) 0.749775

DPC count (execution time <250 µs): 7751638
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 20
DPC count (execution time 1000-1999 µs): 1
DPC count (execution time 2000-3999 µs): 3
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: msmpeng.exe

Total number of hard pagefaults 3300
Hard pagefault count of hardest hit process: 956
Number of processes hit: 27


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 113.955468
CPU 0 ISR highest execution time (µs): 211.764840
CPU 0 ISR total execution time (s): 2.756050
CPU 0 ISR count: 186859
CPU 0 DPC highest execution time (µs): 86319.986301
CPU 0 DPC total execution time (s): 95.049688
CPU 0 DPC count: 7729071
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 4.404043
CPU 1 ISR highest execution time (µs): 12.676941
CPU 1 ISR total execution time (s): 0.000048
CPU 1 ISR count: 4
CPU 1 DPC highest execution time (µs): 84.738014
CPU 1 DPC total execution time (s): 0.030226
CPU 1 DPC count: 13381
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 4.397069
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): 51.611301
CPU 2 DPC total execution time (s): 0.010281
CPU 2 DPC count: 3855
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 4.431714
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): 95.049087
CPU 3 DPC total execution time (s): 0.015949
CPU 3 DPC count: 6415
_________________________________________________________________________________________________________
 

Attachments

  • LatencyMon.png
    LatencyMon.png
    57.2 KB · Views: 4
  • LatencyMon1.png
    LatencyMon1.png
    81.7 KB · Views: 6
A link here to your logs.

Hey, okay so I'm basically almost done and in the last final steps, but when I try to execute the "xperf -on DiagEasy" code, I get an error saying, "xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7)."
Any idea how I can fix this?
 
Stop It with the second command written in the guide, then re-try.
Okay, I tried it again and the error popped up again. I entered the second command and it left a trace.etl on my desktop. Is this the right file? Or should I retry since I got the error to begin with?

Edit: I tried right after and was prompted with "The trace you have just captured "C:\Users\USER\Desktop\trace.etl" may contain personally identifiable information, including but not necessarily limited to paths to files accessed, paths to registry accessed and process names. Exact information depends on the events that were logged. Please be aware of this when sharing out this trace with other people."
 
System Manufacturer?
N/A

Laptop or Desktop?
Desktop

Exact model number
N/A

OS?
Windows 10 Pro

x86 (32-bit) or x64 (64-bit)?
64-bit

Service Pack?
Feature update to Windows 10, version 1909

What was original installed OS on system?
Windows 10 Pro

Is the OS an OEM version or full retail version?
Full Retail Version

Age of system? (hardware)
Approx 3 years

Age of OS installation?
1 week

Have you re-installed the OS?
Yes

CPU
Intel(R) Core(TM) i5-6600K @ 3.50GHz

RAM
2x4GB Patriot Viper DDR4 RAM @ 3200MHz, on slots 2 and 4

Video Card
MSI GeForce GTX 1070 Gaming X 8GB

Motherboard
MSI Z170A Gaming M7

Power Supply - brand & wattage


Is driver verifier enabled or disabled?

Disabled

What security software are you using?
Windows Defender

Are you using proxy, vpn, ipfilters or similar software?
No

Are you using Disk Image tools?
No

Are you currently under/overclocking?
No

Are there overclocking software installed on your system?
No

Speccy System Information: Here
 

Attachments

Before you follow all instructions, create a system restore point and a system image with your preferred tool (example: macrium reflect free... Prepare an USB rescue media, if you didn't already do it).
And backup all of your important data present in the drives.

Update the firmware for your kingston ssd SV300S37A/120G: the current version of it is 505ABBF1, the most updated version of the firmware is 60AABBF0 (on kingston.com).
Update the firmware for your seagate ST1000DM003-1CH162: the current version of it is CC47, the most updated version of the firmware is CC4H (on seagate.com).
There's a new version of nvidia drivers: 442.74.
Set dram speed to 2133 in your bios settings.
 
Last edited:
Before you follow all instructions, create a system restore point and a system image with your preferred tool (example: macrium reflect free... Prepare an USB rescue media, if you didn't already do it).
And backup all of your important data present in the drives.

Update the firmware for your kingston ssd SV300S37A/120G: the current version of it is 505ABBF1, the most updated version of the firmware is 60AABBF0 (on kingston.com).
Update the firmware for your seagate ST1000DM003-1CH162: the current version of it is CC47, the most updated version of the firmware is CC4H (on seagate.com).
There's a new version of nvidia drivers: 442.74.
Set dram speed to 2133 in your bios settings.

I've updated the firmware on my SSD, but I'm having trouble updating the Seagate one. I get an error when I run the .exe update and prompted me to try the .iso version. I can't burn it though cause I don't have a burner and I dont know how to put it on a usb drive. Also, on my bios, the dram speed is at 2176 and there's no 2133 option, just 2142 and 2040 after that
 
Update, so I tried booting my system with the Seagate 1TB HDD unplugged to see if the problem still occurs, and yes, it still does.
I've also set the dram frequency to 2142 down from 2176, and the problem still occurs.
 
Last edited:
Update: I think I've isolated what's causing the problem. I uninstalled all of the network adapter drivers in device manager and have been running LatencyMon for approx. 6 minutes without any issues. I've downloaded the drivers for my adapter, but I'm gonna leave LatencyMon running for a while. Will come back after I've installed drivers and restarted.
 
I ran LatencyMon for about 1 hour and 30 minutes with no latency. Installed my adapter drivers, restarted, and within 1 minute of running LatencyMon, I'm already experiencing the problem. I personally think this might be a hardware issue, but if anyone can tell me otherwise, I'd love to hear it.
 
Did you try to connect with the ethernet cable?

I got the Ethernet cable and ran LatencyMon for an hour with no issues whatsoever. My only concern now is if my network adapter has hardware or software issues, though leaning with the former. Thank you for all the help.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top