Media Encoder Crashing

Same issue.... always happen when i try to change the format on the render queue on AME. i try to reset preferences and all. check the cache, free ram... and nothing...

Experiencing something similar, made a change, got the render to complete.

Here's the deal: I have two computers, a Windows Desktop and a Macbook Pro and I'm running Adobe Media Encoder on both of them (Windows version on the Windows machine, Mac version on the Macbook, naturally). On both machines AME is crashing pretty early in the render. In both cases it's the same file crashing.

I'm trying to render a 360° video, about 2 minutes in duration at a resolution of 5760 x 2880. I have the file pulled into Premiere Pro, and then queued up to Media Encoder (a couple of effects applied in PP) with a bitrate set 15 and 25 on the H.264 preset in AME.

So all of this is happening with AME version 13.1 Build 173 (Same version number / build on both systems, both updated via their respective Creative Cloud apps).

Let's deal with the Windows Machine First

It's crashed several times so I got a clean boot and ensured that nothing was running except AME and Task Manager (Ctrl + Alt + Delete > Task Manager). As I got the render going in AME I opened up the view in Task Manager to see more details on the Processes tab. There I noticed that AME was running up around 98%, 98.7%, 99%, etc. of the CPU. Then it would crash.

After some research I found that AME appears to be able to, and actually will, ask for ALL THE POWER of the CPU! Well, the motherboard won't be hearing that nonsense, so she shuts it all down. In my case I'm getting the Blue Screen of Death (BSoD) with an error code that reads WHE_UNCORRECTABLE_ERROR.

A Couple of Ways to Deal With This:

• You should be able to go into your system's BIOS Setting and turn off any Turbo Boost settings - This I was unwilling to do because I don't know which "turbo boost" settings are in my UEFI BIOS to turn off. I have a preset for higher performance turned on, and I don't want to crank that back down to normal because I do want to game on this machine a little (when I'm not rendering video or 3D) and I don't want to mess with the BIOS every time I want some entertainment. However it may be something you want to try.
• You can go into Windows and Change the Settings for High Performance - This is what I actually did. In Windows 10 go to Control Panel > Hardware and Sound > Power Options > Edit Plan Settings > Change Advanced Power Settings > Processor Power Management >
  • Set your Maximum Processor State down from 100% to 99% or 98%
  • Set your Minimum Processor State down to something lower than your Maximum Processor State. I did 50%, but I think as long as it isn't the same as, or higher than, your maximum, you'll be fine.
• It's worth noting that before I got to this state I had also updated my Nvidia drivers, applied some pending updates to Windows, etc. The updates themselves didn't prevent the crashing in AME, but they can't hurt.

Then I attempted the render again and it completed with no problem. This is weird because I've been rendering out of AME with no issues until today, and today I updated AME and started having render issues.

<rant>Why the hell does AME do this? Why can't Adobe develop AME to NOT crash my frickin' machine? It's been fine until today, but now its starts crashing this way. I mentioned doing some "research." The "research" that led me down this path is some forum postings from about 2 - 3 years ago, but I figured that those were issues that would since be solved in the software itself. I guess not! I mean what's the point of letting AME request so much power that the chip runs so hot that the MB shuts it all down? At least there should be a way in AME's preferences to say, as you can with the RAM, "Look, AME, you can't request it ALL! You have to leave some of it for other services, so just run up to around 9x%, but not 100%." </rant>

Windows System:

Intel Core i9-7980XE @ 2.6GHz

32 GB RAM

Windows 10 - Version 1903 - OS Build 18362.175

Macbook

Now, for the Macbook Pro, I'm seeing the same behaviour from AME (Also version 13.1 Build 173), also updated today via the little CC updater app that runs on the system). I think it's basically the same issue because the fans on that thing are running like crazy before it crashes. Currently I'm looking for a similar solution in MacOS Mohave 10.14, but haven't found it yet.

It may take me some time, but while I'm looking for it, someone else may see this who knows how to do it, and / or some Windows users may try the Windows version of this fix and get a good result. So why hold up that progress?

Try clearing your Encoder and Premiere preferences in Documents. Possibly reinstall both. Also, if it's a certain project that seems to crash AME, try importing that project into a new one.

I've had the same issue for approximately 2 months now. But it wouldn't only crash Media Encoder, it will sometimes crash my actual PC.