In general, such a story After buying a new computer, everything was fine for a whole year, I did not complain about anything. I decided at one point to overclock the video card, everything was stable for some time. But one day, after pressing the "Shut down" button, the computer did not turn off for a long time and then every time it fell out into a blue screen when trying to turn it off. Plus, the video card driver crashed periodically Googling the error led to the fact that it is either a video card driver or a network card driver. I decided to just reinstall Windows (to a newer version), but even after installation this blue screen remained As a result, I updated the network drivers, installed the old video card drivers, did not enable overclocking anymore, and the problem went away. But at the same time, a new one just appeared, these are statters in many games. somewhere they appear strongly, somewhere less, which is not even noticeable, somewhere not at all. So I lived for a year, but I was already completely tired of this and decided to try to fix this problem. And so, what was noticed and done: - When a strong stutter occurs, the msi afterburner graph shows that the load card drops by 10-20% - I updated the BIOS, everything was reset to default. Installed win 11 on another hard drive, all ssd and other drives were disabled. - The statters remain, I test all the time on the game V rising, because the easiest thing to check Thus, I hope I managed to prove to myself that the problem is not software, but hardware. I returned all the ssd and disks back, now I'm on Win 10, which is already a year old. I decided to see if something was related to Latency, and installed LatencyMoon And yes, there is something, but whether what I see is the norm or an anomaly, I can’t understand. High latency is manifested in the ClassPnP.sys driver and processes sometimes have high latency (the maximum I have seen is 10000) Given that the starters were on a new disk, ClassPnP.sys delays may be related to loading map locations, textures, etc. and maybe this is the norm, I don't know. But maybe it's the chipset, the processor, the devil of a clue. (did not check on another drive with Win 11) And yes, I recently replaced the PSU, so the problem is definitely not in it. I am very confused by the beginning of this whole epic, namely from overclocking the video card, maybe I overtook something and it broke, but as for me, either the card works or it does not work. I was going to get a new one, but I'm not sure if the problem is already in it. And so, I ask for your advice and help, whether I correctly came to the conclusion that this is a hardware problem, and where should I dig further, what to try. I'm sorry for my English, I'm using google translate Spec PC: MotherB - Asus Z-490 V CPU - i510600K GPU - GTX 1660ti SSD - samsung 860 evo, 960 evo HDD - Western Digital Blue 1 TB PSU - DeepCool PQ750 Discrete Sound Card - Asus Xonar SE Scrennshot LatencyMoon msi afterburner ( stutter moment)
LatencyMoon Log _________________________________________________________________________________________________________ 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 1:25:57 (h:mm:ss) on all processors. _________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name: DESKTOP-96RE5B8 OS version: Windows 10, 10.0, version 2009, build: 19045 (x64) Hardware: System Product Name, ASUS BIOS: 1621 CPU: GenuineIntel Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz Logical processors: 12 Processor groups: 1 Processor group size: 12 RAM: 16298 MB total _________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed (WMI): 4104 MHz Reported CPU speed (registry): 4104 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): 1543,80 Average measured interrupt to process latency (µs): 4,197951 Highest measured interrupt to DPC latency (µs): 1541,80 Average measured interrupt to DPC latency (µs): 1,862773 _________________________________________________________________________________________________________ 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): 375,451998 Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Highest reported total ISR routine time (%): 0,100565 Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Total time spent in ISRs (%) 0,104483 ISR count (execution time <250 µs): 7675817 ISR count (execution time 250-500 µs): 0 ISR count (execution time 500-1000 µs): 32 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): 1021,880604 Driver with highest DPC routine execution time: CLASSPNP.SYS - SCSI Class System Dll, Microsoft Corporation Highest reported total DPC routine time (%): 0,071915 Driver with highest DPC total execution time: Wdf01000.sys - Среда выполнения платформы драйвера режима ядра, Microsoft Corporation Total time spent in DPCs (%) 0,139784 DPC count (execution time <250 µs): 12738614 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-10000 µs): 94 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: chrome.exe Total number of hard pagefaults 38868 Hard pagefault count of hardest hit process: 6159 Number of processes hit: 123 _________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 254,331189 CPU 0 ISR highest execution time (µs): 375,451998 CPU 0 ISR total execution time (s): 64,158897 CPU 0 ISR count: 7095599 CPU 0 DPC highest execution time (µs): 744,790692 CPU 0 DPC total execution time (s): 80,254106 CPU 0 DPC count: 11532642 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 81,795559 CPU 1 ISR highest execution time (µs): 253,983674 CPU 1 ISR total execution time (s): 0,263382 CPU 1 ISR count: 173841 CPU 1 DPC highest execution time (µs): 218,708333 CPU 1 DPC total execution time (s): 3,794293 CPU 1 DPC count: 312055 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s): 55,369005 CPU 2 ISR highest execution time (µs): 20,995614 CPU 2 ISR total execution time (s): 0,001647 CPU 2 ISR count: 1558 CPU 2 DPC highest execution time (µs): 823,441520 CPU 2 DPC total execution time (s): 1,121869 CPU 2 DPC count: 466357 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s): 55,423132 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): 142,653265 CPU 3 DPC total execution time (s): 0,041883 CPU 3 DPC count: 12379 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s): 52,523160 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): 207,762183 CPU 4 DPC total execution time (s): 0,358381 CPU 4 DPC count: 123884 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s): 53,266402 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): 138,484893 CPU 5 DPC total execution time (s): 0,075043 CPU 5 DPC count: 24473 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s): 43,924948 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): 1021,880604 CPU 6 DPC total execution time (s): 0,248703 CPU 6 DPC count: 89661 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s): 46,102009 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): 231,308236 CPU 7 DPC total execution time (s): 0,058537 CPU 7 DPC count: 19900 _________________________________________________________________________________________________________ CPU 8 Interrupt cycle time (s): 48,617763 CPU 8 ISR highest execution time (µs): 39,430799 CPU 8 ISR total execution time (s): 0,017064 CPU 8 ISR count: 24957 CPU 8 DPC highest execution time (µs): 215,729776 CPU 8 DPC total execution time (s): 0,246881 CPU 8 DPC count: 65614 _________________________________________________________________________________________________________ CPU 9 Interrupt cycle time (s): 57,365937 CPU 9 ISR highest execution time (µs): 150,747807 CPU 9 ISR total execution time (s): 0,195858 CPU 9 ISR count: 336642 CPU 9 DPC highest execution time (µs): 152,650585 CPU 9 DPC total execution time (s): 0,079083 CPU 9 DPC count: 26260 _________________________________________________________________________________________________________ CPU 10 Interrupt cycle time (s): 31,643502 CPU 10 ISR highest execution time (µs): 116,831871 CPU 10 ISR total execution time (s): 0,003698 CPU 10 ISR count: 5298 CPU 10 DPC highest execution time (µs): 198,546053 CPU 10 DPC total execution time (s): 0,179568 CPU 10 DPC count: 51027 _________________________________________________________________________________________________________ CPU 11 Interrupt cycle time (s): 31,827946 CPU 11 ISR highest execution time (µs): 112,826998 CPU 11 ISR total execution time (s): 0,020378 CPU 11 ISR count: 37954 CPU 11 DPC highest execution time (µs): 140,588207 CPU 11 DPC total execution time (s): 0,049075 CPU 11 DPC count: 14457 _________________________________________________________________________________________________________
That`s the bug in LatencyMon I see for years: Code: _________________________________________________________________________________________________________ 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): 375,451998 Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Highest reported total ISR routine time (%): 0,100565 Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Total time spent in ISRs (%) 0,104483 ISR count (execution time <250 µs): 7675817 ISR count (execution time 250-500 µs): 0 ISR count (execution time 500-1000 µs): 32 ISR count (execution time 1000-2000 µs): 0 ISR count (execution time 2000-4000 µs): 0 ISR count (execution time >=4000 µs): 0 We see statement "Highest ISR routine execution time (µs): 375,451998" and then in histogram section we see two statements contradicting first one - "ISR count (execution time 250-500 µs): 0" and "ISR count (execution time 500-1000 µs): 32": - execution time of 375,451998 should go into "ISR count (execution time 250-500 µs):" bucket but we see "0"; - 32 cases of execution time 500-1000 should be noted in "Highest ISR routine execution time (µs)" statement but we see "375,451998". PS That`s why I prefer this method https://forums.guru3d.com/threads/simple-way-to-trace-dpcs-and-isrs.423884/
Also worth to try MSI mode tweak - https://forums.guru3d.com/threads/w...ge-signaled-based-interrupts-msi-tool.378044/ It can reduce ISR latencies a bit. PS Also worth to try to disable hibernation - execute "powercfg /h off" in elevated command prompt, - in case you see file "hiberfil.sys" in root folder of system disk.
I tried your method, I attach the report. I do not quite understand how to read it, which drivers indicate a large delay? More than 512us have multiple drivers, are they the culprits? Any thoughts what it could be? Log: Code: Total = 221346 for module ntoskrnl.exe Elapsed Time, > 0 usecs AND <= 1 usecs, 31966, or 14.44% Elapsed Time, > 1 usecs AND <= 2 usecs, 75674, or 34.19% Elapsed Time, > 2 usecs AND <= 4 usecs, 11844, or 5.35% Elapsed Time, > 4 usecs AND <= 8 usecs, 42905, or 19.38% Elapsed Time, > 8 usecs AND <= 16 usecs, 32537, or 14.70% Elapsed Time, > 16 usecs AND <= 32 usecs, 10841, or 4.90% Elapsed Time, > 32 usecs AND <= 64 usecs, 15454, or 6.98% Elapsed Time, > 64 usecs AND <= 128 usecs, 51, or 0.02% Elapsed Time, > 128 usecs AND <= 256 usecs, 56, or 0.03% Elapsed Time, > 256 usecs AND <= 512 usecs, 6, or 0.00% Elapsed Time, > 512 usecs AND <= 1024 usecs, 10, or 0.00% Elapsed Time, > 1024 usecs AND <= 2048 usecs, 2, or 0.00% Code: Total = 969374 for module nvlddmkm.sys Elapsed Time, > 0 usecs AND <= 1 usecs, 671021, or 69.22% Elapsed Time, > 1 usecs AND <= 2 usecs, 39002, or 4.02% Elapsed Time, > 2 usecs AND <= 4 usecs, 74652, or 7.70% Elapsed Time, > 4 usecs AND <= 8 usecs, 53185, or 5.49% Elapsed Time, > 8 usecs AND <= 16 usecs, 31661, or 3.27% Elapsed Time, > 16 usecs AND <= 32 usecs, 68701, or 7.09% Elapsed Time, > 32 usecs AND <= 64 usecs, 13857, or 1.43% Elapsed Time, > 64 usecs AND <= 128 usecs, 16375, or 1.69% Elapsed Time, > 128 usecs AND <= 256 usecs, 846, or 0.09% Elapsed Time, > 256 usecs AND <= 512 usecs, 53, or 0.01% Elapsed Time, > 512 usecs AND <= 1024 usecs, 21, or 0.00% Total, 969374
I installed the MSI utility program, I see that some drivers use the same IRQ, maybe this is the problem? oh graphic card too lol Change on MSI, time to test Update: Tested, all IRQs are different, starters remain
Set all to MSI mode Also do you have HAGS enabled in windows graphics settings? Oh yeah and run memtest overnight to fully exclude the ram
Shared IRQ is bad thing in any case. In old days it was a sentence to BSOD. Now Windows can handle such thing but it is still no good.
Updatе 2.0 After reading that thread, one person changed the Nvme controller priority to "undefined" and the graphic card to "high", the freeze seems to be gone!! I played for 20 minutes, there was nothing, earlier in 5 minutes the first ones appeared, so far progress !! I'm so happy. But I need to test further, I'll test for a few days and unsubscribe about the result Thank you so much!
https://drive.google.com/file/d/1unL0QXaDV7qIScBYpVyogu3AQNdRSNOy/view?usp=share_link It seems to be off, need to turn it on? ok, i will try
IRQ's above 15 are virtual anyway, there are only 16 hardware irq's on an APIC controller (0-15), anything above is virtualized and allocated onto one of the physical irq's priority change fixing anything means the nvme is generating high pcie errors, so the OS priotises retry requests above the GPU's own packets.
