|
|
Post by Candive on May 3, 2024 3:34:20 GMT
So today I decided to use ProDad-Script...
The system allows me to apply the plugin to the clip on the timeline. I can select the template and make changes but when I press the Create button; I get the BSOD! Admittedly I haven't seen the Blue screen in a long time and didn't expect it on this new computer. ProDad RotoPen works fine. I reinstalled the plugins and SFC scanned my hard drive but the computer still crashes. I wonder if this is a Windows 11 issue?
If anyone can confirm ProDad-Script works without crashing their Win 11 machine, I would be grateful. Also, any suggestions to fix this problem are welcome. My last resort will be to contact Support.
|
|
|
|
Post by robertoz on May 3, 2024 3:49:15 GMT
Can confirm that ProDAD Script works fine with a Win 10 OS
|
|
|
|
Post by Zaťko Vendi on May 3, 2024 4:30:37 GMT
Dnes som sa teda rozhodol použiť ProDad-Script... Systém mi umožňuje aplikovať plugin na klip na časovej osi. Môžem vybrať šablónu a vykonať zmeny, ale keď stlačím tlačidlo Vytvoriť; Chápem BSOD! Priznám sa, že modrú obrazovku som už dlho nevidel a ani som ju na tomto novom počítači neočakával. ProDad RotoPen funguje dobre. Preinštaloval som doplnky a SFC skontroloval môj pevný disk, ale počítač stále padá. Zaujímalo by ma, či je to problém Windows 11? Ak niekto môže potvrdiť, že ProDad-Script funguje bez zlyhania počítača s Win 11, bol by som vďačný. Vítané sú aj akékoľvek návrhy na vyriešenie tohto problému. Mojou poslednou možnosťou bude kontaktovať podporu. |
|
|
|
Post by Zaťko Vendi on May 3, 2024 4:30:54 GMT
Hi. I use Win11, but it crashes for me too. Some subtitles work, but if most don't work, the whole system crashes.
|
|
|
|
Post by Ken Berry on May 3, 2024 4:31:52 GMT
I have only reinstalled VS2023 today on my Win 11 Pro computer so I needed to reinstall Rotopen and Script anyway. Just did so now, and then applied Script to a video. It opened fine. I made a script and applied it to the video, and that too worked fine. And VS is still running as I write this.
|
|
|
|
Post by Candive on May 3, 2024 11:37:55 GMT
I might just do a complete clean reinstall of the software to see if that corrects the crashes. Ken Berry , in another post you seem to have struggled reinstalling VideoStudio. I'm not sure if it was that hot fix or something else!? Anyway, any words of advice before I proceed? One notable difference is your machine is AMD while I'm on Intel and Nvidia. Zaťko Vendi , would you please provide your computer hardware specifications. It would help to determine if this problem is hardware related. See my system specs in my signature below. |
|
|
|
Post by Ken Berry on May 3, 2024 18:17:05 GMT
It's worth a try to reinstall. And yes, I was mystified by the fact that three weeks ago my VS2023 worked perfectly. Then I took a trip to another country, and my computer was not touched during this time. When I came back, the only new thing added was a Win 11 update. Then VS stopped working. I added the hotfix to PSP 2023 then, but that did nothing. So I reinstalled VS2023. Still no change. I tried a number of other things, including removing the Win 11 update (no change) and reinstalling PSP2023 as well, without its hotfix. But nothing worked. Then Trevor suggested I uninstall all the NewBlue filters which had come with VS2023. I thought this strange since they had been working with VS2023 before my trip. Anyway, I decided to cut them from vft_plug and vfx_plug sub-folders in C:\Program Files\Corel\VideoStudio Pro 2023 and paste them to an external hard drive. And VS2023 immediately worked again!
But it has been known for many years now that some NewBlue filters can cause problems for some people. However, proDAD, which makes the Rotopen and Script and other filters which come with VS 2023, has NOT been known to cause such problems. But it is still possible.
Instead of fully uninstalling/reinstalling VS, you might want to consider simply cutting the file proDADScript40Corel4.vft out of the C:\Program Files\Corel\VideoStudio Pro 2023\vft_plug sub-folder. If VS then works, you could try reinstalling the Rotopen and Script filters (which come together as one package) from the VS Store to see if it continues to work. If it doesn't, then you could consider a full reinstallation.
|
|
|
|
Post by Shinjo Kurumi on May 5, 2024 8:42:55 GMT
Maybe you can use some tools like BlueScreenView, to check what is going wrong on your computer...
|
|
|
|
Post by Candive on May 5, 2024 22:56:17 GMT
Hi Shinjo Kurumi , Thanks for the suggestion. I downloaded BlueScreenView and ran it. It indicated an issue with ntoskrnl.exe so I googled. This obviously is a common cause and is related to a number of things; bad drivers, corrupt system files, bad memory etc. Since my computer is from Lenovo, I did the following; -Using Lenovo Vantage, check all drivers provided by Lenovo were up-to-date -Result passed -Using Lenovo Vantage, conducted a hardware check - Result Passed -Conducted an additional check on memory using Windows Memory Diagnostic tool - Result passed -Ran CHKDSK - Result passed -Ran DISM - Result passed -Ran SFC /scan now - Result passed -Ran Windows update - the system installed KB5036980 Retested Prodad Script with my fingers crossed. It worked!! No BSOD!! I guess crossing my fingers worked!!  Shinjo Kurumi, thanks again for your suggestion. It saved me from reinstalling the program. Perhaps Ken Berry or Trevor Andrew can update the subject heading to "Solved". I wonder if there is a system setting to allow the OP to edit the subject heading rather than bugging the moderators to do it? |
|
|
|
Post by andrew on May 6, 2024 17:40:11 GMT
Candive I do not know who updated the subject name to include Solved ( update, it was Ken) but if the OP - that is you edit the original / first post it appears that changing the subject is possible, and does not need admin to do that..
|
|
|
|
Post by Candive on May 7, 2024 1:31:04 GMT
andrew , Thanks! Now I understand. That is good to know since I hate bugging others when I could do it myself. 
|
|
