Quote



I had the exact same problem after updating my Nvidia drivers to version 531.41 (March 23rd 2023), I reverted back to the drivers available on my laptop manufacturer's website, which are older, and PowerDirector stopped crashing. It crashed without me doing anything as well a few seconds after the program was launched.

I am using PowerDirector version 17.0.5003.0

It really seems to be an Nvidia driver issue... at least I hope since my version of PowerDirector is no longer updated by Cyberlink.
If I can't, in the long run, be using Nvidia's latest GPU drivers (which in my case are for an RTX 3050 Laptop), I'll change software entirely and will no longer consider Cyberlink... which would be a shame since I'm a long time user of their software and I kind of liked it.

Just a quick update on this: CyberLink is going to remote access my computer tonight (Houston time) to see if they can determine what's causing this. Nvidia is also awaiting this results of this test. So, hopefully we will have more information soon.

One other thing, there was an Nvidia "hotfix" issued (531.5 which I tested at the request of CyberLink. It did not solve the problem.

Quote I am using PowerDirector version 17.0.5003.0.

Your issue is completely separate from the PD365 discussion here. I have PD17 (with the same -final- build) running with that nVidia driver without any trouble.

I suggest you run the commands I linked to in my Mar 24 post and follow up with a clean install of the new nVidia driver.

If you still need help, please start a new discussion in the PoweDirector (previous versions) forum and include the DxDiag results as shown in the Read Me Before Posting guide

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Quote

Your issue is completely separate from the PD365 discussion here. I have PD17 (with the same -final- build) running with that nVidia driver without any trouble.

I suggest you run the commands I linked to in my Mar 24 post and follow up with a clean install of the new nVidia driver.

If you still need help, please start a new discussion in the PoweDirector (previous versions) forum and include the DxDiag results as shown in the Read Me Before Posting guide

Status update: CyberLink Enginnering spent about 2.5 hours last night accessing my computer remotely for testing. They indicated they think the problem is with the NVIDIA GPU drivers. They have an open ticket with NVIDIA and are working the issue with them directly, so it seems progress is being made.

Recap:

Game Ready Driver 531.29 works okay. Game Ready Driver 531.41 fails.
Studio Driver 528.49 works okay. Studio Driver 531.41 fails.
Hot fix 531.58 fails.

Going back to the prior version of the drivers seems to be an acceptable work-around for now (at least for me).

Tom57 I'm glad to see that people are actively working on the situation for you. Thanks for keeping us updated!

Quote

Your issue is completely separate from the PD365 discussion here. I have PD17 (with the same -final- build) running with that nVidia driver without any trouble.

I suggest you run the commands I linked to in my Mar 24 post and follow up with a clean install of the new nVidia driver.

If you still need help, please start a new discussion in the PoweDirector (previous versions) forum and include the DxDiag results as shown in the Read Me Before Posting guide

My issue presented the same results as Tom57 following an update of my Nvidia drivers to version 531.41 (March 23rd 2023), the direct result was PowerDirector 17 crashing about 30 seconds after launching the application... I had to revert back to a previous version of the Nvidia drivers. I am using the PD17 on an ASUS G14 (2021) laptop equipped with an RTX 3050 Laptop GPU.

I also tested PD17 on an older workstation equipped with a GTX 1060 GPU with the same version of the Nvidia drivers and on that system PD17 did not crash, so I'm thinking that it might have something to do with the fact that my Laptop as an iGPU (AMD), plus a discrete GPU (Nvidia). Tom57 is using an Asus Laptop that as a similar configuration where his iGPU is from Intel and his discrete GPU from Nvidia.

Today, April 18th, 2023, Nvidia has release a new version of their drivers ( version 531.68 ) and it seems that the issue is resolved, so far no crash on my Laptop.

I wanted to share this info hoping it helps others.

Quote



My issue presented the same results as Tom57 following an update of my Nvidia drivers to version 531.41 (March 23rd 2023), the direct result was PowerDirector 17 crashing about 30 seconds after launching the application... I had to revert back to a previous version of the Nvidia drivers. I am using the PD17 on an ASUS G14 (2021) laptop equipped with an RTX 3050 Laptop GPU.

I also tested PD17 on an older workstation equipped with a GTX 1060 GPU with the same version of the Nvidia drivers and on that system PD17 did not crash, so I'm thinking that it might have something to do with the fact that my Laptop as an iGPU (AMD), plus a discrete GPU (Nvidia). Tom57 is using an Asus Laptop that as a similar configuration where is iGPU is from Intel and is discrete GPU from Nvidia.

Today, April 18th, 2023, Nvidia has release a new version of their drivers ( version 531.68 ) and it seems that the issue is resolved, so far no crash on my Laptop.

I wanted to share this info hoping it helps others.

Thanks Pierre. I tested the new versions of both the Studio Driver (531.61) and the Game Ready Driver (531.6 and both seem to have corrected the problem on my system. I think we can finally close this one out. I'll pass this on to CyberLink and Nvidia via the open tickets I have with them.

And a big thanks to all that pitched in to help on this one!

Tom