I have moved the post into a new topic. I hope you don’t mind.
When you open Cubase after the crash, does it open in Safe Start Mode? Can you access a crash log from there?
2 Likes
How do I determine if it’s a crash or just a shut down. Are they both considered the same?
Not sure of my tech/software terminology so please bear with me on that. After a shut down (before this latest .30 update) On re starting Cubase I got a screen with the option to do several things. reset preferences etc. But no option to see/save/access a crash dump log.
I don’t know if that helps.
I can remember a while back (possibly with C11) an option used to come up on this splash screen, after a crash. (but I used to get very few crashes) to send the dump/crash file to Steinberg. Haven’t seen that option for a long while.
At present, and I’m having to run with, rendering out all my vst instruments. So far everything in audio is presenting no stability issues. It’s not an ideal situation for me, but it’s an option.
All my vst instruments are iratic? in their behaviour. C13 just shutting down. This includes Steinberg vst instruments as well.
Nothing has shown up in my system that causes me any concern (that’s not to say a problem doesn’t exist somewhere).
Me, being a 60 year old novice in these matters isn’t helping. 45 years worth of education just has not gone in.
I’m not sure where we go from here? I am the stumbling block not being tech or software savi.
The strangest thing is that all this is random so I cannot track it down, what ever it is.
Windows error reporting only tells me that it is C13. Sadly I don’t fully know my way around Windows and now can’t find these error reports. But I’m quite sure they would be no good in this instance.
And I’m not sure what other information I can pass on to you.
The situation seems to be at a bit of a stalemate?
Shut-down would typically imply that the program quit successfully and normaly as it should. A crash can happen “silently”, meaning you think the application is exiting as it should, but in reality, it encounters issues as it is trying to quit.
The only indication of a “silent crash” would be:
this window popping up next time you start Cubase.
If Cubase generated a crash dump file, you can post it here by just drag&drop it to the text message box when writing a new post.
Dump file get saved here on Windows machines:
Documents\Steinberg\CrashDumps
No. I’m getting no dump files created.
I’m not convinced it’s a crash. Cubase is just quitting.
Have you looked into the folder? Documents\Steinberg\CrashDumps
Is it empty?
Yes. Completely empty.
Hi,
Generate a DMP file and share it via Dropbox or a similar service, please.
Use the Microsoft ProcDump utility to generate a DMP file, please.
-
Please download ProcDump64 from Microsoft (~650kB) and extract the archive to a local folder on your hard disk.
-
Run Command Prompt (cmd) as administrator (right click and select “run as administrator”)
-
Navigate (in the Command Prompt) to the folder with the extracted procdump file.
For example:
cd C:\ Users \ \ Downloads \ Procdump
Note: the dmp file will be written into that folder. -
Launch Cubase/Nuendo. You can work as usual. At any time, change to the command prompt and start procdump, to monitor Cubase/Nuendo for unexpected behaviour (see next step).
-
Launch procdump64 via Command Prompt:
Cubase 13:
procdump64 -e -h -t Cubase13
Nuendo 13:
procdump64 -e -h -t Nuendo13
The -h option will write a dmp file in case of an application hang. This might kick in too early sometimes, in case some action takes a little longer. Feel free to skip the “-h” option, if you are only up for fetching crashes.
The option -e will catch exceptions and the option -t terminations of the application.
- Prodump is now monitoring the Cubase/Nuendo process and will write a crash log, in case Cubase/Nuendo crashes or hangs. Perform the action that causes Cubase/Nuendo to crash and send us the generated crash dmp.
ZIP and share the DMP file via Dropbox or a similar service, please.
As I’ve said before. I’m not good with software.
I will give this a go. But I am not hopeful of any outcome.
Being in bad health this may take me several days to take in and complete.
I’ve done as asked.
In the command prompt I just get the message
System cannot find specified path
Finally managed to generate a dumpfile using Procdump.
I don’t know how to send this file to you as I can’t find an attachment link to you?
Any help.
You can either upload the dump file here, so that someone can check it, or you send a private message to Martin.
For a PM you can click on his name and then on the Message button.
1 Like
Thanks for that quick reply.
Not sure how to upload the dump file here. (not good with computer stuff).
I can see an upload button at the top of this message.
Don’t want to balls it up.
Just drag the file to the reply window, that will upload it.
1 Like
Thanks for that info.
In fact - can’t thank you enough.
This sort of information is priceless to a 65 year old novice who’s only been at it for 45 years.
The older I get sadly, the less sticks in.
It won’t upload. The Dump file created with procdump is too big to upload.
Stumped again in a big way.
There is always “launching Cubase with only stock plugins” dialog box.
If you stil crash then look at system stuff.
What ever it is? it’s been dragging on and on and on.
I’ve not much energy left in the tank with every little thing going wrong…
To. Martin Jirsak.
Sent you a message this morning (I’m in the UK), With a link to the zipped procdump file via dropbox.
Not being good at these things I don’t know if you received it or not.
Neil.
Launch Cubase, and hold down Ctrl/Cmd-Alt-Shift.
In the Plug-Ins section of the Safe Start Mode dialog, activate Deactivate all third party plug-ins.
Click OK.
1 Like
I’ve done all this before.
I’m seeing no difference.
Maybe it’s just me?
I’m not sure if software, teck and me belong in the same environment?
I’ll give it another go later today. Though I’m absolutely sick of the whole process.
I’ve sent (hopefully) Martin the zip procdump file via dropbox. But don’t know if he’s got it or not.
The dump file was too big to upload here.