Reported dpc routine with latest nvidia driver 460.89 on 3080 high?Random stutter in apex

Had this random 50 ms (watched it on a frametimegraph in msi aftburner )stutter in apex happening once/twice a game so I decided to have latencymon up in the background

So I wanted to check if there was anything going on and while playing I noticed the dpc latency went as high up as 700 on nvlddmkm.sys.That test lasted around 33 minutes without any warning even tho I had the stutter happen to me ingame a couple of times while playing in those 33 minutes

Below I posted the pic of a 10 min run of latencymon while simply watching twitch/viewing web pages and I noticed it spike to 700 again without any warnings.

Is there anything I should be worried about even tho its not giving me any warnings?Could be apex being apex.


How it looks like.It's actually not just 1 spike but 3 quick micro stutters (How it looks like when it happens live every time) which look like 1 big spike and it looks like that every time it happens.

UPDATE:So using Windows performance tool it seems to be either a driver issue or game issue.

 

the latency mon bar graphs are false leads, a proper dpc trace is encouraged (on a totally idle system) but the stats tab will tell you how many times the system registered dpc's above certain levels.

All your picture demonstrates is that the device encountered a sequence of blocking interrupts (typical of a performance state transition of the clock or interface), which given what you were doing when it happened, makes it a non issue.

DPC tracing during interactive system activities creates useless data that can't be used to identify any issue,

use nsight to create a performance graph of the application itself and work from there.

 

Is there a guide for this I have a similar stutter on all my games that's driving me crazy and I've tried everything from new hardware to fresh win install. The only nsight I see is the one for developers. There really needs to be a guide visible as I think nsight could help a lot of people figure out problems but its not easy to get any information on how to use it properly.

 

@kman
@BoxChevy

Concerning usage of LatencyMon Astyanax just repeats what developers says. LatencyMon was designed for professional audio processing purposes, hence it should run alone in the system to measure the path from the kernel drivers to user program.
If you want to measure DPCs and ISRs you can use LatencyMon with typical game load. You just need to disable that "kernel to program" measurement in settings.

But there is more detailed and accurate method - https://forums.guru3d.com/threads/simple-way-to-trace-dpcs-and-isrs.423884/

 

I have read that thread but I havent done it because theres no explanation on how to read the logs once done, I have a very specific spike while playing a couple of my games like cp2077 rdr2 insurgency and destiny 2. Its almost identical happens every minute or so. How can I use that tool to see whats happening during that spike.

Here is my reports I let one spike happen then stopped it shortly after the second.
https://drive.google.com/drive/folders/12UCk1vuYqgcgb_tIe_gzKGIzH7vqhdeX?usp=sharing

 

I tried disabling hpet "bcdedit /set useplatformclock no" and "bcdedit /set useplatformtick yes" just to try something (saw it on a video on how to stop stutters for apex.Was highly rated) and I started to go into RED in latencymon.Huge latency spikes.Mainly from the nvidia driver and wierdly ndis.sys (2.6ms from ndis.sys) just from watching twitch.

Used these commands to restore defaults
bcdedit /deletevalue useplatformclock
bcdedit /deletevalue useplatformtick

And restarted but wierdly it didn't fix the issue so I decided to try clean re-installing my nvidia driver and latencymon is fine again.

15 mins of twitch/browsing/discord/steam (I really wanted to push it) to see what would happen and thankfully all back as usual.

Note to self.Don't mess with hpet settings.

Update:also updated the picture at 30mins in with latencymon.Wierdly ndis.sys seems to be the highest dpc execution but still within the green zones.

 

Wierdly in apex I'm experiencing a similar thing.5/10 games I get it once/twice rarely.

Wierd thing is it's always a frametime spike of around 50ms.(51-53 give or take) So I'm assuming its the same thing every time that's causing it but I still haven't figured out what's causing it ingame because of the randomness when it happens.

Like legit I could have 6 ppl firing at me and explosion going of near me and not 1 hitch! but then I could get a random stutter simply running around or while dropping at the start.

 

It is easy.
Here is a distribution of DPCs across CPU cores (a chart)

Spoiler

Code:

CPU Usage Summing By Module For the Whole Trace

CPU Usage from 0 us to 150019996 us:

    CPU 0 Usage,      CPU 1 Usage,      CPU 2 Usage,      CPU 3 Usage,      CPU 4 Usage,      CPU 5 Usage,      CPU 6 Usage,      CPU 7 Usage,      CPU 8 Usage,      CPU 9 Usage,      CPU 10 Usage,      CPU 11 Usage,      CPU 12 Usage,      CPU 13 Usage,      CPU 14 Usage,      CPU 15 Usage,
    usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %, Module
       0   0.00,         0   0.00,         1   0.00,         3   0.00,         4   0.00,         4   0.00,         0   0.00,         1   0.00,         1   0.00,        28   0.00,         2   0.00,         1   0.00,        15   0.00,       436   0.00,         2   0.00,         6   0.00, ACPI.sys
       9   0.00,         0   0.00,         3   0.00,         0   0.00,         4   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         4   0.00,         0   0.00,         8   0.00,        19   0.00,      3078   0.00,         0   0.00,         0   0.00, CLASSPNP.SYS
    3577   0.00,         0   0.00,     12358   0.01,       546   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00, HDAudBus.sys
       0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,       427   0.00,         0   0.00,         0   0.00, HTTP.sys
       2   0.00,         0   0.00,         2   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00, Ndu.sys
       0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,        53   0.00,         0   0.00,         0   0.00, Ntfs.sys
       0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,        10   0.00,         0   0.00,         0   0.00, WdFilter.sys
   238335   0.16,   1438488   0.96,    608254   0.41,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00, Wdf01000.sys
       0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,        13   0.00,         0   0.00,         0   0.00,        11   0.00,     17323   0.01,         0   0.00,         0   0.00, afd.sys
  2339635   1.56,         0   0.00,         0   0.00,         0   0.00,         1   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         1   0.00,        37   0.00,         8   0.00,         1   0.00,         0   0.00, dxgkrnl.sys
       0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,        13   0.00,      1552   0.00,         0   0.00,         0   0.00, dxgmms2.sys
       0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         3   0.00,         0   0.00,         0   0.00, gameflt.sys
       0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,      3485   0.00,         0   0.00,         0   0.00, kbdhid.sys
   20706   0.01,         0   0.00,     22909   0.02,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         5   0.00,         0   0.00,         0   0.00,        17   0.00,      2791   0.00,         0   0.00,         0   0.00, ndis.sys
       0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,       806   0.00,         0   0.00,         0   0.00, netbt.sys
   20262   0.01,      5534   0.00,     14935   0.01,      9550   0.01,     12628   0.01,     16022   0.01,     12653   0.01,      4819   0.00,     11781   0.01,     11810   0.01,     13458   0.01,     10410   0.01,     22921   0.02,     82761   0.06,     70818   0.05,     37076   0.02, ntoskrnl.exe
  3023411   2.02,       191   0.00,         0   0.00,         0   0.00,        87   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,        27   0.00,      2725   0.00,         0   0.00,         0   0.00, nvlddmkm.sys
       0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         1   0.00,         0   0.00,         0   0.00, rdyboost.sys
       7   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00, storahci.sys
    5936   0.00,       311   0.00,      5289   0.00,      3751   0.00,      4415   0.00,      1494   0.00,      4432   0.00,      1014   0.00,      4372   0.00,       647   0.00,      4498   0.00,       411   0.00,     11855   0.01,      1167   0.00,      3441   0.00,      1753   0.00, stornvme.sys
   25417   0.02,      1285   0.00,     21983   0.01,     18030   0.01,     19187   0.01,      7138   0.00,     18205   0.01,      4667   0.00,     18681   0.01,      2875   0.00,     19439   0.01,      1642   0.00,     46435   0.03,      5159   0.00,     15074   0.01,      8586   0.01, storport.sys
    2306   0.00,       727   0.00,       760   0.00,       597   0.00,       193   0.00,       215   0.00,       541   0.00,       226   0.00,       400   0.00,       525   0.00,       911   0.00,       472   0.00,       363   0.00,      1092   0.00,       539   0.00,       303   0.00, tcpip.sys

Right after that you can see a sum of all DPCs timespans distribution (a histogram)

Code:

Total = 945782
Elapsed Time, >        0 usecs AND <=        1 usecs, 197659, or  20.90%
Elapsed Time, >        1 usecs AND <=        2 usecs, 172293, or  18.22%
Elapsed Time, >        2 usecs AND <=        4 usecs, 117023, or  12.37%
Elapsed Time, >        4 usecs AND <=        8 usecs, 202994, or  21.46%
Elapsed Time, >        8 usecs AND <=       16 usecs, 153105, or  16.19%
Elapsed Time, >       16 usecs AND <=       32 usecs,  61943, or   6.55%
Elapsed Time, >       32 usecs AND <=       64 usecs,  21630, or   2.29%
Elapsed Time, >       64 usecs AND <=      128 usecs,   8716, or   0.92%
Elapsed Time, >      128 usecs AND <=      256 usecs,   7590, or   0.80%
Elapsed Time, >      256 usecs AND <=      512 usecs,   2645, or   0.28%
Elapsed Time, >      512 usecs AND <=     1024 usecs,    176, or   0.02%
Elapsed Time, >     1024 usecs AND <=     2048 usecs,      0, or   0.00%
Elapsed Time, >     2048 usecs AND <=     4096 usecs,      8, or   0.00%
Total,

where "usecs" is microseconds.

We see that majority of DPCs were executed for less then 1 microsecond (Elapsed Time, > 0 usecs AND <= 1 usecs, 197659, or 20.90%) - 197659, or 20.90%, and between 4 and 8 microseconds (Elapsed Time, > 4 usecs AND <= 8 usecs, 202994, or 21.46%) - 202994, or 21.46%.
Quite many DPCs were executed for more than 256 microseconds (Elapsed Time, > 256 usecs AND <= 512 usecs, 2645, or 0.28%) - 2645, or 0.28%.
Quite many DPCs were executed for more than 512 microseconds (Elapsed Time, > 512 usecs AND <= 1024 usecs, 176, or 0.02%) - 176, or 0.02%.
But the worst of all we see that 8 DPCs were executed for more than 2048 microseconds (i.e. more than 2 milliseconds) - Elapsed Time, > 2048 usecs AND <= 4096 usecs, 8, or 0.00%. That`s a spike(s) for sure.

Now after the sum of all DPCs we see same DPCs timespan distributions for individual drivers and there we see a culprit:

Code:

Total = 237924 for module nvlddmkm.sys
Elapsed Time, >        0 usecs AND <=        1 usecs,  83174, or  34.96%
Elapsed Time, >        1 usecs AND <=        2 usecs,  74587, or  31.35%
Elapsed Time, >        2 usecs AND <=        4 usecs,  18142, or   7.63%
Elapsed Time, >        4 usecs AND <=        8 usecs,  11857, or   4.98%
Elapsed Time, >        8 usecs AND <=       16 usecs,   9373, or   3.94%
Elapsed Time, >       16 usecs AND <=       32 usecs,  17675, or   7.43%
Elapsed Time, >       32 usecs AND <=       64 usecs,  10701, or   4.50%
Elapsed Time, >       64 usecs AND <=      128 usecs,   5552, or   2.33%
Elapsed Time, >      128 usecs AND <=      256 usecs,   6184, or   2.60%
Elapsed Time, >      256 usecs AND <=      512 usecs,    652, or   0.27%
Elapsed Time, >      512 usecs AND <=     1024 usecs,     19, or   0.01%
Elapsed Time, >     1024 usecs AND <=     2048 usecs,      0, or   0.00%
Elapsed Time, >     2048 usecs AND <=     4096 usecs,      8, or   0.00%
Total,                                                237924

Total = 199227 for module dxgkrnl.sys
Elapsed Time, >        0 usecs AND <=        1 usecs,  14491, or   7.27%
Elapsed Time, >        1 usecs AND <=        2 usecs,   9026, or   4.53%
Elapsed Time, >        2 usecs AND <=        4 usecs,  60288, or  30.26%
Elapsed Time, >        4 usecs AND <=        8 usecs,  55596, or  27.91%
Elapsed Time, >        8 usecs AND <=       16 usecs,  28228, or  14.17%
Elapsed Time, >       16 usecs AND <=       32 usecs,  16282, or   8.17%
Elapsed Time, >       32 usecs AND <=       64 usecs,   8853, or   4.44%
Elapsed Time, >       64 usecs AND <=      128 usecs,   2992, or   1.50%
Elapsed Time, >      128 usecs AND <=      256 usecs,   1359, or   0.68%
Elapsed Time, >      256 usecs AND <=      512 usecs,   1959, or   0.98%
Elapsed Time, >      512 usecs AND <=     1024 usecs,    153, or   0.08%
Total,                                                199227

Nvidia GPU.

***

After the DPC part we see ISR part of the report. It has same structure.
First - distribution across CPU cores

Spoiler

Code:

CPU Usage from 0 us to 150019996 us:

    CPU 0 Usage,      CPU 1 Usage,      CPU 2 Usage,      CPU 3 Usage,      CPU 4 Usage,      CPU 5 Usage,      CPU 6 Usage,      CPU 7 Usage,      CPU 8 Usage,      CPU 9 Usage,      CPU 10 Usage,      CPU 11 Usage,      CPU 12 Usage,      CPU 13 Usage,      CPU 14 Usage,      CPU 15 Usage,
    usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %,      usec      %, Module
   20617   0.01,         0   0.00,     50915   0.03,      2223   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,      3261   0.00,       672   0.00,      1263   0.00,      1990   0.00, HDAudBus.sys
   12889   0.01,     90625   0.06,     32141   0.02,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,     61291   0.04,      7557   0.01,     23218   0.02,     36129   0.02, Wdf01000.sys
  5332393   3.55,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00, dxgkrnl.sys
    1288   0.00,         0   0.00,      1246   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00,         0   0.00, ndis.sys
    3418   0.00,       181   0.00,      2864   0.00,      2257   0.00,      2600   0.00,       894   0.00,      2651   0.00,       666   0.00,      2727   0.00,       464   0.00,      2931   0.00,       256   0.00,      6773   0.00,       641   0.00,      2244   0.00,      1085   0.00, storport.sys

Then - sum of all ISRs timespans distribution

Code:

Total = 802211
Elapsed Time, >        0 usecs AND <=        1 usecs, 533213, or  66.47%
Elapsed Time, >        1 usecs AND <=        2 usecs,  17965, or   2.24%
Elapsed Time, >        2 usecs AND <=        4 usecs,   3678, or   0.46%
Elapsed Time, >        4 usecs AND <=        8 usecs,  21795, or   2.72%
Elapsed Time, >        8 usecs AND <=       16 usecs,  57835, or   7.21%
Elapsed Time, >       16 usecs AND <=       32 usecs, 134815, or  16.81%
Elapsed Time, >       32 usecs AND <=       64 usecs,  26914, or   3.35%
Elapsed Time, >       64 usecs AND <=      128 usecs,   4802, or   0.60%
Elapsed Time, >      128 usecs AND <=      256 usecs,   1150, or   0.14%
Elapsed Time, >      256 usecs AND <=      512 usecs,     32, or   0.00%
Elapsed Time, >      512 usecs AND <=     1024 usecs,     12, or   0.00%

We see that 32 ISRs were executed for more than 256 microseconds, and 12 ISRs were executed for more than 512 microseconds.

Now after the sum of all ISRs we see same ISRs timespan distributions for individual drivers and there we see several culprits:

Code:

Total = 22378 for module HDAudBus.sys
Elapsed Time, >        0 usecs AND <=        1 usecs,  10605, or  47.39%
Elapsed Time, >        1 usecs AND <=        2 usecs,    441, or   1.97%
Elapsed Time, >        2 usecs AND <=        4 usecs,    114, or   0.51%
Elapsed Time, >        4 usecs AND <=        8 usecs,   9630, or  43.03%
Elapsed Time, >        8 usecs AND <=       16 usecs,    958, or   4.28%
Elapsed Time, >       16 usecs AND <=       32 usecs,    556, or   2.48%
Elapsed Time, >       32 usecs AND <=       64 usecs,     71, or   0.32%
Elapsed Time, >       64 usecs AND <=      128 usecs,      1, or   0.00%
Elapsed Time, >      128 usecs AND <=      256 usecs,      1, or   0.00%
Elapsed Time, >      256 usecs AND <=      512 usecs,      1, or   0.00%
Total,                                                 22378

Total = 484884 for module Wdf01000.sys
Elapsed Time, >        0 usecs AND <=        1 usecs, 466468, or  96.20%
Elapsed Time, >        1 usecs AND <=        2 usecs,  13763, or   2.84%
Elapsed Time, >        2 usecs AND <=        4 usecs,   2811, or   0.58%
Elapsed Time, >        4 usecs AND <=        8 usecs,   1214, or   0.25%
Elapsed Time, >        8 usecs AND <=       16 usecs,    414, or   0.09%
Elapsed Time, >       16 usecs AND <=       32 usecs,     85, or   0.02%
Elapsed Time, >       32 usecs AND <=       64 usecs,     70, or   0.01%
Elapsed Time, >       64 usecs AND <=      128 usecs,     39, or   0.01%
Elapsed Time, >      128 usecs AND <=      256 usecs,     18, or   0.00%
Elapsed Time, >      256 usecs AND <=      512 usecs,      2, or   0.00%
Total,                                                484884

Total = 233999 for module dxgkrnl.sys
Elapsed Time, >        0 usecs AND <=        1 usecs,      0, or   0.00%
Elapsed Time, >        1 usecs AND <=        2 usecs,      0, or   0.00%
Elapsed Time, >        2 usecs AND <=        4 usecs,      0, or   0.00%
Elapsed Time, >        4 usecs AND <=        8 usecs,  10717, or   4.58%
Elapsed Time, >        8 usecs AND <=       16 usecs,  56421, or  24.11%
Elapsed Time, >       16 usecs AND <=       32 usecs, 134165, or  57.34%
Elapsed Time, >       32 usecs AND <=       64 usecs,  26768, or  11.44%
Elapsed Time, >       64 usecs AND <=      128 usecs,   4756, or   2.03%
Elapsed Time, >      128 usecs AND <=      256 usecs,   1131, or   0.48%
Elapsed Time, >      256 usecs AND <=      512 usecs,     29, or   0.01%
Elapsed Time, >      512 usecs AND <=     1024 usecs,     12, or   0.01%
Total,                                                233999

Again Nvidia one (dxgkrnl.sys) is worse.

Have you tried to switch video and sound cards into MSI mode
https://forums.guru3d.com/threads/w...ge-signaled-based-interrupts-msi-tool.378044/
?

And another suggestion would be to switch SMT (hyperthreading in terms of Intel) Off in BIOS if CPU supports it.

PS Forgot to point out that to proper read those reports you have to use editors other than Notepad. For example Notepad++.

 

Try to optimise network stack
https://www.speedguide.net/articles/windows-8-2012-server-tcpip-tweaks-5077
https://www.speedguide.net/articles/network-adapter-optimization-3449
https://github.com/djdallmann/GamingPCSetup/tree/master/NETWORK

 

So sounds like what your telling me is the drivers are the issue, I have tried multiple different drivers and using ddu in between. I do use msi mode every driver change. I am on a 5800x ryzen and will try without smt but that kinda defeats the purpose of having a 16 thread cpu. Thanks for the help with this.

 

It's a bit overwhelming.Is there anything specific I should do?Or I could just leave it alone because like I said it was still in the green zone with no warnings.


Best I could do is disable the power saving feature on my network adapter in device manager as it was the most simple one to do.

 

Unfortunately SMT is not fully independent multiple threads. People were reporting minor issues (like stuttering) solved by disabling SMT (on both platforms).

 

Simple things:

Spoiler

Go to "Settings -> Network & Internet" and click "Change adapter options", then (in new window) select your adapter and invoke properties dialog.
There you can uncheck all items except for TCP/IPv4 and TCP/IPv6


Do not close that dialog, select TCP/IPv4 item and click "Properties" button.
In this new dialog click button "Advanced..."


In this new dialog select "WINS" tab, disable NetBIOS over TCP/IP and click "OK" button.


Continue to close dialogs by clicking the "OK" button (to save changes).

 

no, hes saying theres an issue on the system - you can't come to a conclusion about any driver with just latency mon.

DPC spikes logged as a particular device driver are often not caused by that driver but devices preceding it since DPC is one big ass Queue, dpc's in the thousands also tend to be hardware / controller problems where commands are resubmitted due to ECC too. I'd be looking at the nvidia driver only if the dpc spikes were logged in the dx kernel.

a 680 i had would jump to 800us occasionally due where as a 1060 in the same system same driver never spikes at all. 680 had a issue with its pcie 16 interface since it was bought (only negotiated to 8x)

given the 5800 has the same pcie controller as the 3k series, theres chances that its not a very good chiplet where silicon integrity is concerned.

 

Thanks for the explanation, Im leaning towards something with the autosave and spikes in rdr2 and cyberpunk. I downloaded a couple of other games like doom eternal and apex and there pretty smooth. Destiny has had hitches here and there since there move to steam. Death Stranding from what I am reading has occasional hitches as well. It sucks being super sensitive to frametimes.

 

@BoxChevy

Astyanax can be right. But there is still possibility for badly coded drivers. If you tried several versions of NV drivers with the same results then you can rule them out, but there are other devices and their drivers in the system.
Interrupt is handled in two stages - ISR and DPC (ISR should dispatch DPC). As I take it both ISR and DPC can be interrupted by another ISRs (but not by DPCs). So badly implemented ISR in any device driver can introduce the issue: if such device raises big stream of interrupts then its ISRs will interrupt other devices (and OS + normal apps code) a lot.
You can investigate this by disabling PCI-E devices one by one (soundcard, network card) and try to game and record the report. (Obviously you can`t disable a storage controller in use.)

PS Also if you have devices which you do not use then you can disable them either in BIOS or in Device Manager.

 

I tried these settings and restarted pc and now While on apex and got a micro stutter and got this

Spoiler

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns.
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:06:25 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-CRT7896
OS version: Windows 10, 10.0, version 1909, build: 18363 (x64)
Hardware: System Product Name, System manufacturer
CPU: GenuineIntel Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
Logical processors: 16
Processor groups: 1
RAM: 16305 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 360 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): 1675.70
Average measured interrupt to process latency (µs): 2.911749

Highest measured interrupt to DPC latency (µs): 1672.90
Average measured interrupt to DPC latency (µs): 1.195858


_________________________________________________________________________________________________________
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): 57.114444
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0.004931
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Total time spent in ISRs (%) 0.005551

ISR count (execution time <250 µs): 77143
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): 1476.724444
Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

Total time spent in DPCs (%) 0.111337

DPC count (execution time <250 µs): 1632005
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 17
DPC count (execution time 1000-2000 µs): 1
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: svchost.exe

Total number of hard pagefaults 1203
Hard pagefault count of hardest hit process: 539
Number of processes hit: 22


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 21.644169
CPU 0 ISR highest execution time (µs): 57.114444
CPU 0 ISR total execution time (s): 0.242525
CPU 0 ISR count: 37549
CPU 0 DPC highest execution time (µs): 1476.724444
CPU 0 DPC total execution time (s): 6.380668
CPU 0 DPC count: 1548468
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 3.880099
CPU 1 ISR highest execution time (µs): 27.911111
CPU 1 ISR total execution time (s): 0.089136
CPU 1 ISR count: 23015
CPU 1 DPC highest execution time (µs): 199.293889
CPU 1 DPC total execution time (s): 0.317824
CPU 1 DPC count: 24554
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 2.088005
CPU 2 ISR highest execution time (µs): 19.6250
CPU 2 ISR total execution time (s): 0.001037
CPU 2 ISR count: 93
CPU 2 DPC highest execution time (µs): 171.309444
CPU 2 DPC total execution time (s): 0.019281
CPU 2 DPC count: 10450
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2.044334
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): 70.402222
CPU 3 DPC total execution time (s): 0.019416
CPU 3 DPC count: 4825
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 2.343864
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): 41.341111
CPU 4 DPC total execution time (s): 0.012099
CPU 4 DPC count: 6057
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 2.251208
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): 20.742778
CPU 5 DPC total execution time (s): 0.001593
CPU 5 DPC count: 696
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 2.322169
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): 52.067222
CPU 6 DPC total execution time (s): 0.011623
CPU 6 DPC count: 5264
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 1.884020
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): 32.748333
CPU 7 DPC total execution time (s): 0.002970
CPU 7 DPC count: 1296
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 2.381981
CPU 8 ISR highest execution time (µs): 0.0
CPU 8 ISR total execution time (s): 0.0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 29.371667
CPU 8 DPC total execution time (s): 0.009114
CPU 8 DPC count: 3996
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 1.782236
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): 26.069444
CPU 9 DPC total execution time (s): 0.001858
CPU 9 DPC count: 836
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 2.593206
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 time (µs): 27.631111
CPU 10 DPC total execution time (s): 0.009278
CPU 10 DPC count: 3650
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 1.810466
CPU 11 ISR highest execution time (µs): 0.0
CPU 11 ISR total execution time (s): 0.0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 63.034444
CPU 11 DPC total execution time (s): 0.002864
CPU 11 DPC count: 1141
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 2.653665
CPU 12 ISR highest execution time (µs): 4.063333
CPU 12 ISR total execution time (s): 0.003012
CPU 12 ISR count: 3981
CPU 12 DPC highest execution time (µs): 60.038889
CPU 12 DPC total execution time (s): 0.035692
CPU 12 DPC count: 11353
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 2.244222
CPU 13 ISR highest execution time (µs): 4.4350
CPU 13 ISR total execution time (s): 0.006393
CPU 13 ISR count: 12505
CPU 13 DPC highest execution time (µs): 35.154444
CPU 13 DPC total execution time (s): 0.013498
CPU 13 DPC count: 4118
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 2.173208
CPU 14 ISR highest execution time (µs): 0.0
CPU 14 ISR total execution time (s): 0.0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 34.542778
CPU 14 DPC total execution time (s): 0.010334
CPU 14 DPC count: 2810
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 2.301632
CPU 15 ISR highest execution time (µs): 0.0
CPU 15 ISR total execution time (s): 0.0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 41.048333
CPU 15 DPC total execution time (s): 0.013023
CPU 15 DPC count: 2509
_________________________________________________________________________________________________________

 

"Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation" - where in your previous post it was ndis.sys

Upd: You better hide such long texts between tags

Code:

[spoiler]Long text[/spoiler] 

Upd: Obviously to test ndis.sys in heavy load you should either browse some intense site (YT videos in high definition?) or play network game.

 

it's dxgkrnel thats spiking.

Yea I have no idea whats going on.Should I just clean re-install w10?

 

700 microseconds (from OP) is high but not that high. It is less than 1 millisecond.
If you tweaked your OS like a maniac, then you can clear re-install Windows.