VB3 1.4 is crashing Cakelab hard!!!!

As of yesterday my trusty go-to VB3 has started crashing projects! Every project that contains VB3 1.4 opens for a few seconds and then Cakelab disappears off of the screen. It is only VB3 that causes this. For now, I have had to open the project on my desktop that seems to have no problems with VB3. I then replace VB3 with an old 32 bit version of B4. The project then has no problem opening on the laptop that seems to hate VB3 after all this time.
Any help would be appreciated! Please help! I can't afford to upgrade right now and I really rely on VB3. Any help would be appreciated.

I have been using it recently in Platinum without issues, I will try it later in Bandlab Cakewalk. My only suggestion at this stage is to reinstall VB3 on the laptop.

Oh, and do both computers have the same version/updates of Windows?

Glyn, I tried VB3 in Platinum and got an error that says VB3 is not properly installed. Do you know how to do a complete reinstall? I remember the little badge emblem that allows you to type in the registration but there has been no sign of it. The installation instructions for x64 say to simply drag the .dll in to the VST folder. Did this, but I am under the impression that perhaps I need to have the 32 bit version to reinstall.

I did install Melda plugins and GVST plugins but the projects were running fine until a day ago.
I did try a fresh reinstall. This is the 32 bit installation. I scanned the VST folder in 32 bit Platinum and when it hit VB3 an error popped up Can not save configuration. I went ahead with the scan. Opened Platinum x32 pulled up vb3 and the install registration popped up but it now says the registration is invalid. Close but no cigar!!!!
I thank you for taking time with me. Please, if you have anymore ideas they will be welcomed.

Thanks for the info. I have uninstalled the Melds and GVST plugs and trying a system restore. This is a last ditch effort. If it doesn't work. I will continue contact with Guido. Thank you for your time and trouble and I hope to return the favor some day.

I did Windows update a few days ago. This is why I am perplexed! Everything is fine and then from out of the blue, my laptop decides to hate VB3. Still no luck even with a system restore and it is only VB3 causing havoc!!!! Still awaiting word from Guido. Will post here when I hear more. Thanks, again.

Sidroe
Well, after enduring hours of troubleshooting and reinstall I still have VB3 nuclear blasting CbB!!!
Guido, the developer of VB3, has been so gracious and helpful, it is beyond description what he has done today. Still, he couldn't even come up with a solution!
I did learn today that VB3 has the best support on the globe hands down!!!
I no longer believe the problem is the plug as much as I do think a setting is wrong in my laptop. It is just strange that this is the only problem I have. It seems like other apps or tasks would be affected as well. If anyone can think of anything I should take a look at, please, let me know. Thanks, guys! And a huge hats off to Guido!!!!!!!!

Totally agree with your comments concerning Guido. My first experience with him was when he was first starting out producing really good drum SoundFonts, he is very supportive.
I have one suggestion to try:
Have you tried installing VB3 "AS ADMINISTRATOR"?
Some older plugins really need that extra bit of security from Windows somehow. Also when you start Cakewalk go ahead and try running it "AS ADMINISTRATOR" and see if there is any difference?
 
Hoping you find a solution as I know how frustrating these things can be.
 
Very best regards,

Some serious straw clutching here. Have you done a complete disk check. As you has recopied the dll its unlike its a bad sector causing the issue but it won't do any harm. Also try a RAM check.

Does it work in another DAW, you could try the demo of Reaper.

It's not inconceivable that it's not VB3 actually causing the problem. Try this experiment for grins: open the project, click the global fx bypass button and see if the problem persists.

Btw, where is the global FX bypass? I never had to use it!

VB3 is the only plug out of hundreds of them on my system that is wrecking everything. I am still highly suspect of a Windows 10 Cumulative Update that was installed just hours before all this turmoil began.

Hi Sidroe,
 
This sounds suspiciously like a memory error to me --- a programming memory error.  It could have been there for a long time, then suddenly was exposed by the Windows update.  What I mean my "programming memory error" is that there may be an attempt to read/write too large a value for the memory allocated, a null pointer, perhaps use of an uninitialized value, and that type of thing.  These are very difficult to locate manually, much easier to isolate with memory checking tools by the progammer (i.e. by Guido).  I myself program all my math routines and technical stuff in Linux, then check for memory errors with valgrind.  When they pass the memory checks, I copy the routines into Windows folders, then use Visual Studio.  Doing this for every routine has saved me countless hours of fruitless troubleshooting.  I don't know what would be comparable for Windows, but you might ask Guido if he's tested for memory errors such as I have described.  Unless he has the specific version of Windows installed that you do on a similar machine, he may never find this problem, nor may anyone else, without a memory checking tool.
 
Good luck with this problem!
 
Regards,
Dave Clark

Have not tried the 32 bit VB3. But, downloaded the freebie Organized TRIO 3.1 and tried it and it works like a charm. Not that I want to take that many steps back in quality and performance features but I am really scratching my head now that NI B4 32 bit and Organized TRIO, a 32 bit freebie is doing a job that a plug designed for exclusively 64 bit can't handle is beyond me.
BTW, downloaded the demo for VB3-II. It works fine for now but don't feel like I could trust it at this point.
Thanks, Dave! I will pass this info on to Guido and see if there is any progress in that direction.

Are you using JBridge? CbB will show 32 bit VB3 being scanned but it does not show on my instrument list. How exactly are you getting 32 bit VB3 to scan and run in 64 bit Sonar or CbB? BTW, thanks for your help.

When I have these types of problems I'll restore a previous back-up. (Acronis or similar, not Windows)
It usually saves me a lot of grief, sometimes the problem is resolved & won't happen when updating again.