Nektar LX 88 starting to crash Cubase pro 14

Cubase
1

Up until yesterday, My Nektar keyboard and cubase 14 have been happy together for many many month.

I have the latest Cubase and the latest Nektar Cubase script

Yesterday, whilst twiddling a knob on the nektar, cubase informed me of a serious problem, and advised me to save the song as a new version, citing the nektar dll in the program files\common files\steinberg\shared components\impaktLX88+SteinbergDAWControl64.dll.

Today, after firing up cubase, I had to leave to go somewhere, for 30-40 minutes, so nobody touched the computer, yet, when i came back, Cubase presented me with exactly the same problem.

I will add that after the first crash, I went to the nektar site and found that there was a small update to the cubase script (.04 to .05 etc) so I updated it, but I noticed that the dll in question wasn’t updated

With the updated script, it gave me the same error, so not that, sadly.

Has anyone had a similar problem?

I have looked through the forum, but cannot see anything relating to this.

Thanks

2

Hi,

Could you please attach the *.ips/dmp file?

Mac: macOS Console utility > Crash Reports (or ~user/Library/Logs/Diagnostic Reports).
Win: %userprofile%/Documents/Steinberg/Crash Dumps

3

Hi Martin,

Cubase 14.0.20 64bit2025.3.25 8.52.50.332.dmp (2.8 MB)

I have just done an SFC /scannow from the command prompt, but that was ok

Thank you

ps. I don’t know why the forum never tells me someone has posted a reply, it was pure luck i checked

4

As a side note, I have had crashes in the past with cubase, but usually a 3rd party plugin, or recently with windows kernel32.

When prompted by cubase, I send the errors to support with your automatic link when I restart cubase.

With the kernel32 problem, someone on the forum told me to do that sfc /scannow instruction, and it seemed to sort it, as it found problems (didn’t tell what though) and i have not had the problem since.

Sending the errors to Cubase is fine, except I get no feedback to exactly what the problem was, and this the same with this problem.

Which is why I posted the question on this forum to see if anyone else had the same problem.

As you very kindly asked for the dump file, you may be able to tell me what the problem is, hopefully.

5

Hi,

The crash is completely in the Nektar Impact LX88 component:

ImpactLX88_SteinbergDAWControl64+0x57650
ImpactLX88_SteinbergDAWControl64+0x72cb8
0x00000002`25cebcb0
0x00000002`25cebcb0
0x10d
0x00000002`4f82bac0
0x14b130
0x14b150
7

Thank you very much Martin,

Much appreciated

I will now tell Nektar

I would never had known that, looking at that :slight_smile:

8

As an update, which may help someone, it seems that the crash was not caused by Nektar, but the USB cable, which they said would probably be the cause, or the USB port on the computer.

I have changed the cable and at the moment all seems ok.

I would never have thought of the USB situation!

1 Like