Hi everyone,
Only 1 of my 16 logical processors (CPU 0) intermittently reaches nearly 100% utilization for tens of seconds, while overall CPU usage remains low. Cubase’s ASIO-Guard meter spikes during these episodes, and I sometimes hear audio crackles. I’m trying to find out what triggers the CPU 0 saturation.
My setup
- Lenovo ThinkStation P350 Tiny, type 30EF, model 30EF000HFR
- Intel Core i9-11900T with 8 physical cores and 16 logical processors, 64 GB RAM
- NVIDIA T600 and Intel UHD Graphics 750
- Windows 11 Pro 26H2, build 26300.9974
- Windows on the internal SSD (C:), projects normally on an external SSD (D:), and sample libraries on a separate external SSD (G:)
Cubase and audio settings
- Cubase 12 Pro with an RME Babyface connected via USB, using the official ASIO Fireface USB driver.
- ASIO-Guard is normally set to High. I also tested with ASIO-Guard disabled, and the CPU 0 spikes still occurred.
- The spikes also occurred with a 2,048-sample buffer at 44.1 kHz and in a separate test using the Generic Low Latency ASIO Driver.
When the spikes occur
The spikes start appearing as I add more plug-in instances to a project. I’ve reproduced them with different plug-ins and in multiple projects. They can happen while playback is stopped, after the sample libraries have finished loading and Task Manager shows 0% activity on the sample drive.
- Project on the internal SSD. I opened a project from C: instead of the external project drive D:. The same spikes occurred. The sample libraries were still on G:.
- Cubase open with no project loaded. I saw no spikes during a short check on the welcome screen. My usual production projects reproduce the spikes much more reliably than an empty project.
- Cubase closed. The recurring spikes stopped. I saw one isolated spike about 30 seconds after closing Cubase, without checking whether its process had fully exited. I saw no further spikes while Cubase remained closed.
Processor affinity test
I changed the processor affinity of Cubase12.exe in Windows Task Manager to exclude CPU 0 and CPU 1, leaving logical processors 2–15 available to Cubase. With Cubase still open and its threads restricted to CPUs 2–15, CPU 0 still spiked to nearly 100%.
What I measured
During one spike, Task Manager showed approximately 5.5% total CPU usage for System Interrupts, falling to 0.19% afterward. An Adobe process was active during one episode. I didn’t see the same process during the next spike I checked. I also checked Windows Event Viewer and found no event that explained the spikes.
I recorded two .etl traces using Windows Performance Recorder’s GeneralProfile and examined them in Windows Performance Analyzer.
- The first trace started during a spike. It shows roughly 180,000 ISR events attributed to
ACPI.sys!ACPIInterruptServiceRoutinein the first 15 seconds. The dominant sampled call stack includesntoskrnl.exe!HalpAcpiPmRegisterReadandHalpAcpiPmRegisterReadPort. The ACPI activity dropped as the Cubase spike ended. - The second trace, recorded after the BIOS update, shows two sustained bursts dominated by
ACPI.sys, at approximately 0–28 seconds and 69–101 seconds. - LatencyMon also flagged
ACPI.sys,nvlddmkm.sys, andntoskrnl.exe. The source of the sustained ACPI interrupts is still unknown.
Other tests
- I used the Windows High Performance power plan, with minimum and maximum processor states at 100% and PCIe Link State Power Management off.
- I set Cubase to use the NVIDIA T600 in Windows Graphics Settings. The spikes persisted.
- I updated the Lenovo BIOS from M3JKT46A to M3JKT47A through Lenovo Commercial Vantage. The spikes persisted after reboot.
Has anyone seen CPU 0 spike to nearly 100% with Cubase open, even when Cubase’s processor affinity excludes CPU 0? If you found the cause on your system, what was it? I’d also appreciate a targeted, reversible diagnostic step I can run with my usual projects and plug-ins while preserving my Windows installation, licenses, and settings.
Thanks,
Antoine