Cubase projects suddenly spiking when previously they were fine

Cubase
1

Hi,

I have an old i7 6700K machine that I will fairly soon be replacing. Meanwhile, I am using my trusty old i7.

Since yesterday, previously fine projects have suddenly started spiking, the Asio guard meter goes from perhaps 40% all the way to the top and spikes.

I haven’t changed any settings. Even projects that were fine before, suddenly show this behaviour.

I am at a loss what may be causing it. I have an RME AIO soundcard, highest buffer settings, Asio guard set at high. Everything is as before.

When .0.50 came out, I updated from .030. I didn’t start getting these spikes until yesterday, which is some days after updating, so that seems unlikely to be causing it.

Norton Antivirus also decided to update itself the other day, but I don’t think that is causing the spikes, since disabling the virus protection and firewall made no difference.

I use a lot of cpu hungry Acustica Audio stuff, but as I said above, these projects were fine until now, albeit on the very brink, since I push my old cpu really hard.

My projects are audio only, no midi, no vistis etc, merely multitrack recorded audio.

The issue appeared at the mastering stage. I master the exported 24 bit stereo mixes, before exporting them as 16 bit wavs for making mp3s etc.

The temporary workaround is to move three of the processors from the Stereo out to the audio track, and then freeze. After that I can apply the two remaining processors (a clipper and limiter) on the Stereo out, without any issues, before exporting.

Until yesterday, I could have all five processors running with no problems on the Stereo out, and then export directly from there.

Any ideas would be much appreciated.

Best,

Magnus

i7 6700K, 32 GB RAM, Win 10, Cubase Pro 13.0.50, RME AIO

2

Hi,

Test your system by using LatencyMon utility, please.

1 Like
3

Hi Martin!

Just downloade Latmon and did a brief test. See below.

And MANY huge thanks for helping me get to grips with this. It’s driving me nuts.

Best,

Magnus

Latency Mon reprt:

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:04:23 (h:mm:ss) on all processors.

SYSTEM INFORMATION

Computer name: DESKTOP-L6IAAMD
OS version: Windows 10, 10.0, version 2009, build: 19045 (x64)
Hardware: System Product Name, Exertis_CapTech
BIOS: BIOS Date: 11/09/15 17:26:10 Ver: 05.0000B
CPU: GenuineIntel Intel(R) Core™ i7-6700K CPU @ 4.00GHz
Logical processors: 8
Processor groups: 1
Processor group size: 8
RAM: 32621 MB total

CPU SPEED

Reported CPU speed (WMI): 4001 MHz
Reported CPU speed (registry): 4008 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): 790,30
Average measured interrupt to process latency (µs): 10,845508

Highest measured interrupt to DPC latency (µs): 780,40
Average measured interrupt to DPC latency (µs): 4,724508

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): 211,580339
Driver with highest ISR routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Highest reported total ISR routine time (%): 0,000118
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0,000222

ISR count (execution time <250 µs): 1983
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): 806,078343
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation

Highest reported total DPC routine time (%): 0,050116
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 565.90 , NVIDIA Corporation

Total time spent in DPCs (%) 0,080656

DPC count (execution time <250 µs): 161607
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 19
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: latmon.exe

Total number of hard pagefaults 8
Hard pagefault count of hardest hit process: 4
Number of processes hit: 4

PER CPU DATA

CPU 0 Interrupt cycle time (s): 6,378917
CPU 0 ISR highest execution time (µs): 211,580339
CPU 0 ISR total execution time (s): 0,004565
CPU 0 ISR count: 1869
CPU 0 DPC highest execution time (µs): 806,078343
CPU 0 DPC total execution time (s): 1,643205
CPU 0 DPC count: 153215

CPU 1 Interrupt cycle time (s): 0,852967
CPU 1 ISR highest execution time (µs): 7,347305
CPU 1 ISR total execution time (s): 0,000077
CPU 1 ISR count: 88
CPU 1 DPC highest execution time (µs): 286,099052
CPU 1 DPC total execution time (s): 0,002402
CPU 1 DPC count: 433

CPU 2 Interrupt cycle time (s): 0,876116
CPU 2 ISR highest execution time (µs): 0,438124
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 1
CPU 2 DPC highest execution time (µs): 221,132984
CPU 2 DPC total execution time (s): 0,014337
CPU 2 DPC count: 2444

CPU 3 Interrupt cycle time (s): 0,841464
CPU 3 ISR highest execution time (µs): 2,521956
CPU 3 ISR total execution time (s): 0,000023
CPU 3 ISR count: 20
CPU 3 DPC highest execution time (µs): 232,941367
CPU 3 DPC total execution time (s): 0,016868
CPU 3 DPC count: 2640

CPU 4 Interrupt cycle time (s): 0,910140
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): 380,768962
CPU 4 DPC total execution time (s): 0,008697
CPU 4 DPC count: 1268

CPU 5 Interrupt cycle time (s): 0,834830
CPU 5 ISR highest execution time (µs): 2,524701
CPU 5 ISR total execution time (s): 0,000006
CPU 5 ISR count: 4
CPU 5 DPC highest execution time (µs): 78,865768
CPU 5 DPC total execution time (s): 0,001280
CPU 5 DPC count: 206

CPU 6 Interrupt cycle time (s): 0,913219
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): 208,284681
CPU 6 DPC total execution time (s): 0,006304
CPU 6 DPC count: 773

CPU 7 Interrupt cycle time (s): 0,843780
CPU 7 ISR highest execution time (µs): 1,538673
CPU 7 ISR total execution time (s): 0,000002
CPU 7 ISR count: 1
CPU 7 DPC highest execution time (µs): 204,294661
CPU 7 DPC total execution time (s): 0,004911
CPU 7 DPC count: 647

4

While your result from Latencymon says your system is OK for audio, the values you’re getting for IPL and DPC are on the high side (780 - 790us).
You ran LM for four minutes… I would let it run for a good 15 to 20 minutes to see what’s really going on. When you do, Windows should just be idling. Don’t run any other apps for the duration.

1 Like
5

Thank you so much for replying. I will do as you suggest and let Latmon run for 20 minutes, with Win idling.

I’ll post back with the new results later.

Best,

Magnus

6

So, here is a 2nd Latmon rept:

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:26:55 (h:mm:ss) on all processors.

SYSTEM INFORMATION

Computer name: DESKTOP-L6IAAMD
OS version: Windows 10, 10.0, version 2009, build: 19045 (x64)
Hardware: System Product Name, Exertis_CapTech
BIOS: BIOS Date: 11/09/15 17:26:10 Ver: 05.0000B
CPU: GenuineIntel Intel(R) Core™ i7-6700K CPU @ 4.00GHz
Logical processors: 8
Processor groups: 1
Processor group size: 8
RAM: 32621 MB total

CPU SPEED

Reported CPU speed (WMI): 4001 MHz
Reported CPU speed (registry): 4008 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): 167,40
Average measured interrupt to process latency (µs): 2,506127

Highest measured interrupt to DPC latency (µs): 165,20
Average measured interrupt to DPC latency (µs): 0,782606

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): 215,326846
Driver with highest ISR routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Highest reported total ISR routine time (%): 0,000078
Driver with highest ISR total time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Total time spent in ISRs (%) 0,000087

ISR count (execution time <250 µs): 2409
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): 684,798653
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 565.90 , NVIDIA Corporation

Highest reported total DPC routine time (%): 0,010325
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 565.90 , NVIDIA Corporation

Total time spent in DPCs (%) 0,016220

DPC count (execution time <250 µs): 529270
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 3
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: winword.exe

Total number of hard pagefaults 450
Hard pagefault count of hardest hit process: 345
Number of processes hit: 23

PER CPU DATA

CPU 0 Interrupt cycle time (s): 10,606974
CPU 0 ISR highest execution time (µs): 215,326846
CPU 0 ISR total execution time (s): 0,011224
CPU 0 ISR count: 2404
CPU 0 DPC highest execution time (µs): 684,798653
CPU 0 DPC total execution time (s): 1,941738
CPU 0 DPC count: 469232

CPU 1 Interrupt cycle time (s): 1,486236
CPU 1 ISR highest execution time (µs): 1,799651
CPU 1 ISR total execution time (s): 0,000005
CPU 1 ISR count: 5
CPU 1 DPC highest execution time (µs): 78,741517
CPU 1 DPC total execution time (s): 0,003343
CPU 1 DPC count: 1141

CPU 2 Interrupt cycle time (s): 1,447694
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): 87,826846
CPU 2 DPC total execution time (s): 0,030068
CPU 2 DPC count: 12637

CPU 3 Interrupt cycle time (s): 1,407730
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): 158,358034
CPU 3 DPC total execution time (s): 0,060248
CPU 3 DPC count: 23511

CPU 4 Interrupt cycle time (s): 1,461234
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): 87,659681
CPU 4 DPC total execution time (s): 0,042141
CPU 4 DPC count: 16649

CPU 5 Interrupt cycle time (s): 1,280965
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): 114,301148
CPU 5 DPC total execution time (s): 0,002035
CPU 5 DPC count: 604

CPU 6 Interrupt cycle time (s): 1,407795
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): 96,880489
CPU 6 DPC total execution time (s): 0,014079
CPU 6 DPC count: 4841

CPU 7 Interrupt cycle time (s): 1,309905
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): 81,722555
CPU 7 DPC total execution time (s): 0,002363
CPU 7 DPC count: 658

7

OK, so I finally uninstalled NAV. Running only Windows Defender, the issue disappeared. So the update to NAV was the culprit.

I have used Norton for some 20 years with no issues, so this is really a big disappointment.

As I also use my daw pc for my business, I need some kind of professional antivirus software over and above Windows Defender. So I am now trying out Eset - which comes highly recommended by daw users and gamers.

So far, my Cubase experience is back to normal again, i.e. the projects that worked without spiking before the NAV update now work as usual again.

I am glad to have identified the problem. A big thank you to Martin and KT66 for pitching in.

Best,

Magnus

8

Hi Magnus,

You beat me to it! Your Latencymon numbers are good so the next thing on my list was Norton, which is probably one of the worst things you can run on a DAW machine.
Glad you got it sorted.

1 Like
9

Yup. I have always been well aware of Norton´s bad reputation on DAWs. But, as I mentioned, I have used it on my DAW pcs for almost 20 years, with no issues. Suddenly Norton decided to remove their Silent Mode, which suspends a bunch of background activities, and that was the straw that broke the camel’s back in my case.

Best, and thanks again,

Magnus

1 Like