After installing the latest build, I get regular application errors in the event viewer like this:
Faulting application name: bbw64.exe, version: 2023.0.0.1003, time stamp: 0x638e5442
Faulting module name: ntdll.dll, version: 10.0.19041.2130, time stamp: 0xb5ced1c6
Exception code: 0xc000000d
Fault offset: 0x0000000000112684
Faulting process ID: 0x15d0
Faulting application start time: 0x01d9098b802972dd
Faulting application path: L:\bb\bbw64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: c548864d-27dc-424f-9802-ed82fa343884
Faulting package full name:
Faulting package-relative application ID:

I also have problems using BiaB at the same time as Cubase Pro 12, a lot of erratic behavior, crashes and hangs in Cubase. I have Cubase set to use an ASIO driver. The problems occurs regardles of what audio settings I have in BiaB (ASIO, MME or WAS). I have never had this problems before installing BiaB 2023. Using the plugin in Cubase is not an option since it never has worked to my satisfaction.

Biab 2023(1003), Cubase Pro 12 (latest), Win 10 Pro (latest).

ThSve, Welcome to the forum and to Band-in-a-Box. I'm sorry you're having issues.

The overwhelming majority of ASIO audio drivers do not like for multiple programs to use audio at one time. This is an inherent limitation of the ASIO specification when first released. Now the specification is updated but not many developers write to the current specification. Those that do normally don't tell you.

As a general rule-of-thumb you want the program recording audio to use the ASIO driver with all other programs set for MME or WAS.

To overcome this inherent limitation of the ASIO specification Microsoft added a native WAS driver to Windows. Note: some programs list the Microsoft Windows WAS driver as WASPI. WAS or WASPI refers to the same thing.

The WAS audio driver has two operational mode, shared and exclusive. Shared means the driver can be used by more than one program at a time. Exclusive means the driver can only be used by a single program at a time.

Many DAWs have a setting that "releases" the audio driver when the DAW is not in focus, others let you select shared or exclusive and some give you no choice.

May I suggest you check with your audio interface website to see if they have updated the driver?

I’aware of all that you are saying about audio drivers but the issue here is that this only happened after updating to 1003! This has never been an issue before with BiaB or other audio rograms.
I have Cubase set ut with ASIO and it doesn’t matter what I set in BiaB.
So since BiaB 1003 had serious ASIO problems, I tend to suspect that it is still some problems in 2003 regarding audio drivers.

The original 2023 release, build 1001, has a ASIO crash issue but the build 1003 update was released specifically to correct this issue.

Can you go to the top menu and select Help > About Band-in-a-Box or look at the build number listed on the splash screen while the program is opening? I suspect that, for whatever reason the build 1003 update did not take. You may want to get a fresh download and try again. The update file is available +++ HERE +++

I think I was very clear that the issue is with release 1003! Please read my initial post again.

” Faulting application name: bbw64.exe, version: 2023.0.0.1003, time stamp: 0x638e5442”

I have the same error!
There must be a general audio problem. i don't use ASIO. I use MME and have horrible audio cracks with every change i make in the mixer. A mouse click in mixer window is the same problem.