Under Windows, you can generate one crash dump from WaveLab if you do so:
While pressing the Alternate key (press first and maintain), select “Global preferences” from the WaveLab menu with the mouse.
In that case, there is a new tab called “Diagnostics”. There you can activate several functions.
Activate the option “Enable crash report”. Quit and relaunch WaveLab.
If a crash happens, one crash dump is generated and a dialog proposes to save it.
All I get is the text below:
[2022/03/02 13:53:56] INFO: [ 0.300 / 7900 I default] WaveLab Pro 11.0.30 (build 114)
[2022/03/02 13:53:56] INFO: [ 0.300 / 7900 I default] Operating System: “Windows 10.0.19044”
[2022/03/02 13:53:56] INFO: [ 0.300 / 7900 I default] Crash Report Enabled
[2022/03/02 13:53:56] INFO: [ 0.300 / 7900 I Log.SystemInfo] "*** SYSTEM INFO *** "
[2022/03/02 13:53:56] INFO: [ 0.300 / 7900 I Log.SystemInfo] "Windows 10.0.19044 "
[2022/03/02 13:53:56] INFO: [ 0.300 / 7900 I Log.SystemInfo] "Cache Line Size: 64 "
[2022/03/02 13:53:56] INFO: [ 0.300 / 7900 I Log.SystemInfo] "Physical Cores: 6 "
[2022/03/02 13:53:56] INFO: [ 0.300 / 7900 I Log.SystemInfo] "Logical Cores: 12 "
[2022/03/02 13:53:56] INFO: [ 0.300 / 7900 I Log.SystemInfo] "CPU Packages: 1 "
[2022/03/02 13:53:56] INFO: [ 0.300 / 7900 I Log.SystemInfo] "RAM: 64 GB "
[2022/03/02 13:53:56] INFO: [ 0.300 / 7900 I Log.SystemInfo] DSP Performance Index: 1.35366
[2022/03/02 13:53:56] INFO: [ 0.300 / 7900 I Log.SystemInfo] "*** SCREEN INFO *** "
[2022/03/02 13:53:56] INFO: [ 0.300 / 7900 I Log.SystemInfo] "Num. Screens: 2 "
[2022/03/02 13:53:56] INFO: [ 0.300 / 7900 I Log.SystemInfo] "Virtual Desktop: true "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Primary Screen Index: 0 "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "HDPI option: true "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "HDPI Var option: true "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "HDPI Var option: true "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "*** SCREEN # 1 "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Name "\\\\.\\DISPLAY1" "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Physical Size QSizeF(797, 333) mm "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Refresh Rate 30 "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Pixel Ratio 1 "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Logical DPI 96 "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Physical DPI 109.734 "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Geometry QRect(0,0 3440x1440) "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Avail geometry QRect(0,0 3440x1400) "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Virtual desktop including it QRect(0,-1080 3440x2480) "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "*** SCREEN # 2 "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Name "\\\\.\\DISPLAY2" "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Physical Size QSizeF(531, 299) mm "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Refresh Rate 60 "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Pixel Ratio 1 "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Logical DPI 96 "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Physical DPI 91.7938 "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Geometry QRect(610,-1080 1920x1080) "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Avail geometry QRect(610,-1080 1920x1040) "
[2022/03/02 13:53:56] INFO: [ 0.301 / 7900 I Log.SystemInfo] "Virtual desktop including it QRect(0,-1080 3440x2480) "
It seems we’re not getting a crash, just loosing connection to the audio interface.
I have to offer a few ideas here, I’ll try to be brief.
I have had a few WL ‘shutdowns’ that have puzzled me ever since I picked up a MOTU M4. My main interface is an older Mackie 1640i, and I wanted to be able to move from the Mackie to the Motu for mixdown sessions because the conversion and clock is better in the newer M4. At this point I’ve sorted my initial problems (WL suddenly shutting down/closing) at time of initial loading of a fresh session using either interface - and I can explain my ‘fix’ process here. However, first up, the Steinberg Generic Asio Driver DOES need to be deleted in the registry because WL is very quick to recognize this ASIO driver and it will try to install it vs. the interface ASIO drivers. (I also have the Realtek ASIO driver on my PC but it’s of no interest to WL, or Cubase either, in my experience. HOWEVER, I should mention that I have DISABLED the Realtek interface on my PC via the Device Manager.)
So, here’s what I do, and to be transparent, the very first session in WL with the new interface (after having successfully used the other interface) will typically shut down. This said, each time I begin a new session with the different interface (M4 to Mackie or Mackie to M4), I open my audio connection tab, identify the correct ASIO interface driver, and then load my channels, typically 1 and 2 Out, 1 and 2 In, Ext Efx 3 and 4 Out, and Ext Efx 3 and 4 In. At this point I go to the Ext Efx connection in the Master bus and make sure it is turned on and test for a delay ping. Sometimes WL will close right here, but other times it will wait until I try to play audio. OK, so WL closes. Then I open WL the second time, go through the same process, checking for the correct ASIO driver and channel setup, (which WL always remembers, BTW), check that the Ext Efx connection is turned on, test for a delay ping (which does register this time), and then play audio. All is good - every time - after the first go round fail.
This doesn’t happen in Cubase, this ‘closing’ event of a fresh session (having swapped the interfaces) that I see in WL, btw. Cubase just deals with the transition better and accepts the change.
Win10, 21H2, OS build 19044.1526, 32G ram