Hi Mr. Roos,
I see you have the same mobo as me. My LatencyMon figures using 1905 latest are atrocious, the nt kernel delays in the 3 mS range… I did some troubleshooting, to no avail. Can you remember what you did that really got rid of the spiking/delays?
The only thing that seems to help a bit is turning off all processor throttling, but even then I have spikes.
Best,
Zip
I do have some thoughts, Zip.
Briefly, check out the Sweetwater site and the Presonus site for their setup ideas. Install CClean and check out the Startup items that are there. Disable what you can. Remove the AMD control app… and keep the drivers. Open Windows Settings and turn off anything that you don’t use - it’s endless, Cortana, Bluetooth, Xbox Gaming - and open every item line to the left of each category to make sure you have dug deep enough. I revisit this often and every time it seems I had overlooked something. Remove the Explorer browser and keep Edge.
Do everything that the Windows Security wants you to do basically, but as you do this, again look at the lines to the left and open each one. You might see the option ‘Ignore’ come up, I’ve ignored a few things but can’t remember anything in particular but the option does come up, pay attention. When you’ve set this up properly, you will see 5 items with green check marks on them. This is what you want, and I say this because it is my thought that Win10 is very security minded - if something is ignored it will tell you repeatedly - which tells me that WIN10 is searching in the background to resolve the ‘problem’. The last thing you need is to have a search going on while you are recording.
Lastly turn on ‘Airplane mode’ when you record. Again, back to the searching process, I think that if you simply disconnect your internet connection by pulling a cable or even turning wifi off, Win10 will keep searching for the connection. I think it is better that you ‘tell’ Win10 that you are going into Airplane mode so it can chill, and stop the searching.
That’s all I got, I hope this helps. That KB update, though, that’s a BIG deal, get that installed because it is a game changer even after all the setup work I have done, Zip
I got 1903 installed today. 1st try didn’t succeed. I got the error id 0xc1900101 (driver error) and 0x8000ffff.
I enabled “set automatic timezone” and disconnected all my gear (the entire USB hub with all controllers and audio interface).
1903 installed successfully with these steps.
Cubase showed the e-Licenser message (access difficulties). After starting the eLicenser Control Center as Administrator and the maintenance update, it was ok with Cubase. All plugins worked fine (iZotope, Waves 9+10, Fabfilter, Sylenth, Spire, NI, Avenger). I had to reactivate the Atlas Sampler only.
All HW did work except of the Korg nanoKontrol. There is a new driver from Korg required for Windows 1903 for all their USB-stuff.
It was quite a hassle with regedit and several install/deinstall to get it to run: https://thedigitallifestyle.com/w/index.php/2019/04/23/fixing-korg-usb-midi-driver-issues-in-windows-10-may-2019-update
So far so good. Performance is the same as before.
Also Zip, in the Device Manager I disabled the Intel Wireless Bluetooth, the AMD High Def Audio Device and the High Def Audio Device (since all my sounds are produced from my interface). FWIW, again, I see the Bluetooth option as something that is constantly searching for a connection so I turned it off. Also I wonder if you have turned on your Ram so that it uses all of its capacity? Download cpuz_64 and look under the Memory tab. My memory is running at 3200MHz so in my system using this app, I see 1600MHz which is correct (Double the 1600 to see the actual number = 3200). I’m not sure if all MBs do this but without changing some things in the Bios, 3200MHz memory will run at 2133MHz. Look into this.
Here’s my LantencyMon readout today:
CONCLUSION
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 1:02:55 (h:mm:ss) on all processors.
\
SYSTEM INFORMATION
Computer name: DAW
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: Z390 DESIGNARE, Gigabyte Technology Co., Ltd., Z390 DESIGNARE-CF
CPU: GenuineIntel Intel(R) Core™ i7-8700 CPU @ 3.20GHz
Logical processors: 12
Processor groups: 1
RAM: 32700 MB total
\
CPU SPEED
Reported CPU speed: 3192 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.
WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.
\
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): 101.50
Average measured interrupt to process latency (µs): 1.989737
Highest measured interrupt to DPC latency (µs): 99.70
Average measured interrupt to DPC latency (µs): 0.726302
\
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): 1.393170
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Highest reported total ISR routine time (%): 0.0
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in ISRs (%) 0.0
ISR count (execution time <250 µs): 362
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µ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): 213.982456
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation
Highest reported total DPC routine time (%): 0.001398
Driver with highest DPC total execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation
Total time spent in DPCs (%) 0.004198
DPC count (execution time <250 µs): 1754839
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µ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: msmpeng.exe
Total number of hard pagefaults 1521
Hard pagefault count of hardest hit process: 860
Number of processes hit: 11
\
PER CPU DATA
CPU 0 Interrupt cycle time (s): 5.442286
CPU 0 ISR highest execution time (µs): 1.393170
CPU 0 ISR total execution time (s): 0.000095
CPU 0 ISR count: 362
CPU 0 DPC highest execution time (µs): 103.493734
CPU 0 DPC total execution time (s): 1.545829
CPU 0 DPC count: 1553008
CPU 1 Interrupt cycle time (s): 1.155785
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): 15.366541
CPU 1 DPC total execution time (s): 0.000698
CPU 1 DPC count: 519
CPU 2 Interrupt cycle time (s): 1.438444
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): 213.982456
CPU 2 DPC total execution time (s): 0.061554
CPU 2 DPC count: 42377
CPU 3 Interrupt cycle time (s): 1.152778
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): 8.592105
CPU 3 DPC total execution time (s): 0.000718
CPU 3 DPC count: 588
CPU 4 Interrupt cycle time (s): 1.436786
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): 14.145677
CPU 4 DPC total execution time (s): 0.028792
CPU 4 DPC count: 19815
CPU 5 Interrupt cycle time (s): 1.115911
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): 13.101190
CPU 5 DPC total execution time (s): 0.001210
CPU 5 DPC count: 930
CPU 6 Interrupt cycle time (s): 1.486754
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): 23.510652
CPU 6 DPC total execution time (s): 0.066137
CPU 6 DPC count: 40375
CPU 7 Interrupt cycle time (s): 1.125001
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): 10.880013
CPU 7 DPC total execution time (s): 0.000679
CPU 7 DPC count: 426
CPU 8 Interrupt cycle time (s): 1.68880
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): 33.911967
CPU 8 DPC total execution time (s): 0.075670
CPU 8 DPC count: 39351
CPU 9 Interrupt cycle time (s): 1.187143
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): 11.332707
CPU 9 DPC total execution time (s): 0.001335
CPU 9 DPC count: 587
CPU 10 Interrupt cycle time (s): 1.978203
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): 18.415414
CPU 10 DPC total execution time (s): 0.117084
CPU 10 DPC count: 55797
CPU 11 Interrupt cycle time (s): 1.157228
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): 10.631892
CPU 11 DPC total execution time (s): 0.001980
CPU 11 DPC count: 1066
After 30 minutes of running LatencyMon:
The KB4505903 Windows update seems to have fixed my latency issues. Nice.
Thanks for the tips, Mr Roos!
Tested some more. No latency issues. Just the KB4505903 update fixed my problems in Windows.
It broke my two MOTU Midi Interfaces, they no longer work correctly getting all kinds of hiccups, cut notes, etc.
Eventually found out that I had to change the USB cable for one of shorter length and ferrite module in it. Now it is working and while connected to a cheap Targus USB2 - 4 port hub. Saved from having to purchase a $400 iConnectivity Midi mioXL Interface, YAY!
I believe we are going to the 1909 update.
I did not have any problems at all.