Thanks I have. This is not it.
I don’t have any dropouts.
Thanks for trying to solve this! 
I’ll try swapping sound cards and see…
Update - no difference in trying other soundcards. So, it’s not that
It’s NOT about dropouts though , i thought you were getting the windows midi freeze.
this solved it for me.
M
yes, I know, I did try it. Just saying it didn’t work.
Cheers!
1 Like
Cubase 14 pro is crashing here also. It’s unpredictable, very frustrating. I’ve send the logfiles so hopefully it’s fixed soon. Sometimes cubase partially freezes. Never had this in cubase 13. I use a lot of virtual instruments with kontakt. Windows 11 on intel. New system and no overclocking.
I must tell you my crashes are back too. For original entry pls refer to Cubase freezes if started after a complete windows shutdown
I was so happy when I send the “OK” Info to you (Nov 27). I couldn´t tell you since when the situation became so bad again. However I did´t want to bother the board with this situation which I can´t describe precisely. As you said it is unpredictable when and how it happens.
However I kept sending many dumps to Steinberg with the function which is offered in “safe mode” after restarting. Now we have the patchversion 14.0.10. Nothing improved. So I decided to send an official report to be able to track progress. I send the report 2 days ago and already the day after I received a nice mail from support. They requested more details which I partly send (I didn´t get the requested “MiniDump” from Windows).
By now I have the feeling there must be a common rootcause though the appearance is different a the time. Those are the bugs you can hardly catch with a single trace / dump to find a fix after finding out what is wrong. I fully understand if support needs more dumps (even if they differ in detail). The whole thing might take a long time to be settled.
I will only buy the unlimited version, if I am sure this situation is fixed. However my trial period of C14 ends 6th of January. After that I can not support with dumps any more. Maybe it will be reproducable with my official C13 (which I neglected completely before I decided to dig more into Cubase as a new hobby). Another reason why I didn´t test that yet on my new computer.
Let´s see what the experts find.
If you are interested in details about my PC see my original post
I am using C14 Elements. As I am only a learner I just mess around with (stripped down versions of) the Steinberg Demo Programs “Life forever” and “Lucky”.
To learn more about routing and general use of tracks I am using my own mini testproject.
Nothing complicated. With all the crashes and experimenting how to report or get around them I didn´t even get arround yet to use sound effects or so. So the system can definitly not be overloaded or be influenced by strange VSTs.
This mornings crash was that - while I was looping the mini program - I opened the mediabay and listened to some audio tracks. When I wanted to leave the media bay with the “x” on the top right of the media bay the display froze. While I am writing this I did the same test. Everything is fine???..
I keep you updated when I hear from Steinberg.
Un update that I thought could maybe be helpful. Unfortunately no solution yet.
Firstly, the latest patch to Cubase pro 14.10 (Windows11) reset the setmaxMMCSSthreads, so I did that again, and set it to double. I thought that would help, until it froze again.
But, I also see that sometimes it appears to freeze, (I look in the taskmanager and I can see something is working, struggling,) and after about 30 seconds it “unfroze” (at startup of cubase, before loading any projects)
Something is not working at startup. I wish I could see somewhere what is going on, what is causing this struggle.
When it freezes I have to turn off and on my soundscard, because it hangs every time cubase freezes. I am using the ASIO driver that comes with my ur242 (made by steinberg). So far it has definitely been the most stable driver. Well, until recently.
I hope this helps more clever minds than me what this could be, perhaps a dev at Steinberg?
Regards.
Another update. I am certain of this now:
Cubase ALWAYS freezes the second time I start the program.
Meaning, I launch windows, I start up Cubase, it might work or not.
I completely close cubase.
I start cubase again.
It freezes.
Every time the second time, restarting the program.
I have to force quit.
Cubase exe is locked into memory.
Third time I might get it running if I am lucky. (There is still a locked cubase.exe I can’t touch)
I have also seen if I have the resource monitor open that Cubase takes a while to unload everything in a project. about 5 minutes more AFTER it has closed the project down and the hub shows up again. Maybe that is part of the problem? Meaning, I am trying to open something when things are clearly still being used? Or maybe it is just in the memory? I don’t know.
Let me know if anyone finds a solution and I might try cubase again.
It happens with C13 too
SESSION_LOG_1734346161387.zip (224.6 KB)
Steinberg sent me an email this afternoon asking for some tests. So they are looking into it. I am very happy about that.
I think this may be a difficult issue and there may be many steps to be taken. But I am optimistic that things will be resolved in due time. I will update you when the situation becomes more transparent.
Regards
Peter
That’s great. They are not helping me at all, which I find very strange. I have a friend who is on Nuendo, and he gets help the same day. Me, nothing. I have gotten some suggestions on this forum though, but I have no idea if those are the same people. But I haven’t seen anything in regards to my requests on technical help via their website.
Let’s hope your issue is resolved and that it helps me too.
Cheers!
Update. I have done quite a few tweaks and so far I have no freezes anymore. I still have the Komple Kontrol mystery, but at least it seems I have made some progress: (holding my thumbs)
- I set processor scheduling to “Background services” instead of “Programs” in Performance Options (System Properties/advanced)
- I made sure that none of my USBs turn off or gets suspended, and I also changed around with my USB hub configuration, switching what was plugged into what, especially making sure that more important hardware goes directly into my motherboard and don’t use a hub.
- I unabled quick start in Windows.
- I realized that the host integration of Komplete Kontrol often don’t start in windows services, and selected it to restart up to three times if it failed. (this didn’t solve the problem of the crashes, but at least that service never fails now which makes life easier.)
- I also changed the process priority and affinity for Cubase to run on high.
- And I changed the actual cores that cubase run on to only even ones, and made sure that the sound only uses ONE core.
The last too options I make sure always apply with a free program called Process lasso. Bitsum. Real-time CPU Optimization and Automation
All this has made Cubase a whole lot more stable, which is great.
All PCs are slightly different, and I use Gigantic templates which demands a lot from my system and Cubase, but with a custom build powerhouse PC for music I am surprised this much tweaking is necessary to not run into trouble. And it wasn’t like this 4 months ago.
Anyway, I hope this helps someone. If I find (or NI does), what is wrong with komplete kontrol I’ll let you know but otherwise I consider this one “solved” for the time being.
Cheers!
Hello dear Cu-Base ,
I’m absolute Beginner with Cubase 14Pro and Windows PC but experienced all above.
Since nothing helped on my side I figured to trash all VST in the blocklist (see the path with settings button) and now I can reload Cubase-Projects without PC restart.
Hope some help to you.
Cheers @all
I too am locked out of Cubase and have Komplete Kontrol issues. I tried setting to background services with no luck. I sure hope we get an update soon to correct this as I am behind on recording!
I promised to give an update when the situation becomes more transparent:
After some additional exchange of information and testing a few things on Steinbergs suggestion they asked me yesterday to try to disconnect my ancient iRig Keys 37 (Midi keyboard I bought many years ago).
All my problems are gone after doing so. No change of software, configuration or even trying to castrate Intel hardware by limiting cores. It never came into my mind that the keyboard could be the cause of the issue. So I never had the idea to disconnect it for my tests.
I was very happy with Steinberg support. The support manager was very patient with me and handled the process in a very friendly and efficient way!
I’m happy this worked for you, but I’m a little perplexed about how your midi keyboard is making cubase unstable, and isn’t it a problem that you can’t use that controller anymore? I mean, just buying new gear because cubase is unstable doesn’t sound great to me. I’m saying this because other DAWs don’t have these issues (in my experience).
I can’t use my nanokey2 anymore in cubase for example, and only cubase. It’s not great. Not because it makes cubase unstable (it doesn’t) but because it just doesn’t show up anymore.
I find the customer service staff friendly too, but what bothers me slightly is that I often get questions about matters I have already answered in my initial message, and that the best reply is often that I should consider reinstalling and update this and that. Which i have already tried. That’s is why I’m here, I have tried a lot and don’t know anymore, so I ask here or contact support.
I would think that the crashdumps would be more interesting to look at as I assume there would be hints to the issue(s) in there. Why not focus on that instead of asking me things i have already stated. My messages are detailed and thorough so that they can get to the bottom of the problem faster, if they only read it.
I just get the sense 14 is worse and that something isn’t working.
I have the same problem here . cubase 14 pro freezes after opening. It happened like 3-4 times since 3/1/25. It recovers the next day and runs smoothly.
Today I had the same issue, after I tried to open it like 3 times, I left it in the background (not responding) and as I was searching here for help, it started responding probably in about 10-15 min (I saw my controler cc121 blinking the play button and the project opened).
The pronlem isn’t caused by the computer (I9 10th gen, 64 gb ram, sound card rme fireface 800, I also tried without the sound card and still didn’t responding),
it’s not because of the project file ( I tried to open a new project and still didn’t responding),
it’s not because of win 11 ( I updated yesterday to 11 and I had the same issue in win10 few days ago),
it’s not only the cubase 14 (I tried to open cubase 13 and still didn’t responding)
I first had this issue with 14.05 and later with 14.1 again.
I updated ilok manager, activation manager, I even logged out and re logged in, in download assistant and in the support from media bay, and still got the freeze today.
I hope it will be a solution soon, other than waiting if it might start responding.
Hi There! today i was working on a session and Cubase Pro 14 Suddenly Freeze and crashed without notifying anything. It just froze for seconds and then shut down. Im working on a Windows 11 Lenovo legion intel i9 64Gb Ram .Im attaching de dmp file I hope someone could help me identify if its a plugin or what since it shows me no alert window or nothing, it just freezes and crash. Is just with this particular session im working on using plugin alliance, waves, arturia and native plugins and toontrack vst EZD3
Cubase 14.0.10 64bit2025.2.6 10.50.54.436.dmp (3.6 MB)
Cubase 14.0.10 64bit2025.2.6 10.59.49.443.dmp (3.0 MB)
I’ve reported this. The crash looks like it’s related to processing volume curves. Are you able to attach a minimal version of the project that can reproduce the crash?
Hi Paul! Thanks a lot for your quick response.
What do you mean by minimal version? Do you mean to send you the whole project deactivating some tracks?
I appreciate.
If you are happy to send us the full project then please do so, but if you don’t then try deleting some of the tracks that don’t contain volume curves. It’s much easier to fix crashes if we have projects that reproduce the problem.