How do I locate what is making my session crash?

[bythetarpits]

Artist 14.0.20
I save the dump file, but I have no idea how to read it and locate my issue.

Everything worked fine last night then I shut the program down. Yep.

So it loads up normally AND I can navigate and edit with no issues, but as soon as I hit ‘Play’…Crash.

I have frozen as many channels as I can and still dies as soon as I hit play.

Please advise.
Cubase 14.0.20 64bit2025.3.30 18.32.42.431.dmp (1.0 MB)

update. I disabled all 3rd party plug-ins and when I hit play, and large dialog box pops up saying;
“Your computer has become unstable…” and box disappears and I was not able read/capture/screenshot the rest of the large paragraph.

updated update: I can open and play other projects. Just not ‘this’ one.
Hmm, how’d I break just one?

[Johnny_Moneto]

The attached file is from January and from Cubase 13.
Maybe you can find another dump file?

BTW - that crash occured in a file called SFX1.dll.

[bythetarpits]

Oops..thanks for pointing that out. (recent one uploaded)

how did you see the dll file?

[Johnny_Moneto]

Microsoft offers a software to analyze such files called WinDbg.

The current dump file is a crash in the Cubase.exe, so it’s something Steinberg needs to have a look at.

Have you considered updating your Win10 to 22H2?

@Martin.Jirsak : Martin, crash in cubase.exe 14.0.20.240, can you forward the case to the devs? Cubase Artist.

[Reco29]

Hi,

have a look at this

How to analyse Cubase crash dumps on Windows

Since this came up recently, I decided to write a little tutorial on how to analyze Cubase Crash dumps on Windows 10 (and probably 11, too). This can be helpful if you want to find out if it is a specific plugin that is the culprit for the crash. Before you do that, have a look at the windows event log, though, sometimes there is an error message in the Windows->Application section that says something like “The Application Cubase crashed in the module ‘WaveShell1-VST 10.0_x64.dll’”. Then you kn…

I would consider @Johnny_Moneto 's advice to update your system. You are currently operating Cubase on a system that is 4 versions behind its minimum system requirements…

EDIT: The end of service for your Win10 version was in 2021. I would not consider online banking on that system…

[bythetarpits]

JM, I was not aware of this update..so thanks…currently uploading.
..and thanks for taking the time to look into this.

[bythetarpits]

I did download the WinDbg…I just could not figure out how to read it. It seemed to not want to open a dmp file. But I will try again with the prompts that you have shared…and I just started using this computer again.

Thanks for your education and patience.

[Reco29]

You are welcome!

After launching WindDbg you can and open the dmp via File/Open and point to the location of the file. Double clicking on that file might work, too, once WinDbg is installed.

You will see something like this:

Click on !Analyze - v and you have the most important infos all at once.

This is what you get affter clicking on Analyze- v (screenshot of your first dmp)

Good luck!

[bythetarpits]

After removing that suspicious plugin…That session would still crash…so using my new information and de-bug app…I was told the new issue was a exe file named ‘Cubase 14’

[Martin.Jirsak]

Hi,

@bythetarpits

Cubase 14.0.20 64bit2025.3.30 18.32.42.431.dmp (1.0 MB)

I can confirm, the crash is in Cubase. Reported to Steinberg, thank you.

[shaggysiuk]

I’ve had similar problems with a project in 13 pro since I did the latest update to 13.055
It says that AmpliTube is the problem but other saves of the same project still work ok. So I’ve gone back to one of those and offloaded AmpliTube

[rchaisse]

Whenever your computer crashes there’s a good chance that something gets corrupted.
Here is my process to Repair the foundation:
I’m going to suggest that you run an administrative command prompt and type in ‘sfc /scannow’. without the quote marks and press Enter.
If if finds problems and repairs them, then that’s good.
If it finds problems but can’t fix them, then, in that same command prompt, Type ‘DISM.exe /Online /Cleanup-image /Restorehealth’ and press enter.
When it finishes, in that same command prompt, type ‘chkdsk c:/f’ and press Enter.
The C: represents your boot drive. It will ask you if you want to run it next time you restart your computer? Type ‘y’ .
Restart your computer.
This time when it restarts, you should see a black & white screen informing you that a check disk is starting. Don’t touch your keyboard. Let it run.
When finished, it will reboot.
When it gets to your desktop, re-run the ‘sfc /scannow’ as instructed above. You should be good to go.
It’s common for the Operating System to occasionally experience corruption.
When you have these types of problems, it’s important to check and repair the foundation before you try fixing problems above that.
Run CCLeaner and a Malwarebytes scan if you feel comfortable with running those.
Remember… When in Doubt - Back off !!
Hope this helps.