Further note that after uninstalling PD11 and reinstalling without the patch, PD11 works fine.

This is just a quick guess-

Your video driver is listed as:
Driver Date/Size: 7/4/2012
Driver Version: 8.17.0010.1129

Try updating to the latest display driver from AMD then install the 2707 patch to see if that works.
http://support.amd.com/us/gpudownload/Pages/index.aspx

Rob
PD 14 Ultimate Suite / Win10 Pro x64
1. Gigabyte Brix PRO / i7-4770R Intel Iris Pro 5200 / 16 GB / 1 TB SSD
2. Lenovo X230T / 8GB / Intel HD4000 + ViDock 4 Plus & ASUS Nvidia 660 Ti / Link: https://www.youtube.com/watch?v=ZIZw3GPwKMo&feature=youtu.be

there are no more driver updates for this video card. why would a video cause pd11 to crash? the problem follows the patch not the video driver if you get what i mean.

video editing is very hard on video card capabilities.

Vista never was a very good version of windows, the newer versions of PD do have problems with Vista, and your video card is "older". there are good prices on windows 7 64bit upgrades and you can get a reasonable "modern" video card for $100 or so.

That might be the only way to get is going right.
Once working it is very powerful and worth the effort. RTX 2060 SUPER 8GB GDDR6
(2 NVME 2TB, 1 SSD 2TB, 3SATA 18TB )
PD18 ULTIMATE 64bit
WINDOWS 10 PRO 64 BIT
GIGABYTE X570 AORUS PRO WIFI MB
RYZEN 7 3700X 8-CORE , 64 GB DDR4
ORSAIR HX1050 watts PSU

thank you for the responses. i understand about old equipment and the economics of buying new equipment. i understand about vista, etc... but that isn't why i posted this problem in the forum. is there another patch on the horizon that will fix this problem? is there any more data that is useful for actually debugging the problem? if so, i'll see if i can turn it up.

in the meantime, i uninstalled pd11 and reinstalled it without this patch. that works fine.

rjsqxxx,

I get what you are saying- PD11 works fine on your Vista machine so why should an update patch cause issues.

Here is the latest Catalyst Software Update for Vista x64 for the Radeon 4000 series:
Revision Number: 13.1
Release Date: 1/21/2013
Display Driver ver. 8.97.100.7
OpenCL(tm) Driver 10.0.937.2
Catalyst Control Center 2012.1116.1514.27190

http://support.amd.com/us/gpudownload/windows/legacy/Pages/legacy-radeonaiw-vista64.aspx

Have you tried this update ?

If that does not work then Cyberlink tech support might have an answer.

Rob
PD 14 Ultimate Suite / Win10 Pro x64
1. Gigabyte Brix PRO / i7-4770R Intel Iris Pro 5200 / 16 GB / 1 TB SSD
2. Lenovo X230T / 8GB / Intel HD4000 + ViDock 4 Plus & ASUS Nvidia 660 Ti / Link: https://www.youtube.com/watch?v=ZIZw3GPwKMo&feature=youtu.be

thx Rob. i'll take a look at the Catalyst update. at one point, amd was telling their users to expect no more radeon updates for the 4xxx cards so i stopped looking.

beyond this one program, there is not any other video problems. the platform is definitely capable of doing the sort of editing i typically do.

Now I remember this nightmare. The Catalyst garbage doesn't install. Once AMD made this driver "legacy" their install kit stopped working. That's why I never went to 13.1.

So now I have to put back the last install kit that worked.

I don't believe this has anything to do with video drivers. Does PD11 directly call a video driver? Not likely. More likely it is making DirectX calls. DirectX works fine on this PC as does PD11 prior to this patch.

Cyberlink, please look into your patch. It has major bugs. It may very work in newer environments but unless I hear that PD11 is no longer supported on Vista I see no reason to upgrade anything just because of a patch.

Great! Now my system is in flames trying to put back the old driver kits. No more video driver changes unless someone in Cyberlink can point me at the specific bug being fixed that is relevant to a problem in their software.

Okay I am back. Here's what I recall about Catalyst:

12.6 was the last working full release
12.10 is a partial upgrade to 12.6 (but not a video driver change)

Then AMD decided to change it's model and no longer issues monthly updates for older models. They came out with 13.1 in January 2013. Many users (myself included) tried loading and installer does not work right. It makes a total mess of your system. You have manually clean it up.

I just did that and put 12.6 / 12.10 back.

Now mind you, I appreciate the comments and feedback from everyone on the forum. However, I am looking for official feedback from cyberlink.

What level of windows does cyberlink support?
What video cards does cyberlink syupport?
Is there a follow on patch?

I am okay with waiting for the next patch but I just want to be sure that cyberlink understands that some users are having trouble with this patch. The crashes so far have been in their code (not codec's, directx, video drivers, etc...). If I back the patch off powerdirector runs just fine.

What I am trying to do is very basic. Import a media file into a project and put it on time line. I think the first crash tells me that something blew up in shadow file creation. I don't understand the next one at all.

Is there a workaround? An option I can try turning on / off? I would much rather try that than continue to struggle getting catalyst 13.1 to work (unless someone can tell me for sure that there is a known bug with Catalyst levels that 13.1 fixes).

Thx

Oh great so now PD11 won't start at all. This is tragic ... LOL

Cyberlink, why is powerdirector so troublesome? The other products like powerdvd are way more stable.

Got PD11 working again. I been here before.

Deja Vu all over again.

This is caused by the catalyst SDK. I uninstalled that thing and PD11 works fine.

So back to square one with the patch that breaks PD11.

Hi rjsqxxx ,
Please can you send me via PM your contact (name and email) details. I may have a solution but I'm unable to post it on the forum.
Dafydd
Forum Moderator

Ugh- sorry to hear about your troubles.

But at least you know your way around computers and was able to get back which is a good thing.
Keep us informed.

Rob.
PD 14 Ultimate Suite / Win10 Pro x64
1. Gigabyte Brix PRO / i7-4770R Intel Iris Pro 5200 / 16 GB / 1 TB SSD
2. Lenovo X230T / 8GB / Intel HD4000 + ViDock 4 Plus & ASUS Nvidia 660 Ti / Link: https://www.youtube.com/watch?v=ZIZw3GPwKMo&feature=youtu.be

o worries RobAC. I wish I sometimes kept a log of everything I did. But, easy to say but hard to do.

No worries I meant

Okay here's an update. Tried the latest patch with no success. I went back to the working verson of PD11.

I have been using Power irector 11 on a Vista 64 System and have had nothing but problems; I am running an i7 with 18 Megs ram, an Intel 520 series SSD and a Radeon 7800. I have attempted many projects and have only been able to finish one a slide show. During movie editing or producing it will always crash. I have an upgrade to Win 7 64, but Vista 64 is more secure and I have a friend with a similar hardware configuration running Win 7 64 with similar issues so it is obviously not an operating system problem. I have never seen such buggy software and all my drivers are up to date. I purchased PowerDirector Ultimate because they claim it is a 64 bit system and I have regretted the purchase since. I am currently looking for good and reliable video editing software at a reasonable price. I have Pinnacle and works well but it is not written for a 64 bit operating system and is slower, but at least it does not crash. Perhaps if PowerDirector paid more attention to writing software that works instead of trying to always sell an upgrade, they may end up with a good product sometime in the future.

Basically, I fell back to the previous patch level of PD11. It does work. I have yet to hear an explanation for why it broke other than broken video drivers. I can't do much about that because my video card is pretty much end of service life per the vendor. Newer video driver updates (there is only one level newer) don't work and create problems elsewhere. So, I don't see myself as being able to move forward with PD11 on the hardware platform I am running. Disappointing because performance wise it's fine for what I am doing with it.