I am so done. cpu overload with 6 tracks ...i9 14900k

Cubase
1

Hello, I am so exhausted of troubleshooting this. I should have a monster computer (i9 14900k, core parking disabled, steinberg audio power scheme ON, windows defender off, 192 gb ddr5 RAM), RME babyface

I just can’t understand that I got cpu overload pop-up with 6 tracks … 4 truepiano vsts and 2 refx nexus 4…

Buffer size is 96 samples
So yes it’s fixed if I go up to 512 samples but then again dropouts occur with way too few tracks, while cpu usage in task manager is below 10%

Issue cannot be replicated all the time. I just can’t wait to ditch windows and buy myself a mac

1 Like
2

I don’t know if it’s okay to do this, but if you can contact me directly (not sure how to do that), I have lots of notes on these types of problems and I’m sure I can help you. It’s way too complicated to be typing questions & answers.

3

The 13900 and 14900 are well known to be problematic. The chips are generally not up to scratch. Intel corner-cutting? Who knows.

EG

and

4 Likes
4

I feel for you. I had same issues with an i7 12700K/6TB nVME/64GB. After trying everything that you list, uselessly - and things did improve once MS worked out big/little management - I eventually gave up and bought refurb Mac Studio M1 Max/1TB/4TB sample drive on TB/64GB and extra TB to USB and video. It’s a mess with stuff plugged in everywhere to get just enough I/O. BUT it’s much much better than my PC - still far from perfect. I need to use a huge disk buffer for really good results. This after using Cubase since Pro 24 on Atari, and building my own PCs for 40 years! 150 track project still causes some issues but it won’t even open on the PC. Never thought I’d move to Mac although I taught it. Still would have preferred not to, because all systems drive one mad with their idiosyncratic idiocies. But at least I can work.

1 Like
5

I think you need to look at the whole system.
Some motherboards aren’t that good.
I always use gaming boards.
When running Cubase do you have the internet on or off ?

1 Like
6

Make sure to check your DPC latency. This is a common problem, it could be some component or driver in your system is misbehaving. Start here:

7

I have hade the same for my 13700k and after month of troubleshooting and new bios have coming out and tryed different ways to install with some tweeking here and there. And other stuff, its going good now, 13900 14900k its little harder. But from throttling over 100c its now on 85c on tests. And on working heat around 45-70. After all that and dpc latency are happy with other things i put in like process lasso on PRO balance then then its snappy fast and super stabile.
z890 and intel 200 is out soon and i will se if i go over typ that plattform, and have this as a gaming rigg or a nas or somthing.

8

IMO< If you aren’t ready to tweak your rigs then you may wanna rethink your DAW/Studio strategy.

There is no magic rig and if you really think going to the genius bar is the answer then maybe apple intelligence is the route you should go but before you do, search the forum on some other super dooper Powermacs with thunderdolts and all the power cern can muster and see if they have any issues… then, VCD :vulcan_salute:t5: :alien:

9

Hello

In late 2022 I purchased a i9 13900 thinking that it would outperform back then an Amd 5950x setup I had.
The amd system was running smoothly. I was thinking back then with all the hype if I get an i9 I won’t have to think about performance issues

The next day I went back to the computer place and returned all the components.
After several hours of tweeking the bios and windows 10 I had finally passed LatencyMon.
But the i9 was still no where near the performance of the 5950x.
I still have my 5950x build and eventually I moved to the Zen 4. AM5
What can I say !? Amd 7900x with a B650E Asrock Taichi 24 power phase runs like butter on windows 10
Babyface pro fs or the Steinberg UR24C they both run flawlessly on 128 buffer size , Asio Guard on low only as precaution.
For example:
One of the projects I was working on, had around 90 tracks. 40plus Plugins that are enabled and 2 soft synth. Performance meter is around 20%
On the UR24C when I’m exporting in Realtime, I disable the Asio Guard and I lower the buffer size to 96.
The realtime export will go on for 3 minutes and no Cpu Overload message. I’m serious and jokes aside :)) .
The same project with the 5950x , when exporting in realtime, a cpu overload message will show up.

Also I forgot to mention that processing precision is on 64bit float.

Ps : I’m mentioning what I’ve experienced with the 13900. I wasn’t expecting to have issues right out of the box. I’m pretty sure with the right settings and some patience the i9 runs smoothly.
But I knew on the other hand, AMD by disabling C1 state and the power setting on “typical current” was go to go.
Just seemed more praticals and less headaches.
But that’s just me. I have no brand preferences.

Oliver

10

Hi all,
I have a I9 13900k, bios standard settings, no tweaking. Windows 10 standard settings. Cubase 13 pro, factory settings. I run projects with 200+ tracks and never had a problem. No cpu overload, no latency problems, everything running smooth. Am I the lucky guy? I wonder what causes all the problems. Is it the hardware combination or factory software problems? No idea!

11

Hello Twan,
Please take 5 minutes of your time and Record a short Video in OBS if possible.
That would certainly be refreshing to see.
Mention your exact build as well.
Thank you so much.
I can create one as well on demand.
:pray:
Oliver

12

Hello Everyone,

Here’s a Quick OBS Video I just made showing one of my systems.
Running Cubase 12.0.70 with the Amd 7900x CPU

13

Hi Oliz,

Mainboard Gigabyte Z790 Aero G rev 1.0, bios update 12F.
Processor Intel I9-13900K.
Memory TeamGroup DDR5 96gb, running at 6000MHZ.
M2 Kingston Fury Renegade, read 7300mb sec, write 7000mb sec,
3 x 2TB and 1 x 4TB.
Videocard Asrock RX 6600 XT challenger 8gb oc.

14

Just watched this video. When you say standard settings are you referring to using the updated BIOS to counter the issue with CPU’s being pushed beyond their limits? It appears a lot of the issues with all sorts of app use may be attributed to it. Some of the numbers in this vid https://www.youtube.com/watch?v=B3EW5lRIZYc are CRAZY. Looks like both Intel and the board manufacturers were at fault. A lot of CPUs have liklely been permentantly damaged and only a replacement and using the new BIOS default settings can ‘potentially’ lead to a stable system.

15

Discussed extensively over here:

1 Like
16

While there clearly is a problem with the Intel 13th and 14th gen chips, it shouldn’t be considered the go to when somebody has a performance problem with one of these units.
If a user is ‘only’ getting poor performance out of their rig, the cause is much more likely to be a configuration issue or hardware mismatch of some kind. If there’s no actual failure then the chip is probably OK.
OTOH, If a user’s 13th or 14th gen machine is posting spurious errors on a regular basis, apps are crashing, or the machine is repeatedly crashing on blue screens and so on, then there’s a good possibility the chip has failed due to overvolt.

2 Likes
17

I have run latencymoon, anyone can help me read the report ?

image
image1861×705 81.2 KB

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

SYSTEM INFORMATION

Computer name: DESKTOP-96PLDCO
OS version: Windows 11, 10.0, version 2009, build: 22631 (x64)
Hardware: Z790 AORUS MASTER, Gigabyte Technology Co., Ltd.
BIOS: F14f
CPU: GenuineIntel Intel(R) Core™ i9-14900K
Logical processors: 32
Processor groups: 1
Processor group size: 32
RAM: 196368 MB total

CPU SPEED

Reported CPU speed (WMI): 320 MHz
Reported CPU speed (registry): 3187 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): 280,90
Average measured interrupt to process latency (µs): 9,959592

Highest measured interrupt to DPC latency (µs): 273,20
Average measured interrupt to DPC latency (µs): 2,250625

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): 61,294634
Driver with highest ISR routine execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation

Highest reported total ISR routine time (%): 0,000148
Driver with highest ISR total time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation

Total time spent in ISRs (%) 0,000203

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

Highest reported total DPC routine time (%): 0,002181
Driver with highest DPC total execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation

Total time spent in DPCs (%) 0,006072

DPC count (execution time <250 µs): 192903
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 16
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: obs64.exe

Total number of hard pagefaults 14
Hard pagefault count of hardest hit process: 12
Number of processes hit: 2

PER CPU DATA

CPU 0 Interrupt cycle time (s): 9,570628
CPU 0 ISR highest execution time (µs): 61,294634
CPU 0 ISR total execution time (s): 0,018421
CPU 0 ISR count: 47005
CPU 0 DPC highest execution time (µs): 147,804518
CPU 0 DPC total execution time (s): 0,537587
CPU 0 DPC count: 149016

CPU 1 Interrupt cycle time (s): 9,928458
CPU 1 ISR highest execution time (µs): 37,508315
CPU 1 ISR total execution time (s): 0,008645
CPU 1 ISR count: 430
CPU 1 DPC highest execution time (µs): 481,459994
CPU 1 DPC total execution time (s): 0,216321
CPU 1 DPC count: 28183

CPU 2 Interrupt cycle time (s): 7,339131
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): 98,601192
CPU 2 DPC total execution time (s): 0,001332
CPU 2 DPC count: 106

CPU 3 Interrupt cycle time (s): 6,841827
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): 59,914340
CPU 3 DPC total execution time (s): 0,000080
CPU 3 DPC count: 4

CPU 4 Interrupt cycle time (s): 6,746647
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): 139,127079
CPU 4 DPC total execution time (s): 0,001011
CPU 4 DPC count: 31

CPU 5 Interrupt cycle time (s): 6,537953
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): 25,440540
CPU 5 DPC total execution time (s): 0,000202
CPU 5 DPC count: 30

CPU 6 Interrupt cycle time (s): 6,94450
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,329777
CPU 6 DPC total execution time (s): 0,000156
CPU 6 DPC count: 20

CPU 7 Interrupt cycle time (s): 6,787784
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): 6,927705
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): 213,882334
CPU 8 DPC total execution time (s): 0,062928
CPU 8 DPC count: 4764

CPU 9 Interrupt cycle time (s): 7,787294
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): 125,242234
CPU 9 DPC total execution time (s): 0,016997
CPU 9 DPC count: 1250

CPU 10 Interrupt cycle time (s): 7,572771
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): 187,451208
CPU 10 DPC total execution time (s): 0,069994
CPU 10 DPC count: 4954

CPU 11 Interrupt cycle time (s): 7,493106
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): 138,340132
CPU 11 DPC total execution time (s): 0,016679
CPU 11 DPC count: 1512

CPU 12 Interrupt cycle time (s): 6,473686
CPU 12 ISR highest execution time (µs): 0,0
CPU 12 ISR total execution time (s): 0,0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 130,536555
CPU 12 DPC total execution time (s): 0,002725
CPU 12 DPC count: 324

CPU 13 Interrupt cycle time (s): 6,689692
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): 63,641356
CPU 13 DPC total execution time (s): 0,000902
CPU 13 DPC count: 32

CPU 14 Interrupt cycle time (s): 7,306237
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): 179,252589
CPU 14 DPC total execution time (s): 0,000905
CPU 14 DPC count: 53

CPU 15 Interrupt cycle time (s): 6,530288
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): 19,428302
CPU 15 DPC total execution time (s): 0,000096
CPU 15 DPC count: 8

CPU 16 Interrupt cycle time (s): 5,220164
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): 131,668026
CPU 16 DPC total execution time (s): 0,001216
CPU 16 DPC count: 66

CPU 17 Interrupt cycle time (s): 7,030268
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): 138,462818
CPU 17 DPC total execution time (s): 0,000346
CPU 17 DPC count: 15

CPU 18 Interrupt cycle time (s): 5,178224
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): 132,099467
CPU 18 DPC total execution time (s): 0,005542
CPU 18 DPC count: 307

CPU 19 Interrupt cycle time (s): 5,443358
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): 22,013179
CPU 19 DPC total execution time (s): 0,000054
CPU 19 DPC count: 4

CPU 20 Interrupt cycle time (s): 6,357993
CPU 20 ISR highest execution time (µs): 0,0
CPU 20 ISR total execution time (s): 0,0
CPU 20 ISR count: 0
CPU 20 DPC highest execution time (µs): 71,455601
CPU 20 DPC total execution time (s): 0,000395
CPU 20 DPC count: 35

CPU 21 Interrupt cycle time (s): 6,369361
CPU 21 ISR highest execution time (µs): 0,0
CPU 21 ISR total execution time (s): 0,0
CPU 21 ISR count: 0
CPU 21 DPC highest execution time (µs): 26,620019
CPU 21 DPC total execution time (s): 0,000274
CPU 21 DPC count: 23

CPU 22 Interrupt cycle time (s): 5,760485
CPU 22 ISR highest execution time (µs): 0,0
CPU 22 ISR total execution time (s): 0,0
CPU 22 ISR count: 0
CPU 22 DPC highest execution time (µs): 54,670537
CPU 22 DPC total execution time (s): 0,000346
CPU 22 DPC count: 27

CPU 23 Interrupt cycle time (s): 5,515393
CPU 23 ISR highest execution time (µs): 0,0
CPU 23 ISR total execution time (s): 0,0
CPU 23 ISR count: 0
CPU 23 DPC highest execution time (µs): 19,156574
CPU 23 DPC total execution time (s): 0,00010
CPU 23 DPC count: 10

CPU 24 Interrupt cycle time (s): 6,035299
CPU 24 ISR highest execution time (µs): 0,0
CPU 24 ISR total execution time (s): 0,0
CPU 24 ISR count: 0
CPU 24 DPC highest execution time (µs): 39,851271
CPU 24 DPC total execution time (s): 0,000096
CPU 24 DPC count: 7

CPU 25 Interrupt cycle time (s): 6,224146
CPU 25 ISR highest execution time (µs): 0,0
CPU 25 ISR total execution time (s): 0,0
CPU 25 ISR count: 0
CPU 25 DPC highest execution time (µs): 2,724506
CPU 25 DPC total execution time (s): 0,000003
CPU 25 DPC count: 1

CPU 26 Interrupt cycle time (s): 5,629881
CPU 26 ISR highest execution time (µs): 0,0
CPU 26 ISR total execution time (s): 0,0
CPU 26 ISR count: 0
CPU 26 DPC highest execution time (µs): 26,133354
CPU 26 DPC total execution time (s): 0,000057
CPU 26 DPC count: 3

CPU 27 Interrupt cycle time (s): 5,100244
CPU 27 ISR highest execution time (µs): 0,0
CPU 27 ISR total execution time (s): 0,0
CPU 27 ISR count: 0
CPU 27 DPC highest execution time (µs): 48,53530
CPU 27 DPC total execution time (s): 0,000148
CPU 27 DPC count: 12

CPU 28 Interrupt cycle time (s): 7,37590
CPU 28 ISR highest execution time (µs): 31,026985
CPU 28 ISR total execution time (s): 0,005104
CPU 28 ISR count: 10730
CPU 28 DPC highest execution time (µs): 167,964230
CPU 28 DPC total execution time (s): 0,015027
CPU 28 DPC count: 1142

CPU 29 Interrupt cycle time (s): 6,580612
CPU 29 ISR highest execution time (µs): 0,0
CPU 29 ISR total execution time (s): 0,0
CPU 29 ISR count: 0
CPU 29 DPC highest execution time (µs): 213,81550
CPU 29 DPC total execution time (s): 0,009495
CPU 29 DPC count: 820

CPU 30 Interrupt cycle time (s): 5,501308
CPU 30 ISR highest execution time (µs): 0,0
CPU 30 ISR total execution time (s): 0,0
CPU 30 ISR count: 0
CPU 30 DPC highest execution time (µs): 140,968623
CPU 30 DPC total execution time (s): 0,002442
CPU 30 DPC count: 118

CPU 31 Interrupt cycle time (s): 5,319180
CPU 31 ISR highest execution time (µs): 0,0
CPU 31 ISR total execution time (s): 0,0
CPU 31 ISR count: 0
CPU 31 DPC highest execution time (µs): 87,694697
CPU 31 DPC total execution time (s): 0,000613
CPU 31 DPC count: 42

I am getting hanging note when using patchwork from bluecat because there’s a small audio dropout when using this vst, which triggers the hanging note

18

Those Latencymon numbers are OK. I would suggest running LM for a bit longer, say 20 minutes to half an hour.

19

Here a Lenovo legion 5i witj i9 14900HX, not usable even with 1 track, dropiuts and cpu spikes. Implemented the 14 enigine work-a-round but no solution yet. For the time being using old computer.

Pfff what a disaster.

20

For those with a potentially impacted CPU, it’s worth running the Intel Processor Diagnostic Tool to see if you already have a damaged 13- or 14-series CPU. Note it does not affect all 13- and 14-gen CPUs.

Here’s one link to get the tool:

A little more info:

https://www.cpu-monkey.com/en/article/how_to_check_if_your_intel_13_14_gen_cpu_is_affected_by_instability_problems

1 Like