Band-in-a-Box Pro 2024. Fresh install on Windows 11.
Every time I start BIAB, I get an access violation in bbw64.exe. NONAME.SGU is in the title bar.
BIAB seems to work after the crash, but just ignoring this serious problem doesn't seem right.
Any suggestions ?
You should definitely send the error log report to PG Music as suggested. An Access Violation is a serious unhandled error, and should be managed effectively by the program.
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
1. Make sure Band-in-a-Box is not running 2. In the Preferences sub-folder, create a file named safemode.txt It can be an empty file, it's only the file name that's important. 3. Start Band-in-a-Box. You will see a text message confirming that it is in "safe mode". 4. This forces the program to start using factory settings. 5. Test to see if the problem still occurs using this method. 6. Afterwards, you can close Band-in-a-Box and delete or rename the file.
This method means that you won't have made any changes to your overall settings.
(Also, welcome to the forums)
Last edited by AudioTrack; 05/07/2401:27 AM.
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
I just started getting this same error. None of the things PG support asked me to try had any effect. I still get the error.
I'm on the latest version of Win11 Pro.
Question to those of you also experiencing this access violation: are you on the latest version of Win11? Is it possible that a recent Windows update is responsible?
I don't mean to suggest that I'm happy about the situation, but I'm happy that I'm not the only one. That tells me that there's a real problem.
Now, after doing a full reset to factory defaults, I've got to try to remember how I got my BiaB UI set up the way I did. Sigh.
Last edited by TheMaartian; 05/10/2410:23 PM.
ThinkPad i9 32GB RAM 7TB SSD; Win11 Pro; RME Fireface UCX II; BiaB 2025 Ultra Bitwig Studio 5; Studio One Pro 7; Melodyne Studio 5; Acoustica Premium 7 Gig Performer 5; NI S61 MK3; Focal Shape 65; Beyerdynamic DT 880 & 770
Here are some thoughts that occurred to me as I read your post.
Where have you installed BIAB. Is it in C:\Program Files" by any chance? If it is, this is not a good location for the program.
Also, it would be worthwhile right-clicking on the shortcut and then choose "Run as administrator" when you start it to see if that makes a difference.
Lastly... Go to \bb\Prefences and rename intrface.bbw to intrface.bbw.old and MySetup.DK to MySetup.DK.old ... Doing this forces BIAB to create new versions of these start-up files. If that doesn't solve the problem, you can always go to \bb\Preferences and delete the new versions of these files and return to the old versions by removing the .old from the extension.
If any program my company developed crashed with an A/V after first startup, I would make it a priority to resolve and fix. Others may have a different approach, but that's what I would do, without exception.
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
I just started getting this same error. None of the things PG support asked me to try had any effect. I still get the error.
I'm on the latest version of Win11 Pro.
Question to those of you also experiencing this access violation: are you on the latest version of Win11?
I'm using Windows 11 Home version 23H2 build 22631.3447.
Originally Posted by Noel96
Where have you installed BIAB. Is it in C:\Program Files" by any chance? If it is, this is not a good location for the program.
It's in C:\Band-in-a-Box Except one folder, which I didn't choose : C:\Program Files\PG Music Inc\Band-in-a-Box Sounds
Why would Program Files be a bad location for a program ? That's where programs are supposed to be installed, and it has been for almost 30 years.
Originally Posted by Noel96
Also, it would be worthwhile right-clicking on the shortcut and then choose "Run as administrator" when you start it to see if that makes a difference.
[...] rename intrface.bbw to intrface.bbw.old and MySetup.DK to MySetup.DK.old [...]
PG Support told me to do that and to Reset to factory defaults, it didn't help.
Originally Posted by MoultiPass
If Biab works it's a minor problem.
If a program causes an access violation, it doesn't work. It is not a minor problem, it's a major problem. Anything the program does after the crash is Undefined behavior. This is particularly risky in a program that uses plugins from unknown publishers.
Why would Program Files be a bad location for a program ? That's where programs are supposed to be installed, and it has been for almost 30 years.
Well, that's not right at all. That used to be the desired location, but Windows security changes and more in recent years (the last 15 years at least) have indicated that this is now not to desirable location.
C:\bb\ is the default location (substitute 'C:' for any other drive.)
'Program Files', and 'Program Files (x86)' etc are a big no-no (for many years now).
It's all about security.
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
Why would Program Files be a bad location for a program ? That's where programs are supposed to be installed, and it has been for almost 30 years.
Well, that's not right at all. That used to be the desired location, but Windows security changes and more in recent years (the last 15 years at least) have indicated that this is now not to desirable location.
C:\bb\ is the default location (substitute 'C:' for any other drive.)
'Program Files', and 'Program Files (x86)' etc are a big no-no (for many years now).
It's all about security.
The only program installed in a root folder on my system is Band-in-a-box, so if you are right there are a lot of software companies doing this wrong.
Can you point to any information about how Program Files was phased out ?
C:\Band-In-A-Box should be an okay folder to use. While PG Music recommend \bb, it's possible to vary that without issue.
Can you try these couple of things and see what happens.
(1) Go to C:\Band-In-A-Box and then double click on BBW64.EXE. This is simply starting the program without using a shortcut. (Doing this is a check to see if the shortcut might be including some unusual startup instructions.)
(2) Also try starting BIAB in 32-bit mode and see what happens. To do this, go to C:\Band-In-A-Box and double-click on BBW.EXE. Does this version of BIAB start okay or not?
(3) Please have a look under "Help | About Band-In-A-Box" and check that you have the latest update installed. It should say "Version 2024(1111)". This is indicating that you have update #1111 installed (which is the latest update).
1) We know from experience that BIAB will not work if installed into either one of the /Program Files folders. We have known this for decades (I tried it once over twenty years ago) and PG Music has confirmed not to do that.
What we do not know is why. I concur it probably has to do with changes in Windows related to security - the security OF Windows. As I recall, BIAB actually could start to run if it was installed in a /Program Files folder, but would immediately crash when any action took place that tried to save into that folder.
Why other applications install into /Program Files folders and work, when BIAB does not, is unknown to me.
2) The addition of the safemode.txt is an alternative to this: " rename intrface.bbw to intrface.bbw.old and MySetup.DK to MySetup.DK.old ". If one didn't work, it's not a surprise the other did not.
3) I recall reading a comment from Support that you do not HAVE to call the BIAB folder BB. The installer certainly will want to do so, but if you are very careful to change the recommended folders in each step of the install, and each step every upgrade forevermore, then it can go into a different folder. Just not one of the /Program Files folders.
4) What I don't fully understand is exactly what is happening with this: if BIAB crashes on startup, how do you continue to work with it? I think you may be saying something like "BIAB crashes on startup the first time, but then runs normally". Is that correct? That would be quite a different problem statement, requiring a different examination.
EDIT: I like everything Noel just wrote while I was typing my comments.
Last edited by Matt Finley; 05/11/2411:47 AM.
BIAB 2025 Win Audiophile. Software: Studio One 7 Pro, Swam horns, Acoustica-7, Notion 6; Win 11 Home. Hardware: Intel i9, 32 Gb; Roland Integra-7, Presonus Studio 192, Presonus Faderport 8, Royer 121, Adam Sub8 & Neumann 120 monitors
Go to C:\Band-In-A-Box and then double click on BBW64.EXE.
Access violation
Originally Posted by Noel96
go to C:\Band-In-A-Box and double-click on BBW.EXE.
Access violation
Originally Posted by Noel96
Please have a look under "Help | About Band-In-A-Box" and check that you have the latest update installed. It should say "Version 2024(1111)".
It says Version 2024 (1111)
Originally Posted by Noel96
What antivirus software do you use?
Windows Security (Comes with Windows 11)
Originally Posted by Matt Finley
What I don't fully understand is exactly what is happening with this: if BIAB crashes on startup, how do you continue to work with it? I think you may be saying something like "BIAB crashes on startup the first time, but then runs normally". Is that correct? That would be quite a different problem statement, requiring a different examination.
From the first post in this thread : Every time I start BIAB, I get an access violation in bbw64.exe.
Thanks, Sid. This is indeed a strange problem that you have.
Out of curiosity, if you go to "Audio | Audio drivers.settings", what is your Audio Driver Setup? By default, it should be WAS. Try changing this to MME, exit the menu and then restart BIAB. Does this make a difference?
What I don't fully understand is exactly what is happening with this: if BIAB crashes on startup, how do you continue to work with it? I think you may be saying something like "BIAB crashes on startup the first time, but then runs normally". Is that correct? That would be quite a different problem statement, requiring a different examination.
Originally Posted by Sid S
[From the first post in this thread : Every time I start BIAB, I get an access violation in bbw64.exe.
OK. I hope you don't mind that I'm just trying to clarify. Yes, you said that you get an access violation in bbw64.exe every time you start BIAB [my emphasis]. But then you went on to say this "BIAB seems to work after the crash, but just ignoring this serious problem doesn't seem right.". So you do seem to be saying it crashes only the first time, or maybe even most of the time, but then it does not crash.
Please elaborate.
BIAB 2025 Win Audiophile. Software: Studio One 7 Pro, Swam horns, Acoustica-7, Notion 6; Win 11 Home. Hardware: Intel i9, 32 Gb; Roland Integra-7, Presonus Studio 192, Presonus Faderport 8, Royer 121, Adam Sub8 & Neumann 120 monitors
go to "Audio | Audio drivers.settings", what is your Audio Driver Setup? By default, it should be WAS. Try changing this to MME, exit the menu and then restart BIAB. Does this make a difference
It was WAS, changing it to MME does not help.
On a side note, changing it to ASIO causes an immediate access violation, probably because I don't have any ASIO drivers. But that's a different bug.
OK. I hope you don't mind that I'm just trying to clarify. Yes, you said that you get an access violation in bbw64.exe every time you start BIAB [my emphasis]. But then you went on to say this "BIAB seems to work after the crash, but just ignoring this serious problem doesn't seem right.". So you do seem to be saying it crashes only the first time, or maybe even most of the time, but then it does not crash.
Please elaborate.
I don't mind at all, I appreciate that everybody wants to help here.
Every time I start BIAB, I face two message boxes due to an access violation. In my brain, that is a crash.
Now, BIAB detects this serious problem and continues operating. In my book, that's bad practice but anyway - BIAB seems to work after that, until the next time I start it.
Ya, this is not a "crash", but I agree 100% with everything else you are saying. By the way, I have BIAB at c:\BB. And I don't see any access violation message. Good luck.
Update your Band-in-a-Box® 2025 for Windows® Today!
If you’ve already purchased Band-in-a-Box® 2025 for Windows®, great news—a new update is now available! This update introduces a handy new feature: a vertical cursor in the Tracks window that shows the current location across all tracks, and more.
Video: Band-in-a-Box® 2025 for Windows®: Boot Camp: The AI Lyrics Generator
With Band-in-a-Box 2025® for Windows®, we've introduced an exciting new feature: the AI Lyrics Generator! In this video, Tobin guides you step-by-step on how to make the most of this new tool.
Band-in-a-Box® 2025 for Windows®: Boot Camp: The AI Lyrics Generator video.
Video: Band-in-a-Box® 2025 for Windows®: Using VST3 Plugins
Band-in-a-Box 2025® for Windows® now includes support for VST3 plugins, bringing even more creative possibilities to your music production. Join Simon as he guides you through the process in this easy-to-follow demonstration!
Video: Band-in-a-Box® 2025 for Windows®: Using VST3 Plugins
Video: Band-in-a-Box 2025 for Windows: Using The BB Stem Splitter!
In this video, Tobin provides a crash course on using the new BB Stem Splitter feature included in Band-in-a-Box 2025® for Windows®. During this process he also uses the Audio Chord Wizard (ACW) and the new Equalize Tempo feature.
Video: Band-in-a-Box® 2025 for Windows®: Using the BB Stem Splitter
Check out the forum post for some optional Tips & Tricks!
Congrats to Misha (Rustyspoon)…downloaded/installed a full Audiophile 2025!
Breaking News!
We’re thrilled to announce that Rustyspoon has made PG history as the very first person to successfully complete the download and install of the full Band-in-a-Box 2025 Windows Audiophile Edition (with FLAC files)—a whopping 610GB of data!
A big shoutout to Rustyspoon for stepping up to be our test "elf!"
With the launch of Band-in-a-Box® 2025 for Windows, we're adding new videos to our YouTube channel. We'll also share them here once they are published so you can easily find all the Band-in-a-Box® 2025 and new Add-on videos in one place!
Whether it's a summary of the new features, demonstrations of the 202 new RealTracks, new XPro Styles PAK 8, or Xtra Styles PAKs 18, information on the 2025 49-PAK, or detailed tutorials for other Band-in-a-Box® 2025 features, we have you covered!
Band-in-a-Box® 2025 for Windows is here, packed with major new features and an incredible collection of available new content! This includes 202 RealTracks (in Sets 449-467), plus 20 bonus Unreleased RealTracks in the 2025 49-PAK. There are new RealStyles, MIDI SuperTracks, Instrumental Studies, “Songs with Vocals” Artist Performance Sets, Playable RealTracks Set 4, two new sets of “RealDrums Stems,” XPro Styles PAK 8, Xtra Styles PAK 19, and more!
Special Offers
Upgrade to Band-in-a-Box® 2025 with savings of up to 50% on most upgrade packages during our special—available until December 31, 2024! Visit our Band-in-a-Box® packages page for all the purchase options available.
2025 Free Bonus PAK & 49-PAK Add-ons
We've packed our Free Bonus PAK & 49-PAK with some incredible Add-ons! The Free Bonus PAK is automatically included with most Band-in-a-Box® for Windows 2025 packages, but for even more Add-ons (including 20 Unreleased RealTracks!) upgrade to the 2025 49-PAK for only $49. You can see the full lists of items in each package, and listen to demos here.
If you have any questions, feel free to connect with us directly—we’re here to help!
One of our representatives will be happy to help you over the phone. Our hours of operation are from
6:00AM to 6:00PM PST (GMT -8) Monday thru Friday, and 8:00AM to 4:00PM PST Saturday. We are closed Sunday. You can also send us your questions via email.
One of our representatives will be happy to help you on our Live Chat or by email. Our hours of operation are from
6:00AM to 6:00PM PST (GMT -8) Monday thru Friday; 8:00AM to 4:00PM PST (GMT -8) Saturday; Closed Sunday.
Dansk
Deutsch - Windows
Español
Français - Windows
Italiano - Windows
Nederlands
Polski
Português
Svenskt
русский
Japanese
Simplified Chinese
Traditional Chinese
Korean