Richter Di
1000+ Head-Fier
Thank you once more for the great tool LatencyMon. It makes a huge difference to actually see a report with measurements taken over 30 minutes.Most of this audio problems are caused by bad drivers. You can check this on your PC with LatencyMon.
Anyhow the problem seems totally unrelated to the Smyth Realiser A16 since LatencyMon shows problems even if I use the onboard SoundCard or the ifi nano.
I have tried to figure out which Bios settings might be helpful and also changed the Windows 10 Energy Management to High Performance.
Here is the report. Maybe someone more knowledgable than me knows what it says:
___________________________________
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 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:05:42 (h:mm:ss) on all processors.
___________________________________
SYSTEM INFORMATION
___________________________________
Computer name: DESKTOP-B0DG9FM
OS version: Windows 10, 10.0, version 2009, build: 19044 (x64)
Hardware: System Product Name, ASUS
BIOS: 1304
CPU: GenuineIntel 12th Gen Intel(R) Core(TM) i7-12700K
Logical processors: 20
Processor groups: 1
Processor group size: 20
RAM: 65277 MB total
___________________________________
CPU SPEED
___________________________________
Reported CPU speed (WMI): 360 MHz
Reported CPU speed (registry): 3610 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): 1801,80
Average measured interrupt to process latency (µs): 4,279525
Highest measured interrupt to DPC latency (µs): 123,0
Average measured interrupt to DPC latency (µs): 0,731969
___________________________________
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): 67,144044
Driver with highest ISR routine execution time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation
Highest reported total ISR routine time (%): 0,000617
Driver with highest ISR total time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation
Total time spent in ISRs (%) 0,000639
ISR count (execution time <250 µs): 177314
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): 792,886427
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 512.15 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0,024157
Driver with highest DPC total execution time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation
Total time spent in DPCs (%) 0,044936
DPC count (execution time <250 µs): 463827
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 28
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: explorer.exe
Total number of hard pagefaults 17705
Hard pagefault count of hardest hit process: 4129
Number of processes hit: 48
___________________________________
PER CPU DATA
___________________________________
CPU 0 Interrupt cycle time (s): 4,663347
CPU 0 ISR highest execution time (µs): 0,0
CPU 0 ISR total execution time (s): 0,0
CPU 0 ISR count: 0
CPU 0 DPC highest execution time (µs): 111,178393
CPU 0 DPC total execution time (s): 0,067803
CPU 0 DPC count: 113886
___________________________________
CPU 1 Interrupt cycle time (s): 4,172053
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): 2,396676
CPU 1 DPC total execution time (s): 0,000055
CPU 1 DPC count: 56
___________________________________
CPU 2 Interrupt cycle time (s): 2,577662
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): 158,491413
CPU 2 DPC total execution time (s): 0,004664
CPU 2 DPC count: 2720
___________________________________
CPU 3 Interrupt cycle time (s): 2,561963
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): 1,293075
CPU 3 DPC total execution time (s): 0,000053
CPU 3 DPC count: 77
___________________________________
CPU 4 Interrupt cycle time (s): 3,396157
CPU 4 ISR highest execution time (µs): 24,234903
CPU 4 ISR total execution time (s): 0,001555
CPU 4 ISR count: 143
CPU 4 DPC highest execution time (µs): 49,473684
CPU 4 DPC total execution time (s): 0,005423
CPU 4 DPC count: 3982
___________________________________
CPU 5 Interrupt cycle time (s): 3,193061
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): 0,0
CPU 5 DPC total execution time (s): 0,0
CPU 5 DPC count: 0
___________________________________
CPU 6 Interrupt cycle time (s): 0,875063
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): 55,377839
CPU 6 DPC total execution time (s): 0,000982
CPU 6 DPC count: 505
___________________________________
CPU 7 Interrupt cycle time (s): 0,872836
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): 0,0
CPU 7 DPC total execution time (s): 0,0
CPU 7 DPC count: 0
___________________________________
CPU 8 Interrupt cycle time (s): 5,032971
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): 100,839889
CPU 8 DPC total execution time (s): 0,075214
CPU 8 DPC count: 21202
___________________________________
CPU 9 Interrupt cycle time (s): 5,485141
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): 19,877008
CPU 9 DPC total execution time (s): 0,000285
CPU 9 DPC count: 78
___________________________________
CPU 10 Interrupt cycle time (s): 0,884222
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 27,804432
CPU 10 DPC total execution time (s): 0,000490
CPU 10 DPC count: 149
___________________________________
CPU 11 Interrupt cycle time (s): 0,880374
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): 0,0
CPU 11 DPC total execution time (s): 0,0
CPU 11 DPC count: 0
___________________________________
CPU 12 Interrupt cycle time (s): 9,215118
CPU 12 ISR highest execution time (µs): 67,144044
CPU 12 ISR total execution time (s): 0,042183
CPU 12 ISR count: 177171
CPU 12 DPC highest execution time (µs): 218,103601
CPU 12 DPC total execution time (s): 1,717885
CPU 12 DPC count: 194300
___________________________________
CPU 13 Interrupt cycle time (s): 5,494957
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): 0,977285
CPU 13 DPC total execution time (s): 0,000002
CPU 13 DPC count: 2
___________________________________
CPU 14 Interrupt cycle time (s): 1,197843
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): 74,667590
CPU 14 DPC total execution time (s): 0,000416
CPU 14 DPC count: 91
___________________________________
CPU 15 Interrupt cycle time (s): 1,189839
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): 0,0
CPU 15 DPC total execution time (s): 0,0
CPU 15 DPC count: 0
___________________________________
CPU 16 Interrupt cycle time (s): 13,815095
CPU 16 ISR highest execution time (µs): 0,0
CPU 16 ISR total execution time (s): 0,0
CPU 16 ISR count: 0
CPU 16 DPC highest execution time (µs): 792,886427
CPU 16 DPC total execution time (s): 1,098345
CPU 16 DPC count: 110765
___________________________________
CPU 17 Interrupt cycle time (s): 4,776555
CPU 17 ISR highest execution time (µs): 0,0
CPU 17 ISR total execution time (s): 0,0
CPU 17 ISR count: 0
CPU 17 DPC highest execution time (µs): 64,812188
CPU 17 DPC total execution time (s): 0,030692
CPU 17 DPC count: 4746
___________________________________
CPU 18 Interrupt cycle time (s): 5,993094
CPU 18 ISR highest execution time (µs): 0,0
CPU 18 ISR total execution time (s): 0,0
CPU 18 ISR count: 0
CPU 18 DPC highest execution time (µs): 63,715789
CPU 18 DPC total execution time (s): 0,021763
CPU 18 DPC count: 3555
___________________________________
CPU 19 Interrupt cycle time (s): 6,178742
CPU 19 ISR highest execution time (µs): 0,0
CPU 19 ISR total execution time (s): 0,0
CPU 19 ISR count: 0
CPU 19 DPC highest execution time (µs): 100,505817
CPU 19 DPC total execution time (s): 0,050257
CPU 19 DPC count: 7741
___________________________________
Correct, but it does present itself as 7.1 capable and I didn't see anything in your question specific to Atmos.
I don't remember if Windows wraps all audio in an Atmos container when configured to use Dolby Atmos for Home Theater or not, but I would see if the problem exists when using 7.1 LPCM over HDMI and/or USB.
Thanks, but as described above it seems not a A16 specific problem.