Hello everyone, I would like to receive some outside opinions on this matter: Content: 1. Problem 2. Analysis 3. Attempted solutions 4. System specification 1. Problem Game freezes for a very short period of time in no specific interval, accompanied by general delayed response of system. I can't help but notice that during my gaming session the computer has problem executing my inputs or executes them with small delay: Input to (mouse/keyboard) -> delay (0.1s) -> action is displayed on screen 2. Analysis Windows performance analyzer: Result too big to upload in text formatting On game Spoiler: Download link for txt http://www.mediafire.com/file/la2rar340hxv6zh/WPA_game.txt/file On idle Spoiler: Download link for txt http://www.mediafire.com/file/jcbuajucdaituwo/WPA_idle.txt/file Latencymon: Conclusion: Spoiler: text Code: _________________________________________________________________________________________________________ CONCLUSION _________________________________________________________________________________________________________ Your system appears to be suitable for handling real-time audio and other tasks without dropouts. LatencyMon has been analyzing your system for 0:03:04 (h:mm:ss) on all processors. _________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name: POVILO-PC OS version: Windows 10, 10.0, version 2009, build: 19042 (x64) Hardware: MS-7C87, Micro-Star International Co., Ltd. CPU: AuthenticAMD AMD Ryzen 5 2600 Six-Core Processor Logical processors: 12 Processor groups: 1 RAM: 8145 MB total _________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed: 340 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): 244.30 Average measured interrupt to process latency (µs): 8.237888 Highest measured interrupt to DPC latency (µs): 239.90 Average measured interrupt to DPC latency (µs): 2.802892 _________________________________________________________________________________________________________ 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): 3.560 Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation Highest reported total ISR routine time (%): 0.000025 Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation Total time spent in ISRs (%) 0.000025 ISR count (execution time <250 µs): 790 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): 533.950 Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation Highest reported total DPC routine time (%): 0.005703 Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 457.30 , NVIDIA Corporation Total time spent in DPCs (%) 0.014961 DPC count (execution time <250 µs): 32630 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-10000 µs): 12 DPC count (execution time 1000-2000 µs): 0 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 404 Hard pagefault count of hardest hit process: 189 Number of processes hit: 9 _________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 1.894664 CPU 0 ISR highest execution time (µs): 3.560 CPU 0 ISR total execution time (s): 0.000453 CPU 0 ISR count: 631 CPU 0 DPC highest execution time (µs): 471.040 CPU 0 DPC total execution time (s): 0.230288 CPU 0 DPC count: 24648 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 0.687434 CPU 1 ISR highest execution time (µs): 0.0 CPU 1 ISR total execution time (s): 0.0 CPU 1 ISR count: 0 CPU 1 DPC highest execution time (µs): 245.70 CPU 1 DPC total execution time (s): 0.003516 CPU 1 DPC count: 109 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s): 0.628570 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): 288.410 CPU 2 DPC total execution time (s): 0.012616 CPU 2 DPC count: 766 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s): 0.914924 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): 274.970 CPU 3 DPC total execution time (s): 0.033057 CPU 3 DPC count: 873 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s): 0.401661 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): 186.180 CPU 4 DPC total execution time (s): 0.007154 CPU 4 DPC count: 851 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s): 0.863798 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): 533.950 CPU 5 DPC total execution time (s): 0.031429 CPU 5 DPC count: 3896 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s): 0.305979 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): 64.90 CPU 6 DPC total execution time (s): 0.002932 CPU 6 DPC count: 401 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s): 0.313690 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): 14.270 CPU 7 DPC total execution time (s): 0.000048 CPU 7 DPC count: 12 _________________________________________________________________________________________________________ CPU 8 Interrupt cycle time (s): 0.367871 CPU 8 ISR highest execution time (µs): 1.860 CPU 8 ISR total execution time (s): 0.000079 CPU 8 ISR count: 132 CPU 8 DPC highest execution time (µs): 61.230 CPU 8 DPC total execution time (s): 0.002875 CPU 8 DPC count: 378 _________________________________________________________________________________________________________ CPU 9 Interrupt cycle time (s): 0.317521 CPU 9 ISR highest execution time (µs): 1.090 CPU 9 ISR total execution time (s): 0.000015 CPU 9 ISR count: 27 CPU 9 DPC highest execution time (µs): 58.370 CPU 9 DPC total execution time (s): 0.000339 CPU 9 DPC count: 47 _________________________________________________________________________________________________________ CPU 10 Interrupt cycle time (s): 0.314795 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): 69.810 CPU 10 DPC total execution time (s): 0.003599 CPU 10 DPC count: 495 _________________________________________________________________________________________________________ CPU 11 Interrupt cycle time (s): 0.374663 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): 524.540 CPU 11 DPC total execution time (s): 0.003021 CPU 11 DPC count: 166 _________________________________________________________________________________________________________ Main: Hardfault: Driver: CPU: Bufferbloat: Without cake scheduler: Speed result of 16.83/18.74 Mbps | DSLReports, ISP Information With cake scheduler: Speed result of 15.22/14.13 Mbps | DSLReports, ISP Information 3. Attempted solutions Drivers: all drivers in msi mode Chipset: latest revision from amd.com Ethernet: latest revision from realtek.com Wifi: latest revision from intel support Bluetooth: latest revision from intel support Audio: latest revision from motherboard manufacturer Video: latest revision from nvidia.com Windows 10: Build: 19042.662 (20H2) BIOS: ver: 7C87v11 date: 2020-06-16 mods: exposed and disabled hpet xmp: enabled Settings: Power plan: balanced Game bar: disabled Enchanced pointer preccision: disabled Scalling: display scalling Disable fullscreen optimisations: ticked General: sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth chkdsk /b /v 4. System specification CPU: Ryzen 2600 GPU: GTX 1060 6Gb MAINB: MSI B450m bazooka max wifi RAM: Patriot Viper 4 Blackout Series DDR4 8GB (2 x 4GB) 3200MHz PSU: Corsair tx550m gold, modular CASE: Corsair carbide spec-05 NVME: SX8200 pro, 500gb m.2 Monitor: AOC 24g2u 144hz, displayport Any insight is appreciated, thank you!
Have you tried to disable SMT (hyperthreading) in BIOS? As for interrupts, we see a suspect in DPC section - nvlddmkm.sys (with the "helpers" ndis.sys and tcpip.sys). You can try to optimise network stack: https://github.com/djdallmann/GamingPCSetup/tree/master/NETWORK https://www.speedguide.net/articles/windows-8-2012-server-tcpip-tweaks-5077 https://www.speedguide.net/articles/network-adapter-optimization-3449
due to extra works hours I have not had time to apply the tweaks yet, however I have examined the sources, will update tommorow
