@Antoine-B the minidump points to Nahimic Service:
win32u!NtUserEnumDisplayMonitors+0x14
d3d9!CEnum::GetAdapterMonitor+0x7d
NahimicOSD+0x1e43b
0x62645f54
The freeze with Agumented Grand Piano is likely due to the same issue, as it generally occurs on multi-screens setups when moving/opening/operating OpenGL accelerated plugins. The only workaround is to uninstall or disable Nahimic.
[Edit] For completeness, I say “likely” because the call stack is different and the plugin seems to be waiting on something - in the exception analysis, we can see the GPU driver, the plugin and OpenGL (which is the same area as that issue):
nvoglv64.dll
Augmented GRAND PIANO.vst3
nvwgf2umx.dll
4 Likes
Wow thanks Fabio, I looked it up and tried disabling the service ..
Result for now all the previously offending plugins all behaved normally on dual screens. Nice ! Hopefully this was the culprit. I’ll report if any changes.
Thanks Fabio, I love smoothness 
Have a nice weekend !
2 Likes
Whoa, OK, it looks like Fabio_B has sorted your issue. Awesome!
Plainly, your two monitors show up in the Nvidia app so Nividia must be driving both monitors. This is not the case with my laptop but things work as they should here so… Is it possible your MB doesn’t have a built in graphics card? Well, whatever the case, you seem to be all set! Congrats!
BTW, maybe take a look at this:
Nahimic service is a virus. - Microsoft Community
Oh! Finally welcome to my world. The pool’s bug is killing me.
Cool, what about cleaning the pool crashes??
Hi @Fabio_B ,
Thank you for jumping in. That’s great that you are on board! 
3 Likes
Im happy antoine-b’s issue is resolved, but i am still not sure why it got merged into this thread which is about a completely separate issue.
Cubase reliably crashes when I delete or disable/enable a track that is connected to my hardware interface via the Studio Setup Input screen - specifically, my Steinberg UR44C interface. I have my suspicions that it has something to do with the DAW integration of this interface, which I don’t know how to disable.
My apologies, I did end up thinking I had started this post after so many messages, sorry ! 
If I understand you use a Steinberg soundcard so it should not need to be disabled in studio setup. And if crashes happen when a track connected to the soundcard is disabled or enabled, that is indeed a serious stability issue.
I am not sure if Nahimic is on mac, but that seemed to be the issue for me on Windows.
And if your drivers are all up to date, then not sure, but you should post your Studio setup screenshot here, as well as your Audio connections screenshot. Someone might see something on those 2 images !
this is why I always recommend windows laptop users to format/wipe and then do a fresh vanilla install when they first get their machines. It’s a new machine, you’ve nothing to lose but everything to gain… Nahimic would not be there if you follw this rule and you’ll have a vanilla windows install to start from.
M
1 Like
I will add my experience to this thread, I’m experiencing very often crashes on heavily worked projects, specifically i’ve noticed that most of the times my Cubase (from 13, to 14) crashes when i select (and arm, according to my preferences) certain audio tracks that previously had (or still have) an hardware input connected to it. For me getting rid of the audio connections from the connections window isn’t enough, today i found out i can obviously turn off the auto arm feature and this seems to mitigate the issue. Those problems persists and returns on both my machines, a Macbook Pro m1 pro (10 cores, Monterey) and a less support thread friendly machine a Ryzentosh (Ryzen 7 5800x, RX6800xt, Monterey, Cubase modified to work with my CPU, so i’m not going to complain on any problem on this machine ahah). I’ve never opened a thread because when this stuff happens i do usually also have strict timelines and no time to share my problems here. I’ve recently bought the update for the 14 and i can’t really move away from cubase for recording and post production but since the last December i’ve completely switched to a heavily customized Reaper (thanks to DAWProject) to address mix and mastering tasks without the constant pressure of those issues reported above (i do really encounter them on the 70% of the project i’ve worked on since cuabse 12 as far as i can remember). I do hope that the auto arm trick helps someone on the line like me and the guy above.
I think it may help folks a bit more if you could take a minute and post one of your crash dump files. If the per-track crash behavior is replicated across different operating systems and processor architectures, one presumes a shared plugin could be involved. The crash dump would help identify that.
It seems counterintuitive that in the face of strict time crunches the solution was to “completely switch to a heavily customized Reaper” build. My presumption is that most professional engineers won’t be able to record a project in Cubase, then export to another heavily customized DAW for mixing, and then export it back out and into Cubase in order to continue post-production work, particularly if time is a consideration.
A such, details of the crashes you’ve experienced 70% of the time on two different OS’s would probably be invaluable to anyone else experiencing the issue, so hopefully you can provide those too.
Thanks!
Ciao Alessandro, please see the comment from Thor above, maybe you can submit dump files, that could help Steinberg identify an issue and perhaps help the community too.
Grazzie !
Hey i didn’t come back to the thread both because I’m still under strict deadlines and also for the fact that by looking to my Console app on MacOS i found out i could “sample” a process who is not crashed yet (just like my Cubase when it stalls in the above circumstances, this prevented me most of the time from getting a dmp file from this kind of situations) and i found out that probably Cubase isn’t the one to blame directly, I’m very used to work on my usb drives and since i need to be able to transfer files of any size between different platforms (and also because of my Ryzentosh that is a windows dual boot system) i do still use NTFS drives trough TuxeraNTFS (it’s a commercial kernel extension that makes any NTFS drive behave mostly like a mac native drive)… and well, my console right during the crash was spammed with errors from tuxera regarding file indexing and the last action i was performing on cubase was a consolidate so this makes totally sense to me. So my problem turns out to be probably just some strange interaction between tuxera and cubase, note to say that the crashes on my MacBook Pro when i work on its internal APFS drive are non existent.