Cubase random spikes in empty project after CPU change

I changed the CPU from Intel i7-9700 to AMD Ryzen 7950X. What I’ve encountered is that even opening an empty project, I get some random peaks. This has never happened before.
I also changed the motherboard and the RAM.

What I tried:

  1. Open Cubase in safe mode
  2. Activate Steinberg Audio Power Scheme
  3. On and off ASIO Guard
  4. On and off Multi Processing

I tried the same thing in Studio ONE and Reaper. There was no problem, these peaks only occur in the Cubase.
cubasespikes

Please help, I need to finish a project immediately and it’s glitching.

Can you try deleting the main stereo output bus and creating a new one to assign on stereo out?
There is a bug that the ASIO guard is inactive for new projects where the output is assigned with real-time processing causing poor performance.

1 Like

Thank you for your reply. Here’s what I’ve done. I
s that all I have to do? If so, the peaks are still there.
cubasespikes2

Try Latency Monitor

See if that gives you any clues

Hippo

1 Like

Yes, that doesn’t seem to be your issue here.

Thank you for your reply. It looks okay. I’ve seen it jump into the red zone on others.
cubasespikes3

Maybe just a little bit of a jump in this parameter “current measured interrupt to process latency”, like in the gif.

The main problem is that, for example, in Studio One, there is no such thing. Something happened after I changed the CPU or RAM or motherboard, I guess. Cubase didn’t like it, but I don’t know how to figure out what he didn’t like.

cubasespikes4
This is what it looks like in Studio One. And something only shows up if there’s any load at all.

I see that you’ve got quite a collection of different DAWs.
When did you buy Cubase and who is your local dealer?

In the case of cubase, I bought the key. If there is any doubt about the licence, I can provide it. And at the moment, I just need to quickly solve the problem and nothing else. I have a deadline on Monday and I can’t work.

What version of cubase?

have you done a clean install of windows as you should after changing from intel to AMD. have you installed the and chipset drivers

1 Like

Is there a specific reason that someone should provide you with proof of eligibility?

1 Like

Not at all, nobody have to even reply to my question and just ignore it.
Why are you so concerned about what I asked? Does it trigger сonscience deep inside?

Looks like the problem is no longer urgent or has been solved as so much time has elapsed and the original poster has not yet revisited the post.

Did you remove the drivers for your old chipset and install correct ones for your new chipset

1 Like

Thanks to everyone who tried to help. After installing the new hardware, I uninstalled the chipset drivers and installed the new ones. But it seems that was not enough. I reinstalled Windows completely and that solved the problem. Thanks again guys. Problem solved.

1 Like

Wow! That’s a little defensive , isn’t it? Your post triggered my attention for being way off-topic and, as far as I can tell at least, unhelpful.

How was knowing the date and place of purchase going to contribute to solving the problem? I’m confused as to how that information could have been even remotely relevant to the issue at the time. I’d be really appreciative if you could please explain its relevance to me.

BTW, I only counted two DAWs - Cubase and Studio One. Hardly the “collection of DAWs” as you put it and certainly not unusual. Where are you seeing @NikolayF 's DAWs, because I must have missed them??

3 Likes

Sorry to bump the thread but I’m more or less on the same situation with the same new system:

7950x
32GB DDR5 6000 EXPO
MSI MAG B650 MoBo
Win11 freshly installed, latest AMD drivers
RME Babyface Pro lastest FW and drivers.

Changed energy plans, remade stereo output, tried with ASIO Guard on/off, installed Nvidia Studio drivers, checked LatencyMon (OK)… nothing helps. Any more clues? Thanks.

Something funny: when I raise the buffer the problem seems less apparent, so I can work at 512 or 1024 with very tiny spikes, almost nothing. But whenever I want to play VSTis and record midi this turns problematic.