How do i fix microstuttering in windows?

I have had microstutters for a few months now and i have been unable to fix them myself. Please help me out.
Code:
__________________________________________________ __________________________________________________ _____
CONCLUSION
__________________________________________________ __________________________________________________ _____
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:01:20 (h:mm:ss) on all processors.


__________________________________________________ __________________________________________________ _____
SYSTEM INFORMATION
__________________________________________________ __________________________________________________ _____
Computer name: DESKTOP-97FJL74
OS version: Windows 10, 10.0, version 2009, build: 22000 (x64)
Hardware: System Product Name, System manufacturer
CPU: AuthenticAMD AMD Ryzen 5 3600X 6-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 16318 MB total


__________________________________________________ __________________________________________________ _____
CPU SPEED
__________________________________________________ __________________________________________________ _____
Reported CPU speed: 3793 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): 247.936539
Average measured interrupt to process latency (µs): 10.335713

Highest measured interrupt to DPC latency (µs): 223.561933
Average measured interrupt to DPC latency (µs): 4.938517


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

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

Total time spent in ISRs (%) 0.010184

ISR count (execution time <250 µs): 3414
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
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): 420.795149
Driver with highest DPC routine execution time: tcpip.sys - TCP/IP Driver, Microsoft Corporation

Highest reported total DPC routine time (%): 0.010385
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 512.95 , NVIDIA Corporation

Total time spent in DPCs (%) 0.030536

DPC count (execution time <250 µs): 26315
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 44
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µ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: dllhost.exe

Total number of hard pagefaults 111
Hard pagefault count of hardest hit process: 26
Number of processes hit: 16


__________________________________________________ __________________________________________________ _____
PER CPU DATA
__________________________________________________ __________________________________________________ _____
CPU 0 Interrupt cycle time (s): 1.685536
CPU 0 ISR highest execution time (µs): 207.562352
CPU 0 ISR total execution time (s): 0.098743
CPU 0 ISR count: 3322
CPU 0 DPC highest execution time (µs): 420.795149
CPU 0 DPC total execution time (s): 0.283779
CPU 0 DPC count: 25294
__________________________________________________ __________________________________________________ _____
CPU 1 Interrupt cycle time (s): 0.750996
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): 208.934880
CPU 1 DPC total execution time (s): 0.001269
CPU 1 DPC count: 82
__________________________________________________ __________________________________________________ _____
CPU 2 Interrupt cycle time (s): 0.820822
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): 307.877142
CPU 2 DPC total execution time (s): 0.002420
CPU 2 DPC count: 55
__________________________________________________ __________________________________________________ _____
CPU 3 Interrupt cycle time (s): 0.877052
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): 0.0
CPU 3 DPC total execution time (s): 0.0
CPU 3 DPC count: 0
__________________________________________________ __________________________________________________ _____
CPU 4 Interrupt cycle time (s): 0.672083
CPU 4 ISR highest execution time (µs): 0.0
CPU 4 ISR total execution time (s): 0.0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 306.715001
CPU 4 DPC total execution time (s): 0.006742
CPU 4 DPC count: 762
__________________________________________________ __________________________________________________ _____
CPU 5 Interrupt cycle time (s): 0.886103
CPU 5 ISR highest execution time (µs): 0.0
CPU 5 ISR total execution time (s): 0.0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 266.050092
CPU 5 DPC total execution time (s): 0.001091
CPU 5 DPC count: 132
__________________________________________________ __________________________________________________ _____
CPU 6 Interrupt cycle time (s): 0.813802
CPU 6 ISR highest execution time (µs): 0.0
CPU 6 ISR total execution time (s): 0.0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 215.416820
CPU 6 DPC total execution time (s): 0.000356
CPU 6 DPC count: 19
__________________________________________________ __________________________________________________ _____
CPU 7 Interrupt cycle time (s): 0.828680
CPU 7 ISR highest execution time (µs): 0.0
CPU 7 ISR total execution time (s): 0.0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 8.736093
CPU 7 DPC total execution time (s): 0.000013
CPU 7 DPC count: 2
__________________________________________________ __________________________________________________ _____
CPU 8 Interrupt cycle time (s): 0.123189
CPU 8 ISR highest execution time (µs): 0.751384
CPU 8 ISR total execution time (s): 0.000002
CPU 8 ISR count: 3
CPU 8 DPC highest execution time (µs): 266.230424
CPU 8 DPC total execution time (s): 0.000496
CPU 8 DPC count: 4
__________________________________________________ __________________________________________________ _____
CPU 9 Interrupt cycle time (s): 0.122455
CPU 9 ISR highest execution time (µs): 0.0
CPU 9 ISR total execution time (s): 0.0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 7.303454
CPU 9 DPC total execution time (s): 0.000021
CPU 9 DPC count: 3
__________________________________________________ __________________________________________________ _____
CPU 10 Interrupt cycle time (s): 0.125863
CPU 10 ISR highest execution time (µs): 0.0
CPU 10 ISR total execution time (s): 0.0
CPU 10 ISR count: 0
CPU 10 DPC highest execution ti,me (µs): 7.052992
CPU 10 DPC total execution time (s): 0.000007
CPU 10 DPC count: 1
__________________________________________________ __________________________________________________ _____
CPU 11 Interrupt cycle time (s): 0.124081
CPU 11 ISR highest execution time (µs): 0.701292
CPU 11 ISR total execution time (s): 0.000052
CPU 11 ISR count: 89
CPU 11 DPC highest execution time (µs): 12.923807
CPU 11 DPC total execution time (s): 0.000047
CPU 11 DPC count: 5

Ooooh, I know, I know, I know! Sorry this took so long.

This is one of the most common and worst bugs, it really interferes with gaming feedback on the monitor.

I discovered it can be your screen if it is Adaptive sync. You may have to turn on your Gsync/Freesync mode and play games in unlocked framerates. Locked frame rates sometimes interefere with Async and variable refresh.

It can also be a polling bug between your usb mouse and cpu. You can sometimes remedy this one by unplugging the mouse and usb devices. Then you can change the polling rate of your mouse to a lower polling rate, which doesn't affect performance, it's just a silly gimmick.

The mouse bug is a good reason not to have a gaming mouse with all these gimmicky features. There is a polling bug that causes stuttering issues.

Then there is hardware acceleration and scheduling features on the PC.

Then there is software side syncing and other issues you sometimes can't fix.

Many times PC game bugs can be fixed on the user end but sometimes it is software.



Can you provide examples? I see you play CoD and these fixes, particularly variable refresh/unlocked fps should help. That engine is one I've had the problem with. Try these fixes.

What GPU do you have? I see some Nvidia driver info but not what GPU you have.

Couple things to look at:

your hard page faults seems kinda high, for a system with 16GB of memory. Have you fiddled with the pagefile settings in the past?

I noticed your Network card driver is a generic Microsoft one, which implies maybe you haven't installed your motherboard's chipset drivers. This is usually the second thing I do on a new PC, after updating all the BIOS'es. Third is updating all the other drivers, including GPU, network card, sound card, USB, wireless drivers, etc. Your mobo manufacturer should have an update tool that will help you with this process.

I am uncertain all the bugs but monitor stuff is often related to adaptive sync and usb mouse polling as I mentioned. There are no permanent fixes for the bugs. You'll have to reset your mouse polling to 500hz and often resetting the monitor helps with syncing issues. If you have adaptive sync, freesync or gsync they can cause issues off or on. You'll have to experiment with those settings on vsync on off and locked or unlocked frame rate.

Many screens out there are genuinely buggy out of the box with bad pixel clocks or some other busted issues that subliminal. So if you think it's your screen go to blur busters and run some testa and read their articles about latency and pizel clocks. Most of their articles are from years ago so their hardware is outdated but still relevant if you want their monitor choice.


Like I got a LG Ultra Gear 32" 2k 144hz, it's ok but another buggy mess with mediocre oicture quality. 27" is better for 1440p then 4k+ for 32"+.

Other than that it could be cpu, gpu, ram, bios related, lots of troubleshooting there.