[SOLVED] Computer has microstutters after a day or two

[AoDnightshade]

So the simple situations is that about 1-2 months ago I started getting microstutters where the computer would just tank and any sound would glitch for half a second. a simple restart fixed this issue for a few days. I looked at temps and they all seem fine. highest i get with moderate load is about 63c. the only clue i have as to what could be going wrong is when i look at ryzen master the EDC is almost maxed at about 95-97%. nothing on task manager spikes along side the stutters either.

My specs:
Ryzen 2600x
Evga 1070
32gb 3000mhz Ram (xmp enabled)
Asrock K4 Fatal1ty x470 mobo(latest bios to see if that was the issue)

And I did a latencymon test to see what could be having issues. results:

Spoiler

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


_
SYSTEM INFORMATION
_
Computer name: DESKTOP-O3B93NH
OS version: Windows 10, 10.0, version 1909, build: 18363 (x64)
Hardware: To Be Filled By O.E.M., To Be Filled By O.E.M.
CPU: AuthenticAMD AMD Ryzen 5 2600X Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 32699 MB total


_
CPU SPEED
_
Reported CPU speed: 3593 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.


_
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): 261315.50
Average measured interrupt to process latency (µs): 35.428083

Highest measured interrupt to DPC latency (µs): 261310.90
Average measured interrupt to DPC latency (µs): 31.965116


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

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

Total time spent in ISRs (%) 0.175433

ISR count (execution time <250 µs): 2633618
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 2
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µ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): 212985.368216
Driver with highest DPC routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total DPC routine time (%): 0.503906
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0.701588

DPC count (execution time <250 µs): 4787395
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 4799
DPC count (execution time 1000-2000 µs): 7833
DPC count (execution time 2000-4000 µs): 1944
DPC count (execution time >=4000 µs): 1959


_
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: firefox.exe

Total number of hard pagefaults 53171
Hard pagefault count of hardest hit process: 31532
Number of processes hit: 111


_
PER CPU DATA
_
CPU 0 Interrupt cycle time (s): 139.091708
CPU 0 ISR highest execution time (µs): 259.775118
CPU 0 ISR total execution time (s): 14.798834
CPU 0 ISR count: 745211
CPU 0 DPC highest execution time (µs): 212985.368216
CPU 0 DPC total execution time (s): 58.613985
CPU 0 DPC count: 3085660
_
CPU 1 Interrupt cycle time (s): 42.456179
CPU 1 ISR highest execution time (µs): 451.778458
CPU 1 ISR total execution time (s): 4.574579
CPU 1 ISR count: 717600
CPU 1 DPC highest execution time (µs): 128891.522405
CPU 1 DPC total execution time (s): 19.152998
CPU 1 DPC count: 889781
_
CPU 2 Interrupt cycle time (s): 9.464134
CPU 2 ISR highest execution time (µs): 100.625661
CPU 2 ISR total execution time (s): 0.210732
CPU 2 ISR count: 169975
CPU 2 DPC highest execution time (µs): 53677.983858
CPU 2 DPC total execution time (s): 1.417896
CPU 2 DPC count: 224969
_
CPU 3 Interrupt cycle time (s): 6.842840
CPU 3 ISR highest execution time (µs): 17.053159
CPU 3 ISR total execution time (s): 0.035867
CPU 3 ISR count: 9569
CPU 3 DPC highest execution time (µs): 512.977456
CPU 3 DPC total execution time (s): 0.188335
CPU 3 DPC count: 48790
_
CPU 4 Interrupt cycle time (s): 7.725770
CPU 4 ISR highest execution time (µs): 28.194823
CPU 4 ISR total execution time (s): 0.035469
CPU 4 ISR count: 9403
CPU 4 DPC highest execution time (µs): 257.079878
CPU 4 DPC total execution time (s): 0.236818
CPU 4 DPC count: 58349
_
CPU 5 Interrupt cycle time (s): 6.884134
CPU 5 ISR highest execution time (µs): 16.482048
CPU 5 ISR total execution time (s): 0.017469
CPU 5 ISR count: 7236
CPU 5 DPC highest execution time (µs): 256.578903
CPU 5 DPC total execution time (s): 0.162681
CPU 5 DPC count: 39958
_
CPU 6 Interrupt cycle time (s): 20.957751
CPU 6 ISR highest execution time (µs): 14.70860
CPU 6 ISR total execution time (s): 0.011035
CPU 6 ISR count: 6051
CPU 6 DPC highest execution time (µs): 402.672975
CPU 6 DPC total execution time (s): 1.016788
CPU 6 DPC count: 124180
_
CPU 7 Interrupt cycle time (s): 7.482260
CPU 7 ISR highest execution time (µs): 15.490120
CPU 7 ISR total execution time (s): 0.008175
CPU 7 ISR count: 4955
CPU 7 DPC highest execution time (µs): 252.170331
CPU 7 DPC total execution time (s): 0.173495
CPU 7 DPC count: 53331
_
CPU 8 Interrupt cycle time (s): 9.330966
CPU 8 ISR highest execution time (µs): 39.226273
CPU 8 ISR total execution time (s): 0.608877
CPU 8 ISR count: 617877
CPU 8 DPC highest execution time (µs): 253.442805
CPU 8 DPC total execution time (s): 0.350048
CPU 8 DPC count: 69579
_
CPU 9 Interrupt cycle time (s): 7.595240
CPU 9 ISR highest execution time (µs): 19.828556
CPU 9 ISR total execution time (s): 0.060503
CPU 9 ISR count: 51978
CPU 9 DPC highest execution time (µs): 253.142221
CPU 9 DPC total execution time (s): 0.178067
CPU 9 DPC count: 51532
_
CPU 10 Interrupt cycle time (s): 8.547628
CPU 10 ISR highest execution time (µs): 14.267743
CPU 10 ISR total execution time (s): 0.131201
CPU 10 ISR count: 105490
CPU 10 DPC highest execution time (µs): 252.190370
CPU 10 DPC total execution time (s): 0.468061
CPU 10 DPC count: 69021
_
CPU 11 Interrupt cycle time (s): 8.761383
CPU 11 ISR highest execution time (µs): 35.188422
CPU 11 ISR total execution time (s): 0.228339
CPU 11 ISR count: 188275
CPU 11 DPC highest execution time (µs): 859.300863
CPU 11 DPC total execution time (s): 0.908029
CPU 11 DPC count: 88780
_

 

[rocktalkrock]

What drives are in your PC? Do you have any mechanical HDD's? They could be causing your problem.

 

[AoDnightshade]

I do have 2 mechanical ones for mass storage. Windows is on an ssd but like I said it doesnt show spikes on task manager, would it be a cause without anything showing?

 

[rocktalkrock]

I do have 2 mechanical ones for mass storage. Windows is on an ssd but like I said it doesnt show spikes on task manager, would it be a cause without anything showing?

Check In Power Options if your HDD's are set to never turn off. If they are set to turn off, they will need a second or two to restart (while the disk spins back up to 5400rpm) when you try to access data from them. Your computer will appear to freeze.

 

[AoDnightshade]

Sorry for the late reply but I had to restart to do some school work. that didn't help me out though. any other ideas?

 

[TwitchyTanner]

1. Disabling NVIDIA Overlay in games. I should have known something was off with it before; it would make my mouse extremely lagging after games when it would pop up with my replays and make it almost impossible to close. I might try to do a fresh install of GeForce Experience and see if that fixes that issue, but for now, it works a lot better and doesn't seem to have a large spike of FPS drops in-game as much.
2. BIOS Update. This is one people commonly suggest. This was a problem many years ago I had when I was much less technologically inclined than I am today. I had never updated my BIOS after I built my system for a whole year after I made it. I had never owned a gaming computer before so I just thought random frame drops in Rocket League were normal. Along with several other issues I had, I felt pretty dumb after I fixed it. Regardless, I was happier with my setup.
3. Chipset drivers. I had never updated my chipset drivers either. My AMD 2700x seemed like it was slightly underperforming out of the box and wasn't sure why. I did a User Benchmark before and after and the results were slightly better. I am not sure if this had anything to do with remedying my stuttering or not since this was done alongside me disabling NVIDIA overlay.
4. Graphics card drivers. This might seem like an obvious one to a lot of you guys but as a noobie trying to troubleshoot back in the day, I knew very little and this definitely was forgotten a few times until I wondered to myself why my games were sucking more than usual.
5. Windows OS corrupt files. I have seen a few instances of corrupt operating system files causing performance decreases in games, or even just general weird bugs in windows. A few of my games would randomly crash and one of my friends suggested checking my system files. You can run a command through command prompt called sfc /scannow. This has pulled corrupt windows files on a few occasions for me and has fixed them. You will have to run command prompt by searching for it in windows search bar, right click on it and hit run as administrator, type the command above and it should take about 5 minutes or so. Alternatively, you can go to your file explorer and check all your drives independently. Go to "This PC," right-click on the drive you want, click on the Tools tab, then click the "Check" option under "Error Checking." Any drive that does not contain the OS Windows will tell you that it doesn't need to check it but it honestly doesn't hurt.
6. Windows "Game Mode" This might be a big one. I might be wrong, but I think this is set to on by default. According to Techspot, this is a pretty substantial one and could be your golden ticket to better FPS... who knows? Try disabling by searching for Game Mode in Windows search bar.
7. HAGS or Hardware accelerated GPU Scheduling This setting can also be found on the same page as "Game Mode." This setting may or may not help but it seems to be on a case by case basis. It's a newer feature in the NVIDIA driver update. From what I have read online It may help gaming performance in CPU bound situations.
8. Windows 10 Power Plan This one might be less about fixing stuttering and more about getting better performance. Under "Power Options" you can change your system's power options. Go to your systems "Power and Sleep" settings and on the right side click "Additional power settings." Choose "Ultimate Performance." (would not recommend if on a gaming laptop)
9. Disabling Dynamic Tick A number of user's have been helped by this one and it seems generally a safe bet to help with stuttering frame rates. Right-click the Start menu and select Command Prompt (Admin). First, enter bcdedit /set disabledynamictick yes and press Enter. Then input bcdedit /set useplatformclock true in the Command Prompt, and press the Enter key. Thereafter, enter bcdedit /set tscsyncpolicy Enhanced in the Prompt and press Enter. Close the Command Prompt window and restart the system.