PD365 Crashes 1 second after displaying storyboard

John Howson

Newbie Joined: May 12, 2012 12:13 Messages: 9 Offline

Solved by

Feb 21, 2021 16:54

Thanks in advance for the help everyone. I've seen similar topics, but not quite the same, so I'm posting a new one. I did look at several others, but the solutions didn't help and the problems weren't the same.

I just uninstalled PD 2014 because it was crashing, and decided to install PD365 to become up to date, figuring that would solve my problem. It didn't.

PD365 displays the splash, the storyboard, tries to load the sample videos, and just as they finish, the app crashes and the Report to Cyberlink dislog is displayed.

I renamed the Sample Clips director so they couldn't be loaded. If I select Full or Storyboard, the story board is displayed for a few seconds, then top audio and top video track turn a darker black than they were and darker than the other video/audio lines, then the app crashes.

I have uninstalled, rebooted, reinstalled several times but, no joy.

I tried Auto Mode on a WMV file. It ran for a while (not sure how long as I left the room) and when I returned the next morning the Report to Cyberlink dialog was displayed.

Crash occures on Full, Storyboard, Slideshow, and Auto.

There is nothing in the event logs.

I believe I meet exceed the minumum hardware specs. I've attached the dxdiag file for review.

I just tried running PD365 in safe mode and it ran! I was even able to import a video, drop it into the editor and play a bit. So, some service or other piece of software running on startup might be causing a conflict??

Any assistance, clues, pointers, similar experiences would be greatly appreciated.

John

Filename	DxDiag.txt	Download
Description	DxDiag.txt
Filesize	82 Kbytes
Downloaded:	74 time(s)

This message was edited 1 time. Last update was at Feb 21. 2021 17:24

optodata

Senior Contributor Location: California, USA Joined: Sep 16, 2011 16:04 Messages: 8630 Offline

Feb 21, 2021 17:25

Thanks very much for the DxDiag results. If you look at the very end, you'll see that the 3 most recent crashes (WER0-2) were from PD365. There are also several crashes of Edge and one from 7-Zip, and those often indicate problems with Windows system files.

I think you should first run the commands shown in this post as they may be able to identify and correct the kinds of issues I've described.

As for editing with PD365, your system is pretty old and will struggle with any video beyond HD.

The forum consensus is that we like to see CPUs scoring at least 10,000 on the Passmark CPU benchmark, but yours is only 4.5k. You do have the final GPU driver for your Radeon HD 6570, but that was released 5 years ago and the honest truth is that your system will fall further and further behind as apps get updated and require more features and processing power to run.

If at all possible, my suggestion is to look for pretty much any new or used system that's been built within the past couple of years as that will run circles around your current rig. No need to get the latest and greatest of anything, just something with a 10k+ Passmark score and a decent GPU that is supported by PD.

John Howson

Newbie Joined: May 12, 2012 12:13 Messages: 9 Offline

Feb 27, 2021 12:42

Quote Thanks very much for the DxDiag results. If you look at the very end, you'll see that the 3 most recent crashes (WER0-2) were from PD365. There are also several crashes of Edge and one from 7-Zip, and those often indicate problems with Windows system files.

I think you should first run the commands shown in this post as they may be able to identify and correct the kinds of issues I've described.

As for editing with PD365, your system is pretty old and will struggle with any video beyond HD.

The forum consensus is that we like to see CPUs scoring at least 10,000 on the Passmark CPU benchmark, but yours is only 4.5k. You do have the final GPU driver for your Radeon HD 6570, but that was released 5 years ago and the honest truth is that your system will fall further and further behind as apps get updated and require more features and processing power to run.

If at all possible, my suggestion is to look for pretty much any new or used system that's been built within the past couple of years as that will run circles around your current rig. No need to get the latest and greatest of anything, just something with a 10k+ Passmark score and a decent GPU that is supported by PD.

Thank you, Opto.
I'll take a look at the post you referenced and consider a long overdue upgrade!

UPDATE: I ran both commands from the other post. The first said it fixed some files. The second found nothing. (Likely they were fixed by the first.) Regardless, PD365 exhibits the same failure. Guess I'm going shopping!

Cheers!!
John

This message was edited 1 time. Last update was at Feb 27. 2021 13:03

John Howson

Newbie Joined: May 12, 2012 12:13 Messages: 9 Offline

Mar 06, 2021 10:42

Interesting development.

I powered up the PC on which PD365 is installed and AMD said it had a driver updated it wanted to install. Sure, why not.

Well, it worked! PD365 didn't crash.

Not sure why AMD didn't find that driver the first time...unless it decided to download and install the Beta version it was working on. (I had ecided to try the "working" driver before trying the beta. Turns out I shoulda tried the beta first. Who knew.)

I was remote desktop into the machine at the time, but now it seems to be working. When I look at the DXDiag I ran while running RDP It says:
"Card name: Microsoft Remote Display Adapter
Driver Version: 10.0.19041.662"

and below in another section:
"Card name: AMD Radeon HD 6570
Driver Version: 15.301.1901.0"

Maybe starting PD365 in RDP allowed it to get past whatever the cause of the crashing on startup was so that it would run in RDP mode and sitting at the monitor. Who knows.

I am still planning an upgrade as Passmark measures my current systems performance at a staggering 286. Honestly, I don't know how my system even gets out of bed in the morning with a score so low.