Question High DPC latency after fresh windows 10 instal, causes popping and stuttering in audio and video/games

May 7, 2019
1
0
10
Greetings,

So reinstalled windows a few days ago because i got a SSD.
I noticed DPC latency after installing pretty much everything so i did a clean/fresh reinstall of windows, formatted all drives etc.
As soon as it installed i downloaded LatencyMon and i have high DPC latency even without any drivers/software installed.
Since then i've tried every possible fix i found on the internet and none of them work, so here i am asking for help.
Is it possible that the new SSD is faulty in some way and causing the DPC latency?
I will honestly very much appreciate any kind of insight that could lead to a solution.
The latmon data is in the spoiler
PC specs:
Processor: AMD FX-6100
Motherboard: ASRock 960GC -GS FX
8 GB of ram DDR3
GPU: AMD MSI R9 270X Twin Frozr gaming
120 GB Kingston SSD
1TB Seagate HDD

_
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. 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:14:43 (h🇲🇲ss) on all processors.


_
SYSTEM INFORMATION
_
Computer name: DESKTOP-Q5TBVNV
OS version: Windows 10 , 10.0, build: 17763 (x64)
Hardware: ASRock, 960GC-GS FX
CPU: AuthenticAMD AMD FX(tm)-6100 Six-Core Processor
Logical processors: 6
Processor groups: 1
RAM: 8175 MB total


_
CPU SPEED
_
Reported CPU speed: 3307 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): 43562.0
Average measured interrupt to process latency (µs): 10.139245

Highest measured interrupt to DPC latency (µs): 34895.50
Average measured interrupt to DPC latency (µs): 3.494999


_
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): 35037.170547
Driver with highest ISR routine execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0.037884
Driver with highest ISR total time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation

Total time spent in ISRs (%) 0.055423

ISR count (execution time <250 µs): 336652
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 107
ISR count (execution time 1000-1999 µs): 48
ISR count (execution time 2000-3999 µs): 98
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): 27393.724826
Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

Total time spent in DPCs (%) 0.416214

DPC count (execution time <250 µs): 2540717
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 3182
DPC count (execution time 1000-1999 µs): 189
DPC count (execution time 2000-3999 µs): 184
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: winstore.app.exe

Total number of hard pagefaults 6205
Hard pagefault count of hardest hit process: 644
Number of processes hit: 65


_
PER CPU DATA
_
CPU 0 Interrupt cycle time (s): 74.578141
CPU 0 ISR highest execution time (µs): 34800.272755
CPU 0 ISR total execution time (s): 2.319080
CPU 0 ISR count: 313744
CPU 0 DPC highest execution time (µs): 27393.724826
CPU 0 DPC total execution time (s): 17.704694
CPU 0 DPC count: 2409359
_
CPU 1 Interrupt cycle time (s): 26.922139
CPU 1 ISR highest execution time (µs): 35037.170547
CPU 1 ISR total execution time (s): 0.558173
CPU 1 ISR count: 21112
CPU 1 DPC highest execution time (µs): 24795.406713
CPU 1 DPC total execution time (s): 1.893467
CPU 1 DPC count: 92816
_
CPU 2 Interrupt cycle time (s): 20.497894
CPU 2 ISR highest execution time (µs): 5025.901119
CPU 2 ISR total execution time (s): 0.059973
CPU 2 ISR count: 2083
CPU 2 DPC highest execution time (µs): 6573.347142
CPU 2 DPC total execution time (s): 1.382067
CPU 2 DPC count: 19053
_
CPU 3 Interrupt cycle time (s): 19.517024
CPU 3 ISR highest execution time (µs): 2.292108
CPU 3 ISR total execution time (s): 0.000002
CPU 3 ISR count: 1
CPU 3 DPC highest execution time (µs): 4609.775930
CPU 3 DPC total execution time (s): 0.046166
CPU 3 DPC count: 4531
_
CPU 4 Interrupt cycle time (s): 18.052258
CPU 4 ISR highest execution time (µs): 12.524342
CPU 4 ISR total execution time (s): 0.000024
CPU 4 ISR count: 7
CPU 4 DPC highest execution time (µs): 8873.999395
CPU 4 DPC total execution time (s): 0.966241
CPU 4 DPC count: 12594
_
CPU 5 Interrupt cycle time (s): 19.430448
CPU 5 ISR highest execution time (µs): 1.761113
CPU 5 ISR total execution time (s): 0.000006
CPU 5 ISR count: 5
CPU 5 DPC highest execution time (µs): 331.134261
CPU 5 DPC total execution time (s): 0.065393
CPU 5 DPC count: 6036
_
 

JoeMcDonalds27

Reputable
BANNED
Mar 26, 2016
20
0
4,520
To isolate if the issue is somehow being caused by the newly installed SSD, can you remove the SSD from the system and then install OS on the 1TB Seagate HDD and see what the behavior is. If after OS installation on 1TB Seagate HDD the system works fine then we could conclude that the issue was with the SSD drive.

Regards,
Joe
 

ASK THE COMMUNITY

TRENDING THREADS