Tried out using the wavelab in cubase. (Cubase 15 pro)
Edit > Extensions > Wavelab
Loads wavelab go. Pushed play.
Awesome.
Ok closed cubase without saving the project and got another error.
I’ve had cubase for two weeks, this is like crash 10 or 11. I’m having so much fun.
…
I opened my wavelab 13 elements stand alone to grab the version, and now it won’t let me open it.
My wavelab elements license is active, and now I can’t even use it.
Hi,
Attach the mentioned *.dmp file, please.
I’ve asked the bots.
I had to go to the Steinberg Activation Manager. Deactivated then reactivated Wavelab Elements. Restarted my computer. No more errors.
Wavelab go runs fine in cubase.
Running wavelab standalone again, and it booted up wavelab go. Tried again and it’s back to elements, as it should be. ¯\(°_o)/¯ The issue is probably a license bug and is resolved, not sure yet.
The reason I haven’t uploaded the .dmp file is I haven’t been able to look at it. If I don’t know what I’m uploading, then you’re not having it.
What do you think the dump file contains?
It is a binary process dump, if you want to know what is in it try to look into it using WinDbg. It is available via the Microsoft store.
Dunno what it contains. Cause I can’t read it. 
I have my windows store bricked (also for security) so I would have just used windbg but don’t have it. Nirsoft’s bluescreenview can’t read the file for some reason. Dunno, but the sales support has now started giving me a refund on the unwanted cubase 15 elements license, so that might help the issue after it’s gone.
You don’t need Microsoft Store to get WinDbg.
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/
Because it is not a Bluescreen.
However, just follow the link that @mlib has posted and download WinDbg, but I doubt it will help you, if you have never seen any process dump.
Same file extension, but ok.
Sales support removed the old cubase 15 elements license. Refreshed, restarted computer. Cubase 15 Pro is running fine. But wavelab standalone is booting up in wavelab go again.
…
Tried installing win dgb.
I give up 
Here’s ur stupid file
Cubase 15.0.21 64bit 2026.5.6 21.18.33.502-freezedump.dmp (1.4 MB)
Cubase 15.0.21 64bit2026.5.6 21.17.24.994.dmp (1.5 MB)
The two latest ones, both from yesterday, about the right time as the problem.
The file extension in Windows says nothing. You can name file extensions as you like in Windows, without knowledge about the content of the file they mean really nothing.
Which means you do not have a license for a higher release of WaveLab. If you think you have one, look in the Activation Manager or in your online profile.
What is stupid in a dump file? Just because you can’t read it?
So here is what is in the freezedump file, it points to your NVidia graphics drivers. The crash is caused by the driver for your graphics adapter.
The second file is strange, because it seems to point to a memory problem. However, that is hard to tell from the stack trace.
As a first step you should run some Windows system tests and repair. Run these two commands to see if that restores some Windows system components
sfc /scannow
dism /Online /Cleanup-Image /RestoreHealth
What you should definitely do is to check your graphics drivers. Make sure you install just the studio drivers from Nvidia and not the gaming stuff.
I would think .dmp files are alike, so if bluescreen says it reads .dmp files then I’m confused as to why it doesn’t.
I have wavelab elements.
An attempt at humor.
I had my nvidia container blocked from running. That could be it.
Thanks for the help. 
You should ask Nirsoft why not. WinDbg, the Windows Debugger can interpret both.
