Quote: So, I am using PowerDirecter 13, and while editing my computer will shut down. It doesn't seem to be a cooling issue.
my cpu while using will peak at 70 degrees F. video card 60 degrees F. the case inside 76.

Im running a amd fx-8120 8 cores @3.1 ghz
8.00GB Dual-Channel DDR3 @ 803MHz ram
Gigabyte 990FXA-UD3 motherboard
1024MB ATI AMD Radeon HD 7700 Series video card
Windows 8.1 Pro 64-bit os

Quote: So, I am using PowerDirecter 13, and while editing my computer will shut down. It doesn't seem to be a cooling issue.
my cpu while using will peak at 70 degrees F. video card 60 degrees F. the case inside 76.

Im running a amd fx-8120
8.00GB Dual-Channel DDR3 @ 803MHz ram
Gigabyte 990FXA-UD3 motherboard
1024MB ATI AMD Radeon HD 7700 Series video card
Windows 8.1 Pro 64-bit os

PD13 actually consumes much CPU when this editing and more so when this rendering video.
I still think this PD13 very stable here.
AMD-FX 8350 / 8GB DDR3
SSD SUV400S37240G / 2-HD WD 1TB
AMD Radeon R9 270 / AOC M2470SWD
Windows 7-64 / PD16 Ultimate

Dearingjc,
welcome to the forum.
How long have you had your machine, and what does it do when it shuts down? Does it suddenly go dead? Does it make a sound?
When I first got my Phoenix, it kept shutting down with a little "pop", very sudden, no warning, then worked fine, until it happened again.
As it was, it turned out to be a loose, mis-aligned graphics card.
HP Envy Phoenix/4thGen i7-4770(4@3.4GHz~turbo>3.9)
Nvidia GTX 960(4GB)/16GB DDR3/
Canon Vixia HV30/HF-M40/HF-M41/HF-G20/Olympus E-PL5.
Tape capture using 6 VCR, TBC-1000, Elite BVP4+, Sony D8 camcorder with TBC.
https://www.facebook.com/BarryAFTT

Quote: So, I am using PowerDirecter 13, and while editing my computer will shut down. It doesn't seem to be a cooling issue.
my cpu while using will peak at 70 degrees F. video card 60 degrees F. the case inside 76.

Im running a amd fx-8120
8.00GB Dual-Channel DDR3 @ 803MHz ram
Gigabyte 990FXA-UD3 motherboard
1024MB ATI AMD Radeon HD 7700 Series video card
Windows 8.1 Pro 64-bit os

I don't know how you are measuring the temperature, but 70°F is pretty much impossible for an AMD FX-8120 CPU. That's about ambient room temperature usually. But this CPU runs very hot. You are likely hitting 70°C instead.
And at that level, the CPU may indeed overheat. The motherboard may be shutting down.
I know because I I have the same motherboard and I used to have an FX-8120 in it.
I never had it shut down because I have a very large case with plenty of fans. But I did upgrade the cooler on it.
I am now running with an FX-8350 instead which runs a bit cooler - and can be overclocked.

I suggest you download the latest CPUID HWmonitor. This should give you more accurate temperature info.
Next step will probably be to upgrade your cooler Or underclock your CPU / disable some cores in the BIOS until you have a better cooler.

You might have a power supply issue as well. The GA-990FX-UD3 with an FX-8120 requires a beefy one. But this is less likely.
MSI X99A Raider
Intel i7-5820k @ 4.4 GHz
32GB DDR4 RAM
Gigabyte nVidia GTX 960 4GB
480 GB Patriot Ignite SSD (boot)
2 x 480 GB Sandisk Ultra II SSD (striped)
6 x 1 TB Samsung 860 SSD (striped)

2 x LG 32UD59-B 32" 4K
Asus PB238 23" HD (portrait)

I have a similar problem, computer just shuts down when PowerDirctor 13 is producing high quality video output.

To measure temp on components i use Open Hardware Monitor. So I traced the shutting down to significant CPU temp rising. It went above 80 C.
That is not normal, I compared PD 13 video producing to Pinnacle Studio same quality video producing. With Pinnacle my CPU temp did not go above 50 C on the HD video

An interesting thing that only CPU temperature went up, not the graphics card or the motherboard.

These are my PC specs:
Gigabyte GA-990FXA-UD3
AMD FX-8350 8-core
NVIDIA GeForce 9500 GT
24 GB DDR3 memory
liquid cooling system with 3 120mm fan and 1 180mm fan.

Quote: I have a similar problem, computer just shuts down when PowerDirctor 13 is producing high quality video output.

To measure temp on components i use Open Hardware Monitor. So I traced the shutting down to significant CPU temp rising. It went above 80 C.
That is not normal, I compared PD 13 video producing to Pinnacle Studio same quality video producing. With Pinnacle my CPU temp did not go above 50 C on the HD video

An interesting thing that only CPU temperature went up, not the graphics card or the motherboard.

These are my PC specs:
Gigabyte GA-990FXA-UD3
AMD FX-8350 8-core
NVIDIA GeForce 9500 GT
24 GB DDR3 memory
liquid cooling system with 3 120mm fan and 1 180mm fan.

You can hardly blame PowerDirector for temp going too high - that's clearly a hardware problem.

Maybe your CPU cooler isn't properly attached to the CPU ?

FYI, I use a Noctua NH-D14 air cooler with dual fans for my AMD FX-8350 OC at 4.6 GHz, same motherboard. But it took me a month to find BIOS settings that worked stable for this OC. I do have a nice HAF-XM case with a bunch of fans, more and bigger than yours.

200mm side panel fan, 140mm rear fan, dual 200mm fans on top, 200mm front fan.

http://www.coolermaster.com/case/mid-tower/haf-xm/

http://www.noctua.at/main.php?show=productview&products_id=34&lng=en MSI X99A Raider
Intel i7-5820k @ 4.4 GHz
32GB DDR4 RAM
Gigabyte nVidia GTX 960 4GB
480 GB Patriot Ignite SSD (boot)
2 x 480 GB Sandisk Ultra II SSD (striped)
6 x 1 TB Samsung 860 SSD (striped)

2 x LG 32UD59-B 32" 4K
Asus PB238 23" HD (portrait)

I disagree about the HW problem. my cooling system is working fine.

As I wrote I used Pinnacle studio on the same PC, same input file and creating same format output file and had no issues.

Quote: I disagree about the HW problem. my cooling system is working fine.

With all due respect, CPU temp going over 80C shows that your cooling system is NOT working fine. If the cooling system was doing its job, then the CPU would simply never be allowed to reach that temperature, no matter the task. Based on my recollection, things often start to go wrong past 65C on that chip, and almost certainly will past 70C. At 80C, a shutdown is not surprising - it happens to protect the chip, otherwise you would burn it.

Try running Prime95 for 24 hours on your system, then report again if it is really fine.

For me, this was the ultimate test to see if my overclock was working. But it is a fine tool to test stock clocks as well. If the ventilation is not good, then you are going to get failures in the test, or worse, BSODs.

There are other tools such as OCCT, Intel burn. You can try those as well. But in my experience, with the FX-8350, Prime95 was the most stressful of all.

I have never seen an outright shutdown of the computer, however. You might have a power supply problem. What model and size of PSU do you have ?

FYI, not getting an increase in the GPU temperature would be because PD is doing a software encode.

Hardware encode is only available with certain profiles. For your older 9500GT GPU, only with H.264 profiles up to HD resolution, and only if you are running with the older nVidia driver which supports the CUDA encoder.

Pinnacle studio might be doing a hardware encode, or may just be doing something else, like a software encode with only a few threads, which wouldn't utilize all the cores on the FX-8350 and therefore wouldn't run the temperature as high. Have you compared the rendering times when the encode actually completes, maybe for a short one ? PowerDirector is usually the fastest one by a long shot.

With your old GPU, I would advise you to use software encode, as this will provide the best results in terms of encode time. But of course, it will stress your CPU more.

Lastly, are you overclocking your FX-8350 CPU ? If so, I would advise you to return to stock clock, and try PowerDirector again.

The FX-8350 was extremely hard to get to OC stable. It took me about a month of trying different BIOS settings. The torture tests were required to confirm it. And these torture tests correlate very well with the stress put on the CPU when doing software encodes in PowerDirector. I had many OC torture tests that crashed or failed after 12hours+.

Since you have the same motherboard as well, which revision of the board do you have, and which BIOS version ? MSI X99A Raider
Intel i7-5820k @ 4.4 GHz
32GB DDR4 RAM
Gigabyte nVidia GTX 960 4GB
480 GB Patriot Ignite SSD (boot)
2 x 480 GB Sandisk Ultra II SSD (striped)
6 x 1 TB Samsung 860 SSD (striped)

2 x LG 32UD59-B 32" 4K
Asus PB238 23" HD (portrait)

With all due respect temperatures going up does not mean my cooling system is not working fine. It only happens with PD. It never happens with any other video editing software, paid or free.
My test with Pinnacle was exactly the same rendering as with PD. same settings same technique, same input file even, both SW encoding.
Only PD is taxing my CPU.
Don't get me wrong, I am not complaining that my GPU temp is not going up. I am fine with it. My problem is that this software is too taxing for a simple action I am trying to accomplish. And apparently I am not the only one.
My HW is well within specs that Cyberlink requires for the software. And my "old GPU" is well above minimum specs required:
"Graphics Card
128 MB VGA VRAM or higher (1 GB or higher VRAM and OpenCL capable are recommended)."

My CPU is not overclocked, never has been.

I will check the bios version later and will run the Prime95 as you suggest. Will post results later.

thanks

Quote: With all due respect temperatures going up does not mean my cooling system is not working fine. It only happens with PD. It never happens with any other video editing software, paid or free.

It really doesn't matter what software it happens with - video encoding or not - no software should ever be able to drive the CPU temperature up to the point of the computer shutting down. The job of the cooling system is to keep the temperature in check. You simply can't blame the software for what's happening on your system.

And my "old GPU" is well above minimum specs required:
"Graphics Card
128 MB VGA VRAM or higher (1 GB or higher VRAM and OpenCL capable are recommended)."

If you are doing software encodes only, then the type of GPU really doesn't matter, except for some plug-ins.

For example, if you bought PD Ultimate or above, it comes with Newblue titler pro, which has problems with older GPUs with only 128MB of VRAM.

As far as your GPU being old, the 9500GT was released in 2008, which is 7 years ago, so I think that qualifies - but anyway, not relevant to your problem here.

https://en.wikipedia.org/wiki/GeForce_9_series#GeForce_9500_GT

My CPU is not overclocked, never has been.

OK, that's good. I thought it might have been because you have liquid cooling, which is often used to achieve overclocking.

I will check the bios version later and will run the Prime95 as you suggest. Will post results later.

thanks

That will be very interesting.

FYI, I just downloaded the Open Hardware monitor software.

I created a project with a 4K clip , inserted 10 times on the timeline. Total project duration - 10 minutes.

I then did a software encode to H264 MP4 AVC 4K 3840x2160/30p with PD13 (latest patch, 3130).

I have attached a screen capture that includes PD13 in the middle of this encoding, the task manager showing 100% utilization, and open hardware monitor.

As you can see, 3 minutes into the encoding, the CPU temp did not exceed 59°C on my system.

We both have the same CPU, and the same motherboard, same temperature monitoring software, and running PD13.

Only difference is my system is OC which should drive the CPU temps even higher than yours. But it does not, because I have an adequate cooling system.

If you have a project that reproduces the problem on your system, I can run it on mine and measure what the temps are, too.

I will even reboot my computer and disable my OC to make it even closer to your system, and show you what the temps are for that case on my system.

As I type this, the encoding has been going on for 16 minutes, and CPU temp peak was 60.9°C. Still nowhere near your 80°C. There are 8 minutes to go and I fully expect it will finish without issue, but I will let it finish. Edit: it completed. The peak temp was 63.6°C. I actually saw this peak as it occurred when I started using a few other applications while the encoding was still running (no mean feat when PD is using 100% of the CPU). The peak was only for a few seconds. I kept an eye on the Open hardware monitor and for the most part, temp was in the 58-60°C range for the 25 minute encode. MSI X99A Raider
Intel i7-5820k @ 4.4 GHz
32GB DDR4 RAM
Gigabyte nVidia GTX 960 4GB
480 GB Patriot Ignite SSD (boot)
2 x 480 GB Sandisk Ultra II SSD (striped)
6 x 1 TB Samsung 860 SSD (striped)

2 x LG 32UD59-B 32" 4K
Asus PB238 23" HD (portrait)

Quote:
It really doesn't matter what software it happens with - video encoding or not - no software should ever be able to drive the CPU temperature up to the point of the computer shutting down. The job of the cooling system is to keep the temperature in check. You simply can't blame the software for what's happening on your system.

Yes, I can blame the software if the software manufacturer does not require any special eqipment to operate it, by selling me the entire thing with ability to produce hi def output with minimum requirement that are much lower than my HW the supplier guarantees that the software will not require any additional resourves. Which is not true in this case.

Quote: I will check the bios version later and will run the Prime95 as you suggest. Will post results later.

My MB is rev 1.1, so the latest stable BIOS is F9, which I already had installed for a couple of years. GIGABYTE does not recommend going to F10e, which is a beta version. The F10e contains a fix for FX CPUs , but not the one I have.

I ran PRIME95 for 23 hours and some minutes. The CPU temp has not exceeded 61.25 C. I had it on Small FFT, which is a max heat. So going back to my original statement, something is wrong with PD

Quote:
FYI, I just downloaded the Open Hardware monitor software.

I created a project with a 4K clip , inserted 10 times on the timeline. Total project duration - 10 minutes.

I then did a software encode to H264 MP4 AVC 4K 3840x2160/30p with PD13 (latest patch, 3130).

I have attached a screen capture that includes PD13 in the middle of this encoding, the task manager showing 100% utilization, and open hardware monitor.

As you can see, 3 minutes into the encoding, the CPU temp did not exceed 59°C on my system.

We both have the same CPU, and the same motherboard, same temperature monitoring software, and running PD13.

Only difference is my system is OC which should drive the CPU temps even higher than yours. But it does not, because I have an adequate cooling system.

If you have a project that reproduces the problem on your system, I can run it on mine and measure what the temps are, too.

I will even reboot my computer and disable my OC to make it even closer to your system, and show you what the temps are for that case on my system.

As I type this, the encoding has been going on for 16 minutes, and CPU temp peak was 60.9°C. Still nowhere near your 80°C. There are 8 minutes to go and I fully expect it will finish without issue, but I will let it finish. Edit: it completed. The peak temp was 63.6°C. I actually saw this peak as it occurred when I started using a few other applications while the encoding was still running (no mean feat when PD is using 100% of the CPU). The peak was only for a few seconds. I kept an eye on the Open hardware monitor and for the most part, temp was in the 58-60°C range for the 25 minute encode.

My original input file is about 45 minutes, res 600x400, if I make the output of the same res the temp go above 70, but it manages to complete the work, and it takes about 40-45 minutes. The problem occurs when I attempt to make a high def, 1900x700 or something, the time it is supposed to take grows from 40-45 minutes to about 1.5 hour, which is not an issue. But about 15-20 minutes into the work the temps go way above normal.

Quote:

Quote:
It really doesn't matter what software it happens with - video encoding or not - no software should ever be able to drive the CPU temperature up to the point of the computer shutting down. The job of the cooling system is to keep the temperature in check. You simply can't blame the software for what's happening on your system.

Yes, I can blame the software if the software manufacturer does not require any special eqipment to operate it, by selling me the entire thing with ability to produce hi def output with minimum requirement that are much lower than my HW the supplier guarantees that the software will not require any additional resourves. Which is not true in this case.

You can choose to blame whoever you want, but I think you are on the wrong track to blame the software. There is no other component or additional resources the software needs. You simply have a malfunctioning system, for whatever reason. Blaming PowerDirector is not going to help you fix it.

Quote:

My MB is rev 1.1, so the latest stable BIOS is F9, which I already had installed for a couple of years. GIGABYTE does not recommend going to F10e, which is a beta version. The F10e contains a fix for FX CPUs , but not the one I have.

As it turns out, I have the exact same board version and BIOS version that you do.

I ran PRIME95 for 23 hours and some minutes. The CPU temp has not exceeded 61.25 C. I had it on Small FFT, which is a max heat.

Well, that's very good news. May I know which version of Prime95 you used ? Did you run with all the threads ?

I believe I always ran it in "blend" mode before, but that shouldn't matter. I just started running it as I type and my CPU temp is at 55C after 10 mins. So it looks like PowerDirector indeed is raising the CPU temp about 5 degrees more on my system than Prime95. Perhaps I will use a PowerDirector encode for my next OC test instead of Prime95. 55C is still quite low, though.

BTW, when I was initially testing the overclock, I had all the power savings options disabled in the BIOS, and was running Windows in the "Performance" power plan.

Right now, I do have all the BIOS power savings options enabled, except AMD Cool'n Quiet, which messes with my audio records with the Firewire interface - it introduces pops & clicks.

So going back to my original statement, something is wrong with PD

I still don't think that conclusion follows.

My original input file is about 45 minutes, res 600x400, if I make the output of the same res the temp go above 70, but it manages to complete the work, and it takes about 40-45 minutes. The problem occurs when I attempt to make a high def, 1900x700 or something, the time it is supposed to take grows from 40-45 minutes to about 1.5 hour, which is not an issue. But about 15-20 minutes into the work the temps go way above normal.

I would suggest that you make the project available on a cloud drive somewhere, and tell us the exact profile you are trying to render to when this happens (which CODEC, file type, profile name).

I will happily test it on my nearly identical machine, with the same motherboard revision, same CPU, same BIOS, same temp monitoring software, and tell you which temps my system is reaching, either with the overclock or without. And I will gladly report if it causes the system to shut down, and eat my words.

Now, if I were in your position, I would start looking at the other hardware components in your system.

First, switch to a better monitoring software than Open hardware monitor. CPUID Hwmonitor comes to mind. The main problem with Open hardware monitor that I see is that it records the current and maximum values, but not the minimum value. If you had a malfunctioning fan for example, that intermittently stopped, you may not notice the RPM going to 0 in Openhardware monitor, but you would notice it in CPUID hwmonitor. I have seen such problems happen with fans. They sometimes need to be cleaned, replaced, or possibly moved to a different connector of the power supply if sharing molex connectors between devices.

Next, check the termal paste between your CPU and its cooler. Maybe remove the existing coat, and add another. Thermal paste is very cheap so this doesn't cost much to try.

If that doesn't do it, I would look at the PSU next. You didn't say what size PSU size and model you have. Please report on what it is. An underpowered or malfunctioning PSU might cause overheating under load as well.

Also, make sure all the required power connectors area connected from the PSU to the motherboard. I don't know if the system would even start if they weren't, but better check anyway.

Next, turn off the power to any SSD or hard disks except the one with the boot drive to reduce PSU load.

After that, I would also remove anything else from the system that's not needed. Remove any PCI or PCIE card except the video card.

Run the motherboard with just one stick of 8GB RAM .

It may take time, but I believe eventually you will find the faulty component that's causing the overheating . I doubt you are going to find a "Halt and catch fire" type of instruction in Powerdirector .

https://en.wikipedia.org/wiki/Halt_and_Catch_Fire

But truly if it turns out there is a software issue in PowerDirector causing your crazy temps on the FX-8350, you will become famous for helping identify it. MSI X99A Raider
Intel i7-5820k @ 4.4 GHz
32GB DDR4 RAM
Gigabyte nVidia GTX 960 4GB
480 GB Patriot Ignite SSD (boot)
2 x 480 GB Sandisk Ultra II SSD (striped)
6 x 1 TB Samsung 860 SSD (striped)

2 x LG 32UD59-B 32" 4K
Asus PB238 23" HD (portrait)