VST Performance peaks and spikes

I dont know what to do anymore. I am starting to feel a lot of depression because I cant fix this. I have 9.5 updated cubase version. Everything is licensed. I also have a bought Windows 10 Pro 64 bit (that has been updated to the last file). All of my drivers on my laptop are updated. And still I am getting spikes and peaks in the VST performance meter.

I have a HP Omen lap top with the following specifications:

Operating System
Windows 10 Pro 64-bit

Intel Core i7 7700HQ @ 2.80GHz 47 °C
Kaby Lake 14nm Technology

16.0GB Dual-Channel Unknown @ 1197MHz (17-17-17-39)

HP 8392 (U3E1)

Generic PnP Monitor (1920x1080@60Hz)
AAA (1920x1080@60Hz)
Intel HD Graphics 630 (HP)
4095MB NVIDIA GeForce GTX 1050 (HP) 39 °C
ForceWare version: 431.36
SLI Disabled

119GB SAMSUNG MZVLW128HEGR-000H1 (Unknown (SSD))
931GB Hitachi HGST HTS721010A9E630 (SATA ) 29 °C

Optical Drives
DTSOFT Virtual CdRom Device

ZOOM UAC-2 Audio External audio interface

The peaks are also developing when I am not even playing audio just in the open project.
Even sometimes if I load a Waves 88 piano and play some chords, after a while I will get a peak.

I also did tests with Latencymon and these are the results:


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 or more DPC routines that belong to a driver running in your system appear to be executing for too long. 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:01:07 (h:mm:ss) on all processors.



OS version: Windows 10 , 10.0, build: 17134 (x64)
Hardware: OMEN by HP Laptop 17-an0xx, HP, 8392
CPU: GenuineIntel Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Logical processors: 8
Processor groups: 1
RAM: 16263 MB total



Reported CPU speed: 2808 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.



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): 1074.324982
Average measured interrupt to process latency (µs): 5.662990

Highest measured interrupt to DPC latency (µs): 1014.154031
Average measured interrupt to DPC latency (µs): 1.959643



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): 205.015670
Driver with highest ISR routine execution time: ACPI.sys - ACPI Driver for NT, Microsoft Corporation

Highest reported total ISR routine time (%): 0.023822
Driver with highest ISR total time: ACPI.sys - ACPI Driver for NT, Microsoft Corporation

Total time spent in ISRs (%) 0.045241

ISR count (execution time <250 µs): 130816
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



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): 1262.219017
Driver with highest DPC routine execution time: ACPI.sys - ACPI Driver for NT, Microsoft Corporation

Highest reported total DPC routine time (%): 0.332430
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0.553306

DPC count (execution time <250 µs): 434389
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 753
DPC count (execution time 1000-1999 µs): 1
DPC count (execution time 2000-3999 µs): 0
DPC count (execution time >=4000 µs): 0



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: fontdrvhost.exe

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



CPU 0 Interrupt cycle time (s): 6.845962
CPU 0 ISR highest execution time (µs): 205.015670
CPU 0 ISR total execution time (s): 0.214697
CPU 0 ISR count: 121158
CPU 0 DPC highest execution time (µs): 1262.219017
CPU 0 DPC total execution time (s): 2.551728
CPU 0 DPC count: 406937

CPU 1 Interrupt cycle time (s): 6.346285
CPU 1 ISR highest execution time (µs): 201.680556
CPU 1 ISR total execution time (s): 0.027792
CPU 1 ISR count: 9658
CPU 1 DPC highest execution time (µs): 887.524573
CPU 1 DPC total execution time (s): 0.396623
CPU 1 DPC count: 26349

CPU 2 Interrupt cycle time (s): 3.182848
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): 277.392094
CPU 2 DPC total execution time (s): 0.014780
CPU 2 DPC count: 1400

CPU 3 Interrupt cycle time (s): 4.267959
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): 7.606481
CPU 3 DPC total execution time (s): 0.000058
CPU 3 DPC count: 23

CPU 4 Interrupt cycle time (s): 2.759864
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): 69.299145
CPU 4 DPC total execution time (s): 0.001362
CPU 4 DPC count: 252

CPU 5 Interrupt cycle time (s): 4.128033
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): 70.714744
CPU 5 DPC total execution time (s): 0.000149
CPU 5 DPC count: 16

CPU 6 Interrupt cycle time (s): 2.711974
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): 43.501425
CPU 6 DPC total execution time (s): 0.000667
CPU 6 DPC count: 99

CPU 7 Interrupt cycle time (s): 3.772520
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): 61.011396
CPU 7 DPC total execution time (s): 0.000352
CPU 7 DPC count: 67

This is even happening if i put the sample rate to 1024 or 2048. Still everything is bad…

Not its only happening when i click to record something. It is not happening when i am just playing. And the same moment i press on a channel to record a midi track with omnisphere or anything its getting peaks and crackles. The same moment i deselect the channel everything is back to normal.

Solved: I have cubase 9.5, win10-64, I7-9700k (9th) 16 Gb Ram, Audient ID22, Nvidia GTX750. Used to have same problem with a lot of peaks and drop-outs.
My settings: VST Audio System
32 bit float Processing
actvate MultiProcessing - yes
activate asio-Guard-yes
Asio Guard level - normal
Activate Steinberg Audio Power scheme - yes (very important)
…and that is - no more peaks
hope it works for you guys.

That doesnt work for me. WheneverI record enable it starts and when i turn off record enable it goes away…

This worked for me with Cubase 11 and trying to run some Arturia V Collection 8 VSTi plugins. The key was enabling “Activate Steinberg Audio Power Scheme”. My system is really top notch and there was no reason it should have been struggling. Ableton 10 was running the plugins fine.