VideoStudio 2021 (Ultimate) Constant Random Crashing

[dalessad]

Hi All,
Hoping I can get some insight from the community here.
I've used Video Studio Ultimate 2020, and Video Studio Ultimate 2021 and have experienced the same crashing on mostly random actions.

- Just sampling/playing the template files.
- Adding images (jpgs) to the timeline
- Adjusting the time of an image
- Playing the timeline
- Stopping/starting the video
- Moving the scrubber
- Switching between windows (ALT+Tab)
- Too many others to remember

In almost all cases it seems that the QtBridge32.exe file is at fault here.
This is what I get in the log files:
******************************************************************************************************************
Faulting application name: QtBridge32.exe, version: 24.1.0.299, time stamp: 0x609c180d
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x3c20
Faulting application start time: 0x01d8d37b2aac2048
Faulting application path: C:\Program Files\Corel\Corel VideoStudio 2021\x86\QtBridge32.exe
Faulting module path: unknown
Report Id: 2f5a0428-f827-4fc7-ba49-4d7e92ddb8fe
Faulting package full name:
Faulting package-relative application ID:
******************************************************************************************************************

I'm on a modern and pretty powerful system.. Lenovo X1 Extreme, Intel i7, 32GB RAM, 1TB SSD.
I've reinstalled Windows at least twice throughout the past couple of years.
I've reinstalled VS 2020 and VS 2021 several times as well.
I've cleared temp files.
I've performed hardware checks on CPU, RAM using the BIOS diagnostics tools at boot up.

I've sent in dump file to Corel Support, I've send in screenshots and provided the above information, and more, into the support team and there is still no sufficient response. Just generic KB articles about reinstalling/resetting Video Studio, resaving files into other formats like this generic and useless article: https://kb.corel.com/en/127575

I'm thinking this is a know issue with Corel and they've built their product on a flakey base that they can't easily switch over from. This QtBridge32 file seems to be the culprit and from my research it's a third party tool that's seems to be at the core of the software.

Anyone that can help here?

Thank you,
Adam

[Ken Berry]

Welcome to the forum.

You are unfortunately in a rather small group of users who have had this problem with the QtBridge32 file. It has only been reported half a dozen times over the past 8 or 9 years. It is related of course to QuickTime (QT) which governs the .mov codec. The problem is that Apple, which makes the QT codec dropped support for QT in the Windows PC market five or six years ago because of some security issue with the QT player on PCs.

I don't know if you have ever installed the full version of QuickTime, but if you have, our usual advice is to uninstall it, and then go to Apple Support and download and install only the QT .mov codec. You'll find it at https://support.apple.com/kb/dl837?locale=en_US Ignore the warning about Apple no longer supporting QT for Windows, and download Quicktime 7.7.9 for Windows by pressing the Download button at the top. Once downloaded, start the installation process. But in the dialogue box which appears make sure only QuickTime Essentials is active and all the other options below it have an X. Then install just the Essentials, which will give you just the codec.

You might also want to rename the QtBridge32.exe to, say, QtBridge32_OLD.exe to see if a new one is created when you reinstall the QT codec. If this doesn't work, then you can always rename it back again.

[dalessad]

Thanks Ken. I find it hard to believe I'm only one of a few people having this issue considering I've tried both VS 2020 and VS 2021 along with reinstalling Windows from scratch several times with the same crashing behaviour.....unless there is something very specific with my hardware that's causing the issue. Hardware diag comes back clean so unlikely bad memory or CPU.

I've renamed qtbridge32.exe to qtbridge32.OLD.exe in following folder : C:\Program Files\Corel\Corel VideoStudio 2021\x86\

I did have Quick Time 7 already installed and I think that was from another post or article out there suggesting the same as you did you download and install the Quick Time Essentials.

I uninstalled Quick Time 7, downloaded from the link you sent and reinstalled just the essentials component. Quick Time install did not recreate the file in the Video Studio folder but VS was able to start although now I'm getting log errors for ssBridge32.exe which may be dependent on qtbridge32.exe. I'll see if this "fixes" the crashing since now it can't be qtbridge32.exe anymore since it's renamed. Not sure if it's used for rendering or other functions in VS as I try to build out my project but let's see.

Log error below:
******************************************************************************************************************************************************************
Activation context generation failed for "C:\Program Files\Corel\Corel VideoStudio 2021\x86\ssBridge32.exe". Dependent Assembly Microsoft.VC80.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0" could not be found. Please use sxstrace.exe for detailed diagnosis.
******************************************************************************************************************************************************************

Thanks. I'll keep you posted but I'm doubtful.

Adam

[Ken Berry]

Before saying, as I did, that this had only come up a half dozen times, I did a search for QtBridge32 and that was the number it came up with, the earliest being in 2014.

I have to confess that I wasn't sure if reinstalling the QT Essentials package would create a new QtBridge32. My understanding, though, is that VS itself has not installed anything to do with QT for quite a few years. That was why we always have to install things to do with .mov video ourselves. So I have no real idea where that file comes from in the x86 subfolder. But you could always rename it back to its original, and see if it creates a problem now.

For comparison's sake, my file in VS 2021 is 118 kb in size and dated 12 May 2021. I'm not sure what that suggests but I only installed VS 2021 in January 2022 on what was then a brand new computer, so it either came as part of VS itself, or else from my subsequent installation of QT Essentials in February 2022.

[dalessad]

So, I've been chatting with the Corel support folks and they recommended reinstalling and running the cleanup tool.
I've now reinstalled VS 2021 again, twice, in two days, this latest time running the cleanup tool.

But, before I reinstalled, I stared receiving an "Out of Memory" error. I saved my project and tried to restart/reopen the VS Project and getting a message that VS "Failed to open the document".

I received this error before and after the reinstall/cleanup.

I really don't know what to think at this point. Is no one having these crashing and instability issues? Everyone's VS 2021 instance is stable and working as everyone expects?
Is there something I'm missing here? How can the software be this flakey on my system and not just with one thing, it's constant issues and crashing. It's like highschool kids programmed this thing.

I spent the better part of the day working out custom transitions, wipes, timings, etc. and it's all gone because the save didn't work. With all this crashing I've been saving every 10 minutes or less thinking I was capturing my work. Apparently not.

@Corel Product team: What the heck is going on with testing across systems? My system is not unique, It's Windows 10, latest patches, fresh install. Lenovo X1 Extreme system, NVIDIA card, 1TB SSD (Samsung), 32 GB RAM, Hardware checks out ok.

I have no other crashing issues with any other software.

@Community: Is there any other software alternatives you'd recommend other that Corel Video Studio . I wanted to support a Canadian company and the trial and feature set/interface looks promising which made me jump in as a customer but I've really lost all faith in this software and the poor support. I will never get my projects completed the way it's working today.

Thanks,

Adam

[dalessad]

well, despite an uninstall and a cleaning tool of VS 2021 as suggested by the latest response from the support team, the program is still crashing. I uninstalled the quicktime essentials and did not install any extra feature packs that I purchased for VS2021. Despite all that, crashing is still happening.
Corel folks: this can't be a snowflake event. Please acknowledge, make some meaningful suggestions. This is punishing, comical (in a demented sense) and disappointing as a a paying customer. It's impossible that I am in a unique circumstance. There's something more nefarious going on here with your software. I just want this damn software to work.

Does someone from the product team want to figure this out. How can I help make this work. Gawd damn!

Latest error log entry after the application crashed AGAIN after an uninstall, cleaning tool execution and reinstall with a fresh download as provided by the support person:
***************************************************************************************************************
Faulting application name: vstudio.exe, version: 24.1.0.299, time stamp: 0x609c1597
Faulting module name: ntdll.dll, version: 10.0.19041.1949, time stamp: 0xfe96c48e
Exception code: 0xc0000374
Fault offset: 0x00000000000ff689
Faulting process id: 0x5ee4
Faulting application start time: 0x01d8d5221e77daaa
Faulting application path: C:\Program Files\Corel\Corel VideoStudio 2021\vstudio.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 6a99fcf9-c844-46ef-83be-d05b4cf800a1
Faulting package full name:
Faulting package-relative application ID:
***************************************************************************************************************

[dalessad]

...and it contines, another crash just adding 716 files via drag and drop to the media folder.

Faulting application name: vstudio.exe, version: 24.1.0.299, time stamp: 0x609c1597
Faulting module name: ntdll.dll, version: 10.0.19041.1949, time stamp: 0xfe96c48e
Exception code: 0xc0000374
Fault offset: 0x00000000000ff689
Faulting process id: 0x8a8
Faulting application start time: 0x01d8d555ab9e390e
Faulting application path: C:\Program Files\Corel\Corel VideoStudio 2021\vstudio.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 6fe53bc4-93b9-448e-87ec-9fe94a48f417
Faulting package full name:
Faulting package-relative application ID:

[dalessad]

and crashed again adding 434 images.

Log entry:
Faulting application name: vstudio.exe, version: 24.1.0.299, time stamp: 0x609c1597
Faulting module name: ntdll.dll, version: 10.0.19041.1949, time stamp: 0xfe96c48e
Exception code: 0xc0000374
Fault offset: 0x00000000000ff689
Faulting process id: 0x70b4
Faulting application start time: 0x01d8d55a36799967
Faulting application path: C:\Program Files\Corel\Corel VideoStudio 2021\vstudio.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 083176e1-3755-4fc7-8004-c8263902ba09
Faulting package full name:
Faulting package-relative application ID:

[Ken Berry]

Can I ask -- in all this lamentable mayhem -- whether you have installed the NewBlue filters when you installed VS 2021? I assume you have since you haven't mentioned it. And although it doesn't seem to be mentioned in your faulting files, it has caused other users big problems -- to the point where we have suggested they remove NewBlue (NB) from the installation process and from the program where it has been installed. No guarantee -- again, because there is nothing to suggest you're having problems with any NB filter. But simply because it is the only other program which has caused problems with VS 2021...

So in the installation process -- assuming you have uninstalled everything -- make sure you install the Ultimate extras individually, and don't install the NB files...

[dalessad]

Hi Ken,
I used the base install file as recommended by the Support team and have not installed anything else. I did a full redownload and complete install, and I do see NewBlue in the FX folder. I'll uninstall VS 2021 again and do a custom install with as basic of an install as I can.

This link for the cleanup tool that I used (VS 2021 of course):
https://forum.corel.com/viewtopic.php?t=59847

And this download link for VS 2021 reinstall and redownload:
https://dwnld.videostudiopro.com/VideoS ... taller.exe

I did purchase the "Exclusive Video Project Enhancement Bundle" and "Video_overlays_pack.exe" as extras with my VS 2021 purchase but DID NOT install those as I had the same line of thinking to not add other factors to the situation.
I'll keep you posted.

Thank you,
Adam

[lata]

Difficult to pin down a cause for these random crashes

A little additional info regarding New Blue
New Blue filters have apparently caused the program to fail, advice from Corel was to Install Video Studio 2022, then before launching the program go to…..
C:\Program Files\NewBlueFX\uninstallers
uninstall the New Blue filters, then try running the program
I realise these instructions refer to 2022 but just maybe it also affected 2021???

Program Acceleration options
Not sure if this has been mentioned, but can you go to (F6) Preferences – Performance and deselect all acceleration options, just worth a try as some users do have issues with this option.

Installing Video Studio pack by pack
I assume from your comments you are trying this.
Use the custom option to deselect all packs except the Main program, run the program, if ok install again to add the Contents folders.
Then finally install the Bonus Features

[dalessad]

Hi lata, Appreciate the suggestions and insight.

Here's what I did:

- Uninstalled VS 2021
- Used the VS 2021 Cleanup tool to remove any registry / remaining files
- Installed just the main VS 2021 Ultimate program, no extra content/bonus features. Opened and ran VS2021; (use custom install)
- Re-ran setup and added only 1 new content/bonus feature at a time; (ran setup 3 times for Content Bundle #1, Content Bundle #2 and Bonus Features); Opened VS2021 after each install to poke around, open projects.
- Installed the two "Project Enhancement Bundle" packs separately (Video_overlays_pack.exe, VS_templates.exe)

Note: I haven't turned off any of the performance/acceleration option.

I've been heavy editing for about 2 hours now, using masking, motion, zoom/pan, filter, etc. and there has not been any random crashing. VS2021 did hang on a motion dialog window and I had to actively kill the app and restart it but this was different than the crash and close events I mentioned earlier.

Soooo, so far so good with stability but let's see as I load up the project which is likely to reach 2 hours and contain >1000 photos and some video.

Why the separate and staged installation process appears to have addressed the issue is beyond me.

Thanks Ken and lata for the suggestions. If you have any conduit into the Corel team, this installation process and external FX plugin issues really need to be addressed.

Cheers!

[dalessad]

Well, I guess it was too good to be true. After about a day or two of relatively smooth editing, I've noticed more frequent crashing. Today, probably 6 times. Sometimes there are log entries and other times nothing. Seems like VS craps out before the error gets caught and written to the log, other times I can see the error.
I'm no longer seeing the qtBridge32.exe errors, now vstudio.exe is borking.

Here's an example:
************************************************************************************************************
Faulting application name: vstudio.exe, version: 24.1.0.299, time stamp: 0x609c1597
Faulting module name: ntdll.dll, version: 10.0.19041.1949, time stamp: 0xfe96c48e
Exception code: 0xc0000374
Fault offset: 0x00000000000ff689
Faulting process id: 0x4100
Faulting application start time: 0x01d8d824cebf6e8d
Faulting application path: C:\Program Files\Corel\Corel VideoStudio 2021\vstudio.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 0c60273e-e7d9-4ee5-98f6-59bf7e4f233e
Faulting package full name:
Faulting package-relative application ID:
************************************************************************************************************

I haven't installed anything nor have I tried to repair VS.

Any one have any other suggestions.

Adam

[lata]

Back to the ntdll.dll file, I searched the Knowledge Base to find one entry back in X6 days, no real fix other than some mention of Multi Trim Video tool??

Clutching at straws now, there were some reports, long time ago, that using Jpeg images with Progressive encoding caused some problems.
Normally our images would use a BaseLine encode.
Right click one of your images for properties, JPEG tab, what does the encoding mode show.

[dalessad]

Most images were captured on a Pixel 2 or Samsung A3 or in a few instances a point-and-shoot Canon, they are all mostly native jpegs direct from the devices that shot them. Not sure how to upload a screenshot of the file properties or if I need special permission on the forum.
In the previous version with another project I was using pictures from a Sony DSC-W7.

Another (different) error in addition to the several vstudio.exe crashes again today with random activities. This time I hit the 3D editor by mistake and just closed it once it eventually popped up which crashed vstudio.

********************************************************************************************************************
Faulting application name: RenderService.exe, version: 1.0.0.1, time stamp: 0x609c0b8d
Faulting module name: ntdll.dll, version: 10.0.19041.1949, time stamp: 0xfe96c48e
Exception code: 0xc0000374
Fault offset: 0x00000000000ff689
Faulting process id: 0x7614
Faulting application start time: 0x01d8da862a00b020
Faulting application path: C:\Program Files\Corel\Corel VideoStudio 2021\RenderService.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 672880b3-d8ba-439d-a945-865d54c9ff33
Faulting package full name:
Faulting package-relative application ID:
********************************************************************************************************************