Cubase Pro less stable in Windows than macOS?

If you had already run memory tests and it was stable, no need to run them again. It’s incredibly rare for memory to go bad after initial burn-in, unless you have super harsh conditions.

So the .dmp file is likely where you want to look next, if Cubase has crashed.

From your posts, it seems you also game on the PC, so there could be conflicts there as well, but those would normally show up as higher DPC latency and not a crash or hang.

You have VEP installed. Other forum posts I’ve seen with the hang on close also had VEP installed and used via MIDI. The recommendation to try WinRT MIDI with the MMCSS change is a good one to see if this is the usual MIDI problem that has been reported on the forums here. The reason you need to do both together is WinRT MIDI uses MMCSS threads for input devices, which can starve Cubase of them. So you have to increase the number available.

Pete

That’s the weird part. It’s not that Cubase crashes, it just stalls when unloading instruments and the mixer. I’m the one who crashes Cubase, in the sense that I have to kill it from the Task Manager to be able to use it again the next time I want to.

Well, game on the PC would imply I’m a gamer. I’m not, but I always liked racing games, and I thought my RTX 4060 Ti 16 GB card would be terrible for that, and to my surprise I can play games in 4K with all the settings at the highest, or on some demanding games, one step down from the highest settings.

So when I built it I played a few racing games, of which currently I only play F1 24. But despite those UE4 error boxes that show up sometimes when I launch the game, when it loads, I can play for two hours and it doesn’t crash or do weird stuff. Forza Horizon 5 was a game that back in January and February used to crash a lot, but going online I found out it’s the game itself, it happens to everybody.

I do, but hardly use it. The only reason I have it installed is that it allows me to use the Moog instruments that are only available for macOS, like Animoog Z, Model D and Model 15. And that’s not something I’m using in this project at all.

I did that earlier. I haven’t noticed any change in performance. But just now I closed the project and I have the same eternal hanging situation. Sure, there’s always a chance it might un-hang, but it looks the same as all the other times, just as I described in my first post.

Perhaps it’s the MIDI I based the project on, but other than the notes, it’s far from the original. CC automation is completely changed, and I have a macro that deletes pretty much everything because it comes with a lot of CC channels that I don’t need. But I’ve been loading MIDI files I got online in Cubase for two years now, starting with Cubase Pro 12, and I have done about 60 of these MIDIs, some finished, some in different states of progress. This is the first time I have something like this.

It’s not the end of the world, since it never crashes Cubase, but this and other things gave me the general notion that Cubase was less stable in Windows. Would this happen if I were to reinstall Windows from scratch and make it a Cubase-only system with nothing else? Who knows. Maybe.

But pretending I beat Max Verstappen and Lewis Hamilton in all the races around the world is not the only other thing I do with this machine. :rofl:

are you using a template from an older version of Cubase by any chance?

If so, could you build a new template from scratch in C14 or just start a blank new project and see if still hangs.

I’ve seen people with old or downloaded templates have issues like this in the past.

so I’d give that a try , probably along with trashing your prefs as well if they’ve come from an older version of Cubase. Just back them p to a different location or rename them first.

TBH though it sounds like a plugin is not releasing it’s memory and causing this. It used to be a thing back i the day with ealier versions of Cubase and Certain plugins.

M

Hello, you should be able to pull a meaningful crash file by using ProcDump when Cubase freezes / hangs, please see here Cubase 13 is crashing when opening the MixConsole - #27 by Martin.Jirsak
It is no longer needed to use the version number, so you can use procdump64 -e -h -t Cubase and omit it.

These dumps are averagely between 70 and 130 MB, you might want to upload that to a cloud drive, feel free to send me the link via PM.

2 Likes

Thanks, will do shortly. But do I run procdump64.exe or procdump64a.exe? Not sure what the a means.

Just to be clear, the ONLY issue the OP is experiencing is that when he closes Cubase, the program “stalls.” In order to relaunch Cubase, he has to force quit the application first using the Task Manager. Is that right?

I’m not trying to minimize the issue. I just want to make sure there aren’t any other instability or crash issues.

Because if it’s “just” the stalling issue, then that seems solvable and certainly not worth ruminating on whether an $8,000 Mac might have been a better option, especially if the OP is technically-minded and actually enjoys tinkering with PCs. :smiley:

I am going to leave it in the capable hands of @Norbury_Brook and @Psychlist1972. Good luck, gents!

2 Likes

No. That is the most prominent in the past few days. Generally speaking, Cubase in Windows has been less stable than in macOS, and has actually crashed a couple of times. But this project is showing this particular issue, others did different things, but I didn’t document them and my memory is far from great to remember what happened on a specific day and time with Cubase. I just got the notion that Cubase was more stable under macOS. Or at least Cubase Pro 12 and 13, I barely used 14 in macOS.

Well, the thing is Macs are far better than PCs. I’m sure this is going to provoke a lot of rolling eyes and suggestions that I drink the Kool Aid, but I have 30 years of experience with Windows PCs and 26 years with Macs, so I know what I’m talking about. And I know that Macs are not for everyone, and I wouldn’t make a blanket statement that Macs were better for the last 26 years at least, because they weren’t better every single year. In fact, my first Mac was a Powermac G3, which was a piece of crap that ran Mac OS 8.6 and then 9, which were cool looking but awful OSes that crashed all the time, even compared to Windows 98.

But as of today, for most people that are not gamers and other very specific cases, Macs are much better, and not only because of stability. There are plenty of features on macOS that make you much more productive, too many to list here. I miss many of those features every time I use the PC as opposed to the Mac.

So if I had a lot of money to spare, and we didn’t have a government ran by despicable insane people that want to destroy this country’s economy and the whole world (I bet about at least 20 of you will report this post to get deleted, doesn’t mean I’m not right), I would happily spend the $8,000 in a Mac Studio M3 Ultra. But there’s a very dark cloud looming in the horizon that we started to see in the past three weeks, and it’s a good time to save rather than spend.

Now, if these were normal times, I would have been far more inclined to get the Mac Studio rather than a PC. Doesn’t mean that I hate the PC, otherwise I wouldn’t have bought it.

And now I’m going to run the sysinternals tool and see what happens.

Don’t forget your:

sfc /scannow
dism /Online /Cleanup-Image /RestoreHealth

as a first step to rectify that KERNELBASE.DLL error. If the system volume is otherwise good, then you’ll have to find the bad driver.

Well, since this thread has moved into an unfortunate “my opinion = fact” territory, I’ll bow out.

There are some known issues (documented elsewhere in this forum) with Cubase shut down and MIDI. Worth looking into.

Pete
Microsoft

Me too Pete. Unfortunate that this crops up every time…

Ill leave by saying ,i run a commercial studio and if windows was any less stable than Mac OS i wouldn’t use it…that’s not the case.

My Windows studio daw is as stable ,if not more stable with C14 than my M1 max.

Good luck to the OP.

M

1 Like

Thanks. Those have to be run in the opposite order actually, first the dism, then the sfc. But both came back just fine.

Problem is, today I have trouble getting Cubase to do the hanging thing, it’s closing fine. Taking a sweet long time to do it, but after about five minutes it does go back to the welcome screen.

Sorry man, but macOS is not better because it’s my opinion. It just is, because it has productivity features that Windows doesn’t. One example is OCR in every picture and video. I can be scrolling a video in Quicktime Player, I see a banner or something that I want to find out more about, I can select the freaking text right in the video, copy and paste it in a browser. And I can do that with any photo I take, or any old picture that I find in an old drive. And I can’t remember when, but OCR in imagery has been there for years in macOS.

Windows? Oh yeah, they’re testing OCR in the Photo app, and will release it to the public later this year or next. How cute.

I have thousands of RAW photos from my DSLRs in a folder and want to do a quick view so I can delete the ones where the flash didn’t work, or obviously blurry ones? I can scroll all of them from the Finder itself. The Windows File Explorer let’s me view JPGs, PNGs and a couple more formats, really slow, even on this monster machine.

Not just pictures, the Finder can show me thumbnails for almost every single format there is when it comes to stills and video. Any format from the last 20 years or so, it can show and play in quick preview just fine.

That’s just two things. macOS is far better, it’s not my opinion, it’s there for everyone to see. Again, I have used both platforms for over two decades, so I know what I’m talking about. No Kool Aid here, and believe me, I have written plenty of angry messages to Apple for things that they keep screwing up not just in macOS but in some of their other platforms. Just because I say Macs are better doesn’t mean that I think they are perfect, and the same goes for all their hardware and software.

Actually they don’t, irrespective of what MSFT docs may say. I always run sfc first because it will find and fix issues that should be fixed before dism. Not that it really matters, but just letting you know that they were in that order on purpose. :slight_smile:

Quick notes:

  • try condense your writing :wink:
  • Cubase may need optimisations in Project shutdown, I’ve had similar issues
  • You may want to checkout disabling the Nahimic service (Win search Services). Especially on dual monitor setups. It solved many plugins crashing for me, thanks to Fabio ! :heart_eyes:

While I may agree with you to some extent (although there are an awful lot of things about Windows I prefer to similar features in macOS,) you have to ask yourself, “Do I want to solve my problems or do I want to lecture an extremely knowledgeable person (Pete) who is taking time away from his demanding job at Microsoft to help me?”

If the former, then may I politely suggest that you send a PM to @Psychlist1972 and @Norbury_Brook thanking them for their help and reassuring them that you will keep your opinions about the supposed superiority of macOS to yourself from now on, so you can get back to making music with your new PC, something we can all support and hopefully help you achieve.

While on the subject, I took a cheap shot at you, @Psychlist1972, about the “complexity” of one of your earlier replies to the OP. It turns out you were right. He is a knowledgeable PC user who could benefit from a detailed explanation. I meant it in jest, but it was nevertheless a snarky, smartass comment. I apologize for that.

Thank you for helping people on this forum resolve their technical issues (among your many contributions).

1 Like

Well, I wasn’t lecturing Pete or anyone, I was simply having an animated discussion on OSes, and I don’t see anything wrong with that. And it’s funny that you talk about lecturing, when you typed long messages about different solutions for the Mac platform when I told you I was perfectly happy with my PC, even if I would’ve bought a Mac Studio if I had plenty of money. What was your point? Showing me what I missed? I made my decision and I’m fine with it, I don’t need to learn more about enclosures and so on.

I simply wanted to get an idea of whether or not Cubase was less stable on Windows than Mac, and what I gather for various replies is that it’s generally not, so that’s a good thing.

Let’s see. You are perfectly happy with your PC, but somehow the fact that you have to spend ten seconds (if that) closing it in the Task Manager at the end of the day (which I explained wasn’t even necessary) is somehow a big enough deal to waste several people’s time, a couple of whom you so turned off with your smugness that they are no longer willing to help you. Not exactly a winning strategy.

Do you want to know what my point was with pointing out how unnecessary it is for you in particular to spend $8,000 on an M3 Mac Studio Ultra when an M4 Max Mac Studio for half that price would have sufficed? It’s because I immediately sensed that you are the sort of person for whom nothing is ever good enough and that you will always find something to complain about. If it isn’t your inability to copy text from videos and photographs on Windows (as if that is the most important feature in the world to a company like Microsoft,) it would be something else, even about your $8,000 Mac.

But you obviously don’t want to hear that your attitude and behavior are self-defeating. Fair enough. You can have this thread to yourself.

well as we’re talking about running an OS for Cubase how is OCR relevant to the topic?

Here’s one relevant thing I think Windows is far superior to Mac OS when working with Cubase…ASIO direct monitoring… I use the RME, (because it’s the best)… and on my M1 Max using Cubase I have to have total mix open and control everything from a second applicaion(total mix)… On my windows machine Cubase controls things like Level and Pan needed for monitoring directy, I do not need to have total mix open at all.

So… that’s a really useful example of why Windows makes a better OS platform for a DAW(Cubase)
Mac OS has worse window handling than windows(snapping open windows for example) , it also has inconsistent (application) key commands … try closing a Cubase project with the option of not to save using just key commands… then open Reaper and try do the same thing…then open Logic and try!!!.you end up using the mouse a lot more which IMHO slows productivity…again, not so in windows… so I could go on but I don’t want to turn this into a Mac PC thing as i was only tring to help.

I’ve used both OS for a long time now and they both have strengths and weaknesses but IMHO for Native DAW work ASIO direct monitoring is still one of the main reasons windows still gets the heads up in my Studio over Mac OS.

I’m not a photographer or videographer and this is a Cubase(music) forum so surely this is where we should be concentrating our conversations about hardware.

I hope you solve your issues and can work reliably, something we all want.

and to answer the question originally posted I’ve found that Cubase is more stable at the moment on windows than MAc OS here. I’ve had ‘poofs’ to the desktop using M1 Max Mac OS Sonoma and Cubase 14 , no such thing on my AMD 9950x -windows 11 machine. Both machines have the same VST3 only plugins and 64GB ram-2TB system drives.

M

2 Likes

In my experience, over a very long period of time, back and forth over platforms and tons of hardware with tons of projects, and tons of audio devices, I’ve found Cubase and Nuendo to be roughly “approximately equally stable” on either platform, under the following VERY important conditions:

  1. Universal guideline: You should treat your DAW exclusively as a DAW. Not a gaming machine. Not a do-everything machine for all your media and social-media production dreams. Not a dumping ground for tons of junk, apps, and plugins. Just treat it with care and respect, and it will treat you with care and respect. I promise on my grandmother’s mandolin, this advice is still just as relevant today in 2025 as it was when I started decades ago, despite what anyone else will say today. Ignore this at your own risk. Because it’s all about risk factors and playing the odds to your favor. (And so BTW that doesn’t mean someone can’t game on a DAW… sure, it’s possible… but they are introducing risk factors that push them up the risk curve.) So my humble suggestion born out of my own painful experience, is to play the odds in YOUR OWN FAVOR by NOT screwing around, and just treat your DAW exclusively as a DAW. The fact is a DAW is a complex ecosystem, comprised of many interdependent elements, both hardware and software, from the physical hardware to BIOS to OS to drivers to apps to plugins, etc… and any one component can cause issues for a real-time system like a DAW. It’s a miracle it all works so well, right? Why screw around with it?
  2. If on Windows, don’t skimp on hardware components! Pesky little things like power supplies and RAM quality really do matter for example, and don’t just ASSUME everything works if the OS installs! Run a standard burn-in process to validate your hardware! Then you are setting yourself up for a very solid experience if you do it right.
  3. If on Windows, you may also want to make some simple yet sane adjustments and de-crappify the OS (and sometimes BIOS) if needed. This step and #2 are indeed a little more work up front in some cases, and thus it earns MacOS a more “user-friendly out of the box experience” which is more or less true, but this issue is often over-hyped by biased Mac fans. The optimal Windows DAW set up process is not that bad, and while it may take a little more work out of the box, it’s not worth moaning and groaning about. Just deal with it IMO. :smiling_face_with_halo:
  4. If on MacOS, you generally need to stay about ONE major version of MacOS behind the current latest major version (exceptions apply, but then you increase risk factors), and you should NEVER jump the gun on major OS updates. Ignore this at your own risk!
  5. Also, to expand on #4 since it can be such a big deal… if on MacOS, again, you must accept that Apple is more aggressive in “breaking” things from time to time, and thus you frankly need to pay more attention to updates to everything else in general (including apps, plugins, etc.) and the ramifications of updating, compared to your Windows colleagues. In the real world, this CAN result in more work and stress over time for MacOS users, depending on what apps/plugins you use, and CAN actually end up costing more real-world money in upgrade costs than typical Windows users, who can often go for longer periods of time without upgrades that break things.

IF you follow the above guidelines, THEN both platforms, on average, over time, are “approximately equally stable.”

But again, I put “approximately equally stable” in quotes since perhaps someone else’s version of “approximately equally stable” is different than my version of “approximately equally stable” and also can’t be confused with equal performance, equal features, equal ease of use, equal cost, equal maintenance, equally easy to screw up, equally easier to set up out of the box, and so forth. And again, consider the complex ecosystem of hardware, drivers, apps, plugins, etc… the myriad issues that can come up are too many to list. Not to mention user error too. Again, it’s a miracle it works as well as it does.

And in all fairness, guideline #5 is kind of a cheat for MacOS, because the pure fact of life is that Apple breaks things more often than Microsoft, and they tend to break things in such a way that you CAN’T roll back easily, without giving up important OS updates, and you can’t as safely upgrade without introducing higher risk factors of something breaking. And thus, you can be left high and dry if you upgrade too early, OR left stranded on an older OS/app/plugin stack because Apple broke too many things at once. And in some cases, you may end up having to shell out more money for upgrades more often for plugins or apps because a newer version of MacOS won’t run an older app or plugin.

In other words, guideline #5 tilts the whole equation slightly in the favor of Windows IMO… BUT in all fairness, IF you tend to be slightly more risky and loose with guideline #1, or technically challenged with guidelines #2 and #3, then the equation might very well tilt toward MacOS for you!

So it really boils down to how YOU might fit better with one platform or another. In my case, I’ve happily phased out Apple recently (after years of running Windows, MacOS, and Linux DAWs), and don’t plan to look back to Apple again, I’m happy to move on at this point. But YMMV. Cubase 14 has been remarkably stable for me with tons of plugins and complex projects, and I tested it heavily on both platforms and multiple systems. On carefully built and configured Windows systems, I currently find it slightly more stable than on MacOS. But I know what I’m doing and I abide by the guidelines above. However, in the past, at different times over the years, I might have said the same of MacOS at that time.

In any case, the bottom line is that you should pick the platform that you like the best. MacOS has certain advantages over Windows right now, AND vice-versa. And it’s a shifting landscape with dozens of factors that may or may not matter to you. For every advantage someone gives for MacOS, I can give one for Windows, and vice-versa. If you want to talk about bloat, I can make the case either way. If you want to talk about invasion of privacy or too much telemetry, I can make the case either way. If you want to talk about performance, I can make the case either way. If you want to talk about money/cost, I can make the case either way, depending on what you are doing. If you want to talk about size/portability/noise/performance per watt, I can make the case either way, depending on what you are doing and what you really need in your studio.

Just pick your poison for what YOU want/prefer and go with it, and remember the guidelines above. And if you do… stability itself is “approximately equally stable” on either platform.

Cheers!

2 Likes

Wise words, super happy with my PC and would not swap for a Mac, I just don’t need to. Have worked with both PCs and Macs over the years. They both crashed and they both died, it is what it is.

1 Like