Cubase10 High CPU consumption in windows10 (more than double of what the CPU Meter shows in win7!)

[Axis1~SL61]

Also, crazy 100% CPU peaks very frequent, even without pressing the ''play'' button! I have ASIO Guard at maximum level and (as someone advised in the Steinberg forum) 64 bit float enabled, instead of the default 32 bit float, but my laptop BIOS doesn't have an option to disable virtual cores. It's a Toshiba Tecra , i7 CPU , 2.9GHz, from 2012. It has served me very well for MIDI/audio synchronized with video... until Cubase10, that is... At first, I thought the problem was related to CPU overheating, as it's very hot here where I live (Portugal, 40ºC outside these last days and I don't have air conditioning ) but now I'm not so sure anymore that the problem is due to this... I went back (once again) to win7 and the CPU temperature was as high as in win10 (80ºC!!!!), yet Cubase worked without crazy CPU peaks of 100%!...I can't find the possible culprits anymore... it's completely unpredictable! it's probably due to more than one factor, and even when not jumping and peaking up to 100% the CPU meter always shows more than 2 times higher in win10 than in win7 with the exact same project. The only difference is that I have Cubase 10.0.30 in windows7 and Cubase 10.0.50 (and 10.0.60 before going back to .0.50) in win10. I can't find my 10.0.30 so that I can try it in win10, and couldn't find it any longer on the Steinberg site. Can anyone give me a link to version 10.0.30?... maybe on the Steinberg ftp?... HEEELP... ...and Thanks in advance.

[askoan]

Sorry if this is obvious, but as you don't mention this : didn't you forget to set your power profile at full speed cpu (default mode is power saving, even on outlet). Power saving mode produces these things in low latency audio.
Note that i also had these cpu pikes when demoing Audiaire Zenith VST midi tool in both Cubase 10.0.60 and Bitwig. Can't it be due to one precise VST ?

[oneway]

I’d double check the power profile and the High Performance settings same as they recommend on Steinberg’s site. I believe they’re in a different place in W10, not to mention those settings frequently will get reset with Windows updates. I think I’ve seen four or five threads on KVR alone where people said Cubase was all of a sudden going nuts with CPU and each time those settings being at their defaults were to blame.

[SJ_Digriz]

And for the 1 millionth time the performance meter is not a cpu meter.

[Axis1~SL61]

thanks for the replies -- I always have the power profile at High Performance settings -- my own (but I've not checked if it's been altered by the latest windows update, I'll take a look, thanks for the tip) or by activating the "Steinberg Power Plan" inside cubase10 itself. As for the plugins, as I said, the cubase performance meter in win10 shows more than double the CPU usage that it shows in win7 with the same project with ANY plugin or combinations of plugins. I'm going to activate the "Steinberg Power Plan" inside cubase10 again, because that will override (I suppose) any changes made by the last win10 updates (I was using my own High Performance plan). I will report on the results later. Thanks again

[tonymax]

i had this problem, couldnt use cubase at all. my pc is 'general purpose' so used for all things. I found it was my backup processes (backblaze, dropbox, onedrive etc.) pausing them dropped the cpu to reasonable levels.
Do you have any background processes running that you could pause or switch off?

[auron]

I'm going to activate the "Steinberg Power Plan" inside cubase10 again, because that will override (I suppose) any changes made by the last win10 updates (I was using my own High Performance plan). I will report on the results later. Thanks again

Activating that Steinberg power plan is a BAD idea, because it does core parking.

I remember one thread that someone used a very low latency (like 32 samples etc.) and his antivirus was working like hell and he wondererd why there are performance spikes in an empty project, that doesnt work quite good . so check if antivirus is active and avoid anything like microsoft index service . another thing could be that you use the control room and forgot that there can be a plugin active, maximizer plugins tend to rise your performance meter a lot. The next thing you could check , are there any vst3 plugins active? If so try to use vst2 temporarily. One last thing you could look in your windows autostart settings if there is a new service running that is working in the background. I had a service running that is checking for the latest graphics drivers and those files can be quite big.

[fese]

Definitely check antivirus. When I got my new system, I forgot to put the cubase process on the ignore list of the Microsoft antivirus and performance was really bad.

Did you check the cpu usage for cubase in the windows task manager when comparing win7 and 10? If that is roughly the same for the same project, problem is very likely outside of cubase.

[Milkman]

I think I might have commented to you on the steinberg forums, as well. Your comments about the temps (80c on win10 and then win7) and whatnot sound like a comment I replied to the other day.

If you are the same person, did you try disabling all your PC's virtual cores (hyperthreading) in your BIOS? Cubase has a known issue with virtual cores on some hardware platforms on win and mac, and the solution for some is to disable hyperthreading. My own issues, very much like you talk about above, went away 100% once I did this. They talk about this a lot on the steinberg forums now.

[Axis1~SL61]

I think I might have commented to you on the steinberg forums, as well. Your comments about the temps (80c on win10 and then win7) and whatnot sound like a comment I replied to the other day.

If you are the same person, did you try disabling all your PC's virtual cores (hyperthreading) in your BIOS? Cubase has a known issue with virtual cores on some hardware platforms on win and mac, and the solution for some is to disable hyperthreading. My own issues, very much like you talk about above, went away 100% once I did this. They talk about this a lot on the steinberg forums now.

Hi!..., yes, it was me as "Glease581g" on the Steinberg/cubase10 forum -- I'm so desperate about this problem that I decided to ask here too...
My Laptop BIOS doesn't have the option to disable hyperthreading, and anyway, Cubase10
continues to have much better performance on Windows7 than on win10 -- I wouldn't be so worried about this if I hadn't read on the Steinberg forums that from cubase11 onwards they will stop supporting win7...

[audiot]

Windows 7 is not supported by Steinberg anymore. Dont know which minor version of C10 you are using, but that could cause troubles. If you have an nvidia card, replace it by an ATI or your onboard graphics. My cubase is rock solid, since i switched to ATI (no joke ... you'll find informations about it). As the others said, exclude it from your virus scanner and deactivate the steinberg power profile. Good luck!

[Axis1~SL61]

Windows 7 is not supported by Steinberg anymore. Dont know which minor version of C10 you are using, but that could cause troubles. If you have an nvidia card, replace it by an ATI or your onboard graphics. My cubase is rock solid, since i switched to ATI (no joke ... you'll find informations about it). As the others said, exclude it from your virus scanner and deactivate the steinberg power profile. Good luck!

I have Cubase Artist 10.0.30 in win7 and Cubase Artist 10.0.60 in win10. I can't change graphics card, it's a Toshiba Tecra i7 laptop, I'm using the original internal graphics it came with. As I said before, my Cubase 10 works OK in Windows7, but NOT ok on win10, in the very SAME laptop (dual boot). The only difference is I have Cubase 10.0.30 in win7 and 10.0.60 in win10. I can't find my 10.0.30 update and it's no longer available in the Steinberg site, so I've been unable to roll back to 10.0.30 on win10. Can somebody give me a download link to the 10.0.30 version, so that I can try it on win10?...

[audiot]

Windows 7 is not supported by Steinberg anymore. Dont know which minor version of C10 you are using, but that could cause troubles. If you have an nvidia card, replace it by an ATI or your onboard graphics. My cubase is rock solid, since i switched to ATI (no joke ... you'll find informations about it). As the others said, exclude it from your virus scanner and deactivate the steinberg power profile. Good luck!

I have Cubase Artist 10.0.30 in win7 and Cubase Artist 10.0.60 in win10. I can't change graphics card, it's a Toshiba Tecra i7 laptop, I'm using the original internal graphics it came with. As I said before, my Cubase 10 works OK in Windows7, but NOT ok on win10, in the very SAME laptop (dual boot). The only difference is I have Cubase 10.0.30 in win7 and 10.0.60 in win10. I can't find my 10.0.30 update and it's no longer available in the Steinberg site, so I've been unable to roll back to 10.0.30 on win10. Can somebody give me a download link to the 10.0.30 version, so that I can try it on win10?...

Ah okay, then i misunderstood that. Sorry! They have a FTP Archive, but only for very old stuff. Seems that Steinberg doesnt want users to install the 10.0.30 anymore. Your only chance is to contact them.

You can also install a demo version of the latest Cubase 10.5.20. If that demo version has the same problems, then there's something wrong with your Windows 10 setup and the v10.0.30 probably wont fix your problem. Just a guess ...