Windows 10: Fix of high DPC latency for dxgkrnl.sys DirectX 12 for AMD Ryzen 5600X + AMD RX6600

Hello,I have AMD build of the PC AMD AMD Ryzen 5 5600X + Gigabyte AMD RX6600 8GB Eagle.After upgrade of MS Windows 10 Pro to 11 Pro DirectX was updated to version 12.I've started to see stuttering and audio clicks.I started to investigate the possible root causes of this. Installed LatencyMon, which indicated the issue.First, I disabled all mentioned devices by LatencyMon Audio devices, Network adapters via Control Panel -> Device Manager. Didn't helped enabled all back.Then, I started to think that this is something in BIOS, enabled/disabled some features:- HPET [left enabled]- XMP

:)

 

DPC Latency High Crackles popping dxgkrnl.sys, nvlddmkm.sys, USBXHC

So I bought a new computer.
And the problem of crackling and bouncing back.
It is important to note that my previous computer also had the same 3080 video card.
Beyond that all the hardware is new.
I need help attaching information about the problem I have I would love help from anyone who understands.

Windows 10 - version 21h1 os 19043.1055
cpu: AMD Ryzen 9 5900X 12-Core
ram: hyperx 2x16 3600
gpu: nividia evga xc3 3080.
Motherboard: Asus rog X570 - E.

Latencymon-








windows preformance:

 

High DPC Latency caused by wdf01000.sys

Hello,

I am posting this regarding a problem that I ran across in my laptop at the beginning of august 2019, the problem is that I am getting high DPC Latency levels that are apparently caused by wdf01000.sys according to the latency checking
program, latencymon.

I really want to know if there is a fix since I have browsed a wide range of sites trying to find a fix, I could not find any. And also my keyboard stopped working for some reason, if its ok I would like to find a fix for that, but
I prioritize fixing the high latency over the keyboard.

Thank you for taking your time to read this.

 

Extremely high DPC Latency from Directx Graphics Kernel since Anniversary Update.

I'm completely guessing here, could be totally wrong, but it seems like Microsoft changed something with how DirectX works/communicates with Display Drivers (both AMD&Nvidia). Maybe AMD&Nvidia are unaware of said changes or having difficulty dealing with the
changes.