Nektar Panorama CS12 & Ivory II Grand Pianos Crashes Cubase 14 Pro

Cubase
,
1

I’m pulling my hair out troubleshooting in circles, and I desperately need the forum’s wisdom and expertise.

When I try to use the Panorama CS12 in Cubase 14 Pro, it works fine until I click on any track using the Synthogy Ivory II Grand Pianos VSTi. At which point, I receive an error (see screenshot below) stating that Cubase has become unstable, and the CS12 actually reboots itself.

Ivory-II-Grand-Piano-Panorama-CS12-Cubase-Crash-032626
Ivory-II-Grand-Piano-Panorama-CS12-Cubase-Crash-0326261920×1080 356 KB

The Ivory Piano II VSTi works fine in Cubase in every other way. However, when I add the CS12 into the equation and either try to load an Ivory Piano instrument or click on a track that already has an Ivory Piano instrument assigned, I receive the error every time.

What I’ve already done:

  • Updated the Ivory Piano II VSTi to most recent version
  • Uninstalled older version and reinstalled latest version of CS12 Controller
  • Verified I have latest Cubase 14
  • Verified that CS12 is directly connected to USB port of computer with no USB hub
  • Tested that all the other VSTis I use do not cause any problems with the CS12
  • Checked computer with sfc and dism commands (Nothing found)
  • Analyzed the Cubase .dmp files, but I don’t really understand the information or how to fix it (see text below)
  • Searched Steinberg support forum, Synthogy & Nektar sites and online for this issue, or any know resolution, without success

My system specs:

  • Windows 11 Home 64-Bit (Build 26100.6725)
  • 64 GB RAM
  • Steinberg UR44 Audio Interface
  • Cubase 14 Pro (14.0.41)
  • Nektar Panorama CS12 (Control Core 1.1.67/Firmware 01.02.02)
  • Synthogy Ivory II Grand Pianos (2.5.2.21)

.dmp file analysis:

STACK_COMMAND: ~0s; .ecxr ; kb

IP_IN_PAGED_CODE: 
VSTPlugManager!InitDll+56653
00000000`27b8a4c0 0fbe02          movsx   eax,byte ptr [rdx]

SYMBOL_NAME:  VSTPlugManager+5a4c0

MODULE_NAME: VSTPlugManager

IMAGE_NAME:  VSTPlugManager.dll

FAILURE_BUCKET_ID:  INVALID_POINTER_READ_c0000005_VSTPlugManager.dll!Unknown

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  3.1.80.32

FAILURE_ID_HASH:  {f29c49ad-ebcb-4479-c327-8f5ea1bdd32f}

Followup:     MachineOwner

Corresponding Windows Application Error:

Faulting application name: Cubase14.exe, version: 14.0.41.374, time stamp: 0x6928c2a0
Faulting module name: VSTPlugManager.dll, version: 3.1.80.32, time stamp: 0x5f50d5b9
Exception code: 0xc0000005
Fault offset: 0x000000000005a4c0
Faulting process id: 0xDEC
Faulting application start time: 0x1DCBD61E822F318
Faulting application path: C:\Program Files\Steinberg\Cubase 14\Cubase14.exe
Faulting module path: C:\Program Files\Steinberg\Cubase 14\Components\VSTPlugManager.dll
Report Id: 7ebaeca3-864d-4570-8e96-3b8aa283afdd
Faulting package full name:
Faulting package-relative application ID:

Full .dmp file:

Cubase 14.0.41 64bit2026.3.26 16.57.23.138.dmp (1.2 MB)

Ivory Piano II is my primary instrument, so it is crucial that I keep it, but I really want to improve my workflow with the CS12.

What is the .dmp file telling me, and what do I do now? Any help greatly appreciated!

2

I don’t think that you yourself (or anyone here) can do much about it. An invalid pointer read is always a bug in the code somewhere (it means that the application essentially tries to read memory where it is not allowed to).

In this case, it seems that the culprit is Cubase’s own VSTPlugmanager.dll, but as you write that without the CS12, there is no issue with the plugin and Cubase, and because over the years there have been the occasional reports here with Nektar products crashing Cubase, the CS12 looks like a culprit… (I don’t have any of their products, but as far as I know they install some extension to Cubase).

It is always difficult when a problem only occurs with the interaction of different software products (and vendors), but if I were you I’d try the Nektar support and see if they have an idea…

3

Thanks for your input! So basically, it is not something I’m doing wrong, a hardware/computer issue, but rather a code issue. (?)

I have contacted both Nektar and Steinberg, as well, and am awaiting responses. However, from what others have mentioned, I wasn’t feeling too hopeful for a solution from them.

Does it seem more likely to you that the code issue is with Nektar or Cubase? Have you heard of any resolution for these ongoing issues? Do I really have to pay to get a whole new piano VSTi just to get it to work? That would be rather disappointing (and expensive), especially since I’m using a fairly mainstream VSTi.