Cubase Pro 10.5 nor Pro 11 not launching

I have been running Cubase Pro 10 for some while I then purchased an upgrade to pro 10.5 and have always had a problem launching the program, it fails at ARA services, I have just installed the thirty day trial of Cubase Pro 11 and it fails at the same place, even if I turn off third party plugins and preferences.

Any ideas?

I’m running an Apple Mac Pro (Late 2013) - OS Catalina 10.15.7 (19H2) - 3.5 GHz 6-Core Intel Xeon E5 - 32 GB 1866 MHz DDR3 - AMD FirePro D500 3 GB

Regards,
Bill Gautier.

Hi,

Could you share a *.crash file, please?

Mac: macOS Console utility > User Reports folder or Crash Reports in macOS 10.15 (or ~user/Library/Logs/Diagnostic Reports).

Hi Martin,

Here are the latest crash reports, all related to trying to open Cubase Pro 11.

Regards,

BG

ReportCrash_2021-04-07-155057_Bills-Mac-Pro.crash (54.4 KB)

ReportCrash_2021-04-07-155136_Bills-Mac-Pro.crash (54.4 KB)

ReportCrash_2021-04-07-155352_Bills-Mac-Pro.crash (54.4 KB)

ReportCrash_2021-04-07-165533_Bills-Mac-Pro.crash (54.4 KB)

ReportCrash_2021-04-07-155116_Bills-Mac-Pro.crash (54.4 KB)

ReportCrash_2021-04-07-155012_Bills-Mac-Pro.crash (54.6 KB)

Hi,

All crashes are very same, but none of them is Cubase or any plug-in related:

Thread 6 Crashed:
0   com.apple.CoreSymbolication   	0x00007fff4fc34a15 thread_exit_due_to_bad_access() + 0
1   com.apple.CoreSymbolication   	0x00007fff4fc30672 ScanInstructionsForMissingSecondFrameLocation_Intel(_CSTypeRef, bool, unsigned long long, unsigned char const*, unsigned long long, unsigned long long, unsigned long long*, unsigned long long*, _CSTypeRef, mapped_memory_t*) + 46
2   com.apple.CoreSymbolication   	0x00007fff4fbc6e90 CheckForSecondFrame2(sampling_context_t*, CSThread&) + 327
3   com.apple.CoreSymbolication   	0x00007fff4fc30de7 invocation function for block in CheckForSecondFrame(sampling_context_t*, CSThread&) + 30
4   com.apple.CoreSymbolication   	0x00007fff4fbc0930 CSCppExceptionSafeThread::sacrificial_thread_init() + 80
5   com.apple.CoreSymbolication   	0x00007fff4fbc08dc thread_init_trampoline(CSCppExceptionSafeThread*) + 9
6   libsystem_pthread.dylib       	0x00007fff7059a109 _pthread_start + 148
7   libsystem_pthread.dylib       	0x00007fff70595b8b thread_start + 15

Thread 6 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x0000000000000003  rcx: 0x0000000000000000  rdx: 0x0000000000000001
  rdi: 0x0000000000000002  rsi: 0x0000700000698ad0  rbp: 0x0000700000698a60  rsp: 0x0000700000698a18
   r8: 0x0000700000698b20   r9: 0x0000000000000003  r10: 0x0000700000698ad0  r11: 0x00007fdaed00e580
  r12: 0x0000000000000002  r13: 0x0000000104d54250  r14: 0x0000000000000001  r15: 0x0000000000000000
  rip: 0x00007fff4fc34a15  rfl: 0x0000000000000202  cr2: 0x0000000104d54250

Hi Martin,
Would you know the cause for this as Cubase Pro 10 and earlier versions all work OK?
Does Cubase Pro 11 work with the latest Mac OS system, in which case would you recommend updating to that?
Regards,

BG

Hi,

I’m sorry, I have no such a deep knowledge about macOS.

I’m confused, because the X86 refers to the 32-bit instruction set, but there are no 32-bit instructions in macOS 10.15. And moreover, there is the (64-bit) next to the X86.

Often, this points to some memory issues. Could you test your Mac Pro system (Memory Test), please?

…will do Martin.

Hi Martin,

I’ve done a complete check and my computer tells me “No issues found Reference Code ADP000” so I presume my computer’s not at fault.

BG

Hi,

On one hand, I’m glad for this. On the other hand, I have no idea, where to continue with the investigation, sorry.

Thanks for your time Martin, do you work for Steinberg?

If so I’d be very grateful if this problem could be explored more as I’ve always been a Steinberg fan and have never had problems like this before. I’m, very much, liking the look of what Cubase Pro 11 offers.

Outside of all that would you have any idea where I should look to try and find an answer?

Kindest Regards,

BG

Hi,

I’m sorry, there is nothing to explore from Steinberg, I would say, if no Steinberg product is mentioned in the crash thread.

But you can try to rise a ticket via the official Steinberg support.

OK thanks again Martin I’ll try raising a ticket via the official Steinberg support page.

Have a great life.

Regards,

BG