So many crashes - Mac 10.7.5 2.8 GHz Quad-Core Intel Xeon

Just so many crashes. Here is the crash log from one, which is a crash while closing a project, which happens every time. Hope so much that this gives someone at Steinberg an idea about what is happening.

Mac Pro
Model Identifier: MacPro5,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.8 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB
Processor Interconnect Speed: 4.8 GT/s
Running RME RayDat Rev12 Driver 3.04


Are you running Eucon? That crashes Nuendo 6 every time on close. I have another system running a HUI based controller and Nuendo closes just fine with that one. Can’t tell you if it’s Steinberg’s implementation of Eucon or Euphonix’s fault because neither Steinberg nor Euphonix will reply to the threads pointing out the problem. I used to have great faith in Nuendo but it’s starting to get a bit shaky. John.

His crash report doesn’t show the EuCon component as present or crashed (mods must have removed the report). Funny thing-- I have been getting the crash on quit… and suddenly, over the last couple of days, it’s largely stopped. Going to try to track down the reason.


No Eucon. And its not just at shutdown. I get a ton of crashes at launch as well, and occasionally during the session, especially if there is multi-channel audio involved, like 5.1 Surround. I wonder about Altiverb as the issue…

Latest crash during Audio Mixdown, Stereo, Mp3:

Process: Nuendo 6 [6815]
Path: /Applications/Nuendo 6
Identifier: com.steinberg.nuendo
Version: (
Code Type: X86-64 (Native)
Parent Process: launchd [167]

Date/Time: 2013-10-14 14:08:07.376 -0400
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9

Interval Since Last Report: 68631 sec
Crashes Since Last Report: 1
Per-App Interval Since Last Report: 63553 sec
Anonymous UUID: 209DD264-AACB-46D3-A3AE-48C4C6FA6663

Crashed Thread: 0 Dispatch queue:

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000010

Please do not post crashlogs.


Sorry. Didn’t realize it was forbidden. I have contacted support.

Same here, crash on quit. We are running N6.0.6 on a MacPro Lion quad-core with Artist Series on latest Eucon software. N6.0.5 was fine, now it crashes on quit.


I am running QT video, and just a couple of plugins— all native except for Altiverb. I am going to turn it off for awhile and see if it makes a difference.

Crashes happen most anytime, but especially on launch, quit and layoff. So frustrating. Its interfering with my ability to use Nuendo to make a living at the moment. I wish that support would get back to me.

Turning off Altiverb does not seem to make a difference.

Aloha and +1.

@ Fredo.
Is this a ‘new’ policy?

Seems to me users have been posting CR’s for almost three years now
and I have never before read a mod’s post requesting forum members
to cease this behavior.

I know this because I consider CR’s to be a sort of ‘digital/cubase’
version of ‘Where’s Waldo’.

I often read thru them to try and spot the prob (Waldo).

But I also understand that perhaps
with this new forum, things have changed.

1-If this is indeed the case, an announcement would be helpful to readers
of this web site.

2-If this has always been the policy of the board then I
and many others have mis-understood this fact and
apologies are in order.


Crashlogs don’t make any sense, except to a few programmers.
So it’s useless to post them here.

Secondly, each crashlog is a few pages long, which clutters the forum very much.

For both of these reasons, please don’t post crashlogs.


Sure wish I could get any kind of answer from support though… That would be awesome.

Still no answer, or even an auto-reply from support.


I’ve been suffering crashes with N6 and this is what I did to fix it:

I hope it helps

I will certainly give it a try… although that whole “plugins not performing as expected” thing freaks me out…
This shouldn’t be necessary. I don’t see how its ok for it to be so unstable.

Have you had your RAM modules tested? I was in denial about mine until I started having more problems than random crashes. Identified an intermittent DIMM and replaced it, and the world was a much better place.

Maybe worth a try, if all else fails.


I will do that too. Thanks Chewy.