Quick Answer
For the impatient: Go to File > Project Settings > General, set Renderer to Mercury Playback Engine – Software Only, then Edit > Preferences > Media Cache and click Delete Unused. Restart Premiere and export again. If that doesn't do it, read on.
Why This Happens
Here's the thing — the crash you're seeing is almost always tied to the hardware encoder on your GPU. Premiere Pro tries to use Intel Quick Sync, NVIDIA NVENC, or AMD VCE to speed up H.264 exports. Great in theory, but these encoders are notoriously finicky with certain drivers, especially after a Windows update or a Premiere update. When the encoder fails, Premiere throws that generic “This application has encountered a problem” dialog and dies. You'd think Adobe would give you a proper error message, but no.
The second piece of the puzzle is the media cache. Over time, corrupted cache files from previous edits or previews can interfere with the export pipeline. Even if the GPU is fine, a bad cache entry can trigger the same crash. I've seen this happen on projects that have been sitting around for months — the cache is stale and full of junk.
I've fixed this exact issue on dozens of machines — some with high-end RTX cards, some with integrated Intel graphics. The fix is the same, and it's not a coincidence that it always works.
The Fix – Step by Step
- Save your project and close Premiere Pro. Seriously, don't skip this. You don't want to lose your timeline if something goes sideways.
- Disable GPU acceleration: Open Premiere Pro and go to File > Project Settings > General. Under Video Rendering and Playback, change Renderer to Mercury Playback Engine – Software Only. This forces CPU-based encoding, which is slower but stable.
- Clear the media cache: Go to Edit > Preferences > Media Cache (on Windows) or Premiere Pro > Preferences > Media Cache (on Mac). Click Delete Unused to remove cached files that aren't being referenced. If that doesn't fully clean it, you can also click Clean next to the cache database and then Delete next to the cache files. This will rebuild caches on your next project open.
- Restart Premiere Pro. Don't just hit “OK” and try to export — you need a fresh session for these changes to take effect.
- Re-open your project and try exporting to H.264 again. Use the same export settings you had before. If it works, you're good. If it still crashes, move to the alternatives below.
If That Doesn't Work – Try These
Sometimes the main fix is enough, but here are a few other things that have worked for me:
Update or Roll Back Your GPU Driver
NVIDIA and AMD release studio drivers that are tested for Adobe apps. Go to the manufacturer's site, not Windows Update. If you recently updated your driver, try rolling back to the previous version — that's the trigger for a lot of these crashes. I've seen a broken driver be the culprit more than Adobe's code.
Switch to Software Encoding in Export Settings
In the Export Settings dialog, under the Video tab, look for Performance and set it to Software Encoding instead of Hardware Encoding. This does the same thing as disabling GPU acceleration but only for that export, so you can keep GPU acceleration for timeline playback.
Reset Premiere Pro Preferences
If the cache clear didn't help, your preferences might be corrupted. Hold down Alt+Shift (Windows) or Option+Shift (Mac) while launching Premiere Pro and click Yes to clear preferences. You'll lose your custom keyboard shortcuts and workspace, but it's worth a shot.
Check Your Sequence Settings
Make sure your sequence settings match your source footage. If you're editing 4K footage in a sequence that's set to 1080p, the export can sometimes cause issues. Go to Sequence > Sequence Settings and verify the frame size and frame rate are correct.
Prevention – Keep It From Coming Back
Don't wait for the crash to happen. Here's how to avoid it:
- Set Software Only as your default renderer. Go to File > Project Settings > General and save that as your default for new projects. You'll lose GPU acceleration for previews, but I promise the export stability is worth it — especially if you're on a deadline.
- Clear your media cache weekly. Make it a habit. Go to Edit > Preferences > Media Cache and click Delete Unused at least once a week, or use the automatic cleanup options to set a maximum cache size. I set mine to 10 GB and let Premiere handle the rest.
- Update Premiere Pro regularly, but not the same day as a driver update. Give Adobe a few weeks to patch compatibility issues. And when you update your GPU driver, do it manually and reboot before you start a big export.
- If you're on a laptop with hybrid graphics (Intel + NVIDIA or AMD), check which GPU is being used for Premiere Pro. Sometimes Windows decides to use the integrated GPU for the export, which is a recipe for problems. You can set the preferred GPU in the NVIDIA Control Panel or Windows Graphics Settings.
That's the whole fix. It's not glamorous, but it's reliable. I've lost count of how many times I've saved someone's day by simply switching to software encoding and clearing the cache. You'll get your export done, even if it takes a bit longer.