Quote
I'm getting BSODs with any of the Nvidia graphcis card I have tested. It points out the driver, but it is up to date and I have tried different versions as well. I even tried a new install of Windows to no avail. It's a random BSOD while editing, nothing specific, just complex projects with several video tracks. On small projects with little complexity I found no issues.
Setup is Ryzen R5 3600 + RTX 2070. Tried also GTX 1070 and 1080Ti, same issue. No issues when using RX 580, so it's nvidia specific. I even tried another motherboard, the X370 Killer SLI, I'm now using Biostar X570 GT8...
I wonder if I can go back to version 17 with the subscription plan, I dont recall having issues back then.
I know it is related to coding on the CUDA C/C++. My guess is someone failed at coding, maybe too excited about the Christmas season and not their job, lol.
I am waiting for an update that will fix the program. Support is less than helpful at this point. They want a full-screen screen capture of what it is doing, it locks up just like a still picture would show. Only Window's system manager reports there is an issue and I have given them the error message already.
I think at this point only a native English speaker can help with their support contact and I haven't found one yet.
We are thinking of leaving their 360 program, the last 5 updates have been something else. We want to create projects not troubleshoot the program we need to create the projects with.
Ross
On another note, going back a version even within PD18 makes your projects useless as they say it was created with a newer version and can't be opened forcing you to go back to the latest issue filled version. I have never had that with AVID, Pinnacle, Premiere, this is the main reason we are in talks about killing our subscription services. The program is great when it works for the most part but It stops production altogether until issues are fixed on Cyberlink's side in the form of an update. This and this alone is basically the stupidest thing ever, fix at least this issue and we'll be able to deal with updates that fail by resorting to the earlier one that worked.
I am really hoping someone from Cyberlink reads this footnote, end of rant.