I also have an AMD 9950x running Windows 11 24H2 with an RME UCX II. Outside of some irregularities with 2 Roland plugins, I’m having no issues with Cubase 14 Pro. I should mention that everything was a clean install as I just built out a new PC. I did not upgrade Windows from an earlier version and I did not install Cubase on top of an earlier version and port over preferences. I decided to take the time and just manually re-configure Cubase preferences so that everything was fresh with no references to any files created by previous versions. I’m very happy with it.
2 Likes
Scary stuff…
I tried 24H2, there was little problems with USB controller, some bluescreens related aufio drivers (using UAD 16X) .
I tested sistem with C13 and C14. VST performance in C13 was the same as with 23H2 but worse with C14. After 3 days I simply restored back to 23H2. Also edited Group policies to stay with 23H2. Im using Intel i9 13900k with ASUS board.
1 Like
Does this W11 version still works with the legacy Firewire driver?
Hey everyone,
I’m also experiencing issues with Windows 11 24H2, as others have mentioned. It seems like many of us with RME audio interfaces are affected. In my case, I’m using an RME Digiface connected to an RME PCI interface, and after updating to 24H2, my system keeps crashing. The crash dump initially pointed to hdsp_64.dll as the cause.
Hoping to fix it, I did a clean reinstall of Windows, installed only Cubase 13 and the latest RME drivers, but the crashes persist. Now, instead of hdsp_64.dll, the error message is more generic and doesn’t clearly indicate the cause.
I reached out to RME support, and they responded immediately. However, they believe the issue is more related to Cubase or Windows rather than the audio interface itself.
Is anyone else facing the same problem or has found a workaround? Would appreciate any insights!
Thanks!
download Reaper and see if the problem is still there , that will give you the answer if it’s Cubase 13.
I’m running a UFX III on 24H2 on my 9950x and also past 2 days I’ve been working on a film score using an other studios 5950x RME system with a fresh 24H2 windows install and Cubase 14 all running flawlessly.
M
2 Likes
Thanks!
I already tried this as rme support suggested too, and it works with Reaper, but Cubase 13 also seems to work fine when using another ASIO audio interface (Edirol UA-4FX). Unfortunately, still no luck with RME.
Also tried using cubase 11 with same results.
what’s your machine spec?
I’ve seen a couple of people having issues with 24H2 and IIRC they were all intel CPU users.
M
No, it’s AMD Ryzen 5 3600.
It keeps crashing even when not playing or recording, usually within 10 minutes, even on very basic projects—just 8 audio tracks with no inserts, no send FX, no MIDI channels, no instrument tracks, and no VST plugins. I haven’t installed any third-party plugins either.
The only test that worked for about 45 minutes (loop playing) without crashing was after disabling “Multi Processing” and “ASIO Guard”. We eventually quit Cubase normally without any issues in that session.
Thanks
1 Like
Oh boy… I wish I had been tracking this thread A LOT sooner (sigh). I’m at my wits’ end here. I have been in drop out Hell, as well as experiencing frequent instant POOF-> gone! session shutdowns in Cubase 14 Pro. Despite even after thinking it was a driver/corruption issue with my old Windows 11 Home. I bought a Windows 11 Pro upgrade, and completely cleaned off my SSD 2 TB drive, thinking a fresh, more powerful version would fix my issues. Oh my. Nope. It’s too late for me, I checked and I have the dreaded 24H2 Version, I’m not a happy camper. I was so excited to get back to work and use my upgraded VSTs and DAW, but all that money seems wasted, and I can’t work on my songs. This stinks. Sorry, I guess I just needed to vent, my friends…
I have 32 Gigs of RAM, Intel i7 9th Gen, a Focusrite Scarlett 2i2 3rd Gen interface (USB 3), let’s see, what else…
I was going to try maxing out my Dell’s RAM, by swapping the old original 16 G and 2 8GB cards, out for two 32 GB cards. Now, I’m not sure it will amount to any difference. Thoughts? Sorry for the long post. 
Thank you, Ava
1 Like
Happily running c14pro with Win11 24H2 on Intel i5 12600k.
Absolutely no issues…also with last week’s 24H2 update…still no issues.
Full spec in Bio.
1 Like
I’ve been experiencing this same exact issue since January with an RME UCX II. At first, I thought I might have a virus but virus and malware scans revealed nothing. I then wiped Win11 and re-installed everything (which only took about 20 hours!). I open a Cubase 13 Pro Project and it’s the same thing: Projects that used to be around 15%-20% on the VST Performance Meter were now peaking and hovering around 75%!
I did every single tweak available to the Power Options, turned off any USB Root Hub’s ability to shut down if not in use and just everything I could find. Again, no help, at all. I even bought a few 3rd party USB PCIe cards, thinking that it might be the motherboard (Gigabyte Z590 Aorus Pro AX) but it hasn’t improved performance, at all.
Also, it’s impossible to roll back to H23 so if Windows doesn’t fix this disaster in the next week or so, I’ll have to spring for a RayDat because USB is just not an option.
Wow, I thought Windows always gave us that option
The rollback windows is a painfully short ten days.
2 Likes
These kind of issues require the user to create trace files using the Microsoft debugging tools (WDK, SDK) and for Steinberg to analyze them and pinpoint what the exact cause of the issue is. Unfortunately I don’t think that is ever going to happen.
LatencyMon does not suffice in these situations.
I’ve built many computers over the years and none of them seem to work flawlessly with Cubase. It’s a real shame. I wish I just had one computer that worked how I expect it to work 
Unless you change it, this is correct.
If you consider how much disk space the old files are using, 10 days is a good compromise for most people. It’s been 10 days for as far back as I can remember.
You can change it using
DISM /Online /Set-OSUninstallWindow /Value:60
That would give you 60 days (60 is max). But it also means that disk space is being used up during that time. It also means that any apps or tools you’ve installed since the OS install is going to be in a potentially broken state.
I haven’t used that after the uninstall window has elapsed. If the files were already cleaned up, it won’t help you.
Note: DISM is a sysadmin and sysprep tool, so I don’t recommend just randomly experimenting with it.
Pete
Microsoft
1 Like
Folks using RME USB devices: have you tried with their latest drivers? They updated them for x64 right around the same time they created the Arm64 versions.
Pete
Microsoft
Working fine here. AMD 9950x -RME UFX III USB-Windows 11 24H2
M
1 Like
Hey Pete, yes, I’ve tried the latest RME drivers along with the previous two drivers and nothing changed. Projects that used to take 15-20% of the VST Performance Meter at 128 samples are now 50-60% with Peaks that redline. It’s even worse when I use a Ferrofish Pulse 8 AE, or 16 streaming channels.
At this point, I think I’m going to sell the RME UCXII and replace it with a Raydat. I should not have all of these issues with the system I built in 2021. This is crazy.
My teenager is using a computer I built in 2015 with the SSL 2+, an Alesis MIDI drumkit, guitars from a Captor, Toontrack Superior 3 and lots of plugins, and her VST Performance Meter is at like 15%.
1 Like
Taking a stab here based on what another audio developer outside of Microsoft reported, assuming you are still seeing issues.
It’s possible this is related to power plan configuration. However, I know Cubase has their own power plan, so this may not be it. But it’s worth a try.
If you quit Cubase and then open an admin command prompt and type these two things:
powercfg /SETACVALUEINDEX scheme_current SUB_PROCESSOR IDLESTATEMAX 2
powercfg /setactive scheme_current
That will tweak the power management settings and set C-states to C1E/C1 as the lowest allowed. Intel doesn’t recommend disabling C-states completely as that can reduce the lifetime of the processor (some do disable C-states in the BIOS, but again, not recommended unless you have no choice).
On a laptop, this will impact battery life and processor temperature. On a desktop, it will impact how low the processor can go.
Pete
Microsoft