I really would like some help with understanding the results of a LatencyMon test.
I was having playback issues with an arrangement, getting frustrated as, although it’s not a super high spec machine, I thought my laptop should be able to handle what I was asking of it.
After a lot of forum searching, advice reading, bloatware deleting, power management reconfiguring and latest driver checking I found my way to LatencyMon.
The test results were not pretty, telling me that my system was having trouble handling real-time audio. This I already knew, but there was hope as a few problem areas were identified for me to address.
I have to be honest, I really had no idea how to fix, or even look into sorting out the problems. I typed the culprit drivers into google and checked various forums looking for solutions. Commands were commanded to the command prompt, bios was entered but looked to be pretty restricted in its scope of customisation (Huawei’s got it on lockdown?), I’ve tweaked and changed and de-activated and re-activated to no avail. I think I may have gotten myself into a bit of a pickle ‘optimising’ my laptop for Audio.
If anyone can help me through troubleshooting this problem I would really appreciate it.
Laptop specs are:
Huawei Matebook x-Pro 2020
Processor - Intel i7 10th gen - 10510U CPU @ 1.80GHz 2.30 GHz
RAM - 16 GB LPDDR3 2133 MHz
GPU - NVIDIA® GeForce® MX250 (currently disabled as there is no ‘Studio Mode’ driver thingy for this model)
Storage - 1 TB NVMe PCIe SSD
Operating system - Windows 11
I’m running the laptop plugged in, so not on the battery.
My audio interface is the Steinberg UR44C running into the USB 3.0 port
Below are are the results from LatencyMon:
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. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. 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 18:19:14 (h:mm:ss) on all processors. _________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name: LAPTOP OS version: Windows 11, 10.0, version 2009, build: 22631 (x64) Hardware: MACHC-WAX9, HUAWEI BIOS: 1.26 CPU: GenuineIntel Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz Logical processors: 8 Processor groups: 1 Processor group size: 8 RAM: 16219 MB total _________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed (WMI): 1803 MHz Reported CPU speed (registry): 2304 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): 136417.20 Average measured interrupt to process latency (µs): 11.373590 Highest measured interrupt to DPC latency (µs): 136406.20 Average measured interrupt to DPC latency (µs): 3.589035 _________________________________________________________________________________________________________ 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): 314.539063 Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation Highest reported total ISR routine time (%): 0.001328 Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation Total time spent in ISRs (%) 0.001348 ISR count (execution time <250 µs): 419392 ISR count (execution time 250-500 µs): 0 ISR count (execution time 500-1000 µs): 17 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): 2794.988715 Driver with highest DPC routine execution time: ACPI.sys - ACPI Driver for NT, Microsoft Corporation Highest reported total DPC routine time (%): 0.000590 Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp. Total time spent in DPCs (%) 0.002674 DPC count (execution time <250 µs): 1401402 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-10000 µs): 833 DPC count (execution time 1000-2000 µs): 7 DPC count (execution time 2000-4000 µs): 12 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: latmon.exe Total number of hard pagefaults 31014 Hard pagefault count of hardest hit process: 6231 Number of processes hit: 112 _________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 49.646401 CPU 0 ISR highest execution time (µs): 314.539063 CPU 0 ISR total execution time (s): 7.089926 CPU 0 ISR count: 418208 CPU 0 DPC highest execution time (µs): 2794.988715 CPU 0 DPC total execution time (s): 10.204844 CPU 0 DPC count: 1119873 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 15.997483 CPU 1 ISR highest execution time (µs): 163.073785 CPU 1 ISR total execution time (s): 0.018859 CPU 1 ISR count: 1063 CPU 1 DPC highest execution time (µs): 2695.654514 CPU 1 DPC total execution time (s): 0.232166 CPU 1 DPC count: 24173 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s): 26.279998 CPU 2 ISR highest execution time (µs): 71.901910 CPU 2 ISR total execution time (s): 0.002489 CPU 2 ISR count: 138 CPU 2 DPC highest execution time (µs): 837.394965 CPU 2 DPC total execution time (s): 0.382475 CPU 2 DPC count: 37129 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s): 28.440635 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): 544.742188 CPU 3 DPC total execution time (s): 0.639580 CPU 3 DPC count: 45366 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s): 48.987164 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): 831.948785 CPU 4 DPC total execution time (s): 1.299138 CPU 4 DPC count: 75864 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s): 37.968801 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): 835.009549 CPU 5 DPC total execution time (s): 0.332288 CPU 5 DPC count: 28079 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s): 27.403749 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): 582.935764 CPU 6 DPC total execution time (s): 0.850614 CPU 6 DPC count: 57990 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s): 23.294644 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): 197.176215 CPU 7 DPC total execution time (s): 0.169809 CPU 7 DPC count: 13780 _________________________________________________________________________________________________________
Thanks in advance for any help you can give. I know that there is a lot going on under the hood when Cubase is running with windows, I’d just like them to run in a matching stride if it’s at all possible. I (naively) thought it would have been a given, but, alas, tweaking is needed.