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

Render those tracks to audio…
Disable the tracks…
problem gone…

— IPDT64 - Revision: 4.1.9.41
— IPDT64 - Start Time: 03/10/2024 21:35:54

CPU1
Genuine Intel CPU Test
Module Version: 1.0.26.64b.W
Start Time: Thu Oct 3 21:35:54 2024
Test Result - PASS
Expected: GenuineIntel
Detected: GenuineIntel
End Time: Thu Oct 3 21:35:54 2024
Total Time: in seconds: 0

CPU1
CPU Brand String Test
Module Version: 1.0.28.64b.W
Start Time: Thu Oct 3 21:35:54 2024
Test Result - PASS
Expected: Intel(R) Core™
Detected: Intel(R) Core™ i9-14900K
Intel(R) Core™ processor detected…!!..
End Time: Thu Oct 3 21:35:54 2024
Total Time: in seconds: 0

CPU1
Cache Test
Module Version: 1.0.24.64b.W
Start Time: Thu Oct 3 21:35:54 2024
Test Result - PASS

— Reading Cache Size —

  • Detected L1 Data Cache Size → 48

  • Detected L1 Inst Cache Size → 32

  • Detected L2 Cache Size → 2048

  • Detected L3 Cache Size → 36864

Cache Size Test Passed!!!

End Time: Thu Oct 3 21:35:54 2024
Total Time: in seconds: 0

CPU1
MMXSSE Test
Module Version: 1.0.30.64b.W
Start Time: Thu Oct 3 21:35:54 2024
Test Result - PASS

DetectUtils64 DLL Version - 1.1.9

— Determining MMX - SSE capabilities —
…MMX is supported on this CPU…
…SSE is supported on this CPU…
…SSE2 is supported on this CPU…
…SSE3 is supported on this CPU…
…SSSE3 is supported on this CPU…
…SSE4.1 is supported on this CPU…
…SSE4.2 is supported on this CPU…

MMX Test Result — PASS
SSE Test Result — PASS
SSE2 Test Result — PASS
SSE3 Test Result — PASS
SSSE3 Test Result — PASS
SSE4.1 Test Result — PASS
SSE4.2 Test Result — PASS

End Time: Thu Oct 3 21:35:54 2024
Total Time: in seconds: 0

CPU1
IMC Test
Module Version: 1.0.26.64b.W
Start Time: Thu Oct 3 21:35:54 2024
Test Result - PASS
— Reading Memory Size —
Detected Memory Size is → 192.00GB
— Subtest - Memory Size Test Passed!!! —
— Integrated Memory Controller Stress Test —
Memory to be allocated = 1048576 bytes
Memory Allocated.
Test 1 Ones and Zeros Moving Inversions write operations - Passed
Test 1 Ones and Zeros Moving Inversions verification operations - Passed
Test 2 32Bits Sliding Ones write operations - Passed
Test 2 32Bits Sliding Ones verification operations - Passed
Test 3 32Bits Sliding Zero write operations - Passed
Test 3 32Bits Sliding Zero verification operations - Passed
Memory Deallocated.
— Subtest - Memory Stress Test Passed!!! —
Integrated Memory Controller Test Passed!!!
End Time: Thu Oct 3 21:35:55 2024
Total Time: in seconds: 1

CPU1
Parallel_PrimeNum Test
Module Version: 1.0.0.13
Start Time: 03/10/2024 21:35:55
Test Result - PASS

Module Math_PrimeNum.exe Completed - Pass

Prime Number Generation Test
Module Version: 1.0.29.64b.W
Start Time: Thu Oct 3 21:35:55 2024
DetectUtils64 DLL Version - 1.1.9
AVX is supported in your OS
Max AVX supported = AVX2
Test Result - PASS
Operation Per Second: 3756852
Error: 0
— Prime Number Generation Test Passed!!!—
End Time: Thu Oct 3 21:36:40 2024
Total Time: in seconds: 45

Parallel_PrimeNum
End Time: 03/10/2024 21:36:40

CPU1
Parallel_FP Test
Module Version: 1.0.0.13
Start Time: 03/10/2024 21:36:40
Test Result - PASS

Module AVX.exe Completed - Pass
Module Math_FP.exe Completed - Pass

AVX Test
Module Version: 2.0.31.64b.W
Start Time: Thu Oct 3 21:36:40 2024
Test Result - PASS

DetectUtils64 DLL Version - 1.1.9

— CPU Features Detection —
…AVX is supported by this CPU…
…AVX2 is supported by this CPU…
…AVX512BW is NOT supported by this CPU…
…AVX512CD is NOT supported by this CPU…
…AVX512DQ is NOT supported by this CPU…
…AVX512ER is NOT supported by this CPU…
…AVX512F is NOT supported by this CPU…
…AVX512IFMA52 is NOT supported by this CPU…
…AVX512PF is NOT supported by this CPU…
…AVX512VBMI is NOT supported by this CPU…
…AVX512VL is NOT supported by this CPU…
…AES is supported by this CPU…
…PCLMULQDQ is supported by this CPU…

…AVX is supported by this Operating System…

Most Advanced AVX Feature Detected… AVX2
AVX2 Test Result — PASS
AES Test Result — PASS
PCLMULQDQ Test Result — PASS

End Time: Thu Oct 3 21:37:25 2024
Total Time: in seconds: 45

Floating Point Test
Module Version: 1.0.28.64b.W
Start Time: Thu Oct 3 21:36:40 2024
DetectUtils64 DLL Version - 1.1.9
AVX is supported in your OS
Max AVX supported = AVX2
FMA3 supported
Test Result - PASS
Million Floating Points per Second, MFLOPS: 6.37
Error: 0
— Floating Point Test Passed!!!—
End Time: Thu Oct 3 21:37:25 2024
Total Time: in seconds: 45

Parallel_FP
End Time: 03/10/2024 21:37:25

CPU1
Parallel_Math Test
Module Version: 1.0.0.13
Start Time: 03/10/2024 21:37:25
Test Result - PASS

Module Math_PrimeNum.exe Completed - Pass
Module FMA3.exe Completed - Pass

Prime Number Generation Test
Module Version: 1.0.29.64b.W
Start Time: Thu Oct 3 21:37:25 2024
DetectUtils64 DLL Version - 1.1.9
AVX is supported in your OS
Max AVX supported = AVX2
Test Result - PASS
Operation Per Second: 3522431
Error: 0
— Prime Number Generation Test Passed!!!—
End Time: Thu Oct 3 21:38:10 2024
Total Time: in seconds: 45

FMA3 Test
Module Version: 1.0.29.64b.W
Start Time: Thu Oct 3 21:37:25 2024
Test Result - PASS

DetectUtils64 DLL Version - 1.1.9

— CPU Features Detection —
…FMA3 is supported by this CPU…
…FMA3 is supported by this Operating System…

FMA3 Test Result — PASS

End Time: Thu Oct 3 21:38:10 2024
Total Time: in seconds: 45

Parallel_Math
End Time: 03/10/2024 21:38:10

CPU1
Parallel_GPUStressW Test
Module Version: 1.0.0.13
Start Time: 03/10/2024 21:38:10
Test Result - PASS

Module Math_PrimeNum.exe Completed - Pass
Module Math_FP.exe Completed - Pass

Prime Number Generation Test
Module Version: 1.0.29.64b.W
Start Time: Thu Oct 3 21:38:10 2024
DetectUtils64 DLL Version - 1.1.9
AVX is supported in your OS
Max AVX supported = AVX2
Test Result - PASS
Operation Per Second: 3443754
Error: 0
— Prime Number Generation Test Passed!!!—
End Time: Thu Oct 3 21:38:40 2024
Total Time: in seconds: 30

Floating Point Test
Module Version: 1.0.28.64b.W
Start Time: Thu Oct 3 21:38:10 2024
DetectUtils64 DLL Version - 1.1.9
AVX is supported in your OS
Max AVX supported = AVX2
FMA3 supported
Test Result - PASS
Million Floating Points per Second, MFLOPS: 45.89
Error: 0
— Floating Point Test Passed!!!—
End Time: Thu Oct 3 21:38:40 2024
Total Time: in seconds: 30

Parallel_GPUStressW
End Time: 03/10/2024 21:38:40

CPU1
DGEMM Stress Test
Module Version: 1.0.17.64b.W
Start Time: Thu Oct 3 21:38:40 2024
Test Result - PASS

DetectUtils64 DLL Version - 1.1.9

— CPU Features Detection —
…AVX is supported by this Operating System…

Most Advanced AVX Feature Detected… AVX2
DGEMM AVX2 Test Result — PASS

End Time: Thu Oct 3 21:39:40 2024
Total Time: in seconds: 60

CPU1
Frequency Check
Module Version: 1.0.7.64b.W
Start Time: Thu Oct 3 21:39:40 2024
Test Result - NO COMPARE OPTION USED
Processor Name: Intel(R) Core™ i9-14900K
Measured Processor Frequency: 3.186680
End Time: Thu Oct 3 21:39:41 2024
Total Time: in seconds: 1

System Information

Processor Name: Intel(R) Core™ i9-14900K
Processor Information: Family 6 Model B7 Stepping 1
Number of Physical Cores: 24
Number of Logical Cores: 32
Operating System: Microsoft Windows 11 Professionnel 64 bits
Graphics Information: NVIDIA GeForce GT 730

— IPDT64 - End Time: 03/10/2024 21:39:41
— IPDT64 - Result: Pass

Yeah, you’ve got a tough situation. You seem to have passed the Latency and Intel Diagnostics… I feel for you.

If I were in your shoes, I’d be frustrated too. But I’ve been in your shoes before and this is what I’ve done:

1 - Update the firmware, reset the BIOS to default settings, don’t overclock.

2 - Do all the diagnostic tests again. I’d also stress test it under Prime, do a full memtest, etc… but be CAREFUL with this because you need to make sure you have the mitigations in place with 14th gen CPUs to cap the voltage issues (I do NOT use 13th/14th gen)… again, make sure you have the latest BIOS that has the Intel patches for your CPU, so I’d be very very careful with the Prime stress test on 14th gen until you carefully confirm the BIOS and voltage issues.

3 - Make sure to install the studio driver for nVidia, not the gaming driver

4 - Disable all unnecessary devices in the BIOS, starting with wireless.

5 - If the above doesn’t work, I try a different graphics card (BTW I currently use AMD for DAWs, I only use nVidia for DaVinci Resolve – historically I’ve had too many problems with nVidia with my DAWs, and I’ve had much better luck with AMD)

6 - Do a complete fresh reinstallation of Windows and start a slow methodical process of installing only what is necessary, one by one, and testing each step of the way in case you notice a culprit.

7 - If all of that fails above, then I’d honestly throw my hands up and build another machine. Or at least maybe try downgrading to 12900K. I’m not kidding. It sucks. I know it’s illogical. But life has to go on, and I’ve had to ditch a build if I couldn’t get it working before. I’ve just converted it into a video machine, server, or gaming machine, and started over with a fresh DAW build. I know this might sound insane to you, but if you’ve done all the above and still can’t get it to work, I’ve done this myself and finally been able to get back to work.

BTW In my studio I run Macs, Windows machines, and Linux machines, running CPUs all over the map, Apple Silicon for Macs of course, and Linux and Windows are running on everything from older Intel 9900K up to the latest AMD Ryzen 9 9950x CPU, and many different CPUs in between. I do NOT like MacOS or Windows, and I far prefer Linux, but in this world I’ve conceded that I have to keep Mac and Windows around to run the best software and plugins… for now at least.

I have NOT tested Cubase on an Intel 14th gen machine, since I purposely avoided 13th and 14th gen due to the voltage issue (that is apparently now solved by Intel YMMV)… BUT I have tested Cubase on a 12th gen 12900K and it works great, and I have NONE of the issues you talk about.

The only issues I currently have with ANY DAW right now on many different machines, are iLok issues with Ryzen 9950x (Zen 5), which will hopefully be fully resolved with an upcoming BIOS/AGESA update soon. But overall, Cubase currently performs well on ALL of these platforms in my experience. But I am meticulous in my building process and only install what is necessary, and I keep each DAW exclusively dedicated to DAW work, and nothing else.

One difference I do see is that all my Win/Linux DAWs are exclusively running AMD graphics cards. No nVidia except for a machine dedicated to Davinci Resolve. I know some people are doing fine with nVidia and Cubase, but I just had too many weird little issues from time to time over the years. So I gave up on nVidia for DAW stuff. So I can’t help you with getting nVidia to work since I won’t even touch them for DAWs these days. As for AMD cards, I prefer to keep my DAWs very simple, and I stick with conservative, older AMD Radeon Pro graphics cards, which are incredibly stable and reliable. Even a basic old AMD RX550-class card, as simple as it is, will work well with Cubase. I have found that even those old GCN 4.0 generation AMD cards to be quite compatible and stable with just about anything… and plus, they work great on Linux. :slight_smile: Sometimes the old stuff gives the least headaches.

Wish I could help more. But something is indeed off base in your system and I feel your frustration. But don’t give up. Cubase does run very well for me across many different systems. I do think you’ll solve it. Just continue to be patient and scientific in how you solve the situatoin. Sadly, it shouldn’t be so hard to get things working. But sometimes it is.

5 Likes

Hello mroekalea,

There’s settings in the bios probably to configure if you haven’t tweeked.
FN+F2
Ideally Upload a picture of the bios settings to see if I can assist you

Oliver

1 Like

Thanks so much for taking the time. I am investigating my small nvidia gt 730. I didn’t know about the studio drivers. There’s only this driver on nvidia website ! Any idea ?

In our commercial studio we’re running Cubase, Nuendo and Pro Tools on 13th and 14th gen machines. All of them perform really well. The only BIOS config changes are undervolting (wrt the Intel voltage issue) and XMP enabled. That’s it.
My home studio runs on an i9 13900K and an i7 14700K with the same settings as the machines in the main studio. Good performance on both.
Windows 11 on all of them with power set to Ultimate and core parking turned off. All machines are using internal Intel graphics.
I’m at a loss to explain why some folks are having such difficulties with these processors (other than the ones that are actually failing, of course).

2 Likes

Apologies, I completely missed that you are using the NVIDIA GeForce GT 730… FYI the GT 730 has less than 1/2 the capability (maybe 1/3) of your integrated internal intel graphics on your 14th gen machine, depending on the benchmark… so I would not use the GT 730 in your situation. In fact, that might be your problem right there. I thought you were using a more recent nVidia card! The internal (iGPU) will be a better choice IMO. I don’t know how I missed that in your posts. It’s an extremely underpowered card (by today’s standards), and not a good match for your 14th gen CPU. If you are going to use a GPU, at least get one that is more powerful than the iGPU you already have built in.

As for nVidia drivers for more recent cards, there is a studio version that is optimized for “creators.” – “NVIDIA Studio Drivers provide artists, creators, and 3D developers the best performance and reliability when working with creative applications. To achieve the highest level of reliability, Studio Drivers undergo extensive testing against multi-app creator workflows and multiple revisions of the top creative applications from Adobe to Autodesk and beyond.”

However, again, I don’t even bother with nVidia in recent years (except for Dacinci Resolve and maybe gaming), and I stick with AMD Radeon Pro cards for all my DAWs.

In the case of the 12, 13, 14 gen Intel CPUs, many of them, including the i9-14900K, have the Intel UHD Graphics 770 iGPU built in. Try that first. If you need more power, then consider buying an AMD GPU. (BTW, some Intel CPUs, such as the i9-14900F model have NO iGPU. And some of the mobile ones will come with Intel Iris Xe, etc…) For those checking out this thread, just look up your CPU to see what iGPU you already have. In the case of bensmir.hbs, it’s a i9-14900K with an Intel UHD Graphics 770 iGPU.

Hope that helps a little. So just pull that GT 730 out of your machine and retire it.

Best of luck. I think you’re getting closer.

@KT66 Hey, what GPU are you using inside your 14th system ?

@uarte Thanks, I never tought that the gpu was important when doing audio.
I am using 3 monitors, that’s why I use the nvidia gt 730, Can I just unplug all the screens and plug my main monitor to the display port of the mother board or do I have to physically unplug the gpu to test ?

In a lot of cases, it isn’t important… until it is. And then you’ll get dropouts or other issues. Which is what you have been experiencing. If you’re running an ancient GT 730 with three monitors on a 14900K system running complex plugins that use the graphics card for rendering the GUI (for example via OpenGL) then yes, it matters. Many of those modern real-time neato visualizations of plugins and DAWs these days actually use a small amount of GPU power to render the GUI. Some developers even release non-GPU versions of their plugins with reduced visualization framerates exactly for your situation. But some don’t… and I think you need to consider that new plugins going forward will have nicer and nicer GUIs, and thus rely more on some GPU features.

In fact, going beyond all this, some apps can actually utilize GPU resources for AI stem separation acceleration, such as the latest version of SpectraLayers… so it’s in your best interest to consider it for the future.

Then buy a new graphics card that can run all three! Get rid of that GT 730, and put ONE more recent graphics card in there connected to all three monitors.

Now I’m not 100% certain that this will solve all your problems… at this point I’d still suggest you run down my list of suggestions, i.e. do a BIOS update, default settings at first, fresh install of Windows, etc… and use a recent-ish graphics card (I’m recommending you get AMD) and connect all three monitors to the graphics card, then your life will probably be better. At least you will have eliminated one huge potential issue.

Not trying to speak for him, but in his earlier response, he said:

Which means he’s using the Intel UHD Graphics 770 iGPU built in to his CPUs.

Correct!

Prior to converting to internal graphics, we were using Radeon 6500 / 6600 series cards. They didn’t give us any problem either.

1 Like

Hello uarte,

On my windows 10 builds I have Nvidia graphics. (3 systems)
7900x Rtx4070 Ti Super , 7900x Rtx 4070 Super and 5900x Rtx3060.
I have no issues at all.
On the same thread I posted a Video that I recorded in OBS demonstrating the 7900x running a project.

Oliver

Settings


1 Like

@bensmir.hbs

If you’re going to try internal graphics as a test, I strongly suggest pulling your GT730 card out of the machine before you do. Make things as uncomplicated as you can when testing.

2 Likes

agreed 100%

I unpluged the nvidia card and I am now testing with the integrated graphics, will report back.

any recommendation for a modern fanless gpu that can support 3 monitors ?

1 Like

can someone help me understand the cubase audio meter.

So I did a test, I deleted every track from my big template but 5 tracks with data. If I set my rme babyface at 128 samples, I get this meter. It’s constantly peaking at 50% already, why ?
If I improvise a line, the peak get to 70% 80%, and sometimes cpu overload message if I play very fast, sometimes, not always.
Does this look normal to you ?

I know buffer size should be kept around 256/512 minimum, but I am trying to overload things with a small number of track for the sake of troubleshooting fast.

Not much out there that is modern, fanless and half decent these days, however, if you buy an AMD Radeon RX 6600 or RX 7600, for example, with a decent cooling system on it, they are fairly quiet, and some are designed to be silent on idle or even very light usage, as the fans don’t spin up unless under load. General DAW operation won’t be too loud above your existing case/CPU fan noise. A good example of that design is the Asrock Radeon RX 6600 Challenger with 0dB Silent Cooling:

If you want to go with an older AMD card, bottom of the line RX 550 still works fine in my testing, and you can find relatively quiet ones.

You can also pick up low profile and regular-sized older Radeon Pro cards that are pretty quiet. I have a few of those in machines. Those my personal favorites, the most stable IMO.

If you want to stick with nVidia (which I’m not a fan of for DAWs, but other people are happy with them), you can also find similar “0dB” cards like the ASUS RTX 3060 V2 with Axial-tech Fan Design, 0dB Technology. And here’s a 4070 with that kind of cooling system:

Good luck!

1 Like

Thanks

Hey, new test with 256 samples, no playback, just improvising a solo oboe line with nucleus, and it frequently peaks at 100% producing a red overload in the meter and an audible little click

The reason we had to abandon our old fanless graphic cards was because Windows 11 wouldn’t support them (too old).
As I mentioned above, we switched to Radeon 6500 / 6600 cards for a while. They were pretty quiet and the fans only activated when required, which for us seemed to be pretty much never.

1 Like

I see @KT66

I think I am going to unplug the babyface and plug back the focusrite, it’s the one thing I didn’t tried