Hi all, just bought a code for Cubase and regret not testing properly prior to.
Cubase 14 Pro crashes at the ARA Vst Search step every time. Only way to load it is to disable all VSTs. Can someone assist? No issues with Ableton or Pro Tools.
The stack trace from your DMP file shows the crash as being in AutoTune Pro.
PROCESS_NAME: Cubase14.exe
EXECUTE_ADDRESS: 3edc3af0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000008
EXCEPTION_PARAMETER2: 000000003edc3af0
STACK_TEXT:
00000000`45d2ff58 00007ffd`7183e8d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Auto_Tune_Pro+0x653af0
00000000`45d2ff60 00007ffd`735a8d9c : 00000000`00000000 00000000`00000000 000004f0`fffffb30 000004d0`fffffb30 : kernel32!BaseThreadInitThunk+0x17
00000000`45d2ff90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2c
SYMBOL_NAME: Auto_Tune_Pro+653af0
MODULE_NAME: Auto_Tune_Pro
IMAGE_NAME: Auto-Tune Pro.vst3
STACK_COMMAND: ~265s; .ecxr ; kb
FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_INVALID_POINTER_EXECUTE_CODE_c0000005_Auto-Tune_Pro.vst3!Unknown
To work around it temporarily, maybe you could uninstall AutoTune or rename the plugin to not use a .vst3 extension. But you’d need to contact Antares’ support. Maybe there is an update that could address the issue?
Thank you for the response, Rick!
Is there a way to just exclude Auto Tune from Cubase for the startup scan? I won’t be using it in Cubase but I do need it in my other DAWs (where it functions fine)
I created a custom VST3 folder for Ableton, put Antares plugins into it.
Now when I load Cubase it still crashes at the Initializing ARA status but does not create a valid dump file. I guess this marks a swift end to my Cubase journey
I have occasionally seen crashes in the distant past (it would have been on Windows 10 and probably earlier than Cubase 14, though I’m not positive on the latter) after updating an ARA plugin, but it would only have been on the first start after the update, and another start after that would be fine. I’m thinking I saw it after updates of one of the Synchro Arts plugins (RePitch or VocAlign) and/or Melodyne.
My inclination based on the DMP file you supplied would have been to uninstall AutoTune (you could always reinstall it later after doing some troubleshooting). I’m not sure what all is involved in ARA plugins – e.g., would moving a VST3 component of it be sufficient to hide it from Cubase, or is there some other portion of it somewhere?
There are others in these groups who know more about troubleshooting Cubase startup problems than I do, such as some way that only starts with Cubase plugins to check if that works. The only other thought I have is maybe reinstalling Cubase itself in case there is something corrupted in the installation that relates to ARA startup.
FWIW, I’m new to Windows 11 (as of a few weeks ago), but, other than three times (over many more starts) when Cubase hung at the VST3 scan on starting up (and just killing it and restarting it after that started normally), I haven’t had any issues with Cubase 14.0.32 or 14.0.40. I don’t have AutoTune (anymore – the version I had was a very old one and I haven’t used it since fully switching to Melodyne prior to my years with Cubase), but I have used Melodyne, VocAlign, and RePitch, all in ARA mode, on my Windows 11 system. I haven’t tried WaveLab or SpectraLayers in ARA mode thus far (I have used both standalone).
Thank you Rick. You provided more robust support than Cubase customer support has.
Unfortunately no solution has been found as there is no crash dump file produced in the latest crashes.
I think I’ll make do with linking Pro Tools to Ableton with MTC and use that for scoring purposes. Thanks again for your help
While Steinberg people do sometimes participate in this forum, it is really a user forum. If you haven’t already done so, you could submit a support ticket to Steinberg – I’ve never had the need to do so, but the URL for that appears to be:
It might also help to tag this post with “issue” as that might potentially make it more likely to attract the attention of some of the people on this forum whom I’d have expected might be likely to have some ideas on this sort of thing. (I just took a quick look at the DMP file with WinDbg, which is what led to the AutoTune suspicion.)
If Cubase is crashing without producing a DMP file, there will likely be events logged in the Application portion of the Event Viewer. That may or may not provide useful information.