PC Drivers & Software

[daniagatha]

I saw some thread already saying the the issue was resolved with 22.11.2 but with me it was the opposite.

Since I updated to 22.11.2 I am having DPC latency when my second monitor is on and I have chrome or chrome based apps (discord).

my setup

ASUS TUF GAMING B550M-PLUS
AMD Ryzen 5 5600X
AMD Radeon RX 6700 XT

[ThreeDee]

What speed is your memory actually running at? (Task Manager>Performance>Memory)

What is  your FLCK set to? 

Are you running the latest BIOS for your motherboard?

Do you have the latest AM4 Chipset drivers installed from AMD.com?

Have you tried running the program called "DDU"? .. remove all things AMD GPU driver related files .. reboot .. and THEN install latest GPU drivers from AMD.com

Make sure your Windows install is up to date

IF  you don't already use LatencyMon .. maybe give it a go

https://www.sweetwater.com/sweetcare/articles/solving-dpc-latency-issues/ 

[daniagatha]

I always do clean install when ugrading driver. Using the latencymon, I tested without the second monitor and with it and the latecy is enormous.

Highest reported DPC routine execution time (µs): 881,658002 (dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation)

32gb ram@2400Mhz

running the latest BIOS yes with the latest chipset.

[ThreeDee]

starven' your 5600x a bit with those memory speeds

You do a clean install of Windows? ..or just the option in the driver to do a "Clean Install"?

DDU is a bit more thorough than AMD's "Clean Install" option

So DirectX is causing latency? Have you tried just reinstalling DirectX?

https://www.microsoft.com/en-us/download/details.aspx?id=35

or open up a command prompt as admin and type:

sfc /scannow 

It will look for and attempt to repair corrupt system files ..there are various DISM commands to IF sfc finds/repairs a bunch of stuff that I'd run as well

Is your Windows install up to date?

is SAM showing as enabled in drivers?

[daniagatha]

I did everything and still has DPC latency.

[daniagatha]

Just want to bump up saying that the last update (23.2.1) fixed the issue