The pc is being stressed when video editing is done. The life of this pc is about to end. I had this problem years ago with my xp computer. The voltage regulator on the motherboard were being stressed and is going bad. Get the motherboard replaced if it still under warranty or get one of those spot cool fans to cool the specific area on the mb to extend it’s life.

A quick check would be to install one of those pc fan speed and temp monitors popular a few years ago to check the stress while editing. Remove one stick of ram and then try video editing again. If this helps then you probably confirmed the overheating.

But max temp on motherboard is 42 degrees Celsius. In games when temp is much greater problem dosnt exist, when produce movie problem doesnt exist, when processor stressed problem doesnt exist. Only when i edit movie. Even i look at timeline and BOOM! computer restarted when is no stressed and only in PD14

The processor and ram run off the vr on your mb on about 1.5 volts. Remove 1 stick of memory and retest. Let us know the result.

ok, i removed on stick of ram, and problem still exist. Only in PD 14. I open PD and computer restarted after 40 seconds, open PD again and restart after 5 minutes.
I played 40 minutes starcraft 2 multiplayer 4vs4, and no problem.Watch 90 minut football match and no problem. . In CPUID HWmonitor temperatures when i editing in PD14:

TMPIN0 - max 29 celsius

TMPIN1 - max 38 celsius

TMPIN2 - max 32 celsius

Core #0 - 39 celsius

Core #1 - 48 celsius

Core #2 - 40 celsius

Core #3 - 36 celsius

Package - 39 celsius



When i play Starcraft:



TMPIN0 - max 32 celsius

TMPIN1 - max 42 celsius

TMPIN2 - max 44 celsius

Core #0 - 52 celsius

Core #1 - 55 celsius

Core #2 - 54 celsius

Core #3 - 49 celsius

Package - 55 celsius

Temperature outside 31 celsius, in my room 34.




Sorry for my english

Quote: Hi, i got PowerDirector 14 on Windows 10 64 bit.
I got all I have all the latest drivers and updates, WIndows and PowerDirector. Reinstalling the system and the program does not help

Can somebody help me??

Let's look at another possibility. Set up win 10 to write a message to the system log but not to restart. See this documentation: http://support.hp.com/us-en/document/c03413399 .

You can also update the motherboard bios. If this stops the restart with PD14 then it was a win 10 issue.

BIOS is actually. I look at link, and I have uncheck AUTOAMTICALLY RESTART.

Somebody?

I've just had the same issue in PD 18. I discovered that if there are two audio files in the project with different format, this issue will occur. I converted the audio in one of them so both audio files were in .wav, and then I was able to work without the program freezing and Windows restarting. I my case I also wasn't able to complete producing a movie. At the end of the production PD froze. This issue is also gone.

It's quite a while since this thread was created, but I still hope that it will help someone.

Good luck to you all!

Tomas E

Cyberlink needs to FIX this

I have been noticing my PD18 crashing when I try to do a few PIP files as I am using PIP to re size etc

Already happened twice

Then I took the Exact same files and removed the Audio from them and then inputted them into PD 18 and everything works fine

I created a 4 PIP video and it played fine no issues no crashing

So Yes it Must be the Audio that is causing this problem

my orig files had standard audio either AAC or AC3

PD18 is completely different from PD14, and any issues found with PD18 should be posted in the PD18 & PD365 forum.

I'm not aware of any situations where using different audio types will crash PD18/365, so I imagine it's either the specific clips or the combination of those clips and your hardware that are causing the problems. Note that Dolby Digital (AC3) audio is not supported on Win7 systems but neither of you has mentioned which OS version you're using.

The only way forum volunteers can help would be if each of you would follow the steps in the Read Me Before Posting sticky thread and attach the DxDiag file in the new discussion thread so we can see the details of your computer. It would also be great if one or both of you could use File > Pack Project Materials and upload the packed project to a cloud folder on OneDrive or Google Drive and paste a shareable link to it.

That way other people can examine the specific clips and try producing the project on their systems to see what's going on. If there's a bug, the only way Cyberlink will know is if it gets reported using the support page and providing them with all the details I'm asking for here.

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°

Since I'm also on Windows 10 there's no need to mention it since marcin 0218 already has this info in his first post. However, since I'm using PD 18 and this issue hasn't been dealt with yet, that info is relevant.

It's highly relevant to post it here since the issues are clearly closely related. And, since there weren't any other thread with this specific issue it also seemed most relevant to post it. When I see someone desperately reaching out and haven't yet got any help as it seems, I don't hesitate when it comes to trying to help if I can.

This is really not for the users to take care of anymore. It should have been dealt with by Cyberlink a long time ago. They are the ones with the right knowledge of programming, and since I have provided them with my system setup and more they should be able to fix this if they feel it's necessary. Now that they know I've been able to find a workaround and what's causing the issue it shouldn't be that hard.

By the way, one really could expect at least some appreciation from someone like you, who seems very knowledgeable. But the only thing you seem to be good at is correcting and criticizing.

PowerDirector 19 Ultimate, Windows 10
Processor: Intel Core i7-8700 CPU @ 3.20GHz
32 GB RAM

Quote By the way, one really could expect at least some appreciation from someone like you, who seems very knowledgeable. But the only thing you seem to be good at is correcting and criticizing.

I'm sorry that you've taken my post that way. Perhaps if you had read the Read Me Before Posting guide you would have made different choices, or at least would have been informed of the forum protocol and could have adjusted your initial assumptions and expectations.

The main reason you should be posting in the PD18 forum is that PD14 is no longer being supported by the developers, so even if there is a flaw with it there will never be a fix whereas PD18 could be updated.

My offer to help still stands, as does my explanation of how CL cannot fix whatever is happening on your system if you won't provide the necessary technical details and specific clips.

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°