There won't be one, the DPC latency issue has many causes. I remember having it back like 10 years ago, the cause was some Microsoft default driver for my hard drive controller. The fix back then was to install the Intel RST driver. The other guy in here fixed it by enabling CSM... so there will be no "definite" fix. That being said I still think that 22H2 is straight up broken.
Discussion: NVIDIA Display Driver (nvlddmkm.sys) DPC Latency
- Status
There won't be one, the DPC latency issue has many causes. I remember having it back like 10 years ago, the cause was some Microsoft default driver for my hard drive controller. The fix back then was to install the Intel RST driver. The other guy in here fixed it by enabling CSM... so there will be no "definite" fix. That being said I still think that 22H2 is straight up broken.
im getting the spiking on w7 gt710 so its not just a w10 issue. lot of people saying 22H2 is broken. we need to at least have a look at wildcards even just to rule them out cos between them nvidia and ms dont seem to have a bloody clue what the dink is going on, i dare them to find both buttocks with their eyes closed.
Hellbovine
Well-Known Member
I think that's probably where some of the mixup is coming from. I try to speak to the lurkers more than I do to the members on this forum in all my posts/replies because lurkers outnumber active members by the thousands, and I'm rehashing things for their sake so they don't jump to bad conclusions and then apply a ton of tweaks someone suggested that are not going to benefit them, and could instead make performance worse.
What I meant about my testing comments today for example, is I don't think CSM was that member's fix. I was going to write up a response last night, but decided against it because there was no way I could figure out how to write it without sounding like I was backing him into a corner. On that Gigabyte motherboard it's already enabled by default per the PDF manual. Also, you cannot interchangeably switch between UEFI and CSM because UEFI uses GPT while CSM uses MBR and if you switch the setting then Windows stops booting and requires a clean install again...The only way changing CSM could have been a fix in this specific scenario is due to some other sub-setting (Storage Boot Option Control for example), or the fix was misattributed (which happens all the time, it's an understandable mistake), or there is a bug in the bios.
Unless there's more relevant information we're missing, such as he did reinstall Windows, in which case we need that information to properly assess what happened. Maybe I'm just wrong entirely, but I didn't want to get into the CSM stuff because that's just not going to be the universal fix regardless, since there are tons of us on CSM and tons of us on UEFI and we all have the same issue. He also didn't provide any LatencyMon screenshots either, so I decided to let it go and focus on other things instead. But yes, 22H2 is completely broken, that is for sure.
Necrosaro
Active Member
I would still use xp but if I remember correctly the system has issues using all my cores. It's a waste for me if I can only use a few.
Either way 11 is most likely the end of my AMD system since it's not getting any new drivers since 10 and even then I was lucky to get the 10 drivers working well enough and without issues with 11.
I think we all should just leave this thread till the new year and enjoy our holiday's. DPC will be here today and not going to change tomorrow.
Either way 11 is most likely the end of my AMD system since it's not getting any new drivers since 10 and even then I was lucky to get the 10 drivers working well enough and without issues with 11.
I think we all should just leave this thread till the new year and enjoy our holiday's. DPC will be here today and not going to change tomorrow.
I'm following this also, as I've been dealing with this for almost a year. I'm at my wits end. 2 months spent on remote sessions with Dell, swapped out the motherboard, re-installed Windows twice, made all the usual tweaks, sent back to Dell, re-installed a new graphics card, and fixed the heat sink. I did all these similar remote sessions again, but with Microsoft, Sweetwater tech supp, Focusrite tech supp and UA tech support.
Here are my specs and Lat mon attachment :
Dell XPS 8950 running Windows 11 Home. "now" 22H2 had the issue before though.
Processor 12th Gen Intel(R) Core(TM) i9-12900K, 3187 Mhz, 16 Core(s), 24 Logical Processor(s)
64GB RAM,
The nvlddmkm.sys driver doesn't always show the spike, like here, but it's part of the problem I see on the other screens i.e the driver screen
Seems I'll have to post the other file seperately.. It won't attach
Attachments
Hi guys. I found this post because my PC was randomly freezing from time to time and I think it´s because my RAM was set to 6400 and that was a little bit too high (DDR5 6400 with i9 12900K + Asus ROG STRIX Z690-F.
The thing is that someone suggested me to run that LatencyMon app and I was getting these errors (image attached). I googled and found this post. I used what the other user said about Interrupt Affinity Policy tool with the Advanced --> IrqPolicyAllCloseProcessors and IrqPolicyOneCloseProcessors part but I still get the spikes (2nd image).
I used Asus Armoury Crate as well for fixing / updating some drivers just in case, but still the same.
What can I do to fix this?.
The thing is that someone suggested me to run that LatencyMon app and I was getting these errors (image attached). I googled and found this post. I used what the other user said about Interrupt Affinity Policy tool with the Advanced --> IrqPolicyAllCloseProcessors and IrqPolicyOneCloseProcessors part but I still get the spikes (2nd image).
I used Asus Armoury Crate as well for fixing / updating some drivers just in case, but still the same.
What can I do to fix this?.
Attachments
Go back through the thread, some things seem to work for some people but not others but be careful, some tweaks might break your machine.
Some tweaks might break my machine?. LoL, great.
Anyway apart from the random freezings that I have right now due to RAM that I still need to fix, how does these high latency values that LatencyMon reports affect my PC performance when gaming for instance?
Last edited:
ZEFIR001
New Member
LatencyMon does not affect anything,the software does not apply any changes to windows. All it does is showing you what driver/process issues a freeze or high latency.
Originally it was designed for testing audio monitoring delays.
Ok thanks.
ZEFIR001
New Member
As far as i remember you can rely on that markings to fix freezing issues.
Spike with rspLLL64.sys - can be ignored.
Spike with tcpip.sys - network adapter driver. same as Ndis.sys.
Spike with storport.sys - hard disk controller\ssd\nvme - or their driver. Update. It also happens that AMD Sata or NVME controller in the device manager gives freeze,stutters in this case we put the default from Windows there or disable it (Windows may fall)
Spike with ntoskrnl.exe - power problem, power plan does not fit - try different ones, bitsum/muren/everythingtech and so on.
Spike with kbdhid.sys - could be faulty keyboard or its driver (if it need any)
Spike with Storeachy.sys - same as storport.
Spike with CLASSPNP.SYS - some driver in Windows is very bad and it bugs.
Spike with hdaudio.sys or volume.sys - the sound driver,update it - if it didn't help - buy an external sound card, preferably one that work without drivers.
Spike with nvlddmkm.sys - we all know what is this.
Test the tweaks suggested here with a fresh installation of 21H2 instead of 22H2, that's all I can say. 22H2 is broken.
What Windows version are you using? See above, don't use 22H2. The IrqPolicy is what worked for me, doesn't mean it works for you too. Try the other things mentioned here: power plans, speed step, c-states etc.
Hellbovine
Well-Known Member
What the other guys said is good information. I think something I should have made more clear in this thread in order to help people better, is that there are 2 very distinct sets of DPC issues, and some people are affected by only one of them, while others are affected by both. One issue is the "Nvidia Driver DPC Bug" and the other is "General DPC Problems".
NVIDIA DRIVER DPC BUG
GENERAL DPC PROBLEMS
DPC QUICK FIX GUIDE
Happy holidays everyone! I hope this helps at least a few of you. After the new year I'll have more time to really tackle all of this stuff hardcore, and work on my optimized image more too, hopefully finding some more tweaks along the way that can help people.
NVIDIA DRIVER DPC BUG
For people with LatencyMon readings of moderate spikes (less than 1,000) coming from only the Nvidia driver are most likely only suffering from the "Nvidia Driver DPC Bug." This thread was created with the intent of finding a solution for this specific bug. The Nvidia bug is affecting probably almost every single Nvidia user, it just doesn't get noticed very often until someone finally goes down a path that causes them to install LatencyMon so they can visually see the problem that has been plaguing them in their games. Not everyone notices the problems these moderate spikes cause because some people are less sensitive than others to visual and audio disturbances.
GENERAL DPC PROBLEMS
The people that have really bad LatencyMon readings with spikes above 1,000 and also have other drivers spiking up in addition to Nvidia, have "General DPC Problems" as well as the "Nvidia Driver DPC Bug" and the issues are compounding each other which causes all sorts of red bars in LatenyMon. These people need to tackle things much differently to solve this problem, and I will write up a General DPC guide to help those people, hopefully sometime next week, where all the solutions for that can be put together in one post.
DPC QUICK FIX GUIDE
For people that don't want to wait around, and really want to try and tackle this stuff now, here's a quick guide on how to do it methodically, and efficiently. Keep in mind you will need to do some research and apply some general common sense and computer savvy as this isn't a full guide:
1) Backup all important files and then do a clean install of Windows. This is a required step no matter what your situation is. So many general computer problems are fixed by doing this, that it's a must. To answer the question of "which Windows or version do I use", well my opinion is to use W10 21H2. I don't recommend W11 since it's immature, and you definitely don't want version 22H2 for W10 or W11 because it's broken right now. You can use your Windows license key for both W10 and W11 interchangeably. The important step here is that you must either install Windows while offline that way it cannot force you to upgrade to 22H2 right away via Windows Update, or integrate the registry keys that pause Windows Update into an image that you use to install Windows with. You also need to do this because otherwise Windows will forcibly download and install an outdated Nvidia driver as soon as Windows is online. Before installing Windows go into your BIOS and disable all Virtualization (Hyper-V). See the following for those registry keys (link1) and more information.
2) Once you reach the Windows desktop after a clean install, don't install *any* drivers! Instead, run LatencyMon now and check for DPC issues. If you have problems at this point they need to be addressed and fixed before you attempt to deal with the Nvidia driver, since problems at this stage are General DPC Problems. See Zefir001's reply (link2) for information on resolving these kinds of issues. Some easy ways to resolve DPC issues at this point is to optimize your BIOS settings and change the power plan to high performance.
3) If you have no DPC issues on a clean install, continue forward by installing *one* driver at a time, reboot, then run LatencyMon for 5 minutes. If that driver has no DPC issues then move to the next driver. Do this until all required drivers are installed on your machine, except for the Nvidia driver. Use the Device Manager to check for yellow exclamation marks as those indicate missing drivers.
4) If you can get Windows cleanly installed, as well as all other drivers you need, without any DPC issues (or you fixed any issues that appeared so far) then you can install the latest Nvidia driver. You do not need DDU or NvCleanStall, simply use the official Nvidia installer and choose the option that does *not* install GeForce Experience. Choose "Custom" installation, and then only check the 3 boxes for the display driver, audio driver, and physx, and also click the box for "Perform a clean install". Reboot and run LatencyMon again, and the only DPC issue should be coming from the Nvidia driver. If you have other drivers that begin acting up at this point and you have spikes over 1,000 then you probably didn't fully resolve your general DPC issues and need to backtrack a bit to do that. If you can't figure out how to solve problems, try a Windows image that has been optimized to reduce background activity (link3) of the operating system.
5) If you tried all of this and still have general DPC issues not related to Nvidia, then start on page 1 of this thread and read through everything, taking notes along the way of stuff you can experiment with. I would recommend reading through all the pages first while taking notes before actually trying stuff, because replies that come later will be relevant and they discuss what tweaks are good or bad. If you still can't get it figured out, then come post here on the thread and we'll try to help.
1) Backup all important files and then do a clean install of Windows. This is a required step no matter what your situation is. So many general computer problems are fixed by doing this, that it's a must. To answer the question of "which Windows or version do I use", well my opinion is to use W10 21H2. I don't recommend W11 since it's immature, and you definitely don't want version 22H2 for W10 or W11 because it's broken right now. You can use your Windows license key for both W10 and W11 interchangeably. The important step here is that you must either install Windows while offline that way it cannot force you to upgrade to 22H2 right away via Windows Update, or integrate the registry keys that pause Windows Update into an image that you use to install Windows with. You also need to do this because otherwise Windows will forcibly download and install an outdated Nvidia driver as soon as Windows is online. Before installing Windows go into your BIOS and disable all Virtualization (Hyper-V). See the following for those registry keys (link1) and more information.
2) Once you reach the Windows desktop after a clean install, don't install *any* drivers! Instead, run LatencyMon now and check for DPC issues. If you have problems at this point they need to be addressed and fixed before you attempt to deal with the Nvidia driver, since problems at this stage are General DPC Problems. See Zefir001's reply (link2) for information on resolving these kinds of issues. Some easy ways to resolve DPC issues at this point is to optimize your BIOS settings and change the power plan to high performance.
3) If you have no DPC issues on a clean install, continue forward by installing *one* driver at a time, reboot, then run LatencyMon for 5 minutes. If that driver has no DPC issues then move to the next driver. Do this until all required drivers are installed on your machine, except for the Nvidia driver. Use the Device Manager to check for yellow exclamation marks as those indicate missing drivers.
4) If you can get Windows cleanly installed, as well as all other drivers you need, without any DPC issues (or you fixed any issues that appeared so far) then you can install the latest Nvidia driver. You do not need DDU or NvCleanStall, simply use the official Nvidia installer and choose the option that does *not* install GeForce Experience. Choose "Custom" installation, and then only check the 3 boxes for the display driver, audio driver, and physx, and also click the box for "Perform a clean install". Reboot and run LatencyMon again, and the only DPC issue should be coming from the Nvidia driver. If you have other drivers that begin acting up at this point and you have spikes over 1,000 then you probably didn't fully resolve your general DPC issues and need to backtrack a bit to do that. If you can't figure out how to solve problems, try a Windows image that has been optimized to reduce background activity (link3) of the operating system.
5) If you tried all of this and still have general DPC issues not related to Nvidia, then start on page 1 of this thread and read through everything, taking notes along the way of stuff you can experiment with. I would recommend reading through all the pages first while taking notes before actually trying stuff, because replies that come later will be relevant and they discuss what tweaks are good or bad. If you still can't get it figured out, then come post here on the thread and we'll try to help.
Happy holidays everyone! I hope this helps at least a few of you. After the new year I'll have more time to really tackle all of this stuff hardcore, and work on my optimized image more too, hopefully finding some more tweaks along the way that can help people.
Last edited:
Hellbovine
Well-Known Member
Like Zefir001 said, the LatencyMon program itself won't hurt anything, so long as it's not running while you're trying to play a game (it'll just reduce performance in that case). But I don't think that's what you were asking about? I imagine you probably were asking why does DPC matter:
To put it in plain speech, DPC issues mean your drivers and hardware are taking too long to process data. When that happens it can cause a wide range of problems, resulting in stuttering, hitching, high network ping/jitter (lag), audio drop-outs, clicks and pops in audio, really bad 1% lows in frame rates, crashing to the desktop, and BSOD (blue screen of death). Good DPC is more important than high frame rates.
By far the most noticeable of these issues is what's called a "Watchdog Violation", and this is when the graphics driver gets tied up for so long (freezes) that it stops responding and has to restart itself, resulting in an error message that has the word "Watchdog" in it. A lot of the people experiencing that issue don't realize that DPC is to blame, and there's tons and tons of threads out there with this error. They should all be focusing on LatencyMon and DPC to fix it, but are instead misplacing the blame, and tech support everywhere is saying to do things like run sfc /scannow or replace hardware parts, which has nothing to do with this issue.
Last edited:
Like Zefir001 said, the LatencyMon program itself won't hurt anything, so long as it's not running while you're trying to play a game (it'll just reduce performance in that case). But I don't think that's what you were asking about? I imagine you probably were asking why does DPC matter:
I also found in another forum a thread talking about checking in msinfo32.exe the Conflicts part:
and check what´s shared with the GPU so maybe that´s the reason that causes those spikes.
The thing is I don't know if I need to somehow uninstall those shared devices such as the "Intel PEG10 - 460D" which appears in two places there with my RTX 3080Ti.
I will check later and see if I find how to uninstall that PEG10 - 460D.
I also found this thread talking about this and maybe I will have to check in BIOS if my PCI slot for the GPU is set to GEN3 or what:
Right now it looks like setting GEN3 for PCI in BIOS reduced my spikes:
I still need to check later those conflicts.
Ok thanks!.
I also found in another forum a thread talking about checking in msinfo32.exe the Conflicts part:
and check what´s shared with the GPU so maybe that´s the reason that causes those spikes.
The thing is I don't know if I need to somehow uninstall those shared devices such as the "Intel PEG10 - 460D" which appears in two places there with my RTX 3080Ti.
I will check later and see if I find how to uninstall that PEG10 - 460D.
I also found this thread talking about this and maybe I will have to check in BIOS if my PCI slot for the GPU is set to GEN3 or what:
New 12900K build, getting thousands of WHEA 17 errors a minute
I have a 12900k, Gigabyte Z690I DDR4, GSkill 2x16GB DDR4 3600 , EVGA 3080 XC3, Samsung 980 Pro, Windows 11. I get thousands of WHEA errors a minute for ven_8086&dev_ 460d&SUBSYS_86941043&REV_02 with my computer sitting idle. The rate increases if I begin to stress graphics. If I set the PCIe...
community.intel.com
Right now it looks like setting GEN3 for PCI in BIOS reduced my spikes:
I still need to check later those conflicts.
Last edited:
Hello (and merry xmas 
)
I found this thread through googling "nvlddmkm.sys". I built a completely new system last week and noticed that I had audio stutters when watching videos, then ugly stutters while trying some games, making them more or less unplayable. After some googling I tried latencyMon and I get what the reports/screenshots included in this post show. After skimming through this thread I also ran msinfo and found no components sharing the same IRQ, however there seem to be some sharing going on in the sharing/conflict page that I am unsure what it mean (giving it a second thought, it's probably the two PCIe lanes, one for GPU and one for m.2, so it's all good I guess).
I have reseated all my power cables and reseated ram and GPU. It's a fresh install of latest win 11. I'm a bit tired now because it feels like I wasted a ton on money on something that I might as well through out with the garbage, the PC is basically unusable.
So I'm here looking for a bit of support, I'm not computer savvy but not illiterate either. I'm going to skim through this thread and see what tips you guys have but I also have some questions.
I can't remember if it was here in this thread I read it the other day or somewhere else, but I read that you can use some utility to "redirect" what cores do what, and I thought that could be helpful because when looking at my latencyMon CPU usage, everything is on one thread. Do you think that will help and do you know of any guide on how to do that?
My only ssd right now is an m.2 sharing the PCIe with my GPU, do you think that could have anything to do with it?
I guess I'll try to reinstall windows 10 again, on a seperate drive, without internet and see what happens. If I download the win 10 installer, will I get the version recommended here with that or do I have to go the illegal route to get older versions of win? I can't seem to find a way to downgrade my version, after googling a lot.
And when looking at my latencyMon pics, I have a general DCP problem, right? And not a specific Nvidia one, as Hellbovine mentioned here above?
Ugh, that's it I guess, just needed someone to talk to I guess and seems like a lot of people here are in my boat
)I found this thread through googling "nvlddmkm.sys". I built a completely new system last week and noticed that I had audio stutters when watching videos, then ugly stutters while trying some games, making them more or less unplayable. After some googling I tried latencyMon and I get what the reports/screenshots included in this post show. After skimming through this thread I also ran msinfo and found no components sharing the same IRQ, however there seem to be some sharing going on in the sharing/conflict page that I am unsure what it mean (giving it a second thought, it's probably the two PCIe lanes, one for GPU and one for m.2, so it's all good I guess).
I have reseated all my power cables and reseated ram and GPU. It's a fresh install of latest win 11. I'm a bit tired now because it feels like I wasted a ton on money on something that I might as well through out with the garbage, the PC is basically unusable.
So I'm here looking for a bit of support, I'm not computer savvy but not illiterate either. I'm going to skim through this thread and see what tips you guys have but I also have some questions.
I can't remember if it was here in this thread I read it the other day or somewhere else, but I read that you can use some utility to "redirect" what cores do what, and I thought that could be helpful because when looking at my latencyMon CPU usage, everything is on one thread. Do you think that will help and do you know of any guide on how to do that?
My only ssd right now is an m.2 sharing the PCIe with my GPU, do you think that could have anything to do with it?
I guess I'll try to reinstall windows 10 again, on a seperate drive, without internet and see what happens. If I download the win 10 installer, will I get the version recommended here with that or do I have to go the illegal route to get older versions of win? I can't seem to find a way to downgrade my version, after googling a lot.
And when looking at my latencyMon pics, I have a general DCP problem, right? And not a specific Nvidia one, as Hellbovine mentioned here above?
Ugh, that's it I guess, just needed someone to talk to I guess and seems like a lot of people here are in my boat
CPU: Ryzen 7 7700X
cooler: be quiet! Shadow Rock 3
GPU: msi 4080 gaming x trio (connected with three seperate PCIe cables as recommended. )
motherboard: ASUS TUF GAMING X670E-PLUS
memory: Corsair Vengeance 32GB 5600 MHz (running at 4800 Mhz, no xmp setup yet)
psu: Corsair RM850X v3
ssd: Kingston NV2 M.2 1TB
chassi: fractal design define 7 with 3 noctua chassi fans
cooler: be quiet! Shadow Rock 3
GPU: msi 4080 gaming x trio (connected with three seperate PCIe cables as recommended. )
motherboard: ASUS TUF GAMING X670E-PLUS
memory: Corsair Vengeance 32GB 5600 MHz (running at 4800 Mhz, no xmp setup yet)
psu: Corsair RM850X v3
ssd: Kingston NV2 M.2 1TB
chassi: fractal design define 7 with 3 noctua chassi fans
_________________________________________________________________________________________________________
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. Also one or more ISR 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:08:09 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: ARNEWEISE
OS version: Windows 11, 10.0, version 2009, build: 22621 (x64)
Hardware:
BIOS: 0613
CPU: AuthenticAMD AMD Ryzen 7 7700X 8-Core Processor
Logical processors: 16
Processor groups: 1
Processor group size: 16
RAM: 31892 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 4501 MHz
Reported CPU speed (registry): 4491 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): 38455,60
Average measured interrupt to process latency (µs): 7,483337
Highest measured interrupt to DPC latency (µs): 1922,30
Average measured interrupt to DPC latency (µs): 2,225550
_________________________________________________________________________________________________________
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): 38532,885772
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,044366
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,046606
ISR count (execution time <250 µs): 227426
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 58
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): 38549,368737
Driver with highest DPC routine execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel
Library, Resplendence Software Projects Sp.
Highest reported total DPC routine time (%): 0,014446
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 527.56 , NVIDIA
Corporation
Total time spent in DPCs (%) 0,051960
DPC count (execution time <250 µs): 533545
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 680
DPC count (execution time 1000-2000 µs): 19
DPC count (execution time 2000-4000 µs): 5
DPC count (execution time >=4000 µs): 3
_________________________________________________________________________________________________________
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: msmpeng.exe
Total number of hard pagefaults 12065
Hard pagefault count of hardest hit process: 5953
Number of processes hit: 86
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 16,087610
CPU 0 ISR highest execution time (µs): 38532,885772
CPU 0 ISR total execution time (s): 3,638951
CPU 0 ISR count: 227097
CPU 0 DPC highest execution time (µs): 38549,368737
CPU 0 DPC total execution time (s): 3,476297
CPU 0 DPC count: 407742
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 1,960495
CPU 1 ISR highest execution time (µs): 249,829659
CPU 1 ISR total execution time (s): 0,008542
CPU 1 ISR count: 389
CPU 1 DPC highest execution time (µs): 1049,829659
CPU 1 DPC total execution time (s): 0,012814
CPU 1 DPC count: 1247
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 3,166196
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): 241,362725
CPU 2 DPC total execution time (s): 0,066051
CPU 2 DPC count: 21630
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 3,692982
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): 38459,939880
CPU 3 DPC total execution time (s): 0,226243
CPU 3 DPC count: 23777
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0,541637
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): 169,138277
CPU 4 DPC total execution time (s): 0,006508
CPU 4 DPC count: 1587
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0,540972
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): 44,098196
CPU 5 DPC total execution time (s): 0,001725
CPU 5 DPC count: 452
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 1,475746
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): 261,452906
CPU 6 DPC total execution time (s): 0,016964
CPU 6 DPC count: 5349
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 1,420335
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): 131,182365
CPU 7 DPC total execution time (s): 0,008039
CPU 7 DPC count: 2332
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 0,749657
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): 129,579158
CPU 8 DPC total execution time (s): 0,011016
CPU 8 DPC count: 2978
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 0,723881
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): 108,496994
CPU 9 DPC total execution time (s): 0,005279
CPU 9 DPC count: 1362
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 1,037502
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): 126,092184
CPU 10 DPC total execution time (s): 0,013275
CPU 10 DPC count: 4187
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 0,973865
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): 107,484970
CPU 11 DPC total execution time (s): 0,006829
CPU 11 DPC count: 1581
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 1,937059
CPU 12 ISR highest execution time (µs): 0,0
CPU 12 ISR total execution time (s): 0,0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 89,689379
CPU 12 DPC total execution time (s): 0,033121
CPU 12 DPC count: 10144
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 1,833301
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 131,653307
CPU 13 DPC total execution time (s): 0,018984
CPU 13 DPC count: 4432
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 2,741114
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): 130,10020
CPU 14 DPC total execution time (s): 0,088514
CPU 14 DPC count: 27981
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 2,131134
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): 156,743487
CPU 15 DPC total execution time (s): 0,074893
CPU 15 DPC count: 17471
_________________________________________________________________________________________________________
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. Also one or more ISR 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:08:09 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: ARNEWEISE
OS version: Windows 11, 10.0, version 2009, build: 22621 (x64)
Hardware:
BIOS: 0613
CPU: AuthenticAMD AMD Ryzen 7 7700X 8-Core Processor
Logical processors: 16
Processor groups: 1
Processor group size: 16
RAM: 31892 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 4501 MHz
Reported CPU speed (registry): 4491 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): 38455,60
Average measured interrupt to process latency (µs): 7,483337
Highest measured interrupt to DPC latency (µs): 1922,30
Average measured interrupt to DPC latency (µs): 2,225550
_________________________________________________________________________________________________________
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): 38532,885772
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,044366
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,046606
ISR count (execution time <250 µs): 227426
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 58
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): 38549,368737
Driver with highest DPC routine execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel
Library, Resplendence Software Projects Sp.
Highest reported total DPC routine time (%): 0,014446
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 527.56 , NVIDIA
Corporation
Total time spent in DPCs (%) 0,051960
DPC count (execution time <250 µs): 533545
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 680
DPC count (execution time 1000-2000 µs): 19
DPC count (execution time 2000-4000 µs): 5
DPC count (execution time >=4000 µs): 3
_________________________________________________________________________________________________________
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: msmpeng.exe
Total number of hard pagefaults 12065
Hard pagefault count of hardest hit process: 5953
Number of processes hit: 86
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 16,087610
CPU 0 ISR highest execution time (µs): 38532,885772
CPU 0 ISR total execution time (s): 3,638951
CPU 0 ISR count: 227097
CPU 0 DPC highest execution time (µs): 38549,368737
CPU 0 DPC total execution time (s): 3,476297
CPU 0 DPC count: 407742
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 1,960495
CPU 1 ISR highest execution time (µs): 249,829659
CPU 1 ISR total execution time (s): 0,008542
CPU 1 ISR count: 389
CPU 1 DPC highest execution time (µs): 1049,829659
CPU 1 DPC total execution time (s): 0,012814
CPU 1 DPC count: 1247
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 3,166196
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): 241,362725
CPU 2 DPC total execution time (s): 0,066051
CPU 2 DPC count: 21630
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 3,692982
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): 38459,939880
CPU 3 DPC total execution time (s): 0,226243
CPU 3 DPC count: 23777
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0,541637
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): 169,138277
CPU 4 DPC total execution time (s): 0,006508
CPU 4 DPC count: 1587
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0,540972
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): 44,098196
CPU 5 DPC total execution time (s): 0,001725
CPU 5 DPC count: 452
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 1,475746
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): 261,452906
CPU 6 DPC total execution time (s): 0,016964
CPU 6 DPC count: 5349
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 1,420335
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): 131,182365
CPU 7 DPC total execution time (s): 0,008039
CPU 7 DPC count: 2332
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 0,749657
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): 129,579158
CPU 8 DPC total execution time (s): 0,011016
CPU 8 DPC count: 2978
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 0,723881
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): 108,496994
CPU 9 DPC total execution time (s): 0,005279
CPU 9 DPC count: 1362
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 1,037502
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): 126,092184
CPU 10 DPC total execution time (s): 0,013275
CPU 10 DPC count: 4187
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 0,973865
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): 107,484970
CPU 11 DPC total execution time (s): 0,006829
CPU 11 DPC count: 1581
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 1,937059
CPU 12 ISR highest execution time (µs): 0,0
CPU 12 ISR total execution time (s): 0,0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 89,689379
CPU 12 DPC total execution time (s): 0,033121
CPU 12 DPC count: 10144
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 1,833301
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 131,653307
CPU 13 DPC total execution time (s): 0,018984
CPU 13 DPC count: 4432
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 2,741114
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): 130,10020
CPU 14 DPC total execution time (s): 0,088514
CPU 14 DPC count: 27981
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 2,131134
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): 156,743487
CPU 15 DPC total execution time (s): 0,074893
CPU 15 DPC count: 17471
_________________________________________________________________________________________________________
Attachments
Last edited:
I went ahead and installed that Ghost Spectre customized Windows for some latency testing, using version 21H2 (sams as my main Windows atm).
Funnily enough I also get DPC latency issues there from the nvidia driver:
Compare this to my main 21H2 installation without the issues (both ran for around 1 minute):
I've installed all the drivers I have installed on my main installation on the new, broken installation. No change. Went ahead and did the IrcPolicy thing. No change.
What immediately strikes my eyes:
a) way lower DPC count on nvlddmkm.sys and dxkrnl.sys etc.
b) On the CPU tab the interrupts are processed by my physical performance cores (13900KF, 8 physical performance cores, 16 efficiency cores + hyperthreading) on the working installation. On the broken installation the interrupts are processed by all cores. The only explanation I have is that there is a problem which causes a lot of additional DPCs and additional cores are required for processing.
My current theory is, that something is wrong with the M.2 SSD causing the DPC latency issues. Working main system (21H2) is now on my 980 PRO, broken 22H2 installation was on the 970 EVO, current broken 21H2 Ghost Spectre installation is on the 960 PRO.
When I'm in the mood I gonna remove all the M.2 SSDs (will be fun disassembling my PC *again*) and do a fresh installation of 21H2 on a regular SSD connected to the SATA-Controller.
Funnily enough I also get DPC latency issues there from the nvidia driver:
Compare this to my main 21H2 installation without the issues (both ran for around 1 minute):
I've installed all the drivers I have installed on my main installation on the new, broken installation. No change. Went ahead and did the IrcPolicy thing. No change.
What immediately strikes my eyes:
a) way lower DPC count on nvlddmkm.sys and dxkrnl.sys etc.
b) On the CPU tab the interrupts are processed by my physical performance cores (13900KF, 8 physical performance cores, 16 efficiency cores + hyperthreading) on the working installation. On the broken installation the interrupts are processed by all cores. The only explanation I have is that there is a problem which causes a lot of additional DPCs and additional cores are required for processing.
My current theory is, that something is wrong with the M.2 SSD causing the DPC latency issues. Working main system (21H2) is now on my 980 PRO, broken 22H2 installation was on the 970 EVO, current broken 21H2 Ghost Spectre installation is on the 960 PRO.
When I'm in the mood I gonna remove all the M.2 SSDs (will be fun disassembling my PC *again*) and do a fresh installation of 21H2 on a regular SSD connected to the SATA-Controller.
I just had again that electric sound interference and PC totally froze again. After 3-4 tries restarting it, entering BIOS... I could boot Windows again.
So what I thought was an issue caused by RAM maybe it´s because this damned i9 12900K messing around with Asus mobo and my GPU?.
This is a nightmare. Never ever had these problems with any of my previous PCs.
1. New Test: Removed GPU and RAM in slots 1&3 (were in 2&4 before). Moved also M.2 from Slot 1 (above 1st PCI for GPU) to 2nd M.2 slot (Z690-F Asus Strix). Had again the freezing while listening Spotify. Screen ended this way:
https://i.ibb.co/5FjJ8Q6/Sin-t-tulo.png
2. Now I will test with just 1 RAM in slot "1", no GPU and M.2 same place as before (2nd M.2 slot). I will turn on Spotify and see what happens. With LatencyMon in background as well.
These are the conflicts I have without the GPU and just 1 RAM:
VS the ones I had before:
10 mins running LatencyMon with Spotify, using Chrome and normal things... and no freezings:
Mmmmm I will test again with 2 modules of RAM (1&3), but If I get the freezing again as before... does it mean that maybe RAM´s defective?. I still didn´t put again the GPU, as I want to test the freezings first without it.
So it´s not a GPU matter (DPC spikes are of course when I connect it but that again it´s related with Z690 I guess... damned Asus...).
So what I thought was an issue caused by RAM maybe it´s because this damned i9 12900K messing around with Asus mobo and my GPU?.
This is a nightmare. Never ever had these problems with any of my previous PCs.
1. New Test: Removed GPU and RAM in slots 1&3 (were in 2&4 before). Moved also M.2 from Slot 1 (above 1st PCI for GPU) to 2nd M.2 slot (Z690-F Asus Strix). Had again the freezing while listening Spotify. Screen ended this way:
https://i.ibb.co/5FjJ8Q6/Sin-t-tulo.png
2. Now I will test with just 1 RAM in slot "1", no GPU and M.2 same place as before (2nd M.2 slot). I will turn on Spotify and see what happens. With LatencyMon in background as well.
These are the conflicts I have without the GPU and just 1 RAM:
VS the ones I had before:
10 mins running LatencyMon with Spotify, using Chrome and normal things... and no freezings:
Mmmmm I will test again with 2 modules of RAM (1&3), but If I get the freezing again as before... does it mean that maybe RAM´s defective?. I still didn´t put again the GPU, as I want to test the freezings first without it.
So it´s not a GPU matter (DPC spikes are of course when I connect it but that again it´s related with Z690 I guess... damned Asus...).
Last edited:
- Status