The serious problem notification without any visible issue and crashes

Hi guys,

Why this nonsense is happening? I see this error every other time without any crash. Everything works fine, but I can’t save my project under the same name, as it always does iteration saves without asking me. And I press cancel all the time for not seeing it anymore, but it persistently tries to save me nevertheless! Who has developed it in such way? :slight_smile:

It has happened like 50 times already today, it’s very annoying!

Here is the dump: Dropbox - Cubase 64bit 2022.12.29 - Simplify your life


It says to save using another name, not the same name.

It’s not really nonsense.

The people who want you to know when a program has malfunctioned, to eventually help to fix it.

As for this crash, it appears that the Impact LX Mini remote control dynamic link library is causing this crash.

Maybe you can test this by removing this file temporarily:
C:\Program Files\Common Files\Steinberg\Shared Components\ImpactLXMiniSteinbergDAWControl64.dll and run Cubase. Does the crash happen.

00000000`0014e8e0 00007ffd`0728eed3     : 00007ffc`c2ead0f8 00007ffd`0728d35a 00007ffc`c2ead0f8 00000000`0014ea50 : KERNELBASE!RaiseException+0x6c
00000000`0014e9c0 00007ffc`d55709e6     : 00007ffc`d5560000 00000000`474853f0 00000000`00000004 00007ffd`54b92710 : msvcr120!CxxThrowException+0xb3
00000000`0014ea30 00007ffc`c2e3115a     : 00007ffc`c2ead0f8 00000000`00000000 00000000`00000000 00000000`00000000 : msvcp120!std::_Xout_of_range+0x36
00000000`0014ea80 00007ffc`c2ead0f8     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffffff`fffffffe : ImpactLXMiniSteinbergDAWControl64+0x5115a
00000000`0014ea88 00000000`00000000     : 00000000`00000000 00000000`00000000 ffffffff`fffffffe 00000000`00000000 : ImpactLXMiniSteinbergDAWControl64+0xcd0f8

The thing is I save it under the new name after the error, reopen the scene, see the error again, can’t save it, save it under the new name, re-open this new scene, see the same error, save under the new name… You see why it’s not optimal way to do it? And no crashes at all.

Thank you very much for checking the dump, let me try to move that file.

It is crashing though. It doesn’t bring down Cubase, is all.

The Impact script might not be working though.

Yes, it seems it’s Impact LX Mini integration. The issue is gone after removing that file. Will report it to Nektar.

Thank you for the help, Steve.

1 Like


1 Like

Hi @steve , it has returned. Can you look at the crash dump please? What do you think the issue is now?
The new dump: Dropbox - Cubase 64bit 2022.12.30 - Simplify your life

This time the error happened, when I was creating a new group buss.

This one doesn’t have any useful info – it’s a different crash.

When you see a crash the first thing to do is exclude corrupt prefs using Cubase Safe Mode

Also can you please simply paste the file into your reply (if there’s a) next time?

I’m simply using WinDbg Preview to look at basic info supplied by the crash file. You can download it and use it too… save yourself a little time, and maybe learn some useful computer stuff.

1 Like

I thought you are using some proprietary Steinberg software. I will check WinDbg Preview, thanks.

For anybody interested the Nektar support has helped to find the issue. The silent crashes were because I had few tracks with duplicate names. It also explains why I had the error, when I created the new buss, so I’m quite sure it’s more Cubase problem than Nektar’s. I think it would be better to forbid the duplicate names creation in Cubase at all like in most other software, if it can’t handle it properly.

Tracks with duplicate names do not crash Cubase, and also the two crashes you had were different.

This can be tested:

While Cubase has duplicate track names

does it crash
1. when the Nektar extension is loaded?
2. when the Nektar extension is *not* loaded?

The second crash is defintely about the duplicate names, as it happened when I created the new buss, and duplucite names were for folder names and busses. Nektar keybord were not connected as a controller at that moment. Now I’ve given unique names to all tracks, folders and busses and there are zero issues and everything is working like it should including Nektar controller, so to me it looks like it’s about some bug in Cubase connected to duplicate names within the project. I’m not saying it’s a problem for all users, but with my gear and setup it is for sure.

Bug testing uses the scientific method. While you have found a workaround, this hasn’t been tested like this to ascertain the root problem.

Sorry, I don’t have time for it. It’s working now, that’s all I need. I can share the problem project, if you wish, and you can test as much as you want.

Of course - this is not your job, and you have things working. I mainly posted that info to help people to set their expectations in case they have the same problem.

1 Like