WaveLab Pro 12 Crashing

Greetings,

I have spent a good amount of hours trying to find out why WL P12 keeps crashing.

Base line info:

  • I am not opening a project, I am simply trying to open the application.
  • I am running windows 11 Pro 64bit
  • Version 25H2
  • Processor: AMD Ryzen 9 5950X 16-Core Processor
  • RAM: 64GB
  • Graphis card: 6GB Nvidia GeForce GTX 1660
  • Running Cubase Pro 15
  • VST’s
    • Soundtoys
    • UAD
    • AutoTune-Antares
    • Native Instruments
    • Absolute 6 VST Collection
    • Sessionwire

I upgraded WL Pro 11 to WL Pro 12, and read all the information I could find about this problem and tried it all, what I have tried so far:

  1. Deleted cache.
  2. Uninstalled & reinstalled program.
  3. Deleted all VST’s, when I do this the program doesn’t even do a VST search, but still crashes.
  4. Added ALL VST’s to ‘Ignore’ .txt file.
  5. Reinstalled VST’s
  6. Disconnected internet but crash continued.
  7. Here is the Tracer report:
    113C: [ 4.031 / 4412 W ] QWindowsPipeWriter: write failed. (The pipe has been ended.)
    71FC: [ 5.993 / 29180 W ] QWindowsPipeWriter: write failed. (The pipe has been ended.)
    7ED4: [ 4.732 / 32468 W ] QWindowsPipeWriter: write failed. (The pipe has been ended.)
    7DB0: [ 3.759 / 32176 W ] QWindowsPipeWriter: write failed. (The pipe has been ended.)
    3774: [ 1.610 / 14196 W ] QWindowsPipeWriter: write failed. (The pipe has been ended.)
    7DF0: [ 1.400 / 32240 W ] QWindowsPipeWriter: write failed. (The pipe has been ended.)
    71E0: [ 1.082 / 29152 W ] QWindowsPipeWriter: write failed. (The pipe has been ended.)
    2894: [ 0.795 / 10388 W ] QWindowsPipeWriter: write failed. (The pipe has been ended.)
    51DC: [ 1.772 / 20956 W ] QWindowsPipeWriter: write failed. (The pipe has been ended.)
  8. I am unable to find a crash report.
  9. I have installed WL Pro 11.2 and the intro screen appears but when I open an .wav audio file or any audio file it crashes, version 12 doesn’t get to the intro screen.
  10. I am using one-drive to backup all projects’ files and mixdowns. But all software Cubase & WL and VST are all on C: and not on one-drive.
  11. I also uninstalled Sound ID, as one user reported this resolved the problem, but this has not changed my situation.
  12. I also disabled ALL windows firewalls and added WL to the exceptions list.
  13. Completed many restarts and shutdowns

Try starting while keeping control key pressed

1 Like

I have tried this, but it crashes so quickly, but nothing changes.

The tracer info seems to imply there is already a running WaveLab version. Probably the version that crashed and is still dormant.

In your long list, you did not mention the simple action of rebooting your computer. Did you do this?

1 Like

Yes, I have restarted and tried shutting down a few times.

Here is a way to enforce a crash dump, the only way to (possibly) get a clue.

Here is a step-by-step guide to setting it up and capturing the crash data (partially provided by an AI)

1. Install WinDbg

The modern version, WinDbg Preview, is the most user-friendly.

  1. Open the Microsoft Store on your Windows PC.
  2. Search for “WinDbg Preview”.
  3. Click Install (it is free and published by Microsoft).
  • Note: If you don’t have access to the Store, you can download it as part of the Windows SDK, but the Store version is much easier to manage.

2. Reboot your Computer

3. Launch WaveLab through WinDbg

Since WaveLab crashes at startup, the best way to catch it is to have WinDbg “watch” it from the moment it begins.

  1. Open WinDbg Preview from your Start menu.
  2. Go to File (top left) → Start debugging.
  3. Select Launch executable.
  4. Click Browse and navigate to the .exe file of WaveLab.
  5. Click Configure (or simply Open).
  6. The debugger will load, and you will see a command terminal window inside WinDbg. It will likely say “Break instruction exception” and stop. This is normal—the debugger pauses before WaveLab actually starts.

4. Trigger the Crash

  1. In the command box at the bottom of the WinDbg window, type:
    g
    (This stands for “Go”) and press Enter.
  2. WaveLab will now attempt to start.
  3. Use WaveLab until it crashes. Once it crashes, WaveLab will freeze, and WinDbg will display a message like “Exception XXXX encountered”.

5. Generate the Dump File

Once the crash has occurred and the debugger has “caught” it, you need to save that information into a file.

  1. In the WinDbg command box at the bottom, type the following command:
    .dump /ma C:\temp\crash.dmp
  • Note: Make sure the folder C:\temp exists, or change the path to a location you can write to, like C:\Users\YourName\Desktop\crash.dmp.
  1. Press Enter.
  2. WinDbg will take a moment to write the file. Once it says “Dump successfully written,” you are done.

6. Send the Data

The file you just created (.dmp) contains the memory state of WaveLab.

  • Zip the file: Dump files can be quite large, but they compress very well. Right-click the file → Send toCompressed (zipped) folder.

  • Send it: Send the file with whatever method (eg, wetransfer)

1 Like

crash.zip

The end of the ‘DBg’ was slightly different:

(5978.2358): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.

Ran the Dbgr for WL Pro 11.2, and it does not appear to pass ‘Checking Licenses…’ to open the intro access hub as it does when I open this version normally. When I attempt to open a audio file or create an empty project it then crashes.

I stopped the DBging, and started again and then it went to the intro screen/hub, it shows the final error similar to the error on version 12:

(5200.5518): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
ntdll!SbSelectProcedure+0x16b:

crashpro11.2.zip

crash.zip

This was useful. The crash happens in the driver asio4all
Get rid of it to be able to run WaveLab successfully.

See also

4 Likes

Guys, you have made my day!!! Thank you so much it is working perfectly!! Thank you.

Thank you so much!

2 Likes